Setup to closeout, every row.
A systematic pass over payment, schedule, risk, subs, and closeout, not a skim for scary words.
Know what you signed up for.
Specset works the agreement, general conditions, and special provisions through a systematic checklist and returns a severity-flagged review table: the clauses that shift risk to you, what each one means, and the paragraph behind every flag.
Contract review · Ridgeview CenterAI analysis
Checklist complete#Checklist itemSeverityClause
Cost, billing & payment
23Payment to subs conditioned on owner receipt of fundsHigh§12.2
25Retainage 10%, reducing to 5% at half completeStd§12.6
Risk, insurance & indemnity
31No damage for delay; time extension is sole remedyHigh§8.4
Work planning & scheduling
12Written delay notice due within 7 calendar daysAttn§4.7.2
Impact · row 23 · §12.2
Payment obligation to subcontractors is conditioned on owner payment. Cash-flow risk transfers downstream; flag for negotiation or pricing.
Agreement · general conditions · special provisions2 high · 2 attention · 38 standard
Every flag names its paragraph.
Severity and impact notes tied to the exact clause, so review meetings argue positions, not page numbers.
Flags, not legal advice.
Your team and your attorney make the calls. They just start from a cited map of the risk.
Trusted by the teams delivering public work
“The pay-if-paid clause was buried in the supplementary conditions. The review put it in row one with the paragraph beside it.”
2.6M+Pages read into project records on Specset
475+Projects in production, bid through closeout
01 · How the review runs
A systematic pass, not a nervous skim.
Contract risk hides in the edits: the supplementary conditions and special provisions that modify the standard forms. The checklist works all of it, in context.
01 · The contract set
Signed agreementOwner-contractor · GMP amendment
General + supplementary conditionsThe edits are where the risk moved
Division 00–01 · special provisionsRead from the conformed record
Name the document, or let the agent locate the contract content itself, signed agreements in the documents, special provisions in the specifications.
02 · The checklist
Setup to closeout, systematically
- Contract setup and changes
- Work planning and scheduling
- Cost, billing, and payment
- Subcontracting and flow-down
- Risk, insurance, and indemnity
- Document control and closeout
The review runs as its own background agent, working every checklist row against the contract documents instead of skimming for scary words.
03 · The table
High severity · lead the summary
Attention · impact note attached
Standard · confirmed, cited
Every row carries a severity flag, an impact note, and the clause citation. Ask follow-up questions in the thread; the answers cite the same paragraphs.
02 · After the table
Ask the contract, get the clause.
The review is the start of a record you can question. Notice deadlines, flow-down obligations, payment terms: answers come back with the governing paragraph attached, all project long.
How many days do we have to notice a delay, and to whom?
Written notice within 7 calendar days of the event, to the Engineer, with the cost and time impact stated or estimated. Continuing delays require weekly updates.
§4.7.2§4.7.4
Common questions
What teams ask about contract review.
01What documents does the review cover?
The signed agreement and its amendments, general and supplementary conditions, and the Division 00 and 01 content in the specifications, including special provisions. Name a specific document, or let the agent locate the contract content across the project record.
02Is this legal advice?
No. It is a systematic, cited review that puts the contractor-unfavorable clauses on the table with severity flags and impact notes. Your project leadership and your counsel make the judgments; they just start from a map instead of a cold read.
03What does the checklist actually cover?
Contract setup, changes, work planning, scheduling, cost and billing, subcontracting, risk and insurance, document control, and closeout. Each row is checked against the contract documents and returned with a severity flag and impact note.
04What does a finding look like?
A row in the review table: the checklist item, what the contract says, a severity flag, an impact note in plain language, and the clause citation. High-severity rows lead the summary so the pay-if-paid clause is not finding number forty.
05Can we review subcontracts and amendments too?
Yes. Each review runs against whichever document you name: a subcontract, a GMP amendment, a change order package. A re-run is a fresh, independent review with its own table, so you can compare positions across versions.
06What happens after the review?
The table lives with the project. Ask follow-up questions in the thread and get answers cited to the same clauses, route edits and re-reviews from the review itself, and carry the notice deadlines into how the job is run.
Start with the agreement on your desk
Put your next contract through the checklist.
Send an agreement and its conditions. We'll return the severity-flagged table, cited clause by clause, before your review meeting.