As-built and record drawings field guide for data centers

As-built drawings, and why the field is the only place they get made

An as-built drawing is the construction set marked to show what was actually installed, against what was originally drawn. The pipe that moved to clear a beam, the panel that landed three feet off its dimension, the conduit that took a different route because the wall was not where the plan said. The drawing the field works from is a prediction. The as-built is the correction.

The single fact that decides whether an as-built is worth anything is when the change gets marked, and the answer is the day it happens, at the spot it happens. Not at closeout. Nobody on earth remembers in month fourteen where the underground actually ran in month two, which valve got swapped at rough-in, or why the feeder left the plan and went around the structure. The change that did not get marked the day it happened is gone, and the as-built built from memory at the end is a guess wearing the authority of a drawing.

That is the whole discipline in one line. Mark it now or lose it. Everything else here is about making the present moment easy enough to capture that the mark actually gets made on a job with three hundred changes and a crew that has already rolled to the next building.

As-built vs record drawing vs marked-up set vs the model

These four terms get used as if they mean the same thing, and they do not, and the difference is about who owns the document and who carries the liability for it. The as-built drawing is the contractor's product. The trade marks up its own field set to show what it installed, in red, as the work goes in. Those red-lines are the raw record of field conditions, and the architect is generally not responsible for their accuracy, because the contractor made them.

The record drawing is the designer's product, made from the contractor's as-builts. The architect or engineer takes the red-lined set, screens it, incorporates the documented changes, and reissues a clean, official set as the record of the project. The record set carries the design professional's review. The as-built carries the contractor's word. That is why a contract that asks for record drawings is asking for more than a pile of red-lines, and why the handoff between the two is a real step, not a relabeling.

The marked-up set is the working term for any field set in progress, the live red-line before it becomes the formal as-built. The model-based as-built is the same idea in BIM: the design model updated to reflect installed conditions, sometimes carried to a digital twin the operations team runs the building from. Same goal across all four. What is actually there, recorded accurately enough to trust at two in the morning when something has failed.

The red-line discipline: marking the change as it happens

Red-lining is marking the field change directly on the drawing, in red, as the condition changes, so the set on the job always shows the current truth. The color convention is old and useful. Red for what was added or changed, often a cloud around the area and a note with the date and the reason. Some crews strike out removed work in a second color. The exact convention matters less than that it stays consistent across the set and that one person owns the master.

Ownership is where it breaks. Each trade keeps its own as-built set for its own scope, and somebody, usually the general contractor or the project's VDC lead, owns the coordinated master. When two people both think they own it, neither does, and the changes land on two different sets that never get reconciled. Name the owner at buyout, in writing.

Here is the part rookies get wrong and PMs let slide. The as-built set lives on the job, in the field, where the change happens. It does not live in a drawer in the trailer that gets opened at closeout. A set that is not in front of the work when the work changes is a set that will not capture the change. The foreman who marks the relocation while standing at the relocation is the only one who gets it right. Make the field set the working set, not an archive.

What gets red-lined

Anything installed differently from the way it was drawn gets marked, and on a real job that is a long list. Dimensional changes, where something landed off its plan location. Relocations, where a device, a panel, a valve, or a piece of equipment moved. Routing, which is the big one, the conduit, pipe, duct, and cable as they were actually run rather than the single line the designer drew. Buried and concealed work, the category that can only ever be captured before it is covered. Substitutions, where an approved equal went in instead of the specified product. And every documented change: the RFI resolution, the architect's supplemental instruction, the change order, and the addendum issued during bidding that the field set may not yet show.

The thread through all of it is field conditions that differed from the drawing. A drawing is an intent. The building is a negotiation between that intent and the steel, the existing conditions, the other trades, and what the supply house actually had on the shelf. Every place that negotiation moved the work off the drawing is a red-line.

Miss them and the as-built lies in exactly the spots where the building is least like the plan, which is exactly where someone will need the truth later. The clean runs that went in per drawing do not need the as-built. The changes do.

