AI Contract Review for Contractors: Build a Claude Skill That Flags Risky Clauses Before You Sign
A subcontract shows up at 4 p.m. and the GC wants it back by morning. Here is how to set up Claude to flag pay-if-paid, indemnity, retainage and notice traps in ten minutes, what it costs and where you still need a lawyer.
AI contract review for contractors
A general contractor emails a 38-page subcontract at 4 p.m. and wants it signed by the morning so you can mobilize Monday. You skim the scope, check the price, sign the last page and find out four months later that you agreed to pay-if-paid, a seven-day notice window for claims and an indemnity clause that makes you cover the GC's own mistakes. Most small subs do not have a lawyer on call for every contract, and most do not read every page. That is the gap an AI review fills.
It does not replace a construction attorney. It does make sure you never sign blind again. A builder documented on this site, in Reusable AI Skills That Review Construction Contracts and Write Scopes of Work in Minutes, turned contract reviews, estimate checks and scopes of work into repeatable Claude skills that any builder on the team can run. That listing is a methodology walkthrough and reports no measured time savings, so treat it as a pattern to copy, not a promised result. The pattern is simple enough to set up this week.
Why a skill beats pasting the contract into a chat
You can drop a PDF into any chatbot and ask "anything bad in here?" You will get a polite summary that misses the clauses that matter to your trade, because the model does not know your walk-away rules. A roofer cares about warranty length and weather delays. An electrician cares about who pays for utility coordination. A drywall sub cares about backcharges for other trades' damage.
A Claude skill is a saved set of instructions, plus any reference files, that Claude loads when the task calls for it. As of November 2026 skills are available on Free, Pro, Max, Team and Enterprise plans, and they need the code execution setting turned on. You write your checklist and rules once. Every contract after that gets the same review, in the same format, whether you run it or your office manager does.
A worked example: a three-person electrical sub
Picture an electrical subcontractor with two crews doing tenant improvements, about 40 subcontracts a year from eight different GCs. Contracts range from 6 to 60 pages, and the owner reads them at night. Twice in the last two years a clause bit them: once a pay-if-paid that held up 31,000 dollars for five months when the owner stalled, once a backcharge clause that let a GC deduct cleanup costs with no notice.
The owner spends one evening building the skill. The checklist has 12 items: payment terms and pay-if-paid language, retainage percentage and release, indemnity scope, insurance requirements and additional insured wording, notice periods for delays and claims, change order process, backcharges, liquidated damages, no-damage-for-delay, warranty length and start date, flow-down of the prime contract, and termination for convenience. Each item has a rule: red if pay-if-paid appears, amber if retainage is over 5% or released later than substantial completion, red if indemnity covers the GC's own negligence, and so on.
Now a new subcontract takes about ten minutes: upload, read the red and amber flags with the quoted section numbers, check two or three of them against the actual pages, and send the GC a short markup request the skill drafts. Anything over 250,000 dollars, or anything with a red flag the GC refuses to change, goes to the attorney with the memo attached, which also makes that attorney's review shorter. The numbers in this example are illustrative. Replace them with your own contract count and history.
Step by step: build the skill this week
Step 1: Write your walk-away list from your last bad contract
Before you touch any AI tool, sit down with the last two contracts that cost you money and write what went wrong. Then add the standard trouble spots: pay-if-paid versus pay-when-paid, retainage, indemnity, insurance, notice periods, change orders, backcharges, liquidated damages, no-damage-for-delay, warranty, flow-down and termination. For each, write one line saying what is acceptable, what needs negotiating and what makes you walk. This list is the whole value of the skill. If you have a construction attorney, pay for one hour to review it once.
Step 2: Set up Claude and turn on code execution
Sign up for Claude Pro (20 dollars a month, or 17 dollars a month billed annually, as of November 2026). Skills work on the free plan too, but you will hit usage limits fast on long PDFs. In Settings, open Capabilities and turn on "Code execution and file creation" (in the newer layout it is called "Create and edit files"). Skills will not run without it. Before uploading any client contract, go to Settings, then Privacy, and decide whether to turn off "Help improve Claude," which controls whether your chats on consumer plans can be used for model training. Team and Enterprise plans are not trained on by default.
Step 3: Write the skill file
Create a folder called contract-review and inside it a file called SKILL.md. At the top, give it a name and a one-line description such as "Reviews construction subcontracts against our walk-away rules and drafts a markup request." Below that, paste your checklist from Step 1 and these instructions: "For each checklist item, quote the exact clause and its section number. If an item is not in the contract, say NOT FOUND. Rate each item red, amber or green using the rules. Never summarize a clause without quoting it. End with a short email to the GC asking for changes to every red item and the two most important amber items." Zip the folder.
Step 4: Upload the skill
In Claude, go to Customize, then Skills, click the plus button, choose Create skill, then Upload a skill, and select the zip file. The folder name has to match the skill name, and the folder must contain the SKILL.md file. Once it shows in your list, make sure it is toggled on.
Step 5: Test it on three old contracts you already know
Do not trust it on a live contract first. Run it on three contracts you have already signed and know well, including the one that cost you money. Check every red and amber flag against the page it quotes. Check that it did not say NOT FOUND for a clause you know is there. If it misses something, add a sentence to the skill about where that clause usually hides ("Payment terms are often in an exhibit or rider, not the main body"). Re-upload and run again until it catches what you would catch.
Step 6: Use it on every new contract and log what you negotiate
For each new subcontract, upload the PDF along with your bid and scope letter and ask Claude to "review this subcontract." Read the flags, verify the two or three that matter most on the actual pages and send the markup email in your own words. Keep a simple sheet of which GCs accepted which changes. After a year, that sheet tells you which GCs to bid aggressively and which to price for risk.
What this costs
Claude Pro is 20 dollars a month, or 17 dollars a month on annual billing (200 dollars up front), as of November 2026. Team plans cost more per seat and keep your data out of training by default, which is worth it if several people handle contracts. Your setup time is one evening for the checklist and an hour or two to build and test the skill. An hour with a construction attorney to review your walk-away list is money well spent and far cheaper than having every contract reviewed. Compare that to one bad pay-if-paid clause holding up five figures for months.
Where it breaks and when not to rely on it
AI can misread a clause, miss a clause buried in an exhibit or rider, or quote the right section and summarize it wrong. That is why the skill quotes exact text and you check the important flags against the page. It also knows nothing about your state's laws. Pay-if-paid enforceability, lien deadlines and anti-indemnity statutes vary by state, and the skill cannot tell you what a court would do. This is not legal advice, and neither is the skill's output.
Do not rely on it alone for large contracts, design-build work, anything with a performance bond you have not seen before, or a contract where the GC refuses every change. Those deserve a lawyer. And if a contract includes confidential owner information, check whether you are allowed to upload it to any outside tool before you do.
Frequently Asked Questions
Can AI review a construction contract?▾
It can read a subcontract, quote the clauses on your checklist and flag the ones that break your rules in a few minutes. It cannot give legal advice or apply your state's law reliably, so use it to make sure you never sign blind and send big or unusual contracts to a lawyer.
What clauses should a subcontractor look for before signing?▾
The usual trouble spots are pay-if-paid language, retainage and its release, indemnity scope, insurance and additional insured requirements, notice periods for delays and claims, backcharges, liquidated damages, no-damage-for-delay, warranty terms, flow-down of the prime contract and termination for convenience.
Is Claude or ChatGPT better for contract review?▾
Either can read a contract. What matters more is a saved checklist with your own rules so every review is consistent. Claude's skills let you save that checklist once and run it on every contract, and they work on Free, Pro and paid team plans as of November 2026.
Is it safe to upload contracts to Claude?▾
On consumer plans, check the "Help improve Claude" setting under Settings and Privacy, which controls whether chats can be used for training. Team and Enterprise plans are not used for training by default. Check your contract's confidentiality terms before uploading.
How much does AI contract review cost a small contractor?▾
About 20 dollars a month for Claude Pro, or 17 dollars on annual billing, as of November 2026, plus an evening to write your checklist.