Record Drawings vs. As-Builts: A Lean Closeout Standard for Small Teams

The Closeout Nobody Could Read

A small studio finishes a whole-house remodel and asks the contractor for the closeout set. What arrives, three weeks after move-in, is a scanned field set: coffee-ringed sheets, handwritten dimensions in two different hands, a moved door circled on one sheet and not on the elevation that shows it, and a note that says only "per field." Nobody can tell which marks were verified, which were guesses reconstructed at the end, and which changes never made it onto paper at all.

That sequence is illustrative, not a documented project — but the failure in it is ordinary. The team did capture changes. They just never separated the two jobs closeout actually contains: recording what the field did, and issuing a clean set the owner can rely on later. When those two jobs blur into one messy hand-off, the owner cannot tell which changes were confirmed, which were reported but never verified, and which were never documented at all.

A scope note before the method: who owes which set is a contract question, not a custom. On many projects the contractor is required to maintain as-built markups during construction, while preparing record drawings is a separate service the designer provides only when the agreement calls for it. Nothing in this article creates that obligation — it shows how to handle it cleanly when it is yours, and how to specify it clearly when it is not.

The short version

• As-builts are the contractor's running field record — changes marked, usually in red, on the construction set as the work happens.
• Record drawings are the designer's compiled set, prepared from those markups when the contract calls for it: changes incorporated into clean sheets, reviewed against what the designer knows from the site.
• Measured drawings are a third, different thing: drawings made from measuring an existing building — most often before a renovation, and defined by that measurement-based source rather than by closeout.
• The system that makes both sets trustworthy is small: mark changes weekly, never from memory at the end; keep one controlled markup set; and label the final issue with language that says exactly what it is based on.
• If the contract is silent on record drawings, raise it before construction starts — not at closeout, when the leverage and the site team are both gone.

---

Three terms, three different jobs

The words are not interchangeable, and using them loosely is where closeout disputes start. The working convention in this article follows the widely used AIA-style definitions: the lines are drawn by who prepares the drawing and what it is made from, not by how finished it looks. Terminology and who owes which set still vary by contract and by firm — which is exactly why your own agreement should name them explicitly.

One caution belongs in the table itself: a record set compiled from markups is only as reliable as the markups underneath it. The designer's review screens and organizes the field record — it does not independently re-measure the building. Final issue language should say so plainly, which is why the wording in the last section matters.

Mark it when it happens, not at closeout

Late reconstruction compounds every other closeout problem — the illegible notes, the sheet that never got updated, the change nobody can source. A relocated drain, a shifted partition, a rerouted conduit — each is obvious the day it happens and genuinely hard to recall six weeks later, especially once the work is covered. Concealed conditions are the extreme case: if nobody records them before the wall closes, recovering them later becomes uncertain, costly, and sometimes invasive.

The lean fix is a rhythm, not a heroic effort. Keep one controlled markup set — print or digital, but one — and require markups on a fixed cadence:

Tying each markup to its source document does quiet, important work. A source reference makes a change traceable — it shows what instructed or reported the change. It does not by itself verify the installed dimension, so markups should also say, where it matters, whether a dimension was instructed, reported from the field, or actually measured. The same discipline that makes a pre-issue coordination review catch conflicts between drawings and specs makes closeout markups auditable instead of decorative.

The handoff: from markups to a clean set

The designer's job at closeout is compilation and screening — not redrawing from scratch, and not rubber-stamping the field set. Worked in order, on a small remodel with complete markups and few discrepancies, the conversion stays proportionate — effort grows with sheet count, markup quality, and how much checking the set requires:

1. Reconcile before you draw. Check the markup set against the change log — every change order, ASI, and approved substitution should appear on the markups, and every markup should trace to one of them or to a noted field condition. Discrepancies get resolved with the contractor now, while the site team still exists.
2. Incorporate, don't layer. Changed conditions go into the clean sheets themselves — plans, elevations, and details updated to the as-built condition — rather than leaving the owner to read redlines over an obsolete base drawing. Inserted sketches that carried a change get folded into the affected sheets or carried as clearly numbered record sketches.
3. Flag what you could not verify. Anything the designer did not observe and cannot check — concealed routing reported by the contractor is the usual case — stays attributed to its source in the set's notes. Screening means the owner can see which information is whose.
4. Issue it as its own set. New title-block issue entry, its own date, its own name. A record set that masquerades as a reissue of the construction set will be misread for years.

For studios that supply production documentation to a contractor partner, a clean handoff pays off plainly: the partner gets a closeout package their client can actually use, with fewer clarification requests after everyone has left the job. If building and maintaining that kind of documentation discipline is the gap in your own practice, Creo's partnership support covers drawing production behind the scenes, coordinated to the field information the project team supplies.

The final issue language

What the title block and transmittal say is part of the deliverable. Vague language — or worse, language that claims the designer verified every field condition — creates exposure the work itself never did. A small team's standard note needs only three elements:

• Basis: the set was prepared from the contractor's as-built markups and the project's change documents, furnished to the designer.
• Limits: field conditions not observed by the designer are shown as reported; the set is a record of furnished information, not a field survey.
• Status: the issue date, what it supersedes, and that it is issued for the owner's record and future reference.

Build that note once as a reviewed template, with your own professional advice where liability wording is concerned — then fill its basis, limits, and status fields for each project, because sources and observations differ from job to job. The point is consistency of structure without a boilerplate promise that stops being accurate.

Questions small teams ask

Our contracts just say "as-builts." Is that enough?

It is enough to create an argument. The single word does not say who marks what, on what cadence, in what form the set is delivered, or whether a clean compiled set is owed at all. Add four lines to your standard terms before the next job: who maintains markups, how often they are updated, what format the handoff takes, and whether record-drawing compilation is included, excluded, or a separate service.

Can the contractor just deliver record drawings instead?

On many small jobs the contractor's marked-up set is the only closeout set the owner ever receives — and if the contract says that, it can be a legitimate deliverable. What it should not do is borrow the other name. A contractor-prepared set labeled honestly as as-builts, marked legibly and tied to its change documents, serves the owner better than the same set relabeled as record drawings it never went through the process to become.

What about digital markups — do they change the standard?

They change the tooling, not the jobs. A shared PDF markup set or a model updated in the field can be better than paper redlines — searchable, legible, backed up — provided there is still exactly one controlled set, one cadence, and one handoff. Ten people's private markup copies are the digital version of the coffee-ringed field set.

When is it too late to fix a bad markup set?

Earlier than teams hope. Once finishes cover the work and the field crew has moved on, reconstruction depends on memory, photos, and opening finished work nobody will pay for. If you inherit a thin markup set mid-project, restart the weekly cadence from that day forward and document the gap in writing — a partial, honestly bounded record beats a complete-looking one built on guesses.

Do record drawings replace keeping the change documents?

No. The compiled set and its sources travel together: change orders, ASIs, approved submittals, and the markup set itself. The submittal review sequence a team ran during construction is part of that trail. The record set is the readable summary; the file behind it is the evidence.

---

Separate the two jobs on your next closeout: the contractor's markups, kept weekly and tied to their sources, and — when your agreement calls for it — a clean record set compiled from them, honestly labeled with what it is based on. The owner gets documentation they can build the next project on, and your studio gets fewer post-handoff questions about what actually changed.