The underground and concealed as-built: the one you cannot redo

The as-built of buried and concealed work is the one that actually matters, because it is the only record that will ever exist. Once the trench is backfilled, the slab is poured, or the wall is closed, what is in there is invisible. You cannot re-survey a duct bank under four feet of compacted fill. The window to record it is open for a few hours and then it is shut for the life of the building.

This is where the as-built and the photo become one record. Before the cover-up, you shoot the work: the location, the depth, and the routing, dimensioned off something permanent that will still be there later, like a column line or a building corner, not off a stake that gets pulled. A measurement tied to a temporary reference is worthless once the reference is gone. The before-cover-up photo, dated and located, is the backup to the dimension, and it is the same before-and-after photo discipline the punch and closeout process runs on.

Be blunt about the stakes. The underground that did not get recorded is the underground somebody hits with an excavator or a core bit two years from now. Depth and location are not nice-to-haves on concealed work. They are the difference between a planned tie-in and a cut line, a flooded trench, or a backhoe through a live duct bank. Record it before it disappears, because there is no second chance to look.

RFIs, ASIs, change orders, and addenda

Every documented change to the design has to find its way onto the as-built, and the value is in the traceability, not just the mark. When a routing moved because of an RFI response, the red-line should point back to the RFI number. When the architect issued a supplemental instruction, an ASI, that relocated a device, the as-built carries the change and the reference. The change order that added scope, the addendum that revised a detail during bidding, the construction change directive that moved the work before the price was settled, each one is a paper trail that should connect to the physical red-line.

The reason to keep the trace is that a red-line without a source is a change nobody can defend. Six months out somebody asks why the feeder is where it is. A note that reads moved per RFI 142 to clear the new equipment pad is an answer. A shrug is not. The reference turns the as-built from a drawing into a record that holds up under a question.

The common gap is the change that got built but never tracked, and the change that got tracked but never red-lined. Both leave the as-built wrong. The RFI and change log and the as-built set have to agree at the end, the same way the cross-connect record has to agree with the patch field. A documented change that is not on the drawing is a future surprise with a paper trail nobody connected.

The MEP and coordination as-built for the next trade and for operations

The MEP as-built is the actually-installed routing of the mechanical, electrical, and plumbing systems, and it serves two audiences the design drawings never fully did: the next trade in the same space, and the operations team for the life of the building. During construction, the trade that follows needs to know where the duct really ran before they hang their pipe in the same plenum. After turnover, the facility team plans every future change against the real routing.

In a data center the MEP as-built runs deeper than on an ordinary building, because the systems are the product. The power chain from the utility through the switchgear, the UPS, the PDUs, and out to the rack. The cooling distribution from the plant to the aisle. The structured cabling and the cross-connects, which carry their own record discipline in the meet-me room and the patch field. Every future move, add, and change in that building is planned against the as-built of those systems, so an error in it propagates into every change for twenty years.

The coordination model is usually where this lives now. The trades coordinated the routing in a clash-detection model before installation, and the as-built is that coordinated model corrected to what actually got hung, including the field fixes the coordination did not predict. The model said it would fit. The field is where you found out whether it did, and the as-built is where you write down the difference.

Survey, laser scan, and the dimensional as-built

When the as-built has to be dimensionally accurate, you stop sketching and start measuring, and the tools are the surveyor's. A total station shoots precise coordinates for the locations that matter, the underground utilities before backfill, the anchor bolts before steel. For a whole space, a laser scanner captures a point cloud, millions of measured points that record the as-installed geometry of the room, the racks, the overhead, and the routing all at once.

The point cloud is not the as-built by itself. It is the raw measurement. Turning it into a usable record is scan-to-BIM, where the scan is registered and the model is built or corrected to match the measured points. For a data center, a scan-to-BIM as-built of the white space and the support areas gives the operations team a dimensionally real model to plan deployments and changes against, instead of a drawing that was accurate the day it was issued and has been drifting since.

