As-built documentation
No project is built exactly as issued. Routings move around obstructions, dimensions get adjusted to conditions, concessions are granted, changes are ordered — and the as-built set is the documentation reconciled to that reality. The conventional workflow is contractor red-line markups maintained during construction, incorporated by the design organisation into revised documents at the end, and delivered as part of the handover package.
The consumers are everyone who arrives after the project team leaves: operations and maintenance, inspectors, and above all the engineers of the next modification, for whom the as-builts are the starting truth about the facility. Their accuracy is inherited by every future project on the site.
And that is exactly where they fail. As-built production happens at the end of the job, when the budget is spent, the team is demobilising and the incentive to be thorough has left the site; markups go missing, and documents get restamped "as-built" without reconciliation. The gap surfaces years later, on the brownfield project whose first work package is discovering what was actually built — a survey exercise paid for because the last project's final deliverable was fiction.
Related reading
See this workflow in practice.
Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work.