HAWKEYE SYSTEMS

As Built Documentation for Construction Teams: Capture, Don’t Rebuild

See how construction teams capture as built documentation during work, choose digital formats, and prepare records for maintenance and asset management.

Plan a walkthrough

As built documentation is the final record of what was actually built, including every deviation from the contract documents, and it gives owners a usable baseline for operations, maintenance, future changes, and closeout. Specification language such as SECTION 01 78 39 and AIA-MBA guidance shape how teams produce and label it.

TL;DR:

Use “record drawings” in contracts when field measured precision is not promised, and define responsibilities, accuracy expectations, and reliance disclaimers explicitly.
Assign each trade a named owner for the Field Set, record changes when work happens, and photograph concealed conditions before enclosure.
Choose deliverable formats around the owner’s systems: vector PDFs travel easily, CAD files remain editable, and open IFC supports longer term model access.
Contractor redlines are not surveyed measurements; use an independent survey or sealed records for buried utilities, systems requiring fabrication accuracy, or mandated verification.
Submit redlines at punch list, circulate draft electronic files for review, and deliver corrected records, product data, and manuals at final inspection.

Hefieldops

Keep Field Records Ready for Review

Hefieldops connects field activity with office management, helping teams document site work for efficient review and billing.

Explore field operations

What is the difference between as-builts and record drawings?
What belongs in an as-built package?
How do you create accurate as-builts during construction?
Which digital as-built format should you choose?
What accuracy and disclaimers should you expect?
What should the final delivery checklist include?
How do field operations systems and mobile surveillance support as-built records?
What makes as-built data hard to collect on remote or active job sites?
Why does real-time as-built capture improve efficiency and safety?
How do as-builts support regulatory compliance and inspections?
Our view: capture beats reconstruction
How can a field operations platform produce audit-ready closeout packages?
FAQ
Sources

What is the difference between as-builts and record drawings?

The terms get swapped constantly, and the confusion has legal weight. Several document types are in play:

As-builts: the contractor’s marked-up set, usually red-lines on the construction drawings, showing how the work was installed.
Record drawings: the architect’s or engineer’s version, prepared after reviewing contractor data and, in many jurisdictions, sealed once a licensed professional verifies it. ASCE policy says record drawings differ from contractor as-builts because they are verified and often sealed.
Measured drawings: survey-based documents created by measuring the finished conditions directly, independent of the original design set.

The AIA-MBA Joint Committee recommends avoiding “as-built” in contracts because it implies field-measured precision. It suggests “record drawings” plus a disclaimer that the document reflects significant changes based on contractor-provided data, not verified measurements. Practice guidance from the Ontario Association of Architects adds that format and accuracy expectations belong in the contract.

What belongs in an as-built package?

Use this list to specify deliverables or audit a closeout set; consult the metal building site prep checklist for practical site preparation guidance.

Red-line record prints showing every field change
Marked-up shop drawings reflecting what was fabricated and installed
Record product data identifying the products actually used
Project record specifications, annotated for substitutions
O&M manuals and warranty documents
Field records for concealed items such as buried utilities and in-wall routing

On the drawings themselves, capture dimensional changes, underground utilities, foundation depths, final equipment locations, rerouted systems, and change-order references. A concealed duct run that moved significantly is exactly the kind of detail a maintenance crew will hunt for later.

Expected formats typically include hard-copy red-lines, updated CAD/DWG files, and vector PDFs. Set naming conventions and cover-sheet metadata (project, sheet number, revision date, preparer) up front so the owner can index everything later.

How do you create accurate as-builts during construction?

Accuracy comes from capturing information while the work is still visible. Professional guidance from PEO notes the best time to gather as-built information is during construction, when elements are accessible. A workable sequence:

Keep a dedicated Field Set on site, separate from the working construction set, and update it continuously.
Have the installer, subcontractor, or inspector mark changes the day the work is done, using consistent red-pencil conventions.
Cross-reference every change to its change order, RFI, or bulletin number.
Notify the architect when field conditions conflict with the design intent, before the work is covered.
Submit red-lined prints at punch-list, then a draft electronic set for review within the window your specification states.
Resolve review comments and deliver the final set at final inspection.

