To create as-built drawings, you start with the latest approved construction set, capture every deviation that happened in the field (dimension changes, relocated services, substituted equipment, RFIs and change orders), mark those changes onto the drawings as work progresses, and then reconcile all of it into a single, clean record set that reflects what was actually built. The hard part is rarely the final drafting, it's the discipline of capturing changes accurately while they're happening on site. This guide walks through how to create as-built drawings the way we do it in our studio, from the first site markup to the delivered record set.

What as-built drawings actually are

As-built drawings (sometimes called "record drawings" or "as-constructed") are the final set of plans that document a project exactly as it was built, including all the deviations from the original design intent. They matter because almost nothing gets built precisely as drawn, a beam gets moved 200 mm to clear a duct, a panel gets relocated, a wall thickness changes, a buried service runs a different route. If those changes aren't recorded, the next person to touch the building, a facilities manager, a renovation architect, a maintenance contractor, is working blind.

It's worth being honest about the distinction: redlines are the raw field markups (usually red pen or red digital ink on a printed or PDF set). As-builts are the cleaned-up, reconciled drawings produced from those redlines. You need both, and the quality of your as-builts is only ever as good as the quality of your redlines.

How to create as-built drawings: the workflow

1. Start from the correct base set

Begin with the most recent approved-for-construction set, not an early design issue. Confirm the revision number and date on every sheet. If you start from the wrong revision, you'll spend the rest of the project chasing phantom discrepancies. Lock this set as your "as-built master" and date it.

2. Capture changes continuously, not at the end

The single biggest mistake on as-builts is leaving them until handover, then trying to reconstruct six months of field decisions from memory. Don't. Treat the as-built set as a living document updated as work happens. Three things drive every change you need to record:

  • RFIs, the response often changes the work. Note the RFI number directly on the affected drawing.
  • Change orders / variations, anything that altered scope, dimension, material, or location.
  • Field conditions, things that simply came out different from the drawing (existing conditions, coordination clashes resolved on site).

3. Mark up the PDF set on site

For most teams the practical reality is a PDF set on a laptop or tablet. Walk the floor, and for every deviation: draw it in a consistent redline colour, add a short note explaining what changed and why (reference the RFI or CO number), and date it. A few habits that pay off:

  • Use one consistent markup colour for as-built changes so they're instantly distinguishable from QA or coordination markups.
  • Write self-explanatory notes, "duct lowered to 2700 AFF, see RFI-114," not just "moved."
  • Snap measurements on site rather than scaling off the drawing later; record actual dimensions, not assumed ones.
  • Keep the markups on the drawing, never in a separate notebook that drifts away from the set.

If you want the underlying discipline of clean, layered drawing markups, our guide to marking up construction drawings covers colour conventions, layers, and keeping markups reviewable.

4. Reconcile, don't just collect

Before you redraft, sit down with the marked-up set, the RFI log, and the change-order register side by side. Check every recorded change against its paper trail, and flag anything in the logs that isn't reflected on a drawing, those gaps are where as-builts go wrong. This reconciliation pass is the step amateurs skip and professionals never do.

5. Produce the clean record set

Now transfer the verified changes into the drawings properly. For CAD-originated projects this usually means editing the source DWG/RVT and re-exporting clean PDFs. Each affected sheet gets a clear "AS-BUILT" stamp, a record revision (e.g. Rev. AB), and the date. Don't leave informal redline scribbles in the final deliverable, the record set should read like a deliberate, drafted document, because that's what the next user will trust.

6. Compile, check, and hand over

Assemble the full set, verify sheet numbering and revisions are consistent, and cross-check against the spec and equipment schedules. Deliver in the format your client and facilities team will actually use, typically a complete, bookmarked PDF set, often alongside the native CAD files. A well-organised single PDF beats a folder of loose sheets every time at handover.

A few honest pitfalls to avoid

  • Letting the set go stale. An as-built updated only at the end is half-fiction.
  • Recording the change but not the reason. Future readers need the "why," not just the "what."
  • Mixing markup intents. QA comments, coordination notes, and as-built changes on the same colour become unusable.
  • Delivering raw redlines as the final product. Redlines are the input; the clean reconciled set is the deliverable.

FAQ

Who is responsible for creating as-built drawings?

It varies by contract, but typically the contractor maintains the field redlines throughout construction and the design team (or a dedicated drafter) produces the final reconciled record set. The contract documents should state explicitly who owns each step, don't assume.

What's the difference between redlines and as-builts?

Redlines are the raw, hand-marked field changes made as work happens. As-builts are the cleaned-up, verified, properly drafted record drawings produced from those redlines. You capture redlines continuously and produce as-builts from them at (or near) handover.

Can you create as-builts directly on PDFs?

Yes, many teams mark up the PDF set on site and then reconcile and finalise from there. For projects that originated in CAD, the cleanest as-builts come from editing the source model/DWG and re-exporting, but the PDF set is where most of the field capture happens.

If your as-built workflow lives in heavy 50-200 MB+ CAD-exported PDF sets and the daily grind of marking them up on a laptop is slow, Ncored is a fast desktop PDF editor built by our architecture studio for exactly that, try the free 14-day trial at ncored.com.