Back to Blog
LegalMust Read

How to Write a Freelance Contract That Actually Protects You

Most freelance contracts are either too vague to enforce or so long clients never read them. Here's the one-page structure that works.

Vedansh DanotMay 29, 20268 min read

The freelance contract most people use is a template from the internet, lightly edited, pasted into a Google Doc, and sent with "let me know if you have any questions." The client scrolls to the bottom, skims the payment terms, and clicks accept. Nobody has read it. Nobody will read it. And when something goes wrong, nobody can find it.

A contract that doesn't get read is worse than no contract — because it gives you false confidence while providing no actual protection. Here's how to write one that actually works.

The five sections every freelance contract needs

1. Scope of work (the most important section)

This is where most contracts fail. "Website design" is not a scope. "5-page responsive website with custom design, 2 rounds of revisions, excluding copywriting and photography" is a scope. Be specific enough that you could hand this document to a stranger and they'd know exactly what you're delivering.

  • List every deliverable individually
  • State how many revision rounds are included
  • Explicitly list what is NOT included
  • Define what 'done' looks like for this project

2. Payment terms

State the total amount, the payment schedule (milestone or dates), accepted payment methods, and — critically — the late payment fee. A 1.5% per month late fee, clearly stated and signed to, changes client payment behaviour more than any follow-up email.

Key insight

Require a deposit before work begins. Non-negotiable. 30-50% upfront filters out time-wasters and ensures you're covered if the project falls apart mid-way.

3. Timeline and client responsibilities

Include a project timeline — but also include client obligations. If the client takes 2 weeks to provide feedback when they said 3 days, the timeline shifts. Document this. "Client delays may result in revised delivery dates" is a sentence that saves arguments.

4. Revision and change request process

Every request outside the original scope is a change request. Every change request is quoted separately. This section should state clearly how changes are handled, how they're priced, and that work on changes doesn't begin until the client approves the quote in writing.

5. Intellectual property and file ownership

Who owns the work? When? Under what conditions? The standard position: IP transfers to the client upon full payment. Until then, you retain all rights. This is your leverage if a client refuses to pay.

Keep it short

A one-page contract that gets read and signed is infinitely more valuable than a 12-page contract that gets scrolled past. Use plain language. No Latin. No "heretofore". Write it as if you're explaining it to a friend.

Tip

Auto-generate contracts from your project scope. If your project management tool knows the deliverables, timeline, and payment terms — it should be able to produce a ready-to-sign contract without you drafting a new one each time.

Try Onboard

The tool built for exactly this.

Client portals, project tracking, invoicing, contracts — free, forever.

Get Started Free