Cutaway utility corridor showing installed services

Contractors: 5 As Built Documentation Deliverables That Owners Require

September 30, 2026

As-built documentation requirements come down to five deliverables and one governing rule: record drawings, record specifications, native CAD files, PDFs, and a signed certification statement, all reflecting what was actually built, not what was designed. The accuracy principle is simple: document field conditions as they exist, and bring in a licensed surveyor when the owner or contract calls for it. Your project’s CAD manual and submittal standards decide the format, and following them precisely is what gets your package accepted the first time.

TL;DR:

Accurate documentation of deviations, utility locations, and equipment shifts is crucial, especially for buried utilities and changes linked to RFIs or change orders.

Critical underground utilities often require professional surveying, GPS coordinates, or fixed reference points to ensure measurement precision far beyond tape accuracy.

Submittals must follow specific CAD standards, include native files, referenced resources, fonts, and proper stamps; deviations lead to rejection unrelated to actual construction quality.

Maintaining a live, continuously updated field record set during construction reduces errors and rework, with weekly short QA cycles improving data reliability.

Proper roles and responsibilities clarify that contractors record and update data, while architects review for completeness; adherence to owner standards ensures smooth approval and better future project performance.

Federal-rconstructionsolutions

Strengthen Your Next Construction Bid

R. Construction Solutions helps contractors navigate federal procurement, RFP writing, compliance support, and efficient bid strategies.

Explore construction support

Checklist: what belongs on as-built drawings and record documents
How accurate do as-builts need to be, and when do you need a survey?
File formats, CAD standards, and stamping rules that get you approved
Submittal timing, retention, and what a closeout package includes
Roles, responsibilities, and who needs to sign off
Field practices that reduce rejection and rework
Common gotchas from DOT, city, and university requirements
Why documentation discipline protects your next bid, not just this closeout
Getting your closeout documentation across the finish line
Sources
FAQ

Checklist: what belongs on as-built drawings and record documents

Owners reject as-built packages more often for missing detail than for bad drawing quality. The Project Record Documents guidelines from USC Facilities Planning & Management spell out what a complete record set must capture: every deviation from the original design, not just the obvious ones.

Before you submit anything, confirm your drawings account for the following:

Horizontal and vertical locations of concealed utilities, especially anything buried, chased into a wall, or routed above a ceiling.
Routing changes to piping, ductwork, and conduit that differ from the contract drawings.
Revised circuitry and any electrical changes made in the field, including panel and circuit reassignments.
Equipment, damper, and duct locations that shifted during installation, along with the reason if it ties to an RFI or change order.
Items not built clearly crossed out, so a future reader never mistakes a deleted design element for existing work.
Product data including manufacturer, model number, and any installation deviation from the specified product.
Cover-sheet metadata: project name, contractor of record, project number, dates, sheet index, and a revision log that tracks every update.

The USC standard makes clear that these records must include all deviations from the original design, from the actual horizontal and vertical positions of concealed utilities to equipment locations and revisions traced back to RFIs, change orders, or supplemental instructions. Items that were designed but never installed should be crossed out on the sheet, with the new work delineated so there’s no ambiguity for the next contractor or facilities team who opens the file.

Shop drawings and O&M inserts matter here too. If a piece of equipment shipped with a different footprint than the approved submittal, that discrepancy belongs in the record set, not buried in a closeout binder nobody reads again. The same goes for product substitutions made mid-project: note the change, note the approval, and keep the paper trail intact.

Field crews often treat markups as an afterthought, something to clean up the week before final inspection. That habit is exactly what produces incomplete as-builts. A duct that got rerouted around a structural beam in month three is easy to forget by month eleven unless someone wrote it down when it happened. The construction quality control plan requirements that most federal and institutional owners expect follow the same logic: document as you go, not as you remember.

One more detail owners check closely: cross-referencing. If a change traces back to an RFI or change order, note the number directly on the sheet. Reviewers use that reference to confirm the deviation was authorized, and a missing number is one of the fastest ways to trigger a resubmittal request.

