How to Create As-Built Drawings: A Step-by-Step Process

Short answer: To create as-built drawings, capture every site change as a redline on the construction set while the work is being built, keep those markups current as the job proceeds, transfer the verified redlines onto clean drawing files, check that each change matches what was actually constructed, and issue the corrected set as the as-built or record set at handover. The discipline that makes this reliable is marking up as you go rather than reconstructing changes at the end. Archi Check helps capture field redlines as tracked markups, verify each one through Check → Correct → Verify → Close, and apply the AS BUILT stamp before the record set is closed.

As-built drawings are the part of a project that everyone agrees matters and almost nobody enjoys producing. They are the drawings that tell the truth about a building — not what was designed, but what was actually constructed, with every site change, substitution, and field adjustment recorded. They feed handover, facilities management, future renovations, and dispute resolution. And they are routinely produced badly, in a rush, from memory, at the moment the project is trying to close out.

The reason is structural. Capturing as-built information well requires effort spread across the whole construction phase, but the deliverable is only due at the end. Teams that defer the work pay for it with lost redlines, unverifiable changes, and a record set that nobody fully trusts. This guide sets out a practical process for producing as-built drawings that hold up — what to capture, when to capture it, how to get redlines into the set, how to verify them, and what a clean handover actually requires.

What an as-built drawing has to record

Before the process makes sense, it is worth being precise about what an as-built drawing is. It is the construction set, corrected to reflect the finished work. Everything that ended up different from the issued-for-construction drawings should appear on it: dimensional changes, relocated services, substituted products, revised details, and anything resolved by an RFI, a change order, or a field decision that altered the work.

It helps to separate three terms that get used interchangeably and should not be. A redline is the working markup — the marked-up construction drawing the field team annotates as changes happen, traditionally in red ink. An as-built drawing is the clean drawing produced from those redlines once the work is complete. A record drawing is the formal, certified version the design team or owner accepts as the official record. Redlines are the raw material; as-builts are the deliverable; record drawings are the version with a signature behind it. If you are unsure which your contract requires, start with as-built vs record vs red-line drawings before you go further.

The distinction matters because the obligations differ. A redline can be rough; it only has to be legible and correct. A record drawing carries a certification that someone stands behind, which means it cannot contain a change that was never verified. The whole process below exists to get from the first to the last without losing anything in between.

Step 1: capture changes on site, as they happen

The single most important rule of as-built production is that you mark up as the work proceeds, not at the end. A change captured the day it happens is accurate; the same change reconstructed three months later from a half-remembered conversation and a stack of RFIs is a guess. Every team that produces poor as-builts has the same root cause — the markup was deferred.

In practice this means a designated, current set of drawings — paper or digital — lives with the work, and whoever is responsible for the trade marks each deviation onto it as it is built. The redline should record what changed, where, and ideally why, with a reference to the instruction that authorised it.

What to capture

• Dimensional changes. Anything built to a different dimension than drawn — a wall moved, an opening resized, a level adjusted.
• Relocated or rerouted services. Mechanical, electrical, and plumbing runs almost never end up exactly where they were drawn; the as-built routing is some of the most valuable information in the set.
• Substitutions. Products, fittings, and materials that were swapped for an approved alternative, with the substituted item recorded.
• Revised details. Connections, junctions, and assemblies that were resolved differently on site than the detail showed.
• Authorised changes. Anything driven by an RFI response, a change order, a site instruction, or a field decision, cross-referenced to the document that authorised it.

Who captures it

On most projects the responsibility sits with the contractor and each subcontractor for their own scope, because they are the people physically doing the work and the only ones who see the change at the moment it happens. The consultant or design team typically receives, reviews, and incorporates those markups rather than generating them. Whatever the split, it should be assigned explicitly. As-built capture that is "everyone's job" is nobody's job, and that is exactly how changes go unrecorded.

Step 2: keep the redlines current as work proceeds

Capturing a change once is not enough; the redline set has to stay current and stay findable. The two failures that destroy as-built quality both happen here. The first is the lost redline — a markup made on a sheet that gets superseded, soaked, buried, or replaced, taking the only record of a change with it. The second is the unverified change — a markup made by someone who did not fully understand the deviation, recording it wrongly, with no one ever checking.

Keeping redlines current means a few unglamorous habits. There is one controlled set that is the master, not five partial copies on different people's desks. When a revised drawing is issued mid-project, the existing redlines are carried forward onto it rather than abandoned with the old revision. And each markup is attributable, so that when a redline is ambiguous months later, you can ask the person who made it rather than guess.

