Closeout packages get rejected for one of three reasons: missing pieces, sloppy presentation, or insufficient proof. Each kicks the package back to the installer, which means another round of back-and-forth, which means retention money sitting in the client's accounts payable for another two to four weeks.
Here's the structure that lands a signature on the first attempt.
What a closeout package actually is
A closeout package is the single document that says: this project is done. It combines the punch list (closed), the MAC log (resolved or invoiced), the documentation handover (warranties, manuals, contacts), and the sign-off block (the signatures that release retention).
It's not a binder of receipts. It's not a folder of photos. It's a single coherent document — usually a PDF — that a client representative can read end-to-end in 15 minutes and sign at the end without scrolling back.
Done well, the closeout package is the artifact that releases retention money. Done badly, it's the reason retention sits on a desk for eight weeks.
Six things every closeout package needs
In order:
- Project header. Name, client, address, project number, dates (start, substantial completion, closeout submission), PM, lead installer. One page, top of the document.
- Punch list status. Every item, with location, photo, owner, date opened, date closed, and resolution proof (the photo of the fix). Items rejected by the dealer should have a one-sentence explanation. No open items.
- MAC log. Every MAC ticket, with quoted amount, approval reference (email date, signed CO ID), completion date, and invoice number. Each MAC links to its own paper trail.
- Documentation handover. As-built drawings, O&M manuals for each product line, warranty certificates, product data sheets, training delivery confirmation, key/access transfer log, supplier and trade contact sheet. This is what the FM inherits.
- Final walkthrough sign-off. Date of the walk, attendees, named representatives for client and dealer. Signed by both parties.
- Retention release schedule. The contract date for retention release, calendared. Not "60 days sometime."
If any of those is missing, the package is incomplete and the client has a legitimate reason to delay sign-off.
The single biggest reason closeouts get rejected
Missing photos. Or photos without locations. Or signed-off items without resolution proof.
The fix is upstream of the closeout: photos and locations have to be captured at the moment a punch item is opened, not reconstructed at the end. The same goes for resolution proof — the close-out photo gets taken when the fix happens, on the same record as the original.
If you're doing this manually in email and a spreadsheet, plan to lose 1 photo in 5 by the time the closeout is due. Not because anyone's careless — because that's just what happens with attachments distributed across crew member phones.
The order matters
Most rejected packages bury the proof. Don't do that. Sequence the document so the executive summary is up top, the detail follows, and the sign-off block sits at the end after the proof, not before:
- Project header (1 page)
- Executive summary — "Status: complete, X punch items closed, Y MACs resolved, retention release scheduled for {date}" (1 page)
- Detail: punch list (2–10 pages), MAC log (1–3 pages), documentation handover (appendix)
- Sign-off block (last page)
A client reading top to bottom should reach the sign-off block knowing the project is complete and that the proof is right above their signature line. Don't make them flip back.
Sign-off block: who signs and what
Four signatures in the right order:
- Project Manager (you / dealer-side). Signing that the install is complete per scope.
- Lead Installer. Signing that the as-built state matches the documentation.
- Client Representative. Signing acceptance of the work as complete.
- Facilities Manager. Signing the operational handover (training delivered, docs received).
Each signature catches a different category of failure. PM's signature is contractual. Lead installer's is technical. Client rep's is acceptance. FM's is operational. A package missing any of the four leaves a category of post-closeout dispute open.
How long should it be?
Counter-intuitive: shorter is better.
A 4-page closeout with crisp proof gets signed faster than a 40-page binder. The 40-pager makes the client suspicious that something's buried. Keep the punch list to one item per row, one photo per item, one paragraph of resolution. The handover docs go in an appendix the client can flip to but isn't forced to read.
Target: 6–12 pages of body content + appendix. If your typical closeout runs 30+ pages, you're probably padding with handover docs that should be linked rather than embedded.
What to do when the client refuses to sign
Two paths.
Path 1: the proof is missing. A specific item lacks a photo, or a MAC is missing approval evidence. Fix the missing piece, re-issue, and ask the client to sign. This is a recoverable rejection — usually one round.
Path 2: the proof is fine, the client is stalling. This is harder. Most contracts have a "deemed accepted in N days" clause — typically 14, 21, or 30 days from delivery of a complete closeout package. Send a written note referencing the clause: "Per Section X of the contract, the closeout package was delivered on {date}. Absent specific objections in writing, the work is deemed accepted on {date+N}." Don't argue. Document.
Most retention shakes loose once a procedural escalation lands. Going past 60 days without escalation is how installers end up at 90+ days with retention still parked. There's a full breakdown in why your retention money is stuck if this keeps happening on your projects.
Templates vs. tools
A printable template gets you started. The free closeout checklist covers the six-phase workflow above and prints to a clean PDF.
A tool that builds the package as you work is the next step up. Capture punch items with location and photo at the moment they're spotted. Log MACs with their quote and approval inline. The closeout package falls out as a byproduct of doing the install — not a frantic three-day exercise after the crew's already off site.
That's what Cleat does. The closeout PDF generates itself from the punch + MAC + handover artifacts you've been building all along. No re-typing, no last-minute photo-hunting, no "I think I have that picture on my phone somewhere."