Warranty Compiler
Warranty Compiler is the closeout-prep engine that builds the warranty matrix from data already in the project. It reads approved submittals and procurement items and composes one warranty entry per manufactured product, with manufacturer, model, term, start date, conditions and exclusions, and lists the submittals it could not match.
What is the Warranty Compiler?
Warranty Compiler is the closeout-prep engine that builds the warranty matrix without forcing the PM to chase a hundred manufacturers. It reads approved submittals (which name the manufactured products) and purchase orders (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 is saved to the project's warranties 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 should I use the Warranty Compiler?
Use Warranty Compiler about 30 days before substantial completion to start the warranty package, after each major submittal approval batch to keep the matrix current, on demand when an owner asks for the warranty list mid-project, and again if the substantial-completion date moves.
- 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 do I upload to the Warranty Compiler?
Nothing — this is an aggregation engine. It reads approved submittals and purchase orders 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.
How do I run the Warranty Compiler?
To run Warranty Compiler, open it, confirm the substantial-completion date, review the source preview, run the compile, read the warranty matrix, verify the term source, walk the unmatched list and persist the entries for closeout.
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 save each entry to the project's warranties. Closeout Builder reads from there.
How do I read the Warranty Compiler results?
The result is a warranty matrix with a term-source badge, conditions and exclusions, a list of unmatched submittals, manufacturer grouping and the persisted entries.
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 project's warranties 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 warrantiesSaves each entry to the project's warranties for Closeout Builder.
Export PDFFormatted warranty matrix PDF. Standard format for owner closeout binder.
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.