Scan when the accuracy is worth the cost, which is not everywhere. The underground before it is buried, the congested overhead where the next change will be tight, the equipment locations future work keys off. Routine partition walls do not need a point cloud. The skill is knowing which conditions earn the scanner and which are fine with a tape and a red pen.

What does the contract require for as-builts?

The contract requires as-builts, and on almost every commercial and data center job it ties them to money. The requirement lives in Division 01, the general requirements, commonly in the project record documents section, frequently numbered around 01 78 39 in MasterFormat, though the project's own numbering governs. That section defines what the as-built has to be, the format it is delivered in, and when it is due.

The teeth are in the payment language. As-builts are typically a closeout submittal required before final payment is released, and many specs go further and let the owner withhold progress payments if the record set is not kept current. Some require the contractor to certify, with each monthly payment application, that the record drawings are complete and accurate as of that date. That is the mechanism that turns the as-built from a closeout afterthought into a monthly obligation, and it is the smartest thing a spec can do, because it forces the record to keep pace with the work instead of being reconstructed at the end.

Format is project-specific and worth pinning down at buyout. The deliverable might be marked paper, scanned PDF, native CAD to the owner's layer standard, or a BIM model to a stated level of development. The owner's own CAD or BIM standard usually controls layering, naming, and file structure, and the National CAD Standard is a common baseline for the CAD side. Read the actual section, because building the as-built to the wrong format is rework you do at the worst possible time, at closeout, with payment waiting on it.

Keeping the set current: the monthly update beats the closeout scramble

The as-built set is kept current by updating it on a cadence tied to the work, not by saving it all for the end. The cadence that holds up is monthly, tied to the pay application. Before the contractor bills for the month's work, the as-built reflects that month's changes. When payment depends on the record being current, the record stays current. That is not bureaucracy. That is the only thing that reliably works.

The reason the monthly update beats the closeout scramble is arithmetic. Twelve small, accurate updates by the people who did the work, while they still remember it, produce a real as-built. One giant reconstruction at the end, by whoever is left, produces a guess. The scramble is also the most expensive way to do it, because the crews who knew the answers have demobilized and you are paying someone to reverse-engineer a building from incomplete notes.

Audit the field set on a cadence too. Walk the field office, pull the as-built set, and check it against the work in place and the change log, the same way you would audit a punch list against the building. A set nobody has checked in three months has drifted, and the drift is invisible until somebody needs the one page that is wrong. The audit is cheap. The wrong as-built is not.

The handoff from red-lines to record drawings

At the end, the contractor's red-lined as-builts go to the design professional, who turns them into the record drawings. This is a real transfer with real review, not a relabeling. The architect or engineer takes the marked-up set, checks it for completeness and consistency, incorporates the changes into a clean set, and reissues it as the official record of the project. The record set is the version the owner archives, and it carries the designer's certification.

The certification depends on the red-lines being honest. The designer can only certify what the contractor gave them, and the standard caveat, that the record drawings are based on information furnished by the contractor, is there precisely because the architect did not watch every change go in. Garbage red-lines produce a record set that is clean, official, and wrong. The review catches inconsistencies. It does not catch a change that was never marked.

This is why the handoff is only as good as the year of field discipline behind it. A contractor that kept the set current monthly hands over a coordinated, complete red-line set, and the record drawings come out fast and accurate. A contractor that scrambled at the end hands over a partial set, the designer's review turns up gaps, and the back-and-forth to close them is the thing still open while retention sits unreleased. The record set is downstream of the red-line. You cannot fix upstream at the handoff.

Why the owner needs a true as-built, and what a wrong one costs

The owner's facility team runs the building off the as-built for its whole life, so the as-built is the building's permanent memory. When a technician needs to find a shutoff, trace a feeder, locate a buried line before a dig, or plan a tie-in for new equipment, the as-built is the first thing they pull. A complete, accurate as-built makes every future change start from the truth. A wrong one makes every future change start from a lie, and the lie does not announce itself.

