Compresses a 40–80-page subcontract into a 2-page field-ready brief your PM can actually carry. Payment terms, retainage rate and step-down, liquidated damages, insurance minimums, claims notice periods, dispute resolution sequence, and the change-order procedure — each one surfaced with its clause reference so the PM knows exactly where to look when something goes sideways at month 9. The full-risk Contract Review is for review. This is for use.
A signed subcontract is a 60-page binder. The PM running the field never reads it again after award. When the architect rejects a CO at month 9, the PM has to know the claims-notice window. When the sub stops paying lower-tier, the PM has to know if there's a contingent-payment trigger. When the retainage-release request lands, the PM has to know the substantial-completion definition. None of those answers are within easy reach of someone whose desk is a job-site trailer.
Contract Summary reads the executed subcontract and produces a structured 2-page brief: the key terms card up top, then payment + retainage, claims + notice deadlines, insurance requirements, and the dispute resolution sequence. Every section line carries the clause reference (§ + page) so the PM can jump back to the source when they need to quote it. Companion engine to Contract Review — Review surfaces the risks pre-signature, Summary surfaces the obligations post-signature.
Contract Summary runs at handoff and stays a reference for the project's entire life. Run it at the moments where a clause matters.
One required input. Optional context narrows the summary to the contract type if useful.
The executed subcontract, prime contract, or owner-GC agreement. ConsensusDocs, AIA A401 / A201, ConsensusDocs 750/751, or custom forms — all parse. Multi-document contracts (general conditions + supplementary conditions + addenda) are linked and summarized together.
Subcontract / prime contract / owner agreement. The summary structure adapts — a sub gets the contingent-payment row up top, a prime gets the LD exposure and owner-supplied items section.
Contract value, start date, substantial-completion date. If supplied, the deadline rows compute concrete dates (e.g., "Notice of claim due: 06-Sep-2026, 21 days from event") instead of generic windows.
Sample summary for an executed AIA A401 subcontract on a commercial tenant fit-out, $1.86M, 18-month duration:
A PM in a phone call with the owner doesn't have time to read a 60-page contract to find the answer. The summary says "21-day notice per §10.2, p.18." The PM either knows the answer or knows the page to look. The audit trail back to the source document is the whole point — this engine summarizes, it doesn't paraphrase. Every line is a quote or a direct restatement with the clause reference attached.
Contract Summary is the field-side companion to Contract Review. The summary's structured data feeds every downstream engine that needs to enforce a contract term.
Contract Review surfaces risks before signing — clause-by-clause severity ratings, suggested redlines, position vs. standard. Contract Summary surfaces obligations after signing — the executed terms the PM operates under. Most teams run Review during negotiation, then Summary the day the contract is executed. Both engines read the same documents, just answer different questions.
AIA A101 / A102 / A107 / A201 (general conditions) / A401 (subcontract), ConsensusDocs 200 / 500 / 750 / 751, DBIA, EJCDC, and custom forms. The engine identifies the form on parse and uses the form's section numbering convention. Custom contracts (owner-drafted, GC-drafted) work but with slightly lower field-mapping confidence — the summary still composes correctly, the clause references just need PM verification on first run.
Multi-document parsing. Base contract + general conditions + supplementary conditions + addenda all upload together. The engine resolves overrides correctly (e.g., if a supplementary condition modifies the retainage rate, the summary reflects the modified rate with both clause references). The hierarchy is preserved in the audit trail.
Yes. Clauses tagged TRAP CLAUSE are ones with material consequences and tight deadlines (waivers, notice requirements, schedule-modification triggers, pay-when-paid). Each TRAP is severity-highlighted in red on the brief with the consequence spelled out: "Missed notice = waiver of claim." The full Contract Review engine handles the risk-rating side; Summary just flags so the PM knows which lines are non-negotiable.
Yes. If the contract gets amended (executed CO modifies a payment term, agreed-upon change in retainage, etc.), upload the amendment and the summary re-issues with the change reflected. The previous version is archived in the project's contract history. The deadline math (claims windows, etc.) recomputes off the amendment date when relevant.
Both. Subs run it on the GC-issued subcontract before mobilization. GCs run it on the prime contract for the project team and on every executed subcontract for the subcontract management database. Same engine, same plan tier, same structure — perspective is set by the contract type and who's named where.
Bring one executed subcontract or prime contract to a 15-minute call. We'll process it on screen, walk the five sections, and you keep the printable brief for the trailer wall.
Try Free for 14 Days →