Yes, for drafts and paperwork: AI can summarise a subcontract's clauses, compare a returned version with your standard form, list the key dates and draft change orders from site messages. It cannot judge what is enforceable, so a lawyer should still review indemnity, payment and termination terms, anything unusual, and every high-value subcontract. This is general information, not legal advice.
The risk is not that assistants invent clauses; they mostly quote what is there. The risk is what they leave out: a missing insurance requirement, a schedule you never uploaded, a defined term that quietly flips who owes what. Use the output to decide what to ask a lawyer, never to answer the lawyer's questions for them.
What the assistant does well, and the line it should not cross
Four jobs suit an assistant, because each is reading, comparing or formatting rather than judging. It can summarise clauses in plain words, so you know what you are being asked to sign before anyone bills you to read it. It can compare a returned subcontract with your standard form and list every difference. It can extract dates, notice periods and obligations into a table with the clause number and the exact wording beside each. And it can draft a change order (called a variation in some contracts) from a site message and your own price build-up.
Three things stay with someone qualified: deciding whether a clause is enforceable where the project is, deciding who should carry a risk, and advising on how the law treats a dispute. Rules on payment security, notice deadlines and dispute routes differ by place and by project type, so an assistant that sounds certain about them is guessing.
| Task | Assistant | Lawyer or adviser |
|---|---|---|
| Plain-English summary of each clause | Yes | Only for the clauses that matter |
| Comparing returned terms with your standard form | Yes, as a first pass | Reviews the differences that move risk |
| Listing dates and notice periods | Yes, with quotes; you work out the dates | Confirms any deadline the law sets |
| Drafting a change order from your numbers | Yes | Approves your template once |
| Enforceability of an indemnity or liability cap | No | Yes |
| Governing law, venue and dispute steps | No | Yes |
| Anything unusual, or above your value threshold | Flags it | Reviews it |
A returned subcontract, compared clause by clause
Take a small general contractor with a $212,000 whole-house renovation, an invented job used from here on. The electrical package, $38,400, goes to a subcontractor who sends back the firm's standard form with changes. The prompt asks for differences, not opinions:
I am the main contractor. Document A is our standard subcontract. Document B is the version the electrical subcontractor returned.
Compare them clause by clause. For every difference give: topic, clause number in each document, a short quote of our wording, a short quote of their wording, who benefits, and the money or time effect wherever the text lets you calculate it.
Then list every clause in Document A that is missing from Document B.
Do not tell me whether anything is legal or enforceable. Where you are unsure, write "unsure" and quote the text.A typical result, trimmed (illustrative sample output):
| Topic | Our form | Their version | Effect |
|---|---|---|---|
| Retention (cl. 4.6) | 10%, half released at practical completion, the rest after the defects period | 5%, all released at practical completion | Security on $38,400 falls from $3,840 to $1,920 |
| Payment (cl. 4.2) | 30 days, and only after the client pays us | 14 days from invoice, no link to client payment | We may fund each invoice for up to 16 days |
| Claims notice (cl. 6.3) | 7 days | 21 days | Later claims for extra time or money |
| Insurance (cl. 9.2) | $2M public liability; certificate before starting | $1M; certificate "on request" | Lower cover, no proof at the gate |
| Indemnity (cl. 9.3) | Subcontractor indemnifies us for losses from its work | Capped at the subcontract value; consequential loss excluded | Described as "market standard" |
| Suspension (cl. 11.4) | We may terminate on 7 days' notice for default | They may suspend on 3 days' notice if any payment is late | Programme risk sits with us |
| Defects (cl. 10.1) | 12 months | 6 months | Shorter callback cover |
The money lines are the easy part, and they are worth confirming with a calculator: 10% of $38,400 is $3,840, 5% is $1,920, and 30 days minus 14 days leaves 16. Four monthly draws of $9,600 make the funding gap concrete, because each draw would leave your account up to 16 days before the client's money reaches it.
The judgement lines are where a reader should slow down. Three things in that draft need a human:
- "Market standard". That is an opinion, not a reading, and the assistant has no basis for it. A cap on indemnity combined with a consequential-loss exclusion is exactly the sort of term a lawyer should price for you.
- The missing clause. The prompt asked for clauses absent from the sub's version, yet the draft is silent on the fact that clause 7.4 of the firm's form, compliance with the site safety plan, has been deleted. Comparisons are biased towards what exists. Check absent clauses against a list, as in the planted-error test below.
- Who benefits. In the full output the assistant marked the retention change as neutral. It is not: it moves $1,920 of security out of your hands.
Sort the differences into those you can negotiate yourself (retention, payment days, claims notice, insurance, defects) and those that go to a lawyer (indemnity cap, consequential-loss exclusion, suspension rights, and the deleted safety clause). The pay-when-paid clause deserves its own read, since it decides who carries the client's payment risk. For a longer list of clause types an assistant handles badly, see which clauses AI flags and misses.
A one-page summary of the signed subcontract for site
A comparison tells you what changed. Once the subcontract is signed, the people running the job need something different: what the sub must do, by when, and what counts as an instruction. Say the negotiation settled at 5% retention released at practical completion, payment 21 days from a valid invoice, your 7-day claims notice, your $2M insurance with a certificate before starting, a 12-month defects period and the safety clause restored, with the sub's suspension right struck out on the lawyer's advice. The supervisor needs that on one page, in the order the job happens:
Summarise this signed subcontract for my site supervisor in plain English, under 250 words.
Order: start and finish; documents needed before starting; how changes must be instructed; payment dates; retention; delay and claims notices; defects period; what happens if the sub stops work or falls behind.
Give the clause number for every point. Quote the exact words for any deadline, amount or instruction rule.
Do not interpret or advise. If the contract does not cover a point, write "Not covered".A first draft, as an assistant might return it:
Electrical subcontract (signed version): site summary
Start and finish: 2 June to 14 August (cl. 3.1).
Before starting: $2M public liability certificate (cl. 9.2);
signed site safety plan (cl. 7.4).
Changes: should be agreed in writing (cl. 8.1).
Payment: applications by the 25th (cl. 4.1); paid 21 days
from a valid invoice (cl. 4.2).
Retention: 5%, released at practical completion (cl. 4.6).
Claims and delay notices: within 7 days of the event (cl. 6.3).
Defects: 12 months from practical completion (cl. 10.1).
If the sub stops work or falls behind: Not covered.Two lines need fixing, and both are the kind a quick read misses. "Should be agreed in writing" is softer than the clause, which says no change is carried out or valued unless your project manager instructs it in writing. The supervisor is the person most likely to say "go ahead" on site, so the summary must carry the exact words, which the prompt asked for and the draft skipped. "Not covered" on the last line is simply wrong: clause 11.4 lets you terminate for default on 7 days' notice, but it is headed "Termination", and the assistant was looking for "stop" and "suspend". Ask it to search for the idea rather than the word, and read the termination clause yourself. One line deserves a check even though it looks right: had the defects line said 6 months, the assistant would have been reading the sub's returned draft instead of the signed version, the wrong-version trap covered in the last section.
Key dates: extract the clauses, calculate the dates yourself
Missed dates cost more than bad drafting: a notice that goes out a day late, an insurance certificate that expired in July while the sub was still on site. An assistant is good at finding every date-bearing clause. It is poor at calculating dates, because it does not know whether "days" means calendar days or business days in your contract, and it rarely knows which holidays apply. So split the job: it extracts, you calculate.
List every date, deadline, notice period and recurring obligation in this subcontract. For each give: item, clause number, exact quoted wording, the trigger that starts the clock, the period or date, who must act, and whether the period is in calendar days, business days or "not defined".
Do not calculate any date. If a clause points to another document, list it as "external reference: [document name]".The sample extraction, ready to become a tracker:
| Item | Clause | Trigger and period | Alert you set |
|---|---|---|---|
| Sub's insurance certificate | 9.2 | Expires 30 June; the work runs to 14 August, a 45-day gap | Ask for the renewal by 16 June |
| Delay notice from the sub | 6.3 | 7 days from the event; type of day not defined | Ask the lawyer to define it; alert on every delay logged |
| Payment application cut-off | 4.1 | 25th of each month | Reminder three days before |
| Retention, first release | 4.6 | At practical completion | Alert 14 days before the target date |
| Retention, final release | 4.6 | End of the defects period | Alert 30 days before |
Check each quote against the contract by searching for the wording, and read the definitions clause for "business day". The difference matters. Take a notice due within seven days of an event on a Thursday. Seven calendar days ends the following Thursday. Seven business days ends on a Monday, eleven calendar days later, provided no holiday falls in between. A tracker built on the wrong reading gives you a false deadline in one direction or the other.
Once the table is right, put the alerts where you will see them. Google Calendar can import a CSV with Subject and Start Date columns, so a spreadsheet tab can become reminders in a few minutes; check which date format your calendar expects before importing. Insurance certificates deserve their own tracker, and tracking subcontractor insurance expiry sets one up.
Change orders: a site message becomes a priced draft
Change orders go wrong in a predictable way: the work starts on a text message and the paperwork follows weeks later, if ever. The assistant cannot fix that habit, but it can make the paperwork quick enough that nobody has an excuse.
It is Tuesday, 4:40 pm, and the client texts that they would like the kitchen island moved 600 mm towards the window, with two pendant lights added above it. You price it yourself: the electrician's six hours at $85, materials of $240, four hours of carpentry at $60, a 15% margin and two extra working days. Previous approved changes total $6,740. Then you hand the assistant your template and your numbers:
Draft a change order from the notes below using these headings: Change order number; Project; Date; Requested by; Description of change; Reason; Price breakdown (labour, materials, margin); Total; Effect on programme; Effect on contract sum; Approval and signature; Statement that work starts only after signature.
Rules: use only the figures I give. If a figure is missing write TO BE CONFIRMED. Do not describe any verbal agreement. Do not say work may proceed before signature. Keep it under 250 words.
Notes: client text at 4:40 pm Tuesday asked to move the kitchen island 600 mm towards the window and add two pendant lights over it. Electrician 6 h at $85. Materials $240. Carpenter 4 h at $60. Margin 15%. Two extra working days. Approved changes so far $6,740. Original contract sum $212,000. This is change order 3.The arithmetic the draft should contain: labour and materials come to $510 plus $240 plus $240, which is $990; a 15% margin adds $148.50; the change is $1,138.50. The revised contract sum is $212,000 plus $6,740 plus $1,138.50, which is $219,878.50. A typical draft reads:
Change order 3. Description: relocate the kitchen island 600 mm towards the window and add two pendant lights above it. Reason: client request, received Tuesday at 4:40 pm. Price: electrician $510; materials $240; carpentry $240; margin (15%) $148.50; total $1,138.50. Programme: two additional working days. Contract sum: original $212,000; approved changes $6,740; this change $1,138.50; revised $219,878.50. Work on this change starts only after the client signs below.
That draft is good, which is why the check matters. Before it goes out, confirm that the revised sum includes the earlier changes: a draft that forgot them would show $213,138.50, and nobody would notice until the final account. Look for any phrase such as "as discussed" or "work will begin immediately", which implies agreement the contract may not recognise. Check that the margin has been applied once and not again to a contingency the assistant invented. Make sure every figure appears the same way in the breakdown and the total, since a draft will sometimes round one and not the other.
If the electrician's price came from a subcontractor, ask for a written quote valid for a fixed period, and make sure the change order you send the client does not promise a number before the sub's price is firm. Your own subcontract should say how a change reaches a sub and who is allowed to instruct it; if it does not, that is a question for the lawyer. Turning site messages into change orders goes deeper on the capture side.
Passing the change down to the electrician
The client's signature covers your side of the change. The electrician still needs an instruction that follows your subcontract's change clause, and on small jobs it usually goes out as a text like this one:
"Island's moving 600 towards the window and they want 2 pendants over it. Can you sort Thursday? Cheers"
The same assistant can draft the written version from change order 3, the electrician's quote and the clause number, and you send it only after the client has signed. Something like this:
Instruction 3 under the electrical subcontract, issued under clause 8.1. Scope: move the island power supply 600 mm towards the window and add two pendant light points above the new island position, as marked on the attached plan. Price: $510, as in your written quote of [date]. Timing: complete by [date]; no change to your finish date. This instruction follows the client's signed change order 3. Please confirm receipt by reply.
The text asked for work with no scope, price or authority attached, so if the client had then declined to sign, you could end up paying for work you cannot bill. The written instruction ties the sub's price to the client's approval and names the clause the sub signed. Check one thing before it goes: the scope words must match the change order exactly, because a sub who fits three pendants against a client order for two has started your next dispute.
A change-order log that keeps the contract sum honest
The $6,740 of approved changes in the prompt came from somewhere, and that somewhere should be a log rather than memory. A filled-in version for this job:
| No. | Description | Value | Days | Status | Sub instructed |
|---|---|---|---|---|---|
| CO1 | Replace rotten subfloor found under the bathroom; plumber refits the WC | $4,210.00 | 1 | Signed by client | Plumber, after signature |
| CO2 | Wider sliding door to the garden, client upgrade | $2,530.00 | 0 | Signed by client | Not needed (own crew) |
| CO3 | Move the kitchen island 600 mm; add two pendants | $1,138.50 | 2 | Sent, awaiting signature | Not yet |
Approved changes are $4,210 plus $2,530, which is $6,740, the figure in the prompt. The contract sum today is $218,740 and becomes $219,878.50 only when the client signs change order 3; the programme carries one approved extra day and two pending. Paste the log into the prompt instead of typing "approved changes so far" from memory, and the draft picks up the right figure every time. Read the last column every Friday: a sub instructed against a change order the client has not signed is money at risk.
What a lawyer still reviews, and a rule for deciding when
Ask a lawyer once, properly, to review your standard subcontract and your change-order template. After that, the work is deciding which deviations need to go back. These are the clause types where a lawyer earns the fee, with the reason each one needs a person:
- Indemnity and liability caps. Who pays when something goes wrong, up to what limit. Some places restrict how far an indemnity can reach.
- Exclusions such as consequential loss. Short clauses with large effects, which assistants tend to wave through as standard.
- Payment mechanics. Pay-when-paid versus pay-if-paid wording, set-off rights, retention release triggers, and payment rules the law sets that may override the contract.
- Termination and suspension. Notice periods, cure periods and what happens to materials and money when the relationship ends.
- Incorporation by reference. Wording such as "the terms of the main contract apply" imports clauses the assistant may never have seen.
- Delay damages. Whether you can pass a client's delay charges down to a sub, and whether the sub has remedies against you.
- Dispute resolution. Governing law, venue, mediation or arbitration steps, and any statutory dispute route.
- Worker status and licensing. Whether the sub is genuinely independent and properly licensed is a legal and tax question.
A threshold rule keeps the habit consistent. These tiers are illustrations, and you should set the numbers with your own lawyer.
| Tier | When it applies | Who reviews |
|---|---|---|
| 1 | Repeat sub, your form unchanged, under $10,000 | You, using the assistant's comparison |
| 2 | New sub, or changes to price, time or insurance terms, $10,000 to $50,000 | You negotiate; the lawyer sees only the clauses marked as risk |
| 3 | Above $50,000 or 10% of annual turnover, or any change to indemnity, liability, termination, set-off or dispute terms, or any term the assistant called unusual or unsure | Lawyer reviews the full contract |
| 4 | A claim, a notice of default or a termination | Lawyer first; do not let an assistant draft the reply |
The electrical subcontract above is $38,400, under the $50,000 line, yet it lands in tier 3 because it changes the indemnity and the suspension rights. Terms beat value. When you brief the lawyer, send the whole contract with its schedules, your standard form, the comparison table with clause numbers, the value and key dates, and your three biggest worries. Asking for answers by clause turns the assistant's table into a checklist the lawyer can work down.
Five planted errors: a test before you trust any tool
Before an assistant or a contract platform sees a live subcontract, test it on one you already know. Copy your standard form and plant five problems: cut the retention from 10% to 5%; delete the insurance clause; change "pay when paid" to payment on demand; stretch the claims notice from 7 days to 21; add a clause that makes you waive consequential loss. Then run the comparison and score it.
| Planted change | Result | Note |
|---|---|---|
| Retention cut from 10% to 5% | Found | Money effect calculated correctly |
| Insurance clause deleted | Missed | Absent clauses are the weak spot |
| Pay-when-paid replaced by payment on demand | Found | Risk to you not explained |
| Claims notice 7 days to 21 | Found | None |
| Consequential-loss waiver added | Found, called "standard" | Needs a lawyer, not an opinion |
This illustrative run found four of five, missed one omission, mislabelled one risk and raised three false alarms on clauses that had not changed. The verdict is a sensible one: use the tool as a first-pass reader and a source of questions, and keep a human checklist for omissions. If a tool misses more than one planted error, use it for summaries only. Repeat the test after any large change to the tool or your form.
Tools: what they cost and where each one fits
For most small contractors, a general assistant, a lawyer-approved standard form and a tracker sheet cover the work. Dedicated contract platforms earn their fee when you hold hundreds of live contracts or need alerts without anyone remembering to look. Prices below are what each vendor's own page showed on 29 October 2026, in USD.
| Option | What it does | List price | Catch |
|---|---|---|---|
| Claude or ChatGPT, with a saved Project | Summaries, comparisons, date extraction, change-order drafts | Claude Pro $17 a month billed annually ($20 monthly); Claude Team $20 a seat annually ($25 monthly), two-seat minimum; ChatGPT Plus about $20 a month | Confidentiality depends on the plan. Scanned PDFs may need the Word version or text recognition first. |
| ContractSafe | Contract repository with AI data extraction and contract chat; AI contract review described as spotting "risks and omissions" on its top plan; reminders for payment dates, milestones and renewals | "Starting at $450/month" (in the page title), unlimited users, priced by features and number of active contracts | Not construction-specific. Plan prices beyond the entry figure sit in a PDF. |
| Lexilio | Contract analysis with a risks and obligations register on Starter; a notice and deadline tracker on Professional; its home page also describes checking subcontracts against the main contract for flow-down gaps | Starter $29 a month (one seat, up to 25 contracts, one project); Professional $299 (10 seats, 250 contracts, 20 projects); Enterprise $1,999 (unlimited, adds cross-document conflict detection) | Its home page says "Engineered for Tier 1 & 2 contractors". The 7-day trial needs a card and starts the plan automatically. I saw no plain "not legal advice" line on that page, so read its AI disclaimer first. |
| Document Crunch | Calls itself an "AI Risk Intelligence Platform Built for Construction" and says every flag is traced to a clause | No price on its page; free trial offered | Ask for a price and trial it on your own subcontract. |
JobTread also lists change orders among its features, so a firm already on it can raise them where the job costs live. Whichever route you choose, price the tool against the number of contracts you actually sign, and be wary of any page that promises to replace legal review. The planted-error test settles most arguments about whether a platform is worth the money.
Three ways contract summaries mislead
Most bad summaries trace back to three causes, and each can be checked in a few minutes.
- Flipped parties. In a subcontract, "Contractor" means the main contractor, while in a client contract it means you as the builder. An assistant that has read both can attribute a duty to the wrong side. Ask it to restate each obligation as "[named party] must...", then check the first few against the text.
- Missing pieces. Schedules, riders and incorporated documents carry key terms: the price, the programme, the insurance limits. If you upload the body and not the schedules, the summary will confidently describe an incomplete deal. Count the pages in the contract against the pages you uploaded.
- The wrong version. Subs return PDFs of different drafts. Ask the assistant to state the document's version or date, check it against your email trail, and ask for the Word file when you can, because tracked changes show what moved.
For firms that want a fuller routine, the subcontractor agreement clauses an assistant can draft and the payment notice and deadline tutorials cover the next two jobs. Keep one rule above the rest: the assistant reads, you decide, and a lawyer reviews whatever could cost you the job.
Questions to settle before AI touches a contract
Is it safe to upload a subcontract to ChatGPT or Claude?
It depends on the plan and on what the contract says about confidentiality. Business plans such as ChatGPT Business and Claude Team do not train on your content by default, while consumer plans have a training switch in privacy settings you should check. If in doubt, replace party names, addresses and prices with placeholders before you paste anything.
Will an AI-drafted change order stand up in a dispute?
Whether it binds anyone depends on your contract's change procedure and on signatures, not on how it was drafted. The usual failure is working on a verbal instruction before anything is signed. Have a lawyer approve your change-order template once, then use the assistant to fill it from your own figures.
What should I send my lawyer along with the AI summary?
Send the full contract including every schedule, your standard form, the comparison table with clause numbers, the contract value and key dates, and the three questions that worry you most. Ask for answers by clause. The summary helps the lawyer start in the right place. It should never replace reading the document.
How do I stop an assistant missing clauses that are absent?
Give it a checklist of clauses you require, such as insurance, notice, retention, defects and safety compliance, and ask it to mark each present or absent with a quote. An assistant comparing two documents tends to describe what is there. A checklist forces it to report what is not.
Further reads
- AI Construction Contract Review Software: What Builders Should Test — What to test in contract-review software before paying.
- AI in Contracting: Subcontractor Paperwork Chasing Checklist — The paperwork to collect from subs before they start.
- How Small Builders Use AI to Price Variations and Change Orders — Pricing variations from site messages on small jobs.
- AI Contract Management Software Demo: 10 Questions for Contractors — Ten demo questions for contractors, each with an example: data location, clause accuracy, retention dates, scans, export, price and cancellation.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: ContractSafe, Lexilio, Document Crunch, JobTread and Anthropic Claude vendor pages (read 29 October 2026); OpenAI and Anthropic plan and data-use details from vendor pages. General information only, not legal advice.