SECTION 01 78 39 follows this logic: maintain marked-up record prints on site, mark concealed elements promptly, and submit sets at punch-list and final inspection. Use the timing language in your own contract rather than a generic deadline. A municipal closeout manual from Los Angeles makes the same point: concealed items are hard or impossible to verify afterward.

Pro Tip: Set verification intervals at each milestone, and photograph and measure concealed conditions before enclosure. A quick walk with a tape and phone camera beats a ceiling demolition later.

Which digital as-built format should you choose?

Format should follow downstream use. If the owner runs a facility management system, a GIS, or a digital twin, the deliverable has to feed it. FHWA guidance on digital as-builts describes them as electronic, searchable, extractable, and durable, and lists vector PDF mark-ups, field survey points, GIS datasets, 3D models, and digital twins as implementation options.

Vector PDF mark-ups: the most portable and durable option, readable by anyone, though less useful for data extraction.
CAD/DWG: editable files that let the design team fold field changes into the drawings.
BIM/IFC: model-based asset data, strongest when the owner needs equipment attributes and spatial relationships.
3D laser scans and point clouds: high-fidelity capture of installed conditions, valuable where precision matters.
GIS datasets: the natural fit for utilities and linear infrastructure.

Where long-term extractability matters, prefer open standards such as IFC over proprietary formats that may become inaccessible. Ask the owner which systems will consume the data before choosing, not after.

What accuracy and disclaimers should you expect?

Contractor red-lines are working records, not surveyed measurements, and the guidance is consistent on how to label them:

The AIA-MBA Joint Committee advises against implying absolute precision and recommends a clear disclaimer on record drawings.
Specifications such as SECTION 01 78 39 commonly require contractor mark-ups, retention of the Field Set, and a stated number of submitted copies.
Bring in an independent survey or sealed record drawings for critical buried utilities, fabrication-critical systems, or any project where the owner requires a verified record.

The Ontario Association of Architects and Ontario General Contractors Association joint best practice statement advises distinguishing contractor as-builts from architect and engineer record drawings, defining responsibilities in the contract, and disclaiming reliance on contractor-supplied information.

What should the final delivery checklist include?

Missing record documents can hold up final payment, so treat closeout as a checklist:

Submit marked-up record prints at punch-list, in the quantity the specification requires.
Distribute the draft electronic set (CAD or PDF) to the consultants and owner for comment.
Respond to review comments within the turnaround your contract sets.
Deliver corrected final sets, product data, and O&M manuals at final inspection.
Confirm every cover sheet carries project name, sheet number, revision date, and preparer, so the owner can index and retrieve files later.

Institutional standards, such as Brown University’s facilities requirements, combine design-team updates with contractor red-lines into final record plans on a defined review cycle. Read the owner’s standards early, because copy counts and file conventions vary.

How do field operations systems and mobile surveillance support as-built records?

Paper red-lines depend on someone remembering to mark them. A field operations system moves that discipline into daily work: crews log activity, attach photos and notes to specific locations, and tie changes to the job and ticket they belong to. Time-stamped photos of an open trench or an uncovered wall cavity become evidence that a concealed condition existed and what it looked like before it was buried.

Mobile surveillance adds a second layer. Cameras positioned at the site can show when work happened and in what sequence, which helps reconcile disputes about installation order or who touched what. Our overview of construction site surveillance covers how camera roles and evidence capture work in practice.

The practical gain is linkage. When field records, photos, and change documentation live in one place, the person assembling the closeout package is compiling existing evidence, not reconstructing months of work from memory. Our change order tracking page explains how field proof supports approvals. Treat the platform as the collection layer and your drawings as the controlled output: the red-line set stays authoritative, but it is built from verified, dated field evidence.

What makes as-built data hard to collect on remote or active job sites?

The obstacles are predictable, and so are the fixes:

Concealed work gets covered fast. Schedule pressure means trenches close and walls get drywall before anyone measures. Build a hold point into the schedule: no enclosure until the installer has photographed and recorded the condition.
No one owns the Field Set. When every trade assumes someone else is marking changes, nobody does. Assign a named person per trade and review the set weekly.
Poor connectivity at remote sites. Use tools that capture offline and sync later, so a dead zone does not become a documentation gap.
Active sites are hazardous and crowded. Short, frequent captures taken during normal work beat a big end-of-job survey that interrupts crews.
Pencil marks disappear. Rain, mud, and handling destroy paper. Photograph red-lines at the end of each week as a backup.
Locations are ambiguous. “Near the northeast corner” fails a maintenance crew. Reference grid lines, stationing, or surveyed points.

