Win the Bid.Hold the Margin.Protect the Closeout.
Sub bond threshold dropped to $250K (Add. 03)
Source: Mercy West Tower SOW.pdf · Page 47 · §11.4.1
- ·Sub bond reduction tightens compliance margin → severity factor +1
- ·Historical: similar bond change on past federal courthouse cost $87K in unrecouped premium
- ·Exposure projected: +$140K across 11 affected subs
Drawn from active engagements · Numbers vary by spec length, division mix, and your firm's historical risk profile
Where great precon teams take the blame.
Your estimators are buried under 600-page specs, cross-referencing addenda against general requirements in spreadsheets. Your subs are quoting against incomplete scope. And when a $140K scope gap surfaces post-award, everyone points fingers at preconstruction.
Static Checklists
Today's tools extract obligations into flat lists. They don't reason about conflicts between specs, addenda, and sub-scopes.
Siloed Documents
Addenda contradict general requirements. MEPs conflict with structural specs. Nobody catches it until the field does.
No Audit Trail
When the change order hits, you can't trace the decision. When closeout comes, you can't defend the claim.
Read. Assess. Export. Analyze.
By the time the estimator opens the matrix, the spec's already mapped. The Obligation Matrix shows what's required. The Risk Register scores what could hurt you. Per-sub packets get pricing right. Every decision feeds the next bid's institutional memory.
Every requirement, cited.
Tender docs in. Contract, addenda, geotech, drawings. AI parses everything and populates the Live Obligation Matrix — every requirement mapped to its source clause and page. CSI-classified during project setup. Conflicts between divisions flagged before the drawing set opens.
What could hurt you.
The Risk Register builds on the obligation matrix. Impact and likelihood scoring, dollar exposure with reasoning shown, ownership assignment, mitigation actions. Cross-trade conflict and overlap detection as a first-class signal. New addenda flag modified rows on both surfaces. Nothing hides until the field finds it.
Subs price the right scope.
Per-sub obligation packets filtered by CSI division. Excel or Word. Cited to section and page. Attaches to the bid package the GC already sends. Halozen produces the obligations exhibit; the GC keeps owning the bid package.
The loop closes.
Sub quotes uploaded and tagged. Per-obligation gap analysis: covered, partially covered, not covered, clarification needed. Every decision captured in the Reasoning Ledger. The Risk Register feeds institutional memory — which sharpens Step 1 on the next bid.
Ask anything. Get a cited answer.
The questions your team actually asks — answered from your spec, your ledger, your past bids.
Bid Assist is the chat panel that's always on every project screen. It pulls from the live obligation register, the reasoning ledger, and your firm's history of past bids. Every answer cites its source. Pulls up before the bid for research, during the bid for sub coordination, and after award when a change order needs defending. One assistant, every phase.
Same three foundations every other agent reads. No siloed tools.
What your team gets.
Five exports — Excel, PDF, DOCX, or direct to Procore. Plus Bid Assist, the chat dock that's always there. Every one cites its source.
Every clause cited to source. Plus the assessment layer on top: category, status, impact, likelihood, and dollar exposure per row.
XLSX / PDFCSI-classified obligation extract per trade, ready to attach to the bid package you already send. One packet per sub.
XLSX / DOCXCoverage status per obligation when sub quotes come back: covered, partially covered, not covered, clarification needed.
XLSX / PDFAudit-ready trail of every bid decision with deterministic citations. For change orders, claims, and closeout.
JSON / PDFAuto-drafted procurement responses tied back to the spec. PQQ responses, RFI drafts from spec ambiguities and cross-trade conflicts, and clarification requests. Ready for owner or architect submission.
DOCX / PDFChat panel that's always on every project screen. Cited Q&A on any artifact: pre-bid research, sub coordination, post-award change-order defense.
◆ Always OnWe don't leave at the bid.
The obligation register and reasoning ledger don't stop at award. Two new agents pick up where the bid ends: Project Controls runs schedule and submittals, JHA Studio drafts the daily safety docs. Same register. Same ledger. No re-entry.