Punch list, closeout, and turnover field guide for data centers

The punch list and what closeout actually is

A punch list is the list of incomplete or deficient items found near the end of a project that have to be fixed before the work is finally accepted. A door that binds, a missing cover plate, paint holidays, a label that does not match the drawing, a duct hanger short of the detail. None of it stops the building from working. All of it stops the building from being done.

Closeout is the larger thing the punch list lives inside. It is the whole handoff: the punch corrected and verified, the as-built drawings turned over, the operation and maintenance manuals delivered, the warranties documented with their start dates, the training given, the spare parts handed over, and the commissioning record closed. The punch is the part everyone can see. The documentation is the part that decides whether the owner can actually run what you built.

Two things drag a job at the end, and they are not the work itself. The first is a punch list that nobody is managing, so items get found, lost, half-fixed, and re-found until the same walk happens four times. The second is a closeout package that gets assembled from memory in the last two weeks because nobody captured the record as the work happened. Both cost the same thing in the end, which is your retention sitting in someone else's account while the job is functionally complete.

Substantial completion vs final completion

Substantial completion is the milestone where the work is complete enough that the owner can occupy and use it for its intended purpose, even though punch items remain. It is not done. It is usable. On a data center that means the critical environment can take load and be operated, with a list of incomplete or deficient items attached that the contractor still owes. Final completion is the later milestone where every punch item is corrected, every closeout document is in, and the last payment with the remaining retention is released.

The date matters because a stack of clocks start on it. Beneficial occupancy and the responsibility for the space shift toward the owner. The warranty period typically starts here, not at final. And retention is commonly reduced at substantial completion, often from something like ten percent down to five, because the risk has dropped now that the building works. The certificate is the instrument that records the date, frequently on a form such as AIA G704, with the punch list attached as the list of items still to be completed or corrected. The exact form, the retention numbers, and what substantial completion legally requires are set by the contract and, for retention, by state statute, so read the agreement rather than assuming the round numbers.

Where this goes wrong is treating substantial completion as the finish line. It is the line where the owner starts using the building and the punch list becomes the thing standing between you and final payment. The work that felt ninety-five percent done at substantial completion is exactly the five percent that takes the last three months, because it is scattered, unglamorous, and split across every trade. Manage that five percent like it is the job, because for the purposes of getting paid, it is.

The punch walk: who walks it and when

The punch walk is the systematic inspection, near substantial completion, where the team goes through the building area by area and writes down everything that is incomplete or deficient. Who walks depends on the contract, but the typical room holds the owner or the owner's representative, the architect or engineer of record, the commissioning agent on a job that has one, the general contractor, and the trade whose work is being looked at. The architect's punch, the owner's punch, and the contractor's own pre-punch are often separate passes, and the smart contractor runs its own first so the official walk finds less.

Walk it the way the building is organized, not at random. Room by room, level by level, system by system. Every item gets tied to a location the moment it is written, because an item without a location is an item the trade cannot find tomorrow. On a data hall the location is a grid coordinate the same way the raised floor acceptance packet keys every defect to a tile like AA-07, so the punch, the photo, and the fix all point at the same physical spot. A vague entry like punch paint in the electrical room generates a phone call. An entry that reads scuff at column line AA-07, north face, does not.

Time the walk to substantial completion, not before the work is ready to be judged. Walking too early generates a list full of work that was always going to be finished, which buries the real deficiencies in noise and burns goodwill. Walking too late means the owner is already occupying around open items and the pressure to get them fixed has quietly moved to the contractor's side.

How does a punch item move from found to closed?

A punch item moves through a fixed lifecycle, and skipping any step is where closeout leaks time. Identify it and write it down with enough detail and a photo that someone who was not on the walk understands it. Assign it to the trade that owns the fix. Fix it. Verify it, meaning someone independent back-checks the corrected condition on the actual location. Then close it, with the evidence attached. Identify, assign, fix, verify, close.

