top of page

Part 15 of 15 Construction Project Closeout Process: Why Your Building Opens But Your Books Never Close

Writer: Lettie Boggs
Lettie Boggs
Sep 8
7 min read

A project is not finished at the ribbon-cutting; it is finished when the books balance, the records are complete, and the auditor signs off.

Architectural plans, binders, and laptop on a table with engineers wearing safety vests inspecting a new building project.

If you're still reconciling project costs 18 months after occupancy, the problem wasn't complexity—it was your closeout process, and every month of delay costs you credibility and carries unnecessary risk.


School construction projects don't truly end at the ribbon-cutting ceremony with smiling board members and excited students. They end when the books balance to the penny, the documentation files prove the complete story, and the external auditor finishes their review without findings.


I've watched facilities directors celebrate grand openings while their project closeout drags on for years. Final change orders never get processed. Asset tags never get recorded. Contingency balances sit in limbo. Documentation lives in random email threads and site trailers instead of organized archives.


Then audit season arrives, and suddenly everyone's scrambling to reconstruct 18 months of decisions and transactions. That's not a project completion—that's a project abandoned before the finish line.


This is the lean closeout system that actually gets you to true completion—fast, clean, audit-ready, and completely repeatable across every project.


The immediate win

  • Zero loose ends remaining: Every dollar lands exactly where it belongs with clear documentation.

  • Short, painless audits: External reviewers can trace source → use → project in minutes, not days of reconciliation meetings.

  • Credible completion story: Leadership sees exactly what you built, what it cost, and what funding remains for future work.


When project closeout is done right, it's invisible routine paperwork. When it's done wrong, it haunts your program for years.


The Complete Closeout Playbook (10 steps that work every time)


Step 1: Freeze the final scope.

Publish a one-page "What We Actually Delivered" summary showing final base scope plus all accepted alternates and approved changes. No surprises. No after-the-fact backfill trying to justify costs.


Step 2: Lock down the project ledger.

Finalize all Fund–Object–Project coding and A–G category assignments. Tag every single transaction with document link and board action reference number. No source document link? Then that transaction doesn't belong in closeout.


Step 3: Stop capitalizing at placed-in-service date.

All soft costs incurred after occupancy or formal acceptance get coded to operations or FF&E Phase 2 per your documented policy. Draw a bright line at the placed-in-service date and enforce it religiously.


Step 4: Reconcile all outstanding commitments.

Purchase orders, contracts, change orders, and pay applications must tie perfectly to General Ledger totals. Close commitments, de-obligate unused amounts, or provide written justification for each open item.


Step 5: Close contingency accounts with clear intent.

Publish a complete contingency glidepath showing starting balances → approved draws by layer (CC/PC/ProgC) → remaining balances. Reallocate any residual amounts per board policy. Don't let contingency evaporate into "miscellaneous."


Step 6: Settle all allowances to actual costs.

True-up each allowance to actual expenses within 30 days of substantial completion. Document credits or additional charges with clear one-sentence explanations of variance causes.


Step 7: Complete final FF&E and asset capture.

Barcode every item at room level, record manufacturer serial numbers, assign current locations, and export the capital asset list. If an item isn't physically tagged and recorded, it doesn't exist for accounting purposes.


Step 8: Produce and organize all record documents.

Accepted as-built drawings, Operations & Maintenance manuals, warranty documents with contact information, commissioning reports, complete testing logs, DSA or other regulatory closeout proof—all indexed and digitally linked.


Step 9: Run the complete funding stack reconciliation.

Show Grant + Match + Interest + Applied Savings and tie it exactly to both your General Ledger and (if applicable) your DLOPE report. The math must close perfectly on one reconciliation sheet.


Step 10: Write the project narrative summary.

Two clear paragraphs: what scope changed from original plan, why changes were necessary, and how you funded them. Auditors appreciate context. Board members need clarity.


These aren't suggestions. These are the ten steps that separate projects that actually finish from projects that limp along indefinitely.


Your Complete Closeout Documentation Packet (print this checklist)


Financial Documentation:

  • One-page Budget Summary Sheet: Budget/Committed/Actual/Forecast broken down by A–G categories

  • Funding Stack Reconciliation: Grant, Match, Interest, Applied Savings—all reconciled to the penny

  • Contingency Draw Log: CC/PC/ProgC showing every draw with trigger, approval, and remaining balance

  • Buyout Variance Report: Estimated costs versus awarded contract amounts with documented reasons for deltas

  • Allowance True-Up Summary: Each allowance item showing planned versus actual with variance explanations

  • Final FF&E and Capital Asset Register: Asset tags, serial numbers, room assignments, unit costs, funding sources


Technical Documentation:

  • Record Drawings and BIM Models (formally accepted and stamped)

  • Operations & Maintenance Manual Index with warranty expiration dates and vendor contacts

  • Commissioning Reports and Testing Logs (pass/fail summary plus complete detailed logs)

  • Permits and Regulatory Closeout: DSA approval letters, final inspections closed, all authority signoffs


Governance Documentation:

  • Board Actions Index: Award resolutions, change order approvals, acceptance resolutions—exact item numbers and dates

  • Project Decision Log: All scope additions, deductions, VE outcomes with assigned owners and decision dates

  • Lessons Learned Summary: 10 bullet points (what to repeat on future projects, what to change immediately)