How accurate do as-builts need to be, and when do you need a survey?

Accuracy requirements are not one-size-fits-all. They depend on what the record will be used for later, and getting this wrong is one of the most common reasons owners send drawings back.

A single figure worth knowing: according to Rutgers Institutional Planning & Operations utility as-built specifications, measurement-tape accuracy is acceptable for many non-critical installations, but critical underground utilities or special cases may require professional surveying instead. That distinction shapes how much you spend on field verification, and skipping it on the wrong item can force a costly rework of your entire record set.

Tape measurement and surveying accuracy comparison

For a fence line, an interior partition, or a piece of surface-mounted equipment, a tape measure and a careful field crew are usually enough. For a buried gas line, a storm drain crossing under a roadway, or any utility a future excavation crew will need to locate without digging blind, that standard changes. Some DOT contracts require GPS coordinates or full professional survey data for underground utilities, precisely because the cost of a wrong guess later (a struck line, a delayed dig permit) is far higher than the cost of getting it right now.

The Rutgers guidance also stresses tying measurements to permanent reference points, such as structural columns or established baselines, rather than relative offsets from something that might not exist in five years. A distance measured “12 feet from the temporary fence” is useless once the fence comes down. A distance measured from a column line or a fixed benchmark holds up.

What happens when your as-builts don’t meet the bar? Owners are not always sympathetic to good intentions. Under some contract terms, if your record documents are inadequate, the owner can bring in a third-party locator or surveyor to verify field conditions, and bill that cost back to you. That single clause is often enough to change how seriously a project team treats redline discipline from day one. Better to build the habit of accurate field marking into your weekly routine than to pay someone else to do it after the fact.

File formats, CAD standards, and stamping rules that get you approved

Most as-built rejections have nothing to do with whether the work was documented accurately. They happen because the files don’t match the owner’s CAD manual. Every city, DOT, and institutional owner has its own standard, and ignoring it is the single most preventable mistake on this list.

Start with the deliverables you’ll need to produce, not just the drawings themselves:

Native CAD files in the format the owner specifies (DWG for AutoCAD and Civil3D, DGN for MicroStation), plus PDF copies of every sheet.
Xrefs and referenced external files included on the delivery medium, not just linked, so the owner’s team can open the drawing without missing resources.
Pen weight and plot style files (.ctb or .stb) that match what was used to produce the final plots.
Font files for any custom text styles, since a missing font silently changes drawing appearance on the owner’s machine.
An index of sheets that matches the physical or electronic set exactly, with no orphaned or missing sheet numbers.

The ASU as-built and record drawings requirements make this point directly: for electronic submissions, contractors need to include all referenced external files and plot definitions so the owner’s CAD team can open and plot the drawing without hunting down fonts, raster images, or style files separately.

On the drawing itself, resist the urge to delete anything. Redline and cloud changes instead of erasing the original design lines, since owners often want to see what changed, not just the final state. Follow the owner’s layer names and text sizes exactly, since most CAD manuals specify both down to the point size. The SPU/SDOT as-built drawing requirements illustrate how specific these conventions get: deviations get incorporated without RFI or payment references cluttering the drawing itself, specified layers and colors are mandatory, and only certain file formats (AutoCAD DWG, DWF, PDF, or a physical print) are accepted for submission.

Every sheet also needs a clear “AS-BUILT” stamp, a revision box that tracks each update with a date and description, and space for a signature and seal where the project requires one. Certification language typically states that the drawings reflect conditions as observed and recorded by the contractor during construction, signed and dated by the person responsible for the field records.

Submittal timing, retention, and what a closeout package includes

Record documents are not a task you complete in the final week. They are maintained continuously, then packaged at the end.