The verify step is the one that gets skipped, and an item closed without verification is the failure that defines a bad closeout. A contractor reports the door fixed, the list gets a checkmark, and nobody walks back to the door. Three weeks later the owner finds it still binding, the trust in the whole list is gone, and now every closed item is suspect and the walk happens again. This is the same discipline the commissioning deficiency log runs on, where a deficiency closed on paper without a re-test is still in the building. The punch item closed without a back-check is the same animal in a cheaper suit.

Back-check by location and by category. Walk the corrected items in a route, not by chasing emails, and confirm the fix at the coordinate it was written against. The status the record carries should be honest: open, corrected and pending verification, or verified and closed. Corrected is the trade's word. Closed is the QA manager's word, and the two are not the same until someone has looked.

What is the difference between a punch item and a commissioning deficiency?

A punch item is a cosmetic or incomplete condition. A commissioning deficiency is a function that does not work. Both get tracked, but they have different owners, different urgency, and different proof of closure, and confusing the two is how a real performance problem gets buried under touch-up paint.

The punch item is the scuffed wall, the missing label, the door that binds, the sealant that was never struck. It is about whether the work is finished and clean to the contract. The commissioning deficiency is the generator that does not accept block load in the time the sequence allows, the transfer that drops the critical bus, the CRAC unit that will not hold setpoint. That lives on the commissioning deficiency log, gets classified by severity, and closes only on a re-test under the conditions that found it. The full process for that side is the subject of the data center commissioning operations overview, and the line between the two matters because they answer different questions. The punch asks whether it is done. Commissioning asks whether it works.

Keep them on separate tracks even when the same person is walking both. A severity-one commissioning deficiency gates turnover and can keep the building from taking load. A punch item rarely does. If you fold them into one undifferentiated list, the urgent functional failure sorts next to the missing escutcheon, and the thing that can hurt someone competes for attention with the thing that is merely ugly. Different owners, different clocks, different definitions of closed.

Tying the item to a photo and a location

The proof that a punch item was actually corrected is a photo of the deficiency, a photo of the fix, the location, and the date, all attached to the same record. A status that says closed with nothing behind it is a claim. The before-and-after pair at a known coordinate is evidence, and evidence is what survives the owner pulling the file a year later.

Capture the defect photo when the item is written, on the walk, while you are standing at the spot. Capture the fix photo when the back-check confirms it, from a close enough angle that the same condition is recognizable. The two images at one location, dated, answer the only question that matters later: was this item really fixed, or just marked. On a job with thousands of small items, that chain is the difference between a closeout you can defend and a spreadsheet of optimistic checkmarks.

This is exactly the kind of record the tradeos workflow is built to hold, where the punch item, the before photo, the after photo, the responsible trade, and the signoff all stay attached to the same location instead of scattering across a camera roll, an email thread, and a spreadsheet that lives on one person's laptop. The location ties it to the floor. The photos prove the fix. The signoff closes it. When all three live on one record, the back-check is a walk, not an archaeology project.

How does the punch list affect retainage?

Retainage, also called retention, is the percentage of each payment the owner withholds until the work is complete, commonly around ten percent, held specifically as the financial pressure that makes sure the job actually gets finished. The punch list is the work that stands between substantial completion and the release of that money. An unmanaged punch list is your own retention sitting in someone else's account, earning them interest, while the building is functionally done.

The mechanics usually run in two steps. At substantial completion the retention is often reduced, frequently from ten percent to five, because the risk drops once the building is usable. The remaining retention releases at final completion, when the punch is closed and the closeout documents are in. So every open punch item and every missing O&M manual is, in dollar terms, a hold on the back half of your retention. The exact percentages, the reduction at substantial completion, and the timing are set by the contract and by state retainage statutes, which vary, so the agreement and the law control, not the rule of thumb.