If any section of this packet is blank or incomplete, your closeout isn't done. Don't pretend otherwise.


Closeout timeline that maintains momentum


Day 0 (at Substantial Completion):

Freeze capitalization date. Launch formal closeout sprint. Assign specific owners for each packet section with clear deadlines.


Day +15:

Record documents submitted for review. Asset tagging physically completed in all rooms. Allowance true-ups drafted with variance explanations. All financial commitments reconciled to General Ledger.


Day +30:

Contingency glidepath and funding stack reconciliation finalized. DSA and other regulatory closeout items at "submitted awaiting approval" status. Complete draft closeout packet ready for internal review.


Day +45 to +60:

Final packet approved internally. Board acceptance resolution scheduled and completed. Complete archives stored in document management system. Lessons learned report published to team.


Taking longer than 60 days from substantial completion? You're dragging historical baggage forward—identify and fix the visible bottleneck immediately.


I've seen districts take 24 months to close projects that should have closed in 60 days. That's not thoroughness. That's organizational dysfunction.


Controls that prevent endless rework cycles

  • Two-person review rule: One person compiles the closeout packet; second person reviews and signs a standardized 7-point verification checklist (coding accuracy, document links, commitment reconciliation, contingency accounting, allowance settlement, asset tagging, funding stack math).

  • Edge case decision log: One documented line per accounting exception showing the specific rule or policy you relied on (program manual section, board policy citation, GAAP guidance reference).

  • Query-based reports, not manual spreadsheets: All closeout financial reports are saved queries pulling directly from ledger and document systems—zero bespoke spreadsheets that someone has to manually update.

  • "No orphan dollars" verification test: Every budget variance line must name a specific cause and document the funding decision. No vague "miscellaneous adjustments."


These controls prevent the months of cleanup work that doom most closeouts.


Visual dashboards that make closeout progress visible


Create four simple tracking dashboards:

  • Punch Items to Documentation: Field punch list items remaining versus required document deliverables received and accepted.

  • Financial Burn-Down Chart: Final costs versus remaining contingency tracked over time from award through closeout.

  • Open Financial Commitments: Count and dollar value by vendor with aging analysis showing how long items have been open.

  • Asset Capture Progress: Percentage of rooms with completed tagging and reconciliation versus total rooms in project.


If any dashboard requires paragraphs of explanation to understand, your closeout process isn't tight enough. Simplify.


Common closeout failure modes (and what to do instead)


Failure: You keep capitalizing project soft costs for weeks or months after building occupancy.


Fix: Strictly enforce your placed-in-service date. Route all late soft costs to operations or FF&E Phase 2 per documented policy. No exceptions for convenience.


Failure: You maintain one pooled contingency account that hides actual decision-making.


Fix: Split contingency into CC/PC/ProgC layers from day one. Require documented trigger plus named approver for every single draw.


Failure: Project allowances never get reconciled to actual costs.


Fix: True-up all allowances within 30 days of substantial completion with written variance notes. Process change orders immediately if actual costs exceed allowances.


Failure: Furniture and equipment arrive without asset tags or serial number records.


Fix: Enforce "no tag, no move from staging to room" policy. Barcode everything at receipt and verify during installation.


Failure: Project teams rebuild financial reports manually in Excel every month.


Fix: Create and lock saved queries in your accounting system. Treat spreadsheets as temporary views, never as systems of record.


Every one of these failures has personally cost someone I know months of their life in cleanup work. Learn from their expensive mistakes.


Quick implementation (one focused week)


Week 1 Setup:

Day 1: Publish a one-page Closeout Standard Operating Procedure documenting these 10 steps with your district's specific requirements.


Day 2: Stand up saved queries for Budget Summary, Funding Stack Reconciliation, Contingency Log, Commitment Reconciliation, and Asset Register reports.


Day 3: Issue the standard Document Index Template and require document links for every deliverable item.


Day 4: Schedule the 45-day closeout review meeting on calendars right now for your next completing project.


Day 5: Run a complete pilot closeout on your nearest-to-completion project. Fix identified gaps once, then reuse the refined process everywhere.


Five days of setup work creates a system that runs itself for every future project.


What "good" looks like (the reality check)

  • Your board acceptance presentation is one clean slide. Questions focus on project outcomes and lessons learned—not on accounting mysteries or missing documentation.

  • External auditors finish their fieldwork ahead of schedule because everything they requested was already organized and linked in your closeout packet.

  • Your finance department closes the project fund with pennies in variance, not thousands of dollars in unexplained differences or "miscellaneous adjustments."

  • Your project team moves confidently to the next project without carrying a banker's box full of "we'll reconcile this later" loose ends.


When closeout is working properly, it's boring routine paperwork that happens quickly. That's exactly what success looks like.


The takeaway

Project closeout is a deliverable product just like the building itself. Build it with the same discipline you used for construction: clear scope definition, clean data management, and tight ownership accountability.


Do that consistent work, and you'll finish every project strong—on paper, in the field, and at the audit table. Your program builds momentum instead of dragging historical baggage forward.


The ribbon-cutting ceremony is the middle of the project story, not the end. The real finish line is when every dollar is accounted for, every document is filed and linked, every asset is tagged and recorded, and the auditor signs off without findings.


That's when you've actually finished the project. Everything before that point is just hoping nobody asks hard questions.


Construction Project Closeout

Construction Project Closeout

Comments


bottom of page