Maintain a live field record set throughout construction, kept separately from the working contract documents so changes don’t get lost among daily markups.
Post changes as they occur, or at minimum within the window your contract specifies. The USC record documents standard notes that owners often review record documents monthly, and payment can be withheld when the field set isn’t kept current.
Assemble the final package with every required component: hard copies or mylar sheets if the contract calls for them, full electronic native files plus PDFs, a sheet index, and a binder or folder structure containing record specifications and product data.
Include the certification statement required under 01 78 00 Closeout Submittal and Project Record Documents, which governs the administrative requirements for record drawings, record specifications, and record product data on most institutional projects.
Confirm retention obligations before you archive or discard anything. Retention periods vary by contract and jurisdiction, so the controlling document is always your specific project manual, not general industry habit.

A common failure point here is treating the “field set” and “final set” as the same document. The field set is a working copy, marked up daily and sometimes messy by necessity. The final set is the clean, reconciled version, delivered at closeout. Confusing the two, or submitting the field set as the final deliverable, is a fast way to get a package bounced back for cleanup.

Roles, responsibilities, and who needs to sign off

As-built documentation involves more than one party, and confusion about who owns which step is a frequent source of delay.

The contractor maintains the record prints in the field, posts redlines as changes happen, and is responsible for the accuracy of the as-built content itself.
The architect or engineer reviews the final record set, initials or transmits it, but under AIA contract language (A201/B101), the architect is generally not responsible for the accuracy of contractor-provided as-built information unless that verification was contracted as a separate, supplemental service.
A licensed professional (PE or registered architect) seals pages only when the contract or jurisdiction requires it, and a sealed page typically carries specific liability language limiting what the seal certifies.
The owner performs final review and acceptance, which is the step that actually closes out the documentation requirement.

That AIA distinction matters more than most contractors realize. Architects reviewing your record set are checking for completeness and general consistency, not personally verifying every dimension in the field. The responsibility for what’s actually correct sits with the contractor who marked it up. Sample certification language usually reads something close to: “The undersigned certifies that these record drawings reflect conditions observed and recorded during construction, to the best of the contractor’s knowledge.” An architect’s initials on a transmittal typically mean the set was received and appears complete, not that every measurement was independently confirmed. Keeping that boundary clear on federal and institutional work, where the change order process already requires tight documentation of every deviation, prevents disputes about who owns an error discovered after closeout.

Field practices that reduce rejection and rework

The contractors who get as-builts approved on the first pass share one habit: they never let the redline set go stale. Waiting until the punch list to reconstruct three months of changes from memory is how errors creep in, and it’s avoidable with a few disciplined routines.

Keep the field record set on the job site at all times, and treat it as a living document rather than a folder that gets touched once a week. Every RFI response, every change order, every field adjustment gets marked the same day it happens, while the detail is still fresh. The construction process improvement approach that reduces rework on federal projects applies the same principle here: capturing changes continuously costs less than reconstructing them later.

Tie concealed items to permanent reference points, not temporary ones. A utility located “6 feet from the trailer” is unusable once the trailer moves. Reference structural columns, foundation lines, or a surveyed baseline instead, per the Rutgers utility as-built guidance, so anyone excavating years later can find it without guesswork.

Build short QA cycles into your schedule rather than one big push at the end:

Pro Tip: Run a 15-minute weekly redline reconciliation with your superintendent, spot-check three dimensions against the drawings, and sign off before any wall or ceiling closes over concealed work.

Digital field-capture tools can support this rhythm without adding administrative burden, such as Operiva’s digital jobsite documentation tools, which let field crews log changes from a phone or tablet the moment they happen rather than waiting for end-of-day paperwork. Platforms built for continuous documentation, such as Operiva’s digital jobsite documentation tools, let field crews log changes from a phone or tablet the moment they happen rather than waiting for end-of-day paperwork. For trade-specific concealed work like plumbing, HVAC, or electrical, an app such as MEPflow’s field service software can capture equipment locations and routing changes directly from the technician doing the install, which keeps the record closer to the actual field condition than a markup added from memory later.

Field practices that reduce rejection and rework — overview diagram

Common gotchas from DOT, city, and university requirements

