What Are As-Built Drawings? A Guide for AEC Teams

As-built drawings document the building as it was actually constructed, rather than simply reproducing the original design intent.

For MEP systems, this distinction matters. Routes, equipment locations, connections and installed conditions can change during construction.

What separates design intent from as-built fact

Design drawings vs. as-built drawings

Design information describes what was intended. As-built information records what was installed, subject to the project's agreed verification and documentation process. What MEP as-built information typically includes:

• Final equipment locations
• Duct and pipe routes
• Valve and access locations
• Cable tray and containment routes
• Equipment connections
• System identifiers
• Relevant asset information
• Final drawings and model information where required

Marked-up drawings, field verification, and model updates

The process can combine marked-up drawings, site records, approved changes, field verification, surveys, photographs, commissioning information and model updates. The exact process depends on project requirements — a good workflow establishes how site changes are captured before the project reaches handover.

When the coordinated model is maintained through construction, as-built updates can be incorporated into the same information environment rather than recreated from scratch — which is the main reason we keep the federated model live through to handover rather than treating it as a design-stage artefact only.

If the project waits until handover to discover what changed, important information may already be difficult to recover.

Accuracy is the obvious requirement — usability is the one that gets missed

The final information should help facilities teams locate equipment, understand systems, plan maintenance and support future modifications. Common mistakes that undermine that: updating drawings without verifying the field condition, ignoring approved variations, leaving temporary or construction-only elements in the final information, using outdated model versions, failing to define who owns final verification, and treating as-built documentation as a last-minute task.

A practical record the building actually operates from

The best as-built process starts before construction is finished, not at handover. For MEPF projects, as-built documentation isn't just an archive — done well, it's a practical record of the systems the building actually operates on. This is part of our as-built BIM service, and pairs closely with Scan-to-BIM when existing-condition verification is part of the picture.