The incentive is to close fast and prove it. The contractor that runs a clean, located, photo-backed punch and turns over a complete package gets final payment released because there is nothing left to argue about. The contractor that emails a stale spreadsheet around and reports items closed without proof gives the owner every reason to keep holding the money, because the owner cannot tell what is actually done. Retention is not released on trust. It is released on a record.

The closeout document package

The closeout document package is the set of records the owner needs to operate, maintain, and warrant the building, and it is what final completion and the last retention release hang on. It is not one document. It is a bound and indexed set that, assembled well, is the building's permanent reference. The contract spells out exactly what it contains, typically in the Division 01 closeout sections of the specification, and that spec governs, so build the package to it rather than to a generic template.

The contents are consistent across most commercial and data center jobs even when the numbering is not. The list below is the common spine. Each item has its own section in this guide where it earns more detail, because as-builts, warranties, and the commissioning record each fail in their own specific way when they are rushed.

Above the individual documents sits the systems manual, the operations-facing rollup that pulls the as-builts, the final sequences, the as-left settings, the O&M information, and the training records into one reference the facility team runs the building from. A box of binders is not a systems manual. The organized, indexed, operable set is.

As-builts and record drawings

As-built drawings, also called record drawings, are the set marked up to show what was actually installed, including every field change from the design documents. The conduit that got rerouted around a beam, the valve that moved, the panel that landed three feet from where it was drawn. They are the drawings the facility team will trust the night something fails, and a wrong as-built is worse than no as-built, because it sends a technician to the wrong place with confidence.

The single most important thing about as-builts is when they get marked, and the answer is as the work happens, not at the end. The trade keeps a field set and redlines it as conditions change, ideally reviewed at each pay application so the markup keeps pace with the money. An as-built drawn from memory at closeout is a guess wearing the authority of a drawing. Nobody remembers in month ten where the underground actually ran in month two, and the change that did not get marked is the one that bites at 2 a.m.

Make the redline a condition of payment and it stays current. Wait until closeout and you get a frantic reconstruction by people who have already rolled to the next job, missing exactly the buried and concealed conditions that as-builts exist to capture. On a data center, the as-built of the power chain, the cooling distribution, and the cabling is what the operations team plans every future change against. Get it wrong and every move, add, and change for the life of the building starts from a lie.

O&M manuals and operator training

The operation and maintenance manuals are the documents the owner needs to actually run and maintain the equipment, and they are only useful if they are organized by system and reflect what was installed. Each system, HVAC, electrical, plumbing, fire protection, gets its manufacturer data, the model and serial numbers of the units that are physically in the building, the maintenance procedures and intervals, the parts lists, and the warranty information. A binder of generic catalog cuts for equipment that was value-engineered out is not an O&M manual. It is paper.

Training is the half of this that gets rushed and the half the operators remember. The manuals tell them what the equipment is. The training tells them how this building runs, the sequences, the failure responses, the quirks the commissioning agent found. A building handed to a team that was never trained on its own sequences runs on guesswork until something breaks, and the first real failure event is a bad time to learn how the transfer scheme behaves.

Record the training and, where you can, record it on video. The operator who is hired eighteen months from now was not in the room for the startup walkthrough, and a recorded session is the difference between institutional knowledge that walks out the door and knowledge that stays with the building. The training record also belongs in the closeout package as proof the sessions happened, because a contract that requires training and a job that skipped it is a final-payment problem waiting to surface.

Warranties and when the clock starts

The warranty is the contractor's and the manufacturers' commitment to correct defects for a defined period, and the detail that gets missed is when the clock starts. The contractor's general warranty, commonly a year of workmanship coverage, typically runs from substantial completion or beneficial occupancy, not from final completion. So the date on the certificate of substantial completion is the date that sets the warranty calendar, and the owner who does not pin that date down loses coverage at the back end without noticing.

