Most freelancers either skip the contract entirely or use a template they found on Google without reading it. Both are mistakes. A contract you didn't write is a contract you don't understand. And a contract you don't understand won't protect you when things go sideways.
This guide walks you through writing your own freelance contract from scratch, section by section. If you already know what belongs in a contract, this is the next step: actually drafting one.
Why You Need a Contract (Even for Small Projects)
You might think a $500 project doesn't justify the overhead. It does. Three reasons.
Scope protection. Without a written scope, you have no way to push back when a client asks for "one more thing." A contract draws a line between what's included and what's extra. That line saves you hours of unpaid work.
Payment terms enforcement. Verbal agreements about payment are worth exactly nothing when a client decides to delay. A signed contract with clear terms, due dates, and late fees gives you standing to follow up. It also changes how clients prioritize your invoice. More on that in our invoicing guide.
Dispute resolution. If something goes wrong, the contract is the document everyone refers to. No contract means the dispute becomes a he-said-she-said situation, which you will almost always lose as the freelancer.
How to Write Each Section
Work through these in order. Each section builds on the last.
1. Parties
Start with who's entering the agreement. Use full legal names and addresses, not nicknames or first names.
For you, this means your registered business name (if you have one) or your full legal name. Include your business address and email. If you're a sole proprietor in the US, your legal name is your business name unless you've filed a DBA.
For the client, use their official company name as registered. If you're working with a company in the EU, include their registration number (KvK in the Netherlands, Companies House number in the UK). This detail matters if you ever need to enforce the agreement.
Example:
This agreement is between [Your Full Name / Business Name], located at [Your Address] ("Contractor"), and [Client Company Name], located at [Client Address] ("Client").
2. Scope of Work
This is the section that prevents the most disputes. Be as specific as possible about what you will deliver, and equally specific about what you won't.
Bad scope: "Website design and development."
Good scope: "Design and development of a 5-page responsive marketing website (Home, About, Services, Portfolio, Contact), built on WordPress, using client-provided copy and brand assets. Does not include copywriting, SEO optimization, or ongoing maintenance."
List every deliverable. If you're designing, specify how many concepts you'll present. If you're developing, list the features. If you're writing, state the word count per piece.
The "does not include" section is just as important as what's included. Clients rarely try to exploit you on purpose. They just assume things are included because nobody said otherwise.
3. Timeline and Milestones
Break the project into phases with dates. Don't just set a final deadline. Milestones create checkpoints where both sides confirm the work is on track.
Example structure:
- Week 1-2: Discovery and wireframes. Client provides all content and brand assets by [date].
- Week 3-4: Design concepts delivered for review.
- Week 5: Revisions based on client feedback.
- Week 6-7: Development.
- Week 8: Testing, final revisions, launch.
Add a dependency clause: "All dates assume client feedback within 5 business days of each deliverable. Delays in client response will shift subsequent milestones by an equal number of days."
This single sentence prevents arguments about missed deadlines caused by slow client feedback.
4. Payment Terms
State four things clearly: the total fee (or your rate), the payment schedule, when payment is due, and what happens when it's late.
Fixed-price example: "Total project fee: $4,500. Payment schedule: 50% ($2,250) due upon signing, 25% ($1,125) due at design approval, 25% ($1,125) due at launch."
Hourly example: "Work will be billed at $95/hour in 30-minute increments. Invoices issued bi-weekly, due within 14 days of receipt."
Always include a late payment clause. A standard rate is 1.5% per month on overdue balances. You may never enforce it, but its presence on the contract changes behavior.
If you're unsure how to set your rate, read our guide on how to set your freelance rate.
For EU freelancers: If you're VAT-registered, specify whether your quoted prices include or exclude VAT. For cross-border EU work, note which party is responsible for VAT compliance.
5. Revision Policy
Define what counts as a revision, how many are included, and what happens after that.
"Two rounds of revisions are included in the project fee. A revision round is defined as a single consolidated set of feedback provided in writing. Additional rounds will be billed at $95/hour."
The word "consolidated" matters. Without it, clients send feedback in five separate emails over two weeks and claim each one is part of the same round. One round equals one set of organized feedback, delivered at one time.
6. Intellectual Property
This section answers one question: who owns the work, and when does ownership transfer?
The most common arrangement for freelancers in the US is: you retain all rights until final payment is received, at which point full ownership transfers to the client. This protects you from doing work and never getting paid for it.
Example: "Upon receipt of final payment, the Contractor assigns all intellectual property rights in the deliverables to the Client. Until final payment is received, all rights remain with the Contractor. The Contractor retains the right to display the work in their portfolio."
If you want to keep using parts of the work (code libraries, design components, templates), add a license-back clause: "The Contractor retains ownership of pre-existing tools and frameworks used in the project and grants the Client a perpetual, non-exclusive license to use them as part of the deliverables."
7. Termination
Either party should be able to end the engagement. The question is what happens financially when they do.
Example: "Either party may terminate this agreement with 14 days written notice. If the Client terminates, the Contractor will be paid for all work completed to date plus 25% of the remaining project value as a kill fee. If the Contractor terminates, the Contractor will deliver all work completed to date and refund any payments for undelivered milestones."
The kill fee compensates you for turning down other work and scheduling around this project. Without it, a client can cancel midway and you absorb the full cost of their decision.
8. Liability and Indemnification
Keep this section simple. You're not writing a corporate contract for a Fortune 500 company.
Example: "The Contractor's total liability under this agreement shall not exceed the total fees paid by the Client. Neither party shall be liable for indirect, incidental, or consequential damages."
This caps your exposure at the project fee. Without it, a client could theoretically claim damages far exceeding what they paid you.
Add a mutual indemnification clause: "Each party agrees to indemnify the other against any claims arising from their own negligence or breach of this agreement."
9. Governing Law
One sentence. Which jurisdiction's laws apply if there's a dispute?
US example: "This agreement is governed by the laws of the State of New York."
EU example: "This agreement is governed by the laws of the Netherlands."
Pick the jurisdiction where you're based. If you're working with international clients, this clause determines which court system applies. Without it, the answer is ambiguous and expensive to figure out.
Free Freelance Contract Template
Use this structure as a starting point for your own contracts. Fill in the bracketed sections with your specific details.
- Parties - Full legal names, addresses, and contact information for both Contractor and Client.
- Effective Date - The date the agreement begins.
- Scope of Work - Detailed description of deliverables. List what is included and what is explicitly excluded.
- Timeline and Milestones - Project phases with dates. Include a clause for delays caused by client response times.
- Payment Terms - Total fee or rate, payment schedule, accepted payment methods, currency, and due dates.
- Late Payment - Interest rate on overdue invoices (e.g., 1.5% per month).
- Revision Policy - Number of included rounds, definition of a revision round, rate for additional rounds.
- Intellectual Property - Ownership transfer terms. When rights transfer, portfolio usage rights, pre-existing IP.
- Confidentiality - Mutual NDA covering project details and business information.
- Independent Contractor Status - Statement that the Contractor is not an employee and is responsible for their own taxes and insurance.
- Termination - Notice period, kill fee for client termination, obligations on contractor termination.
- Liability Cap - Maximum liability equal to total fees paid. Exclusion of indirect damages.
- Governing Law - Jurisdiction for disputes.
- Dispute Resolution - Mediation or arbitration before litigation.
- Force Majeure - Terms for circumstances beyond either party's control.
- Signatures - Signature lines, printed names, dates for both parties.
This is a framework, not legal advice. If you regularly work on projects over $10,000 or in regulated industries, have an attorney review your template once. That one-time cost pays for itself many times over.
Common Mistakes
Being too vague. "I'll build you a website" is not a contract term. Every deliverable, every deadline, every dollar amount should be written out. Vagueness favors whoever didn't write the contract, and that's usually the client.
Not getting it signed before starting work. A contract that gets sent after the project kicks off is a suggestion, not an agreement. Get the signature before you write a single line of code or open a design file. No exceptions.
Relying on verbal agreements. "We agreed on the phone that revisions would be free." Did you? Prove it. Anything that matters goes in writing. If a client agrees to something verbally, follow up with an email confirming it and add it to the contract.
Using someone else's template without reading it. Templates from the internet are written for a generic situation that is probably not yours. They may include clauses that work against you or miss protections you need. Start from a template if you want, but read every word and adapt it.
Skipping the contract for repeat clients. Familiarity is not a substitute for a signed agreement. In fact, scope creep is often worse with long-term clients because both sides get comfortable and stop documenting changes.
Skip the Drafting, Keep the Protection
Writing contracts from scratch takes time. Every new project means adapting your template, formatting the document, sending it for signature, and following up.
TAV handles this automatically. When a client accepts your proposal, TAV generates a compliant contract based on your project details. Your scope, payment terms, and timeline are pulled directly from the proposal. Both parties sign digitally, and the signed contract is stored with a full audit trail.
No copying and pasting from old contracts. No chasing signatures. No wondering which version the client agreed to.