Traceable sources
Engineering inputs carry their origin, so a reviewer can see where a value came from without asking who typed it.
Engineering that can be reviewed, evidenced and defended.
Assurance is not a reporting feature added at the end. In ATLAS, information carries its source, changes carry their version, and decisions carry their reasoning — because engineering work is eventually read by someone who was not present when it was done.
- 01
Engineering output
Calculated, documented result
- 02
Review
Examined by a competent engineer
- 03
Approval
Accepted under company process
- 04
Auditable record
Retained, versioned, retrievable
Six principles the platform is built around.
These principles describe how engineering information is treated. They are structural, not optional presentation.
Versioned evidence
Changes to engineering information are versioned rather than overwritten, so the record of what was used remains intact.
Recorded assumptions
Assumptions form part of the engineering case rather than living in a comment, a margin note or someone's memory.
Auditable decisions
Decisions, reviews and approvals are captured as reviewable records against the work they relate to.
Human verification
Verification stays an explicit engineering step. The platform does not treat a calculated result as a verified one.
Manual engineering input
Project-specific engineering input remains possible — and remains auditable when it is used.
From source to decision, without gaps.
Traceability is only useful if it survives the whole way through: the value, what supports it, which revision applied, and what the engineer concluded.
- 01
Source
Where the value originates
- 02
Evidence
What supports it
- 03
Version
Which revision applies
- 04
Decision
What the engineer concluded
Lineage is retained so a reviewer can reconstruct how an engineering conclusion was reached.
What takes precedence over what.
This is stated plainly because it matters more than any platform capability.
Where authority sits.
Clear boundaries make assurance meaningful — a platform cannot hold engineering responsibility.
- The engineer
- Judgement, verification, interpretation and the engineering decision.
- The organisation
- Standards, procedures, competence, review process and approval authority.
- ATLAS
- Structure, governed information, analysis support and an auditable record.
ATLAS supports engineering judgement. It does not replace the engineer.
Four questions an engineering record should answer.
Assurance is best judged by what a reviewer, auditor or partner can establish months after the work was completed.
- Can it be found?
- The engineering record is retrievable rather than reconstructed.
- Can it be explained?
- Inputs, sources and assumptions are visible with the result.
- Can it be defended?
- Review and approval are recorded against the engineering work.
- Can it be reconstructed?
- The applicable inputs, sources, versions, assumptions and recorded reasoning remain available for review.
Evidence is what makes learning possible.
An organisation can only learn from a well if the engineering record of that well is trustworthy. Assurance and the learning loop are the same discipline seen from two directions.
The engineering workflow describes how a single well is engineered. This loop describes something different: how an organisation improves between wells. Outcomes captured during execution are reviewed and fed back into planning, so the next well starts from what the last one demonstrated.
Capture
Outcomes recorded as engineering evidence, not anecdote.
Learn
Reviews turn outcomes into stated engineering findings.
Improve
Findings inform the next design basis.
Plan
The cycle restarts with more context than before.