Equipment warranties are their own layer and they do not all start on the same day. A chiller, a UPS, a generator, each carries a manufacturer warranty with its own term and its own start condition, sometimes the date of startup, sometimes the date of substantial completion, sometimes the date the unit was energized. The closeout package has to capture each warranty, its term, its start date, and the contact and process for a call-back, because a warranty nobody can find or date is a warranty the owner cannot use.

The call-back is the part that lives past turnover. A defect that shows up in month eight is a warranty event, and the owner needs the document, the date, and the path to make the claim. Tie each warranty to the system and the equipment it covers in the record, so the operator who finds the failing unit can go straight from the asset to its coverage instead of digging through a box to learn whether they are still inside the period.

Attic stock and spare parts

Attic stock is the specified inventory of spare materials the contractor hands the owner at closeout so the building can be maintained without chasing matching parts later. The extra floor tiles for the data hall, the spare lamps and filters, the touch-up paint mixed to the actual batch, the spare keys, sometimes spare panels and breakers. The specification calls out what and how much, often a percentage of installed quantity or a fixed count, and that spec governs the obligation.

The reason it matters is matching. The tile that matches the floor, the paint that matches the wall, the lamp that matches the fixture color temperature, all of it is easy to get on the day you are buying truckloads and nearly impossible to match two years later when one is damaged. Attic stock is the owner's insurance against a maintenance repair that stands out because nobody could find the matching part.

Hand it over as a documented transfer, not a pile left in a storage room. The closeout record should list what spares were specified, what was delivered, and where they were stored, with the owner's acknowledgment. A pallet of tiles dropped in a back room with no record is attic stock that gets thrown out by the next cleanup crew, and then the obligation that was satisfied on paper is gone in fact.

Commissioning and the turnover

On any building with a commissioning program, the commissioning record set feeds directly into closeout, and on a data center it is the heart of the turnover. The commissioning portion is the plan, the test reports at every level, the signed functional scripts, the integrated systems test results, and the deficiency log closed out with evidence. The level-5 integrated systems test signoff is the proof the plant rode through a simulated failure at load, and it is what tells the owner the redundancy they paid for is real, not just drawn on the one-line.

The acceptance work upstream feeds it too. The gear that was checked at receiving, the switchgear inspected and accepted on delivery against the approved submittal, is the first link in the chain that ends at the integrated test, and that receiving record belongs in the turnover so the owner can trace any unit back to the condition it arrived in. The receiving and acceptance discipline for major equipment, and the raised floor acceptance packet that proves the floor is fit to take load, both land in the same closeout set and both are covered in their own guides. The full program view, the levels, the witnessing, and the systems manual, is the subject of the data center commissioning operations overview.

The line to hold is that a commissioning deficiency closed on paper does not become a closed punch item by being moved to a different list. The commissioning record and the punch list are both part of turnover, but the severity-one functional deficiencies have to be genuinely re-tested and closed before the building is accepted, regardless of what the cosmetic punch count looks like. The integrated test signoff is the gate. The punch list is the cleanup behind it.

Owner acceptance and the certificate of occupancy

Two acceptances close a building, and they are not the same. The authority having jurisdiction, the AHJ, signs off the final inspections and issues the certificate of occupancy, the CO, which is the legal permission to occupy the space. The owner signs off acceptance of the work against the contract, which is the commercial event that drives substantial and final completion and the release of retention. You need both, and one does not substitute for the other.

The CO depends on the AHJ's final inspections passing, which on a complex building means the building, electrical, mechanical, fire, and life-safety inspections are all cleared. Fire and life-safety is often the long pole, because the fire alarm acceptance test, the sprinkler sign-off, and the egress and emergency power checks all have to land before the AHJ will issue. A data center frequently runs on a temporary certificate of occupancy while final items close, so confirm what kind of CO is actually in hand, because a temporary CO with conditions is not a final one.