This is the stage where paper-based as-built capture quietly falls apart. A folded, annotated drawing in a site cabin is a single point of failure, and a photographed redline that lives in someone's phone is not a controlled record. Treating each markup as a tracked item — with an author, a date, and a reference to the sheet and revision it belongs to — is what stops the slow leak of information between capture and handover.

Step 3: transfer redlines into the drawing set

At or near completion, the accumulated redlines have to be turned into corrected drawings. This is the step most people picture when they think of "producing as-built drawings," and it is the most mechanical, but it depends entirely on the first two steps being done well. Good redlines transfer cleanly; bad redlines turn this step into forensic archaeology.

The sequence is straightforward in principle. Each trade submits its completed redlined drawings. The general contractor or lead consultant collects every subcontractor's markups and compiles them into a single authoritative set, resolving any conflicts where two trades marked the same area. Working markups are commonly required to be submitted some weeks before the handover date precisely so this compilation has time to happen. The compiled, reconciled changes are then transferred onto clean drawing files to produce the as-built set.

Two ways to record the change

There are two legitimate approaches, and the choice depends on what your client and contract require.

• Edit the geometry. The drawing itself is corrected so it shows the as-built condition — the wall is moved in the model or CAD file, the service is rerouted, the dimension is updated. This produces the cleanest deliverable and is usually what a formal record set requires.
• Annotate the change. The original geometry is kept and the change is recorded as a clear, permanent annotation on the sheet. This is faster and preserves the visible history of what changed, which some clients prefer for traceability.

Whichever route you take, the cardinal rule is that nothing gets transferred that has not been verified. Transferring an unverified redline into a clean, professional-looking drawing is worse than leaving it as a scruffy markup, because the polish lends false confidence to a change nobody confirmed.

Step 4: verify each change against reality

Verification is the step that separates a record set people trust from one they merely possess. A redline records what someone believed changed; verification confirms it actually changed that way. The two are not the same, and the gap between them is where as-built drawings go wrong.

Verification asks a simple question of each transferred change: does this match what was built? The answer comes from the evidence behind the redline — the authorising RFI or change order, site photographs, survey data, inspection records, or, on the items that matter most, a physical check. The principle that makes this trustworthy is the same one that underpins any quality process: the person who verifies a change should not be the same person who made it. A second pair of eyes catches the transcription error, the misread dimension, and the change that was marked up but never actually executed.

This is the same Check → Correct → Verify → Close loop that governs drawing QC generally. A redline is raised, the correction is transferred into the set, an independent reviewer verifies it against the evidence, and only then is the item closed. For the broader version of this loop, see the drawing QA/QC process in 4 stages. Applied to as-builts, it gives you something paper redlines never can: a record of which changes were confirmed, by whom, and on what evidence.

Step 5: issue the as-built or record set at handover

The final step is releasing the corrected, verified set as the official record. By now the changes are captured, transferred, and verified; issuing is the act of declaring the set complete and handing the truth about the building to whoever will own and operate it.

What handover requires depends on the contract, but most as-built deliverables share a common shape.

The status mark is where the as-built process meets the wider stamping convention. A sheet that records the finished work should carry an AS BUILT status so that no one ever mistakes it for a drawing to build from. For how that stamp sits among the others, see drawing approval stamps explained. Issuing the set with the right status, the verification behind it, and a record of what changed is what turns a pile of corrected drawings into a deliverable the owner can rely on for the life of the building.

Common failures and how to avoid them

Most as-built problems are not exotic. They are the same handful of failures, repeated, and each one traces back to a missing step above.

• The end-of-job reconstruction. Nothing is marked up during construction, so the as-builts are assembled from memory and paperwork at close-out. The fix is non-negotiable: mark up as you go, with capture assigned to named people.
• The lost redline. A change is captured on a sheet that gets superseded or destroyed, and the record goes with it. The fix is one controlled master set and markups that are carried forward across revisions.
• The unverified change. A redline is transferred straight into the clean set with no one confirming it. The fix is independent verification before any change is closed.
• The silent omission. An authorised change never gets recorded at all, and its absence is invisible — you cannot see what was left out. The fix is cross-referencing every RFI and change order against the as-built set.
• The wrong status. The record set is issued still carrying a "for construction" stamp, inviting someone to build from it. The fix is applying the AS BUILT status as part of closing the set.

