How to Write a Freelance Contract or SOW Without Hiring a Lawyer

A contract protects you and your client. Most freelancers don't use one because writing one feels complicated. It doesn't have to be.

Most freelancers skip contracts not because they think they're unnecessary but because writing one feels like it requires a law degree. The result is a handshake agreement that works fine until it doesn't - until the client wants six rounds of revisions on a project that was quoted for two, or until the invoice sits unpaid for sixty days with no agreed-upon due date, or until a misunderstanding over deliverables turns a good client relationship into a tense one. A basic written agreement prevents most of these problems, and you don't need a lawyer to create one.

The first thing to understand is the difference between a contract and a statement of work. A contract governs the overall relationship between you and a client: how you work together, payment terms, what happens if things go wrong, who owns what you create. A statement of work, or SOW, describes the specific work for a specific engagement: what you'll deliver, when, for how much. You can use them together or separately. For ongoing client relationships, a master contract covering the relationship terms plus individual SOWs for each project is the cleanest approach. For one-off projects, a single document covering both works fine. The Contract / SOW Generator lets you produce either format and download a clean PDF in minutes.

## Six Clauses That Belong in Every Freelance Contract

Six clauses belong in almost every freelance contract. The first is scope. Describe what you will deliver in specific, measurable terms. Not "a website" but "a five-page website with the pages listed in Exhibit A, built in WordPress, with a contact form and mobile-responsive layout." Vague scope is the root cause of most scope creep disputes. If the client later asks for something not listed, you have a documented basis for discussing a change order rather than absorbing the extra work.

The second clause is payment terms. Specify the total amount, payment schedule, acceptable methods, and due dates. "Net 30" is common but you can negotiate better terms - "50% upfront, 50% on delivery" is reasonable for project work and protects you if the engagement goes sideways. State what happens if payment is late: most freelancers charge 1.5% per month on overdue balances, which is consistent with standard late payment practices. If you're in the UK, the UK Late Payment Calculator shows exactly what interest accrues under the Late Payment of Commercial Debts Act. Build your invoices with the Invoice Maker so the payment terms appear clearly on every invoice you send.

The third clause is revision policy. Define what a revision is and how many are included. "Two rounds of revisions" means two structured feedback cycles where you implement the client's consolidated notes. It does not mean unlimited tweaks until they're happy. Without a revision clause, every project is implicitly open-ended. Clients aren't usually malicious about this - they simply don't know the scope has been exceeded unless someone names it.

The fourth clause is intellectual property. By default in most jurisdictions, the creator owns the work until full payment is received, at which point ownership transfers. State this explicitly: "All intellectual property in the work product transfers to the client upon receipt of final payment in full." This gives you leverage if a client uses your work before paying. It also clarifies that work created outside this contract, including existing tools, templates, or code you bring to the engagement, remains yours.

The fifth clause is a kill fee or cancellation policy. Projects get cancelled for reasons that have nothing to do with your performance. A kill fee specifies what the client owes you if they cancel mid-project - typically a percentage of the remaining contract value based on how far along the work is. Without this, you absorb all the risk of a client changing their mind after you've turned down other work to take on theirs.

The sixth clause is dispute resolution. Specify the governing law (your county or country), and whether disputes go to arbitration or small claims court before any legal action. This is rarely used but signals professionalism and sets expectations before anything goes wrong.

## Getting the Contract Signed

Once you've filled in these sections using the Contract / SOW Generator, getting it signed doesn't require printing and scanning. Drawing your signature and embedding it directly into the PDF using Digital Signature takes about two minutes. Share the signed copy with the client and ask them to countersign and return it before work begins.

How you send a contract matters as much as what's in it. Most clients won't push back on a contract if you frame it correctly. "I've put together a simple agreement covering the project scope and timeline - happy to answer any questions before we get started" is a normal professional communication, not an accusation. Sending a contract signals that you're organised and that you take the engagement seriously. Clients who work with experienced professionals expect to sign something.

After the contract is signed, the Proposal / Quote Generator can help you document the agreed scope in a format that works as a project brief for yourself. Set a follow-up reminder using Follow-up Reminder Scheduler for the first milestone check-in or payment due date so nothing slips through the cracks. The administrative side of freelancing isn't glamorous, but it's what separates projects that run smoothly from ones that don't.

← More articles | Free SMB Tools