1. Home
  2. Help
  3. Engines
  4. Closeout Builder
Post-Award · Engine

Closeout Builder

Aggregates the project's warranties, as-built redlines, punch closeout state, and O&M documents into a structured owner-ready deliverable. Computes a completeness score and surfaces gaps before handover.

Engine Phase: Closeout Runtime: 15-25 seconds Pro+

What it does

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.

v1 ships the structured package. v1.1 ships the PDF and ZIP export with the warranty matrix as a tab, the O&M index as a sectioned PDF, and the as-built drawings as a directory in the ZIP.

When to use it

Run after Warranty Compiler and As-built Reconciler

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 to upload

Nothing — this is an aggregation engine. It reads the project's warranties table, asbuilt_redlines table, 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.

Step by step

  1. Open the engine

    Sidebar → EnginesCloseout Builder.

  2. Confirm substantial completion date

    Defaults to the project's recorded date; override if needed. Anchors warranty start dates.

  3. 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.

  4. Run the build

    15–25 seconds. The engine doesn't re-parse documents; it just composes from project data.

  5. Read the completeness score

    Top of the result: percentage complete with breakdown by category (warranties / as-builts / punch / O&M).

  6. 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.

  7. Iterate

    Close gaps in their source trackers, then re-run Closeout Builder to recompute the score.

  8. Export the package

    v1.1 supports PDF / ZIP export. v1 is structured data only — share the live page with the owner.

Understanding the results

Completeness score

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%.

Warranty matrix

One row per warranted product with manufacturer, term (months), start date, conditions, and exclusions. Pulled from Warranty Compiler output.

O&M index by spec section

Tree of expected O&M docs grouped by spec section. Each entry shows present / missing / partial with the file reference.

As-built summary

Headline count of redline deltas by severity. Drilldown to As-built Reconciler for individual deltas.

Punch closeout state

Outstanding punch items count, sign-off status, and the responsible trade for each open item.

Gap list

Single actionable list of every missing item. Each gap names the responsible party and the action needed to close it.

Every control, explained

Run build

Consumes one run. 15–25 seconds.

Override substantial-completion date

Sets the warranty start anchor. Default reads the project's recorded date.

Re-run upstream engine

Quick links to re-run Warranty Compiler / As-built Reconciler if the banner flags them as stale.

Mark gap as resolved

Manually close a gap (e.g., O&M doc is in the corporate share drive, not project storage). Adds a note.

Filter gaps by responsible party

Narrow to gaps owned by one sub or one trade. Useful for the call list.

Export package (v1.1)

Generates the PDF closeout booklet plus a ZIP with as-built drawings, warranties, and O&M docs.

Share with owner

Read-only link the owner can review before final acceptance.