A worked example

Consider a mid-sized fit-out where the mechanical contractor reroutes a duct run on Level 2 to clear a structural beam that the coordination model missed. Here is the process working as it should.

• On the day of the change, the mechanical foreman marks the new duct route onto the controlled redline set, notes the beam clash, and references the site instruction that authorised the move.
• Two weeks later the structural engineer issues a revised Level 2 plan; the duct redline is carried forward onto the new revision rather than left behind on the old one.
• At close-out, the contractor transfers the redline into the clean coordination drawing, editing the duct geometry to the as-built route.
• The lead consultant verifies the change against the site instruction and a set of progress photographs, confirms the routing matches what was installed, and only then closes the item.
• The Level 2 sheet is issued with an AS BUILT status, and the audit trail shows the change, the author, the verifier, and the authorising instruction.

The same duct, handled the common way, would have been a verbal "we moved it to miss the beam" at close-out, transferred from memory onto a sheet nobody verified, issued without a clear record of why the route differs from the design. Both sets look identical on paper. Only one of them is true.

Where Archi Check fits

Archi Check is purpose-built QC software for architectural drawing sets, and the as-built process is exactly the kind of work it is designed to hold together. The problem with producing as-builts has never been the drawing; it is keeping every change captured, current, and verified across months of construction. Archi Check treats each field change as a tracked markup rather than ink that can be lost.

In practice that means redlines are captured as markups using the nine tools — pin, cloud, arrow, callout, text, and the rest — each one becoming a tracked comment with an author, a date, and the sheet and revision it belongs to. As work proceeds, every markup carries a status through Check → Correct → Verify → Close, so a change cannot quietly disappear: it stays open until someone other than the author verifies it against the evidence and closes it. When the record set is ready, you apply the AS BUILT stamp preset to mark the set's status, and the audit trail shows exactly what changed, who verified it, and when. Because Archi Check is folder-first and keeps your QC data in your own project folders rather than a vendor cloud, that audit trail belongs to you and travels with the project at handover. You work across two screens — the register tracking every change on one monitor while you mark up the full-size drawing on the other. Archi Check runs on Windows today, with macOS coming soon, and there is a 14-day free trial.

FAQ

How do you create as-built drawings step by step?

Capture every site change as a redline on the construction set while the work is being built, keep those markups current and findable as the job proceeds, transfer the redlines onto clean drawing files at completion, verify each change against what was actually constructed, and issue the corrected set with an AS BUILT or record status at handover. The key discipline is marking up as you go rather than reconstructing changes at the end.

What is the difference between a redline and an as-built drawing?

A redline is the working markup — the construction drawing the field team annotates as changes happen, traditionally in red ink. An as-built drawing is the clean, corrected drawing produced from those redlines once the work is complete. Redlines are the raw record; as-builts are the finished deliverable. A record drawing is the formal, certified version accepted as the official account of the finished work.

When should you mark up as-built changes?

As the work happens, not at the end of the project. A change captured the day it occurs is accurate; the same change reconstructed months later from memory and paperwork is a guess. Marking up as you go is the single most important habit in as-built production, and end-of-job reconstruction is the most common reason record sets are unreliable.

Who is responsible for creating as-built drawings?

On most projects the contractor and each subcontractor capture the redlines for their own scope, because they do the work and see each change as it happens. The lead consultant or design team then receives, reviews, verifies, and incorporates those markups into the final set. The responsibility should be assigned explicitly, because as-built capture treated as everyone's job tends to become nobody's job.

Why is verification important for as-built drawings?

A redline records what someone believed changed; verification confirms it actually changed that way. Without an independent check, transcription errors, misread dimensions, and changes that were marked up but never executed all flow straight into the record set. Having someone other than the author verify each change against the evidence before it is closed is what makes a record set trustworthy rather than merely complete-looking.

Produce as-built sets you can stand behind

If your as-built drawings are still being reconstructed from lost redlines at close-out, see how Archi Check captures field changes as tracked markups, verifies each one, and applies the AS BUILT status before the record set closes: Try Archi Check free for 14 days.

Related guides

Keep building out your drawing QC process with Archi Check and these related guides:

• As-built vs record vs red-line drawings
• Defect tracking on drawings
• Snag list vs punch list
• The drawing QA/QC process in 4 stages

Archi Check is an independent product by Archi for architectural drawing QA/QC. Product names and trademarks referenced belong to their respective owners and are used for identification only.