Aggregates approved submittal_revisions and procurement_items for the project, then composes one warranty entry per manufactured product with term_months (spec-stated, manufacturer-published, or industry-standard), start date aligned to substantial completion, conditions, and exclusions. Persists each entry to the warranties table for the closeout package. Flags unmatched submittals for PM follow-up.
A typical mid-size CRE project installs 200–400 distinct manufactured products. Each has its own warranty — spec-stated, manufacturer-published, or industry-standard. Closeout day, the owner expects all of them listed in one matrix with terms, expirations, and claim contacts. Most GCs build this by hand the week before delivery and miss 15–25% of products.
Warranty Compiler reads every approved submittal_revision and every procurement_item in the project's tables, joins them on product+manufacturer, and writes a warranty entry for each match. Three-tier term resolution: spec-stated term wins, manufacturer-published term is fallback, industry-standard term is last resort. Start dates align to substantial completion (or install date, configurable). Each entry persists to the warranties table that Closeout Builder reads.
Warranty Compiler is built to run repeatedly — not once at closeout. The first run, mid-project, is the most valuable because it catches the gaps while you still have leverage with the subs.
Server-side aggregation engine. The trigger button replaces an upload form — everything's already in the project's tables.
submittal_revisions table. Each row carries the approved cut-sheet, the spec section it satisfies, and any warranty PDF the sub attached at approval. The cut-sheet's manufacturer + model is the join key.
procurement_items table. Each PO carries quantity, manufacturer, model, supplier, delivery date. Joins to submittal_revisions on (manufacturer, model) to confirm match.
Default warranty start. Per-product override allowed (some warranties start from install date, not SC). The engine resolves this per the spec's payment terms section.
Sample compile output for a 14-story office build, showing the three-tier term resolution and the unmatched flag for PM follow-up:
Persisted warranty entries grouped by manufacturer, term + conditions per product with source attribution, unmatched-submittals list with the suggested PM action per item, and the matrix Closeout Builder consumes directly. Industry-standard terms are explicitly flagged so the PM verifies the high-stakes ones (chillers, switchgear) by phoning the manufacturer.
Warranty Compiler is the inflection point between the project-phase trackers and the closeout deliverable. It reads from two trackers, persists to one table, feeds one downstream engine.
The engine still composes the entry using the manufacturer-published or industry-standard term, but flags the row as "warranty PDF missing." The unmatched list surfaces the gap for PM follow-up. Best practice: chase the sub to upload before closeout day. Worst case: the matrix carries the term but the owner can't see the original document.
Each tier becomes a separate entry attribute. Example: Square D panelboards typically carry 18-month labor + 5-year equipment + optional 10-year extended (purchased separately). The composed entry lists all three with effective dates and exclusions. Owner sees the full picture, not just the headline term.
Workmanship warranties come from the installing sub's contract, not from the manufacturer. v1 of Warranty Compiler handles manufacturer warranties; workmanship warranties are pulled from contract_review at closeout time as a separate matrix section in Closeout Builder. v1.1 will merge both into one unified register.
v1 doesn't auto-register on the manufacturer's portal — that varies too much by brand (Carrier, Trane, Schlage all have different flows). The engine surfaces the registration URL + serial number requirement per product so the PM can complete registration. Bulk auto-registration is on the v4.2 roadmap.
Unmatched submittal = approved cut-sheet but no PO with the same manufacturer/model. Often a substitution that was approved but never procured. Unmatched PO = procurement record but no approved submittal. Often a small-quantity buy without formal submittal flow. Both flag separately so the PM resolves the right gap.
If your project is 50% installed, Warranty Compiler will surface every approved submittal without a manufacturer warranty PDF in 30 seconds. That's the list to give your subs before final pay app withholding becomes the conversation.
Start free — 14 days, no card →