Five years of freelancing and exactly one uncomfortable contract dispute have given me a morbid hobby: collecting the clauses that quietly drain money from people like me. The dangerous ones are almost never the obviously evil ones. They're the clauses that read as perfectly reasonable on the first pass and contain a single word — 'unlimited,' 'concepts,' 'industry' — that changes who's holding the risk. Here are the five I hunt for now, and the part of the Contract Red-Flag Spotter for Faster, Cheaper Lawyer Review prompt that catches each one for me.
1. The unlimited-revisions clause
'Revisions as necessary until the client is fully satisfied,' with no number and no hourly rate attached, is a budget bonfire waiting for a match. 'Satisfied' has no objective definition, which means the work ends when they say it ends, not when the deliverable meets the spec. I once did seven rounds of revisions on a logo for a client who simply enjoyed having opinions. The Red-Flag Spotter reliably tags this pattern as High Priority and tells me to ask for a defined revision count plus an hourly rate for anything beyond it.
2. The broad IP assignment
There is a universe of difference between 'the deliverables described in this agreement' and 'all work product, concepts, and ideas.' The second version can sweep up methodologies, templates, and frameworks you reuse across every client. This is the exact clause that bit me in year two, so it's the first thing I look for, and it's reliably the first thing the prompt's High Priority bucket surfaces. The fix is usually a one-line edit narrowing the assignment to the named deliverables — and most clients agree the moment you ask, because they never wanted your whole toolkit, just their logo.
- Unlimited revisions with no cap and no extra rate
- IP assignment covering 'concepts and ideas' instead of just the named deliverables
- Indemnification with no liability cap, where one bad claim can exceed the whole contract value
- Non-solicitation language broad enough to cover the client's entire industry, not just their staff
- Auto-renewal clauses with a punishingly short cancellation-notice window
3, 4, and 5: the expensive trio
Uncapped indemnification is the scariest of the bunch — it means a single claim could cost you more than the entire project paid, which is how a $5,000 job becomes a $50,000 problem. A non-solicitation clause drawn around the client's whole industry can quietly forbid you from working with anyone similar for a year, which for a niche freelancer means no work at all. And auto-renewal with a five-day notice window is how a one-off project becomes an accidental annual subscription you forgot to cancel. None of these scream 'danger' on a casual read, which is the entire reason they keep working on people.
How the spotter actually catches them
I paste the contract, set my role to 'service provider,' and let Claude Sonnet 4.6 do the first read. The High Priority section nearly always surfaces the same handful of patterns above, with a short quote so I can find the clause instantly and a ready-made question I can copy-paste to the other side. But the section that has saved me actual money twice is Missing Clauses — once it flagged that a contract had no dispute-resolution mechanism at all, meaning my only recourse for a disagreement would have been a full lawsuit. I added a mediation step before signing, and a year later, when there was a small disagreement, that one clause kept it out of court.
The clause that isn't on the list but should scare you anyway
There's a sixth pattern I've started watching for that doesn't fit neatly into a single word: the payment-terms clause that pairs net-60 with a 'subject to client approval of all milestones' trigger. On paper it's two reasonable-sounding sentences. In practice it means you can finish the work, invoice it, and then wait two months for money that only starts the clock once a busy client gets around to 'approving' a milestone they have no deadline to approve. I once waited 94 days for a payment that was technically never late, because the approval that started the net-60 clock kept not happening. Now I ask the spotter to read payment terms specifically through the lens of 'when, exactly, does the clock start,' and it reliably calls out approval-gated triggers as worth a conversation.
The point of all six is the same: the damage is hidden in language that reads as normal, and the only defense is a careful first pass that knows the patterns. A human reviewer who's tired at 6pm misses these. A structured prompt that's been told exactly what to hunt for does not get tired, and it quotes the clause so you can't talk yourself out of what you just read.
This is not a lawyer and it doesn't pretend to be — it's a first pass that makes the lawyer conversation faster and the contract less scary to a non-lawyer. If you want to stop signing things you haven't really read, grab the Contract Red-Flag Spotter for Faster, Cheaper Lawyer Review prompt on Prompt Dock and run your next client agreement through it. For a single gnarly clause rather than a full contract, I switch to my Plain-English Contract Clause Translator with Red-Flag Triage prompt — but to learn which five (okay, six) patterns to fear in the first place, start here.