Most freelance payment fights are not about bad clients or bad work. They are about a missing sentence. The client assumed two more revisions were included; you assumed they were extra. Nobody wrote it down, so now it is a negotiation at the worst moment: after the work is done.
A freelance contract does not need to be long or written in legalese. It needs to answer, in advance, every question that turns into an argument later. This guide covers the 10 clauses that do exactly that. One framing note first: this is general information for a US audience, not legal advice. Contract rules vary by state and jurisdiction, so have a lawyer review your template once, then reuse it.
The quick version
A freelance contract should cover 10 things: (1) scope of work with explicit exclusions, (2) payment terms and schedule, (3) a deposit, (4) a revisions cap, (5) a kill fee for cancelled projects, (6) late fees, (7) IP transfer on final payment, (8) an independent-contractor status line, (9) termination notice, and (10) a dispute path. Each clause answers a specific question before it becomes a fight. Have a lawyer review your template once, then reuse it on every project with only the project-specific details changed.
Why the contract is your payment tool, not just your legal tool
Freelancers often treat a contract as something you pull out when things go wrong. Its real job is prevention. According to the Intuit QuickBooks 2025 US Small Business Late Payments Report, 56% of US small businesses are owed money from unpaid invoices, averaging about $17,500, and 47% report invoices already more than 30 days past due. Many of those situations start as ambiguity, not malice: unclear terms give a slow-paying client room to stall.
A contract closes that room. When the payment date, the late fee, and the cost of cancellation are in a document the client signed before work began, the client either pays on the agreed terms or visibly breaks an agreement they signed. Clients care about the difference.
The 10 clauses, one by one
1. Scope of work, with exclusions
Describe what you will deliver in concrete, countable terms: "a five-page website (Home, About, Services, Blog, Contact), responsive, launched on the client's hosting." Then add the part most freelancers skip: what is NOT included. "Copywriting, logo design, and post-launch maintenance can be quoted separately." Exclusions are where scope creep goes to die. If a request is not on the list, it is a new quote.
2. Payment terms and schedule
State the total, currency, due dates, and payment window. For a $6,000 project, a common structure is milestone billing: 50% ($3,000) to start, 30% ($1,800) at design approval, 20% ($1,200) on delivery. Then set how long the client has to pay each invoice; net 15 is a reasonable freelancer default, and the tradeoffs are covered in net 30 vs net 15 payment terms. List accepted payment methods too, so there is no "we only pay by check" surprise.
3. Deposit
Require money before work begins. A deposit funds your early weeks and filters out clients who were never going to pay. State the amount, when it is due, and whether it is refundable. For most service work, deposits are non-refundable once work has begun, because they compensate for the calendar time you reserved. Our guide to deposit invoices and upfront payments covers how to structure and bill them.
4. Revisions cap
"Unlimited revisions" is how a two-week project becomes a two-month project at the same price. Cap it: "This price includes two rounds of revisions per deliverable. Additional rounds are billed at $95 per hour." Define a "round" as one consolidated list of changes, not a drip of emails, so the cap actually caps something.
5. Kill fee
Projects get cancelled for reasons that have nothing to do with you: budgets vanish, teams reorganize, priorities shift. A kill fee clause says what happens then. A common structure pays you for all work completed plus a percentage of the remaining balance; on a $4,000 project cancelled halfway through, you might invoice the completed milestones plus a 30% kill fee on the unbilled remainder. How to size the percentage by project stage is covered in our guide to kill fees for cancelled projects.
6. Late fees
A late fee clause gives your due date teeth. Common practice is 1.5% per month on overdue balances, but a late fee is generally only enforceable if the client agreed to it in advance, which is exactly what the contract does. State the rate, when it starts, and repeat the same term on every invoice; see our post on invoice late fees for wording. Maximum allowable rates vary by state, so verify yours.
7. IP transfer on final payment
This is the freelancer's strongest lever, and many contracts get it backwards. Do not transfer ownership on delivery. Transfer it on payment: "All intellectual property rights in the deliverables transfer to the client upon receipt of final payment in full. Until then, all rights remain with the contractor." Now a client using your unpaid work is not just late, they are using work they do not own. That sentence resolves more standoffs than any collections letter.
8. Independent-contractor status line
A short clause stating that you are an independent contractor, not an employee, responsible for your own taxes, equipment, and schedule. This sets expectations about control and availability and supports the correct tax treatment of the relationship. Worker-classification rules depend on the actual working relationship, not just the label, so treat this clause as necessary but not sufficient, and verify current IRS and state guidance for your situation.
9. Termination notice
Either side should be able to exit, but not instantly and not for free. A typical clause: "Either party may terminate with 14 days' written notice. The client will pay for all work completed through the termination date, plus any applicable kill fee." This turns a ghosting into an orderly wind-down with a final invoice attached.
10. Dispute path
Decide now how disagreements get resolved, while everyone still likes each other. A simple escalation works: good-faith negotiation, then mediation, then small claims court or arbitration in a named state and county. Naming the venue matters, because arguing about where to argue is its own expensive fight. The right options vary by state, so this clause is worth your lawyer's attention.
The clauses at a glance
| # | Clause | The fight it prevents |
|---|---|---|
| 1 | Scope + exclusions | "I thought that was included" |
| 2 | Payment terms + schedule | "We pay all vendors in 60 days" |
| 3 | Deposit | Working for weeks with zero committed money |
| 4 | Revisions cap | Round seven of "just one more tweak" |
| 5 | Kill fee | Cancelled project, wasted calendar, no pay |
| 6 | Late fees | Due dates treated as suggestions |
| 7 | IP transfer on payment | Client uses the work, never pays |
| 8 | Contractor status | Employee-style demands, tax confusion |
| 9 | Termination notice | Ghosting mid-project |
| 10 | Dispute path | Arguing about where and how to argue |
Make the contract, quote, and invoice tell the same story
The contract sits in a chain of documents, and payment fights often start when the links disagree: the quote says one price, the contract says another, and the invoice invents a third.
Keep them synchronized. The quote or estimate comes first and states scope, price, and payment schedule in summary form. The contract references the quote by number and date ("as described in Quote #2026-014") and adds the legal terms: revisions, kill fee, IP, termination. Each invoice then references the contract or quote number, bills the milestone exactly as scheduled, and repeats the payment window and late fee terms the client already agreed to.
When all three documents carry the same numbers and terms, a client can never say "that's the first I'm hearing of this." If a dispute escalates, the matching trail is strong evidence of what was agreed, which matters because an invoice by itself usually is not a contract.
Write it once, reuse it forever
Build one template with all 10 clauses, pay a lawyer in your state to review it once, then reuse it, changing only the project-specific details: scope, price, schedule, dates. A one-time review costs far less than a single collections headache, and every project starts on terms you already trust.
The same reuse logic applies to your billing documents. With Invoity's free invoice generator you can create the quote, the deposit invoice, and each milestone invoice with consistent numbering and matching payment terms, then download each as a PDF instantly, no signup needed. The freelancer invoice template is a good starting point, and the e-signature option lets clients sign off on quotes before work begins.
Frequently asked questions
Does a freelance contract need to be written by a lawyer?
No, but it should be reviewed by one. Draft the 10 clauses yourself in plain English, then pay a lawyer licensed in your state to review the template once. After that, reuse it for every project, changing only scope, price, and dates. Enforceability rules vary by state, so a local review is worth the cost.
Is an email agreement enough, or do I need a signed contract?
An email exchange that clearly captures the offer, price, and acceptance can form a binding agreement in many situations, but it rarely covers revisions, kill fees, IP, or disputes. A signed contract, even a short one, covers all ten pressure points and is easier to rely on if a project goes sideways. At minimum, get written confirmation of scope, price, and payment schedule before starting.
What is the most important clause for actually getting paid?
IP transfer on final payment, closely followed by the deposit. The deposit means you never work entirely on faith, and the IP clause means an unpaid client does not own the work they are using. Together they flip the default: instead of you chasing money after delivery, the client has concrete reasons to pay on time.
Should my invoice repeat the contract terms?
Repeat the payment-critical ones: due date, payment window, accepted payment methods, and the late fee term. Reference the contract or quote number so the paper trail connects. Never introduce new terms on an invoice; terms the client first sees after the work is done are generally hard to enforce.