The cost of a wrong as-built is the wrong dig and the wrong cut. A crew trusts the drawing, cores a slab where the as-built shows nothing, and hits a conduit, a chilled water line, or a post-tension cable the as-built never recorded. The drawing said it was clear. The drawing was wrong. This is exactly why nobody fully trusts an as-built before they open a slab, and why concrete scanning and ground-penetrating radar exist as a discipline. You scan because the as-built is never trusted on its own for concealed work. The scan and the as-built check each other.

Treat the as-built as the asset it is. It is not a closeout deliverable that gets archived and forgotten. It is the document the building is operated, maintained, and modified against until it is demolished, and the quality of every future decision about that building is bounded by the quality of the record you hand over.

BIM, LOD 500, and the digital twin

The model-based as-built is the design BIM updated to reflect what was installed, and at the top end it becomes the digital twin the operations team runs the building from. The level of development, the LOD, is how the industry describes how real the model is. LOD 500 is the field-verified, as-built level, where the model elements match the installed conditions and carry the actual equipment data rather than the design placeholders. The number is a common reference, but verify what your contract actually means by it, because LOD definitions vary in practice and the spec controls.

The value of the model over flat drawings is the data attached to the geometry. An as-built model can carry the make, model, serial number, and maintenance data for each piece of equipment, so the operations team can select a unit and pull its record instead of digging through binders. In a data center that ties directly into DCIM, the data center infrastructure management system, where the model of the power, cooling, and space feeds the live operational picture the facility runs the floor from.

Be honest about what a model-based as-built costs and demands. A digital twin that is not maintained after turnover is a snapshot that goes stale like any other drawing, only more expensively. The model is worth building to LOD 500 when the owner has the program to keep it alive. When they do not, an accurate flat as-built they will actually update beats a twin nobody maintains.

Capturing the field change where it happens

The reason as-builts fail is not that people do not know they matter. It is that capturing a change in the field, at the moment it happens, with everything you need, is harder than it should be. The foreman has the change in front of them. They also have a paper set in the trailer, a phone full of photos with no location, and a closeout deadline months away. So the mark does not get made, and the change joins the pile that gets reconstructed at the end.

The fix is to make the field capture as close to free as possible. The markup, the photo, and the location captured together, at the spot, attached to the area of the building they belong to, so the as-built is assembled from a real running record instead of memory. The before-cover-up photo of the underground, dated and tied to a column line. The red-line note with the RFI reference. The relocation marked against the grid. When all of that lands on one record keyed to the location, the as-built at the end is a rollup of what was captured, not a reconstruction of what was forgotten.

This is the workflow the tradeos approach is built around, the field markup and the photo and the location on one record that holds even when there is no signal in a concrete basement or a half-built data hall. Offline matters here, because the place the change happens is usually the place with the worst connectivity. The record that captures the change the day it happens is the record that becomes a real as-built. Everything else is a scramble with a deadline.

How as-builts fail

As-builts fail in a handful of predictable ways, and every one of them traces back to the record not being captured when and where the change happened. The biggest is the memory as-built, the whole set reconstructed at closeout from incomplete notes by people who were not there for half the changes. It looks like a drawing and it is a guess.

Close behind is the buried work that was never recorded before it was covered, which is unrecoverable, not just incomplete. There is the red-line set that was kept but then lost, left on one super's laptop or in a trailer that got demobilized, so the whole year of marks goes with it. There are the documented changes, the RFIs and change orders, that never made it onto the drawing, so the as-built and the change log disagree and nobody can tell which is right. And there is the wrong routing, the as-built that shows a line where there is none or omits one that is there, which is the failure that sends the next crew to the wrong dig.

The pattern is the same every time. The information existed at one moment, in the field, and nobody captured it then. There is no recovering it later at any price. That is why the whole discipline collapses to one rule, repeated because it is the only one that matters. Mark the change the day it happens, where it happens, or accept that the as-built will be wrong exactly where the building is least like the plan.