Every owner’s CAD manual reads a little differently, but the failure patterns repeat across agencies.

State DOT conventions typically require revised or additional sheets to carry specific labels, use CCO (Change/Contract Change Order) notation tied to stationing, and in some contracts, mandate GPS coordinates for underground utilities rather than relative offsets. Caltrans CADD manual guidance reflects this pattern, alongside similar practices at other state agencies.
City CAD manuals often specify exact layer names, text sizes, and plotting conventions, and a mismatch on any one of these is a common reason submittals bounce back before anyone even reviews the drawing content.
University and institutional owners frequently follow a closeout structure similar to Section 01 78 00, requiring both a certification statement and a defined electronic file package before final acceptance.

The most frequent contractor mistakes are avoidable with a pre-submission checklist: missing native files (submitting only a PDF when the owner needs the DWG), wrong layer colors that don’t match the CAD manual, and omitted Xrefs or fonts that leave the owner unable to open the drawing correctly on their end. None of these relate to whether the work was built correctly. They relate entirely to whether the paperwork follows the rules, which is exactly why reviewing the project manual before you start drafting saves far more time than fixing it after rejection.

Why documentation discipline protects your next bid, not just this closeout

Federal and institutional owners remember contractors who deliver clean closeout packages, and they remember the ones who don’t. A record set full of missing layers, undocumented deviations, or a stale field set signals the same risk profile evaluators look for when they check past performance on a new procurement.

The contractors who treat as-built documentation as a daily habit, not a closeout scramble, tend to get through review cycles faster and with fewer punch-list items tied to documentation gaps. That’s not a small advantage on a federal contract, where past performance ratings follow you into the next bid. Building this discipline into your standard operating procedure, the same way you’d standardize a safety plan or a quality control checklist, pays off well beyond the current project.

If your firm is preparing for federal work and wants a second set of eyes on closeout procedures before submission, that review is worth scheduling early rather than the week before final acceptance.

— Rowena

Getting your closeout documentation across the finish line

Meeting every layer name, stamp requirement, and certification detail in a CAD manual takes time most project teams don’t have to spare, especially when you’re also managing the next bid. We work with construction businesses on compliance aspects of federal and private contracts, including closeout documentation, submission formatting, and certification language that influence package acceptance.

Federal-rconstructionsolutions

Our Compliance Support service helps contractors align record documents and closeout submissions with owner and agency standards before they go out the door, which means fewer resubmittals and faster sign-off from the reviewing architect or engineer. For firms managing both federal and private sector workloads, our Private Sector Guidance team applies the same documentation discipline to commercial closeout requirements, so your process doesn’t change project to project.

If your last as-built package was rejected, or you want a compliance review before your next submission, consider consulting a specialist to review your specific owner or agency requirements.

Sources

FAQ

What should be included in as-built drawings?

As-built drawings need to show every deviation from the original design, including actual horizontal and vertical locations of concealed utilities, routing changes, revised circuitry, and equipment locations, according to USC’s record documents standard. Items that were designed but never built should be crossed out, and changes should reference the RFI or change order that authorized them.

What are the 9 essential contract documents?

Definitions vary by project and owner, but a typical contract document set includes the agreement, general and supplementary conditions, drawings, specifications, addenda, change orders, and the record documents produced during construction. Your specific project manual, not a generic list, determines which documents your contract actually requires.

How accurate do as-built drawings need to be?

Accuracy requirements depend on the item: Rutgers utility as-built specifications note that measurement-tape accuracy is acceptable for many non-critical installations, while critical underground utilities may require professional surveying. Some DOT contracts also require GPS coordinates for utility locations rather than relative field measurements.

Who is responsible for as-built drawings?

The contractor is responsible for maintaining the field record set and posting accurate redlines as work happens, while the architect or engineer reviews and transmits the final set. Under AIA contract language, architects are generally not responsible for verifying the accuracy of contractor-provided as-built information unless that review was contracted separately.