As-built drawings are contractor-created, unverified records of what was actually installed on site. Record drawings are the cleaned, consolidated set that a design professional compiles and, once verified, may seal. The contractor produces one; the architect or engineer produces the other, and only the second carries any professional certification.
TL;DR:
- Contractors are responsible for updating red-line markups throughout construction, but these are often unverified until reviewed by a design professional.
- Only a review that confirms the contractor’s notes have been checked allows a record drawing to be sealed by a licensed practitioner; unverified sheets should be clearly labeled.
- Disputes frequently arise when confusion exists over responsibilities, timing, and scope for producing and verifying as-built and record drawings.
- Modern digital methods like scan-to-BIM require strict verification of models before sealing, as high-accuracy point clouds still pose trust issues.
- Owners and facilities managers should specify verification levels and file formats in contracts early, to avoid inheriting unreliable documentation and unnecessary re-surveys.
Table of Contents
- As-built vs record drawings: definitions and contents
- Who prepares them and when: contractor, consultant and close-out roles
- Legal and professional-liability implications: sealing, disclaimers and scope
- Accuracy expectations, standards and labelling best practice
- Modern workflows: scan-to-BIM, point clouds and digital handover
- How owners and FM teams use these sets: handover checklist and best practice
- Practical summary: what each role should request and why
- Publisher perspective: how Xponexus approaches verified record documentation
- How Xponexus Engineering can help with record drawing production
- Sources
As-built vs record drawings: definitions and contents
An as-built drawing is a working document. It usually starts life as a set of red-line mark-ups on the original construction drawings, made by site staff as work progresses. Nobody checks it for accuracy before it lands on the design professional’s desk.
A record drawing is what happens after someone competent reviews that mark-up. The design professional consolidates the contractor’s changes, cross-checks anything that matters structurally or in terms of services, and issues a clean set. That distinction between “raw contractor notes” and “verified professional output” runs through almost every dispute over as-built documentation.
Typical content differs too:
- As-built content: red-lined deviations, notes on hidden services (pipework, cabling routed differently to the design), field dimensions scrawled in the margin
- Record drawing content: a single coordinated set, practitioner annotations, a formal title block and revision history
- Measured drawings: a separate category entirely, produced by surveying an existing building from scratch rather than tracking changes during construction
Confusing these three categories is the single most common cause of handover disputes.
Who prepares them and when: contractor, consultant and close-out roles
Responsibility splits cleanly along contractual lines, and confusion here usually stems from nobody stating it in writing.
- The contractor marks up drawings throughout the build, ideally against an agreed redline protocol, updating locations, dimensions and specification changes as work happens rather than reconstructing them from memory at the end.
- The design professional takes those mark-ups during close-out, reviews them against site knowledge, and compiles the record drawing set, flagging anything that cannot be independently verified.
- Handover should follow a fixed contractual checkpoint. AIA’s standard forms, for instance, require contractors to maintain an updated as-built record throughout construction, with the architect providing record drawings only as a supplemental service if the contract calls for it.
Leaving this timing loose is how projects end up with as-built sets delivered weeks after practical completion, by which point half the site team has moved on and nobody can answer questions about the deviations.
Legal and professional-liability implications: sealing, disclaimers and scope
This is where the difference between as-built vs record drawings stops being academic and starts affecting who carries risk.
A design professional can seal a record drawing, but only after genuinely verifying the conditions it shows. PEO’s guidance is explicit on this: sealing implies the practitioner has checked what is on the page, not simply republished what a contractor handed over. Sealing an as-built drawing that rests entirely on unverified contractor information is a professional-liability trap. If a later party relies on that seal and something turns out wrong, the sealing engineer or architect owns the consequence, regardless of who actually made the change on site.
Good disclaimer practice closes that gap:
- Strip or replace the original design seal before issuing a record drawing based on contractor data
- Label unverified sheets plainly: “Not verified. Based on contractor-supplied information.”
- Note precisely which elements were field-checked and which were not
- Agree the scope and fee for record-document compilation before the project starts, not during close-out
Statistic callout: joint guidance from the OAA and OGCA treats early scope and fee agreement for record-drawing compilation as standard best practice precisely because disputes over “who pays for this and who’s liable” are common enough to warrant a joint industry statement.
AIA contract language backs this up too: architects are not responsible for the accuracy of contractor mark-ups unless they’ve actually verified them. Silence on this point in a contract is an invitation for argument later.
Accuracy expectations, standards and labelling best practice
Accuracy expectations shift depending on what the drawing is for. Construction-stage verification demands checking against physical conditions; FM use often tolerates lower precision, provided the documentation is honest about its own limits.
Labelling conventions worth adopting on every sheet:
- “Record drawing”: verified by a named practitioner, dated, sealed where appropriate
- “As-built”: contractor-supplied, not independently verified
- “Not verified”: applies wherever field data hasn’t been checked against the actual installed condition
Pro Tip: If a drawing mixes verified and unverified elements, note it element by element rather than applying one blanket disclaimer to the whole sheet. A single caveat buried in the title block gets missed; annotations next to the specific unverified item don’t.
Commission a proper measured survey when the existing documentation is missing, contradictory, or the works are safety-critical (structural alterations, fire compartmentation). Guessing from an old as-built is not a substitute.
Modern workflows: scan-to-BIM, point clouds and digital handover
Laser scanning has changed how as-built information gets captured, but it hasn’t changed the verification problem. It’s moved it.
Point-cloud data feeds directly into as-built records and, eventually, record drawing or model production, and the geometry is often more precise than a hand-measured survey. The risk sits in trusting a vendor-supplied model without checking it. Scan-to-BIM outputs still need supervised verification against site records before a practitioner seals anything derived from them, because a beautifully rendered point cloud can still misrepresent what’s actually behind a wall.
Recommended handover deliverables:
- PDF for a stable, non-editable reference set
- DWG for parties who need to keep working in the drawings
- IFC where BIM coordination continues into FM or future design work
- Linked O&M data so equipment records travel with the model rather than sitting in a separate folder nobody opens
Owners should specify format, level of detail, and whether the model needs chartered verification before signing off the brief, not after the deliverable lands.
How owners and FM teams use these sets: handover checklist and best practice
Facilities managers should rely on record drawings wherever they exist, because that’s the set someone has actually checked. As-built mark-ups fill gaps only where no verified record has been produced.
- Confirm file formats match what your FM software actually opens (DWG, IFC, PDF)
- Check metadata: revision dates, author, verification status per sheet
- Confirm O&M manuals and warranty documents are linked to the correct asset, not just bundled loosely
- Tie the drawing set to the asset register so maintenance staff can find the right sheet without hunting
Pro Tip: Write the handover format requirements into the contract at award stage, not at practical completion. By close-out, there’s no leverage left to demand a different format.
Without this, FM teams inherit documentation nobody trusts and end up re-surveying buildings that were, in theory, already documented.
Practical summary: what each role should request and why
Contractors should keep disciplined redline records throughout the build. Architects and engineers should verify before sealing anything, and label what they haven’t checked. Owners should specify formats and verification requirements in the contract, not after handover. On drawings, use plain wording: “Record drawing, verified [date]” or “As-built, contractor-supplied, not verified.”
Publisher perspective: how Xponexus approaches verified record documentation
At Xponexus, embedded engineers work inside client workflows to produce calculations, drawings and BIM coordination that meet UK standards and Eurocodes from the outset, not retrofitted at close-out.
— Mohammed
How Xponexus Engineering can help with record drawing production
Xponexus Engineering is the alternative to hiring another permanent drafter or waiting weeks for an agency slot when your as-built or record drawing set needs turning around fast. Rather than stretching an already busy in-house team, you get an embedded engineer working inside your existing workflow, producing CAD and BIM outputs to UK standards and Eurocodes, at a fraction of the cost of a local hire.
This suits consultancies facing complex building services coordination, a backlog of record-drawing compilation, or simply no spare in-house capacity to verify contractor mark-ups properly before close-out. NDA protection and a 48-hour kick-off mean you’re not waiting on procurement to solve a documentation gap that’s already overdue. Visit the Xponexus services page to scope your next as-built or record drawing package and get a project moving this week.
Sources
- As Built v. Record Drawings (Great American Insurance Group)
- Preparing As-Built and Record Documents Guideline (PEO)
- Joint best practice statement: As-Built and Record Drawings (OAA / OGCA)
- As-built drawings in AIA contract documents explained (AIA Contracts Learn)
- As-built drawings (Procore library)
Leave a Reply