Closeout Builder
Closeout Builder is the assembly engine for the owner-ready closeout package. It pulls the project's warranties, as-built redlines, punch closeout state and O&M documents into one structured deliverable and computes a completeness score, so you can see what is still missing before owner handover.
What is the Closeout Builder?
Closeout Builder is the assembly engine for the final deliverable package. It pulls the project's warranties (from Warranty Compiler), as-built redlines (from As-built Reconciler), punch closeout state (from Punch List Drafter and Punch List Tracker), and O&M documents, then composes a structured owner-ready package with a warranty matrix, O&M index by spec section, as-built summary, punch closeout state, and a completeness score.
The completeness score is the load-bearing output: it tells you what's missing before owner handover. Outstanding punch items, missing warranties for installed equipment, gaps in the O&M index — all surfaced as actionable gaps rather than buried in a 500-page PDF.
The result is the structured package, and it exports two ways: Export PDF gives the closeout booklet, and Export ZIP bundles the warranty documents, the O&M manuals and that PDF in one download. The ZIP button appears once the package has been saved.
When should I use the Closeout Builder?
Use Closeout Builder when substantial completion is about 30 days out and you need to know what is missing, when the owner asks whether you are ready to hand over, when the last pay-app release depends on closeout, or to audit a closed project's deliverables.
- Substantial completion is 30 days out and you need to know what's missing for the closeout package.
- Owner asked "are you ready to hand over?" and you need a defensible answer with a completeness number.
- Last-pay-app release depends on closeout being complete — gap report drives the punch list.
- Audit a recently-closed project to confirm the deliverables are intact.
Closeout Builder reads from the structured outputs of Warranty Compiler and As-built Reconciler. Run those first — their persisted data is the closeout source. Closeout Builder runs in 15–25 seconds because it doesn't reparse documents.
What do I upload to the Closeout Builder?
Nothing — this is an aggregation engine. It reads the project's warranties, as-built redlines, punch list state, and O&M documents in project storage. Upstream engines (Warranty Compiler, As-built Reconciler, Punch List Drafter) are the source of truth.
Optional inputs: a target substantial-completion date (anchors the warranty start dates), the owner's closeout requirements document (overrides the standard checklist), and any contract-specific deliverable list.
How do I run the Closeout Builder?
To run Closeout Builder, open it, confirm the substantial completion date and that the upstream engines have run, run the build, read the completeness score, walk the gaps, iterate, and export the package.
Open the engine
Sidebar → Engines → Closeout Builder.
Confirm substantial completion date
Defaults to the project's recorded date; override if needed. Anchors warranty start dates.
Confirm prerequisites are ready
Banner shows status of upstream engines — warranty compile run, as-built reconcile run, punch list status. If any are stale, prompt to re-run.
Run the build
15–25 seconds. The engine doesn't re-parse documents; it just composes from project data.
Read the completeness score
Top of the result: percentage complete with breakdown by category (warranties / as-builts / punch / O&M).
Walk the gaps
Each missing item is listed with the responsible party and the action to close it. Often resolves to a single sub-call.
Iterate
Close gaps in their source trackers, then re-run Closeout Builder to recompute the score.
Export the package
Click Export PDF for the booklet, or Export ZIP for the PDF plus the warranty documents and O&M manuals.
How do I read the Closeout Builder results?
The result is a completeness score plus the warranty matrix, an O&M index by spec section, an as-built summary, the punch closeout state and a list of gaps.
Single percentage at the top. Breakdown shows the contribution from warranties, as-builts, punch closeout, and O&M. Color-coded green at ≥95%, amber 80–95%, red below 80%.
One row per warranted product with manufacturer, term (months), start date, conditions, and exclusions. Pulled from Warranty Compiler output.
Tree of expected O&M docs grouped by spec section. Each entry shows present / missing / partial with the file reference.
Headline count of redline deltas by severity. Drilldown to As-built Reconciler for individual deltas.
Outstanding punch items count, sign-off status, and the responsible trade for each open item.
Single actionable list of every missing item. Each gap names the responsible party and the action needed to close it.
Every control, explained
Run buildConsumes one run. 15–25 seconds.
Override substantial-completion dateSets the warranty start anchor. Default reads the project's recorded date.
Re-run upstream engineQuick links to re-run Warranty Compiler / As-built Reconciler if the banner flags them as stale.
Mark gap as resolvedManually close a gap (e.g., O&M doc is in the corporate share drive, not project storage). Adds a note.
Filter gaps by responsible partyNarrow to gaps owned by one sub or one trade. Useful for the call list.
Export PDF / Export ZIPExport PDF generates the closeout booklet. Export ZIP bundles that PDF with the warranty documents and O&M manuals that are attached in Trueleveler.
Share with ownerRead-only link the owner can review before final acceptance.
Sources
- FAR 52.246-21: Warranty of ConstructionAcquisition.gov, Federal Acquisition RegulationThe federal construction warranty clause: the one-year term, notice and correction of defects.
- Summary: A201-2017, General Conditions of the Contract for ConstructionAIA Contract DocumentsThe AIA overview of the general conditions that set out the rights and duties of owner, contractor and architect.