Most freelancers treat contracts as paperwork. The freelancers who get paid on time treat them as a system. Late-payment and non-payment trouble is widespread enough that second-hand industry figures put it at the majority of freelancers at some point — the exact numbers are soft, but the direction is not. Here are the ten clauses that separate the freelancers who get paid from the ones who chase invoices, drawn from collective practitioner experience. (Practical guidance, not legal advice — for large engagements, pay a local attorney to review your template.)
1. Scope: what exactly are you delivering?
Numbered deliverables, verifiable outcomes, acceptance criteria. "Migrated checkout flow" is not scope. "Checkout flow migrated to Stripe, handling 500 concurrent users, sub-2-second response, verified by load test" is scope. If it is not written down, it does not exist.
2. The out-of-scope list
The mirror of clause 1, and the highest-leverage block of text in the contract. List what you are NOT doing. Every scope dispute you will ever have is a sentence that should have been here.
3. Payment terms with a real deposit
Total, schedule, method, currency — and a 30 to 50 percent deposit upfront, non-negotiable, before work begins. A client who will not pay a deposit is telling you politely that they will not pay the final invoice either.
4. Deadlines on both sides
Your phase deadlines plus theirs: feedback within 5 business days, assets by agreed dates. Add a deemed-acceptance provision — if the client does not reject a deliverable within 15 business days, it is accepted. One unresponsive client can otherwise stall your cash flow indefinitely.
5. Revision limits
State the number of revision rounds per deliverable, and define the line between a revision (correction inside the agreed scope) and a new project. The "just make the text bigger" pattern is how four free favors become a second unpaid job.
6. Change orders in writing, always
Client requests change, you provide a written estimate, client approves in writing, then work begins. Verbal change orders evaporate the moment there is a dispute — which is exactly the moment you need them.
7. A kill fee
If the client cancels mid-project: 25 to 50 percent of the remaining contract value, plus payment for work performed through termination. Either side can terminate with written notice. The fee makes endings orderly instead of catastrophic.
8. IP transfer timing
State explicitly when intellectual property transfers: on final payment (safer for you) or on delivery. Refuse IP transfer before payment, and refuse blanket assignment of your pre-existing IP, methods, and tooling.
9. Late-payment terms
Interest on overdue invoices plus fixed compensation per late invoice. But prevention beats enforcement: deposits, milestone invoicing, and IP transfer on final payment only.
10. A liability cap
Cap your liability at the fees paid under the contract, and exclude consequential loss. One bug in a client's revenue system should not be able to bankrupt you.
Phrases that should make you flinch
Watch for these in client-drafted contracts: "as may be reasonably requested" (unlimited scope in reasonable clothing), "contractor shall ensure client is satisfied" (an infinite revision clause), "pay-when-paid" (you underwriting someone else's credit risk for free), and uncapped liability. Strike or rewrite every one.
This is one chapter of a bigger system. I put together The Freelancer Client-Acquisition Kit — 37 pages covering outreach scripts, proposal structure, 2026 rate tables, contracts, retainers, and referrals, with every data point labeled by source and evidence strength. If this article saved you one bad contract, the kit will save you ten: https://cjettoostudent.gumroad.com/l/qfckgb
Top comments (0)