Contract Summary
Contract Summary is the engine that turns a signed contract into a readable two-page brief. It covers the parties and scope, the financial structure, critical dates, the change-order process in plain language and the top five risks worth watching, for a PM or owner who will not read 40 pages.
Updated
What does Contract Summary do?
Contract Summary reads the full contract and produces a readable 2-page brief covering the parties and scope, the financial structure (contract value, retainage, pay schedule, LDs, bond and insurance), the critical dates (start, substantial completion, final completion, notice windows), the change-order process in plain language, and the top 5 risks worth watching.
Where Contract Review gives you a clause-by-clause risk register, Contract Summary gives you the one-page-rear-of-laptop reference the field PM actually keeps.
When should I use Contract Summary?
Use Contract Summary when you hand a contract to a field PM who did not run the negotiation, when you brief an owner or GC partner on a signed contract, or as your own reference to the payment schedule and LD rate after signing.
- Handing a contract off to a field PM who didn't run the negotiation.
- Briefing an owner or GC partner on a signed contract.
- Your own reference after signing — you'll want the payment schedule + LD rate within reach for the entire project.
What do I upload to Contract Summary?
One signed contract. Same formats as Contract Review (PDF best, DOCX fine).
How do I run Contract Summary?
To run Contract Summary, open it, upload the contract, run the analysis, review the sections and export the PDF.
Open the engine
Sidebar → Engines → Contract Summary.
Upload the contract
Or chain from Contract Review — the contract carries forward.
Run analysis
40–70 seconds typical.
Review the sections
Output is structured into ~7 sections: parties + scope, financials, dates, deliverables, change orders, risks, notable clauses.
Export PDF
2-page formatted brief. Hand to the PM.
How do I read the Contract Summary results?
The result is a brief with the parties and scope, financials, critical dates, the change-order process, the top risks and notable clauses.
Who signed, work covered, project name, location.
Contract value, retainage %, retainage release schedule, pay-app cycle, LD rate, LD cap, bonding requirement, insurance limits summary.
Notice to proceed, start, substantial completion, final completion, notice-window lengths for delay / default / change.
Plain-language how-to for getting a change approved — who signs, what's required, default response times.
5-item list pulled from the same pass as Contract Review — the things most worth watching during execution.
Non-standard or unusual clauses worth flagging for the field team.
Every control, explained
Run analysisOne run.
Export PDFFormatted 2-page brief.
Export XLSXFielded data — dates, amounts, limits — useful for plugging into a project dashboard.
Chain to PM HandoffFull handoff bundle with all sections plus contacts and action items.
Chains
Chains into
Chained from
Exports
- PDF — 2-page brief.
- XLSX — fielded data for dashboards.
- CSV — flat key-value list.
Troubleshooting
Contract didn't specify them (common — dates often come from a separate schedule). Add them manually in the exported PDF, or capture them in the Schedule tracker after signing.
Not all contracts cap LDs. If left blank, that's the contract's actual state — flag it as a risk for your PM.