Win the bid.Stop margin leak.Protect the closeout.
- Builder's Risk all-risk policy w/ $50K deductibleFinancialCOVERED5/54/5R-01FinancialCOVERED$151KI·5L·4$151K
- Sub bond threshold dropped to $250K (Add. 03)FinancialSCOPE GAP4/54/5R-02FinancialSCOPE GAP+$140KI·4L·4+$140K
- LDs $7,500/day from substantial completionFinancialCOVERED5/53/5R-03FinancialCOVERED$7,500/dI·5L·3$7,500/d
- Imaging-suite vibration limits during demoRegulatorySCOPE GAP4/53/5R-04RegulatorySCOPE GAP+$92KI·4L·3+$92K
- Hospital ops shutdown coordination, 14-day noticeScheduleCOVERED3/52/5R-05ScheduleCOVERED$0–$35KI·3L·2$0–$35K
- Final retention release after as-built + O&MFinancialCOVERED2/52/5R-06FinancialCOVERED$18KI·2L·2$18K
Drawn from active engagements · Numbers vary by spec length, division mix, and your firm's historical risk profile
Where great precon teams get blamed.
Your estimators are buried in 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.
Halozen starts where the estimate ends. The Obligation Matrix captures what the spec requires. The Risk Register scores what could hurt you. Per-sub packets get pricing right. Then every decision feeds the next project'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.
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.
Bid Assist is the chat panel that's always on every project screen. It reads your live obligation register, your 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 citation-backed exports in Excel, PDF, DOCX, or direct to Procore. Plus Bid Assist, the persistent chat dock that runs on every screen.
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 keep running. Four new agents come online — Project Controls picks up schedule and submittals, JHA Studio drafts the daily safety docs, Site Vision and Fleet Ops watch the field. Every one reads the same register. Every one writes to the same ledger.