Most freelancers learn what should be in a contract the hard way: by working a project that doesn't have one, or working under one written by the client. Both ways are expensive.
A good freelance contract isn't long, but it covers a specific set of risks. Each clause exists because someone, somewhere, lost real money because it wasn't there.
Scope of work: the foundation
Every dispute eventually traces back to scope. 'We agreed I'd design a logo' turns into 'we agreed you'd design a logo, a brand book, social templates, and three pitch decks.' The client believes their version. You believe yours. Neither of you wrote it down.
A scope section needs three things:
- What's included. Specific deliverables, with names and quantities. 'Logo design' is vague. 'Primary logo, one secondary mark, two color variants, files delivered in SVG and PNG at standard sizes' is specific.
- What's explicitly excluded. This sounds defensive — write it anyway. 'Brand strategy, naming, and social asset templates are not included in this engagement and would be quoted separately.'
- How many revisions are included. Two rounds is standard for design work. State what happens after: 'Additional revision rounds beyond the two included are billed at $X per round.'
Specificity here is what saves you from scope creep. Without it, every 'small tweak' the client requests is a discretionary act of generosity on your part. With it, every tweak past the agreed scope is a contractual change.
Payment terms and milestones
Three things to specify:
- The total fee, and what it covers. '$8,000 for the scope described in Section 2.'
- The payment schedule. For projects over two weeks, split into milestones. 50/50 is the floor; 30/40/30 or 25/25/25/25 works for longer engagements.
- Late payment consequences. 'Invoices unpaid 14 days past due will accrue interest at 1.5% per month.' You will rarely enforce this, but its presence is what makes late payment uncomfortable for the client.
A kill fee deserves its own line. If the client cancels mid-project, what do you keep? Standard is 'all milestones paid to date are non-refundable, plus 50% of the next unstarted milestone.' It's not punitive — it's the cost of you having reserved the time.
Intellectual property transfer
When does the client own the work? The wrong answer is 'when they pay you.' The right answer is 'when the final invoice is paid in full.'
A short clause does this:
All intellectual property created under this agreement transfers to the Client upon receipt of final payment. Until then, ownership of all deliverables remains with the Contractor.
This single sentence is the most powerful collection tool you have. A client who hasn't paid doesn't own what you made. They can't use the logo, the code, or the copy until they wire the money. Most freelancers skip this clause and then wonder why clients drag payment after delivery.
Also worth including: a portfolio clause. 'Contractor retains the right to display the work in their portfolio and marketing materials.' Without it, you technically need permission to put the project on your website.
Revisions and additional work
A revision is a change within scope. Additional work is a change outside scope. Clients conflate the two on purpose. The contract should not.
Revisions are included as specified in Section 2. Additional work, defined as any deliverable or change outside the scope of this agreement, will be quoted separately and billed at the Contractor's then-current rate.
When the client emails to ask for 'just one more page on the site,' you respond with a one-line quote. They either approve it (more revenue) or they retract the request (no scope creep). Either way you don't do it for free.
Termination
Either party should be able to terminate, but the consequences should be clear.
Either party may terminate this agreement with 14 days written notice. Upon termination, Client agrees to pay for all work completed through the termination date. Deliverables produced will be transferred to the Client upon receipt of all outstanding payments.
The 14-day notice protects you from being dropped on Friday afternoon with three weeks of work in progress. The payment clause ensures the client pays for what they got, even if they don't use it.
Liability and indemnification
This is the boring section everyone skips. Read it once, then use the same language forever:
Contractor's total liability under this agreement is limited to the total fees paid by Client to Contractor. Contractor is not liable for indirect, consequential, or incidental damages.
This is your shield against a client whose product fails to launch suing you for lost revenue. Most freelance work is low-risk for this kind of claim, but a single bad client can end your business if you're on the hook for their losses. The cap-at-fees-paid clause is non-negotiable.
What you don't need
Contracts get long because lawyers get paid by the page. You don't need force majeure clauses unless you're working in a regulated industry. You don't need arbitration clauses unless you've consulted a lawyer about your jurisdiction. You don't need NDAs as part of the master contract — keep those separate so you can sign NDAs without renegotiating the work agreement.
A three-page contract that covers the six items above is bulletproof for 95% of freelance work. The other 5% needs a lawyer. Knowing which 5% you're in is what experience teaches you.
Sign before you start
The single rule that matters most: nothing gets done before the contract is signed and the first invoice is paid. Not the kickoff call, not the discovery doc, not the 'quick mockup to make sure we're aligned.' Signed and paid. Then work begins.
Every freelancer who has been burned has the same story: 'we were going to sign it next week, but I started anyway because the client seemed nice.' Nice clients sign contracts. The ones who won't are telling you something important.
This article is general guidance, not legal advice. For high-value engagements or contracts in regulated industries, consult a licensed attorney in your jurisdiction.