For underground utilities, municipal standards are specific. The Pennsylvania-area PWSB procedures call for clouding as-built changes, noting pipe sizes, inverts, and lengths, and accepting only drawings within a stated margin of error. Following a conventions list like that removes judgment calls from tired crews.

Why does real-time as-built capture improve efficiency and safety?

Capturing changes as they happen shortens almost every downstream task. Change orders move faster when photographs and dated notes already document the field condition. Billing disputes shrink because the record shows what was installed and when. Closeout stops being a scramble, since the package is largely assembled by the time the punch-list opens.

Safety gains are quieter but real. Accurate records of buried lines, utility offsets, and structural penetrations tell the next crew where not to dig, drill, or cut. A maintenance technician who knows a conduit runs somewhere other than where the contract drawings show it can avoid a strike. Operators also gain: facility teams plan shutdowns, replacements, and renovations from the record set, so wrong records create wrong plans.

There is a cost-control angle too. Rework to verify hidden conditions, such as potholing to find an undocumented line or opening finished walls to trace a run, is expensive and disruptive. Contemporaneous records are cheaper than forensic ones. Related field records matter here as well: labor and materials captured daily support clean time and materials billing when changed work needs to be paid for.

How do as-builts support regulatory compliance and inspections?

Inspectors and utility owners rely on record documentation to confirm that installed work matches approved designs or that deviations were reviewed. For utilities, the municipal standards cited above show the practical reality: agencies specify marking conventions, accepted formats, and tolerances, and may withhold acceptance of new infrastructure until compliant records arrive. In construction, record sets feed certificates of completion, warranty claims, and later permit applications for alterations.

Provenance matters in regulated work. A record showing who documented a change, when, and under what authority holds up better in an audit than an undated marked-up print. Cross-references to change orders and RFIs show a deviation was approved, not improvised.

Requirements differ by jurisdiction, agency, and contract, so confirm what your authority having jurisdiction and owner demand before assuming a format or seal is acceptable. Where licensed verification is required, involve the engineer or surveyor of record early, since sealing happens only after verification. Treat compliance as an input to your capture process: if the inspector will ask for it, record it in the field.

Our view: capture beats reconstruction

Most as-built problems are timing problems. Teams that treat record documents as closeout paperwork end up guessing about work that is already buried, while teams that mark changes at installation rarely argue about it later. In our view, the payoff shows up in faster change-order approvals, better maintenance planning, and fewer disputes over what was actually built. Build capture into field operations, not into the last month of the schedule.

— Client

How can a field operations platform produce audit-ready closeout packages?

If your crews already log work, photos, and changes daily, closeout should mostly be assembly. Hawkeye Field Ops helps connect field activity with office review, supporting clearer records for closeout. Reviewers can use the field records to support their closeout review.

See how this works for construction teams, then book a demo of Hawkeye Field Ops and ask us to walk through a closeout workflow built around your specifications.

FAQ

What is the correct term, as-built or as build?

“As-built” is the standard term, hyphenated, as in as-built drawings or as-built documentation. “As build” is a common misspelling. Many contracts prefer “record drawings” instead, because it avoids implying field-measured precision.

Are as-built drawings legally required?

It depends on the contract, owner standards, and the authority having jurisdiction. Many project specifications, such as SECTION 01 78 39, require record documents as a closeout deliverable. Confirm the exact requirement with your contract and local authority.

What does an as-built drawing look like?

It is usually the contract drawing set with field changes marked in red pencil or digitally, annotated with dimensions, product changes, and change-order references. Digital versions may be vector PDFs, CAD files, or models.

Who prepares record drawings?

Contractors generally prepare as-builts, while the architect or engineer prepares record drawings when the contract assigns it. As the OAA practice tip notes, format and accuracy expectations belong in the contract and that added work may warrant a fee adjustment.

Sources

See your operations in action.

Walk through the handoffs that slow your team down—and see where a connected record can help.