The owner's acceptance is the signature that the work meets the contract, taken against the closeout record rather than a walkthrough. Hold the owner sign-off until the punch is closed or the remaining items are documented exceptions the owner has knowingly accepted in writing. A signature given on a verbal promise that the last items will get done is a signature that releases your hold and the owner's, and the items it was supposed to cover tend to evaporate the day the pen leaves the paper.

What is different about data center turnover?

Data center turnover carries everything a commercial closeout does and then adds the pieces that come from running a critical environment, where the cost of an undocumented gap is measured in downtime, not callbacks. The integrated systems test signoff is the centerpiece, because the owner is accepting a plant that has to survive a utility failure without dropping load, and the IST result is the only document that proves it did.

The as-built record runs deeper than on an ordinary building. The owner needs an accurate as-built of the power chain from the utility to the rack, the cooling distribution from the plant to the aisle, and the structured cabling, because every future move, add, and change is planned against it. Labeling and identification are part of the deliverable, not an afterthought, and on a modern job that means the cross-connect labeling and the QR or barcode asset tags are verified and tied to the record so a technician can scan a unit and pull its documentation. That labeling discipline is what keeps the cabling and the asset record honest for the life of the building.

Then there is the day-one operations handoff. The facility team takes a live, loaded critical environment, so the handoff is not a binder drop, it is a transfer of an operating building with its maintenance already underway. The systems manual, the as-lefts, the training, and the open warranty calendar all have to be in the operators' hands before the first maintenance window, because in a data center the operator inherits the consequences of every closeout shortcut the moment they take the keys.

How do you keep a punch list from dragging on?

You keep a punch list from dragging by making it live, located, assigned, dated, and visible to everyone, so the same item is never found twice and no item closes without proof. The drag comes from the opposite of each of those: a static list, items with no location, no clear owner, no due date, and a status nobody can see. Fix the structure and the list closes itself.

The stale spreadsheet emailed around is the classic failure. Someone owns the master copy, edits it on their laptop, and sends a version out. By the time a trade reads it, it is a day old, three other people have marked items on their own copies, and the photos live on four different phones. Now the walk happens again to reconcile the versions, which is the rework with no defect that eats the last month of a job. The list is not wrong because the work is hard. It is wrong because the record is fractured.

The live version is one record everyone sees: each item at its location, assigned to the responsible trade with a due date, the before photo attached, and the status visible on a dashboard so the QA manager can see at a glance what is open, what is corrected and pending verification, and what is closed with proof. This is the workflow the tradeos approach is built for, the punch list and the photos and the signoff on one shared record instead of a spreadsheet aging in an inbox. The trade sees its own open items by location. The owner sees the count fall. Nobody re-walks a building to find out what is actually done.

The handoff to facilities and operations

The last move in closeout is the handoff to the people who will run the building for the next twenty years, and what they inherit is not a finished punch list, it is a running record. The closeout package is a snapshot of the building at acceptance. The facility team needs that snapshot to become the first page of an operating history, the baseline they maintain against, re-test against, and plan changes from.

The strong handoffs treat the turnover record as the building's permanent memory rather than a closeout deliverable that gets archived and forgotten. The as-built, the asset tags, the warranty calendar, the commissioning baseline, and the maintenance intervals from the systems manual become the live reference the operations team works from on day one. The property keeps its own record, and every future condition, repair, and change writes back to it, so the building two years out still has a documented account of what it is and what has been done to it.

This is where the field record earns its keep past the end of the job. When the punch, the photos, the as-built conditions, and the signoffs were captured against the building as the work happened, the owner inherits a baseline that is complete because it was recorded, not because someone reconstructed it in a heroic final month. A building handed over with a real, located, photo-backed record is a building the facility team can actually run. A building handed over with a box of binders and a shrug is one they spend the first year reverse-engineering.

What to document

A punch and closeout record is judged by whether someone who was never on the job can tell, item by item, what was wrong, where, who fixed it, and how you know. Capture each item against its location with the proof of correction, and capture the closeout package as the work happens rather than at the end. The table is the spine of a punch record that closes the job and releases the money.

