What Are As-Built Drawings?

No building is constructed exactly as drawn, and this is not a failure of design. Existing conditions differ from what a survey showed. A field-verified dimension moves a wall. Coordination in the field resolves a conflict the documents left ambiguous. A substitution is approved. Each of these is a legitimate deviation, and each one makes the design set slightly less true.

The as-built set is how those deviations are captured while the knowledge still exists. The person who rerouted the duct knows exactly where it went for about a week. After that it is buried above a ceiling and the only record is whether someone marked it.

The contract requires a dedicated set kept on site and marked as work proceeds, with each subcontractor responsible for its own scope. In practice this is where the process most often breaks: the markups get deferred, and at closeout somebody reconstructs six months of changes from memory, RFI responses and change orders.

The result is a set that looks complete and is quietly unreliable. Teams that treat as-built markup as a monthly requirement tied to the pay application get usable documents; teams that treat it as a closeout deliverable get a document nobody trusts. Underground utilities are the clearest case for surveying deviations as they are installed rather than recording them afterwards.

The two terms are used interchangeably on site and mean different things in the contract. As-builts are the contractor’s marked-up set — a factual statement about what was installed, made by the party that installed it. Record drawings are what the architect or engineer produces by incorporating those markups into the drawing files.

The distinction is about responsibility. The design team incorporating markups is transcribing information it did not observe, which is why record drawings are typically issued with language stating they are based on information furnished by the contractor. Anyone relying on them for a renovation should read that disclaimer as the warning it is.

The phrase "as-built drawings" does not appear in the AIA general conditions. What A201-2017 requires, at §3.11, is that the contractor maintain a complete set of the contract documents annotated to show field changes and selections, together with the approved submittals, and turn that set over to the architect for the owner. That annotated set is what everyone on site calls the as-builts, and the obligation sits squarely with the contractor.

The architect's side is separate and is not automatic. B101-2017 lists as-constructed record drawings, which it notes are "commonly called as-builts," as a Supplemental Service rather than part of Basic Services, so somebody has to agree to it and pay for it. The same clause states that because the record drawings rely on the contractor's mark-ups, the architect is not responsible for their accuracy or completeness. There is also a distinct document: as-designed record drawings, meaning the construction documents plus every addendum, ASI, change order, construction change directive and minor change the design team issued. If an owner asks for "the as-builts" without saying which of these three they mean, the answer they get will depend on who is cheapest to ask. Specifications usually pin it down in MasterFormat section 017839, Project Record Documents, which is where record drawings, record specifications and record product data are actually scoped.

The method matters less than the cadence. A usable set comes from marking changes within days of the work happening, with each subcontractor responsible for its own scope and a single party responsible for consolidating. The practical mechanism is to make the markup a condition of the monthly pay application, so there is a reason to do it while the information is still in someone's head rather than in a buried ceiling.

What gets recorded is narrower than people assume. Dimensional changes to the installed work, routing changes for concealed services, actual invert elevations and locations for anything underground, substituted products with their approved submittal reference, and the authorising document for each change. What does not belong is design opinion or a reconstruction of intent. Underground utilities deserve a survey rather than a pencil line, because the cost of getting them wrong is excavation. At closeout the consolidator checks that every change order and approved substitution is reflected somewhere in the set, which is the step that usually exposes how much was deferred.

Teams searching for as-built software are usually trying to solve one of three different problems, and the tools that address them barely overlap. The first is capture in the field: marking a PDF or a model on a tablet so the change is recorded where it happened. The second is survey and reality capture: total stations, GPS and laser scanning for underground services and existing conditions, where a drawn line is not accurate enough to rely on. The third is reconciliation: working out what actually changed by reading back through RFI responses, change orders, approved substitutions and field reports.

The third is the one that eats closeout, and it is a document problem rather than a drafting one. It is also the step a renovation team repeats years later from the other direction, trying to work out whether the record set can be trusted before they price demolition. Buying a field markup app does nothing for either, which is why closeout keeps overrunning on projects that bought one.

Their value shows up years after the ribbon is cut. A renovation team that can trust the as-builts prices demolition and tie-ins from documents instead of exploratory openings. A facilities group locates a valve without opening four ceilings. An owner defending a claim has a contemporaneous record of what was installed and when.

Their absence is equally measurable, and it is why renovation projects carry contingencies that new construction does not. On a project where the as-builts are unreliable, the first change orders are almost always differing conditions that a good record set would have shown.