Warranty Compiler
Aggregates approved submittals and purchase orders, composes one warranty entry per manufactured product with term, start date, conditions, and exclusions. Persists to the warranties table for the closeout package.
What it does
Warranty Compiler is the closeout-prep engine that builds the warranty matrix without forcing the PM to chase a hundred manufacturers. It reads approved submittal_revisions (which name the manufactured products) and procurement_items (which name the suppliers and quantities), then composes one structured warranty entry per product: manufacturer, model, term in months, start date anchored to substantial completion, conditions, and exclusions.
For the term, the engine reads in priority order: (1) the spec-stated term in the submittal, (2) the manufacturer-published term if known, (3) the industry-standard term for the product class. The source is recorded with each entry so the PM can verify or override.
Each entry persists to the warranties table for downstream consumption by Closeout Builder. Unmatched submittals (the engine couldn't determine a warranted product) are flagged for PM follow-up rather than guessed at.
When to use it
- Closeout prep — 30 days before substantial completion, run the compiler to start the warranty package.
- After every major submittal approval batch — keep the warranty matrix current rather than racing at the end.
- Owner asked for the warranty list mid-project (e.g., financing or insurance review) — produce it on demand.
- Re-running with updated substantial-completion date if the schedule shifted.
Compiled warranty entries flow directly into Closeout Builder as the source for the warranty matrix in the owner deliverables booklet.
What to upload
Nothing — this is an aggregation engine. It reads submittal_revisions (approved state) and procurement_items for the active project. What you provide is the substantial-completion date as the warranty start anchor (defaults to the project's recorded date).
What it needs is well-maintained upstream data: submittals approved and tagged with manufacturer + model, procurement items linked to their submittals where appropriate. Garbage in, garbage out — the compiler is honest about gaps and flags unmatched submittals.
Step by step
Open the engine
Sidebar → Engines → Warranty Compiler.
Confirm substantial-completion date
Defaults to the project's recorded date. Override if needed — this anchors every warranty's start date.
Review source preview
Banner shows: N approved submittals will be read, M procurement items linked. If unexpectedly low, refresh upstream data before running.
Run compile
20–40 seconds.
Read the warranty matrix
One row per warranted product: manufacturer, model, term (months), start, conditions, exclusions, source.
Verify the term source
Each row shows where the term came from (spec / manufacturer published / industry standard). PM should verify spec-derived terms and override industry-standard rows if the actual manufacturer term is known.
Walk the unmatched list
Submittals the engine couldn't tie to a warranted product show as unmatched. PM follow-up: either add the manufacturer/model to the submittal record, or confirm the product isn't separately warranted.
Persist for closeout
Click Persist Warranties to write each entry to the warranties table. Closeout Builder reads from there.
Understanding the results
One row per warranted product. Columns: manufacturer, model, term (months), start, conditions, exclusions, source.
Each row shows where the term value came from (spec / manufacturer-published / industry-standard). Override if you have better information.
What activates and what voids the warranty. Pulled from the submittal terms; the PM can edit before persisting.
Approved submittals where the engine couldn't determine a warranted product. Listed for PM follow-up.
Optional roll-up by manufacturer — useful when one supplier provides many products and you want a single warranty entry covering all.
Confirmation that warranty entries saved to the warranties table for downstream consumption by Closeout Builder.
Every control, explained
Run compileConsumes one run. 20–40 seconds.
Override substantial-completion dateSets the warranty start anchor for every entry.
Edit termOverride the engine's term value. Re-tags the source as PM override.
Edit conditions / exclusionsPolish the contractual language before persisting.
Resolve unmatched submittalTag the submittal with manufacturer + model or mark it as no-warranty so the compiler stops surfacing it.
Persist warrantiesWrites each entry to the warranties table for Closeout Builder.
Export PDFFormatted warranty matrix PDF. Standard format for owner closeout binder.