Common mistakes

• Writing punch items with no location, so the trade cannot find them and the back-check becomes a hunt.
• Closing items on the trade's self-report without an independent back-check at the location.
• Marking as-builts from memory at closeout instead of redlining the field set as the work happens.
• Turning over a closeout package missing the O&M manuals, the warranties, or the warranty start dates.
• Leaving retention on the table by reporting items closed without the photo proof that releases the money.
• Confusing a commissioning deficiency, a function that does not work, with a punch item, a cosmetic or incomplete condition, so the urgent failure sorts next to the missing cover plate.
• Treating substantial completion as the finish line instead of the start of the punch and documentation push.
• Running the official punch walk before the work is ready, so real deficiencies drown in items that were always going to be finished.
• Managing the list as a stale spreadsheet emailed around, so versions fork and the building gets re-walked to reconcile them.
• Dropping attic stock in a back room with no documented transfer, so the spares are gone by the next cleanup.

Field checklist

Standards and references

Closeout is governed first by the contract. The Division 01 closeout sections of the project specification, the general requirements division, define what the closeout package contains, the punch and back-check process, the as-built and O&M requirements, and the attic stock obligation. That specification controls the actual scope, so read it at buyout rather than assuming the contents, and the exact section numbers follow the CSI MasterFormat the project adopted.

The commercial milestones are commonly documented on standard contract forms. The certificate of substantial completion is frequently the AIA G704 form, with the punch list attached as the list of items still to be completed or corrected, and final payment commonly runs through the contractor's affidavit and consent of surety forms in the same family. The forms a given project uses, the retention percentages, and the reduction at substantial completion are set by the agreement and, for retention timing, by state statute, which varies, so the contract and the applicable law control, not the rule of thumb.

The commissioning side feeds closeout through the commissioning plan and the framework in ASHRAE Guideline 0 and Standard 202, with the integrated systems test signoff and the closed deficiency log carried into the turnover record. The certificate of occupancy is issued by the AHJ against the adopted building code and the final inspections, so confirm the code edition, the inspection requirements, and whether the CO in hand is temporary or final with the AHJ. The discipline acceptance standards behind the test reports, NETA for the electrical scope, the fire alarm and sprinkler acceptance tests, and the TAB reports for the mechanical scope, are covered in their own guides; here they are line items in the closeout package.

Terms and definitions

Closeout carries its own vocabulary, and the same word can read differently across a contract, a specification, and a commissioning plan. The terms below are the ones that travel across the whole handoff.

Punch list

The list of incomplete or deficient items found near completion that must be corrected before final acceptance; also called a snag list

Substantial completion

The milestone where the work is usable for its intended purpose and the owner takes beneficial occupancy, with punch items still open

Final completion

The milestone where the punch is closed, all closeout documents are in, and final payment with remaining retention is released

Retainage / retention

The percentage of payment withheld until completion, commonly reduced at substantial completion and released at final; set by contract and statute

As-built / record drawings

The drawings marked to show what was actually installed, including every field change, redlined as the work happens

O&M manual

Operation and maintenance documentation organized by system, with the installed equipment's model, serial, parts, and maintenance data

Attic stock

The specified spare materials handed to the owner at closeout: tiles, lamps, filters, paint, keys, and the like

Closeout

The whole handoff: punch correction, documentation, training, warranties, spares, and the commissioning record turned over to the owner

Systems manual

The operations-facing rollup tying the as-builts, sequences, as-left settings, O&M, and training into one operable reference

Certificate of occupancy (CO)

The AHJ's legal permission to occupy the space, issued against passed final inspections; may be temporary with conditions

Related tools

Calculators and readiness checks for this work

Compare your options

FAQ

People also ask

• What is commissioning in construction?
• What load rating does a data center raised floor need?
• What is construction closeout?
• What is an as-built drawing?
• What is the difference between cold and hot commissioning of a BESS?