What to document

An as-built record is judged by whether someone who was never on the job can tell, change by change, what moved, where, why, and when it was captured. Tie each change to the sheet and the physical location, carry the reference back to the document that drove it, and capture it as the work happens rather than at the end. The table is the spine of a red-line that becomes a record drawing instead of a guess.

Common mistakes

• Reconstructing the as-built from memory at closeout instead of marking changes as they happen.
• Backfilling, pouring, or closing a wall before the underground or concealed work was recorded and photographed.
• Keeping the red-line set in a trailer drawer or on one laptop instead of on the working field set, so it drifts or gets lost.
• Marking a change on the drawing with no reference back to the RFI, ASI, or change order that drove it.
• Building the as-built to a generic format instead of the owner's CAD or BIM standard, so it gets rejected at closeout.
• Letting the RFI and change log disagree with the as-built set, so nobody can tell which one is right.
• Dimensioning concealed work off a stake or temporary reference that is gone once the work is covered.
• Treating substantial completion as the time to start the as-built instead of the time it should already be done.

Field checklist

Standards and references

As-builts are governed first by the contract, and specifically by Division 01, the general requirements. The project record documents section, commonly numbered around 01 78 39 in MasterFormat with the project's own numbering controlling, defines what the as-built has to contain, the format it is delivered in, and the closeout and payment conditions attached to it. That section is the governing document for the deliverable, so read it at buyout rather than assuming a generic scope.

On the design side, the AIA contract documents address the split between the contractor's as-builts and the architect's record drawings, including the standard position that the record drawings are based on information furnished by the contractor and that the architect is not responsible for the accuracy of the contractor's markups. The exact language depends on the agreement and the edition in force, so the contract controls, not the general principle. The owner's own CAD or BIM standard usually governs the electronic format, the layering, and the naming, with the National CAD Standard a common baseline for CAD deliverables and the level of development language describing how field-verified a BIM model has to be.

Where as-builts are required by the authority having jurisdiction, for permitted underground utilities or for fire and life-safety systems, the AHJ's record requirements apply on top of the contract. Confirm the adopted code edition, the local amendments, and the AHJ's own record-drawing requirements before treating any of it as settled. Across all of it, the contract documents and the owner's standard control the deliverable, and the specifics move between projects and editions, so verify them against the job in hand.

Terms and definitions

As-built work carries its own vocabulary, and the same term reads differently across a contract, a specification, and a BIM execution plan. The terms below travel across the whole record-drawing scope.

As-built drawing

The construction set marked by the contractor to show what was actually installed, including every field change from the design

Record drawing

The designer's official set, produced from the as-builts by screening and incorporating the changes; carries the design professional's review

Red-line

The mark made directly on the drawing, in red, to show a field change as it happens, with the date and reason

Marked-up set

Any field set in progress, the live working red-line before it becomes the formal as-built

RFI

Request for information, the formal question whose answer often moves the work; its number ties to the resulting red-line

ASI

Architect's supplemental instruction, a minor design change directing the work without a cost or time change

Change order (CO)

A documented change to scope, cost, or time that the as-built has to reflect and reference

Addendum

A revision issued during bidding before the contract; may differ from what an early field set shows

LOD

Level of development, how field-verified a BIM model is; LOD 500 is the as-built, installed-conditions level, with the spec's definition controlling

Point cloud

The set of measured points from a laser scan that records as-installed geometry; raw input to a scan-to-BIM as-built

Concealed work

Buried or hidden work that can only be recorded before cover-up, after which the as-built is the only record

Digital twin

The maintained as-built model the operations team runs the building from, often tied to DCIM in a data center

Related tools

Calculators and readiness checks for this work

Compare your options

FAQ

People also ask

• What is a punch list in construction?
• What is a meet-me room?
• Why do battery rooms need ventilation?
• What is the maximum cable tray fill?
• What is the difference between an F-rating and a T-rating?