Documentation & records
How to organize as-built drawings
As-built drawings are the design set updated to reflect what was actually installed — every dimension that shifted, every routing that changed to dodge a conflict, every RFI answer that moved something. The mistake almost everyone makes is treating as-builts as a closeout task: a scramble at the end to remember changes that happened months ago. The record that works is the one maintained as the work goes in. This is how to keep as-builts organized so they're accurate when the owner needs them.
For superintendents, field engineers and QC staff responsible for maintaining the record set through construction and handing over accurate as-builts at closeout.
Step by step
Keep a controlled current set
Work from one authoritative, current drawing set — with the latest revisions, addenda and bulletins folded in — that everyone red-lines against. Red-lining onto a superseded sheet is how conflicting as-builts get created.
Red-line changes as they happen
Mark up the drawing the day a change goes in, not from memory at closeout. A rerouted line, a relocated cleanout, a dimension that shifted in the field — if it isn't captured when it happens, it's lost.
Trace each change to its source
Tie every red-line to the RFI, change order, or field directive that authorized it. A change with no traceable authority behind it is the one that gets disputed later.
Back concealed work with dated photos
Before an assembly is closed up, photograph the actual routing tied to its location. A pre-cover photo is proof of the real condition that a clean drawing can never provide on its own — and it's what the owner's team relies on years later.
Organize by discipline and area
Keep the marked set structured the way it'll be used — by discipline (architectural, structural, MEP) and by area or level — so a specific concealed run can be found without flipping the whole set.
Reconcile against RFIs and submittals
Periodically cross-check the red-lines against the RFI log and approved submittals to catch changes that got built but never marked. This is the step that keeps the set honest before it hardens into the record drawings.
Produce the record set for turnover
At closeout, compile the red-lines into the final record drawings and fold them into the turnover package alongside the O&M manuals and warranties. The set the owner receives should let them open a wall and trust what they find.
What gets missed
- Treating as-builts as an end-of-job task, then reconstructing months of changes from memory.
- Red-lining onto a superseded drawing set instead of the current controlled set.
- Changes with no traceable RFI or change order behind them, which invites disputes.
- Concealed runs with no pre-cover photo, leaving the owner to guess at what's behind the wall.
- A record set no one reconciled against the RFI log, so built-but-unmarked changes slip through.
Questions people ask
- When should as-builts be updated?
- As the work goes in, not at closeout. Field conditions never match the plans perfectly, and a change that isn't red-lined the day it happens is a change no one will accurately remember at the end of the job.
- What's the strongest form of as-built record?
- Red-lines backed by dated, location-tied photos of the condition before it was concealed. A pre-cover photo of an assembly is proof of the real routing that a clean drawing on its own can never provide.
Terms worth knowing
Checklists that make this a one-tap job
Free, field-ready checklists, each with the photo every item needs before it can be submitted.
Related guides
- How to write an RFIWrite an RFI that gets a clear, usable answer fast — one specific question, the documents it references, and a proposed answer — instead of a slow round of clarifying questions.
- How to assemble a turnover packageCollect the records the owner needs to run and warrant the building — O&M manuals, as-builts, warranties, permits, and inspection proof — organized so they can actually find them.
- How to hand over O&M manualsCollect operation and maintenance manuals from every sub, verify they match what was actually installed, organize them by system, and train the owner's operators.
Reading the steps is one thing. Proving you walked them is the job.
RTI holds the submit button until every mandatory item is answered and the photos are attached, then chains the record so it can be proven untouched later.