Punch List to Retainage: Closing the Last Items and Getting Paid

The system runs. The owner is using it. Five to ten percent of the contract value is sitting in retainage, and between you and that money is a list of small things: a missing nameplate, a loop that never got its final calibration sheet, an HMI screen with the wrong tag, a spare parts box that was never receipted. None of them is hard. All of them are on a spreadsheet three people have different versions of, and the version the owner has is a photo.

The punch list is the last controlled document on the job, and it deserves the same discipline as the first submittal. Here is how it works, from the general conditions down to the row.

What a punch item is

At substantial completion, the work is complete enough for the owner to use it for its intended purpose, and a list of items remains to be completed or corrected before final payment. That list is the punch list. In the standard general conditions the contractor prepares it and submits it with the request for substantial completion; the engineer or architect inspects, adds anything the contractor missed, and the resulting list rides on the certificate of substantial completion. Failing to list an item does not excuse it. One of the Division 01 closeout sections I hold adds a threshold: the work is not substantially complete unless the remaining punch items can be completed within thirty days.

Two things follow. Punch items do not prevent substantial completion; that is the whole point of the mechanism. And a punch item is a contractual obligation with a deadline, not a courtesy list. The certificate typically fixes the time for completing them.

Items arrive from several sources on a controls job, and knowing the source is half of resolving the item:

• The engineer's substantial completion inspection.
• The owner's operators, once they start using the system.
• Startup and demonstration testing, where the test report's exceptions become punch items.
• Returned submittal reviews, where a closeout submittal (O&M manual, record drawings) comes back with comments that must be closed before final.
• Your own QC walk, which should have found most of the above first.

Who owns each item

Every item has exactly one responsible party, and writing it down is the step most lists skip. On an integration job the candidates are the integrator, the panel shop, the electrical subcontractor, the equipment vendor, the general contractor, and the owner. A punch item that says "instrument reads wrong" with no owner is an item three parties will each assume belongs to someone else.

Assign each item on the day it is logged, with a due date and a severity. The industry's own best-practice standard for integrators describes acceptance as conditional on a punch list of non-critical items with severity and responsibility recorded, later retested and signed off. Severity matters because it sorts what blocks substantial completion from what blocks final: a safety interlock that fails is not a punch item, it is incomplete work; a wrong nameplate is a punch item.

Each item also carries its round. When the owner raises an item, you correct it, and they raise it again, that is the same item on its second round, not a new number. The history of rounds is what tells you at final inspection which items have been contentious and which are genuinely done.

Accepted as-is versus closed

An item closes one of two ways, and the record should say which.

Closed means the responsible party corrected it and the person who raised it verified the correction. Both halves. The contractor's own note that a thing was fixed is a claim, not a closure; the closeout sections I hold all describe the same loop, in which the contractor corrects the items and gives written notice, the engineer re-inspects, and only then is the item struck. Some owners charge for repeat inspections, deducting the cost by change order when incomplete punch items or premature notices cause extra visits. Two clean notices are cheaper than four sloppy ones.

Accepted as-is means the owner has decided to keep nonconforming work instead of requiring correction, and the contract sum is reduced as appropriate. The general conditions allow this explicitly, and it is the right answer for the item that would cost more to correct than it is worth to anyone: the enclosure scratch, the conduit that entered from the wrong side but works. It is a negotiated outcome, in writing, with a credit if one is due. An item that just stops being mentioned is not accepted as-is; it is an open item that will reappear when the retainage request lands on someone's desk.

The For Record snapshot at each milestone

The punch list changes daily. The certificate of substantial completion needs a version that does not. So does the demonstration test acceptance, and so does the final inspection. The practice that keeps the list honest is a frozen copy at each milestone: every item, its status, its owner, and the counts, exactly as they stood on that date, attached to the record of the milestone.

This is the same idea the industry applies to any controlled document, and the name for the terminal version is For Record. A list issued For Record at substantial completion is the list the certificate refers to. Items raised after it are new items, dated after the milestone, and their existence does not reopen the certificate. At final inspection the closed For Record list, showing every item with the evidence that it was completed, is one of the record documents; one university's closeout section names "completed punch lists" among them alongside the as-builts and the O&M manuals.

Without the snapshot, the argument at final is always the same: the owner says twelve items are still open, you say those twelve were raised after substantial completion and three of them were accepted as-is, and nobody can prove either. With it, the argument is a comparison of two dated lists.

Substantial completion to final payment

What substantial completion triggers, in the standard general conditions:

• The warranty clock starts. Warranties commence on the date of substantial completion, and the one-year correction period runs from it. On a long job this is worth a year of coverage compared with warranty-from-shipment, and it is the reason to push for the certificate rather than let the job drift to final.
• Responsibility shifts. Security, maintenance, utilities, insurance, and damage to the work move to the owner as the certificate assigns them.
• Retainage is reduced or released, subject to the surety's consent, adjusted for the work still incomplete. The agreement between owner and contractor usually names the percentage and the conditions; one common form releases retainage at substantial completion less a multiple of the estimated value of the punch list.

Between substantial and final, the punch list gets worked. Then final payment, and the general conditions are strict about it: neither final payment nor the remaining retainage is due until the contractor delivers the affidavit that debts are paid, the insurance certificate, the consent of surety, any special warranties, and lien releases if the owner asks for them. The Division 01 closeout section stacks its own list on top. One I hold names O&M manuals approved, record documents delivered, spare parts transferred with a full accounting, training complete, and demonstration test certificates submitted as conditions of the substantial completion request itself, not final; a public university's section adds the completed punch list to the record documents due at final.

Retainage on the integrator's own subcontract usually mirrors the prime: the same percentage held by the general contractor that the owner holds from them, released when the owner releases it. Which means your retainage is hostage to every other trade's punch list too, and the only lever you hold is having your own closed and documented early enough to be the sub who is not the problem.

The rest of the closeout list, and when each item should have started, is in closeout checklist for a control system project.

One closure example

Lift station panel, substantial completion inspection on a Tuesday, list issued For Record that day with eleven items. Three of them, as the record shows them at final:

Eleven items, eleven dated closures, two lists (For Record at substantial, For Record at final) that reconcile line by line. The retainage request attaches both, and the conversation about it is short.

Disclosure: I build Submittal Kit, which keeps one numbered punch list per project with a source, owner, and rounds on every item, and freezes it as a Punch List for Record at each milestone. The two-list reconciliation is the thing that gets you paid, and a spreadsheet can do it if someone freezes the copies.