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

Most freelancers skip contracts because writing one feels like it requires a law degree, not because they think contracts are pointless. What they get instead is a handshake agreement that works fine until it does not: until the client wants six rounds of revisions on a project quoted for two, or the invoice sits unpaid for sixty days with no agreed due date, or a misunderstanding about deliverables turns a good relationship tense. A basic written agreement heads off most of that, and no lawyer is required.

Start with the difference between a contract and a statement of work. A contract governs the relationship: how you work together, payment terms, what happens when things go wrong, who owns what you create. A statement of work describes one specific engagement: what you will deliver, when, for how much. Use them together or separately. For ongoing clients, a master contract plus individual SOWs per project is cleanest. For one-off work, a single combined document is fine. The Contract / SOW Generator produces either and downloads a clean PDF in minutes.

Six clauses that belong in every freelance contract

Scope comes first. 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 causes most scope creep disputes. When a client later asks for something outside the list, you have a documented basis for a change order rather than absorbing the work.

Payment terms come second. Give the total, the schedule, the acceptable methods, and the due dates. "Net 30" is common and negotiable, and "50% upfront, 50% on delivery" is reasonable for project work and protects you if the engagement goes sideways. Say what happens when payment is late. Most freelancers charge 1.5% per month on overdue balances, consistent with standard practice. In the UK, the UK Late Payment Calculator shows what interest accrues under the Late Payment of Commercial Debts Act. Build invoices with the Invoice Maker so the terms appear on every one you send.

Revision policy is third. 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 are happy. Without the clause, every project is implicitly open-ended. Clients are rarely malicious about this. They simply do not know the scope has been exceeded until someone says so.

Intellectual property is fourth. In most jurisdictions the creator owns the work until full payment, at which point ownership transfers. Put it in writing: "All intellectual property in the work product transfers to the client upon receipt of final payment in full." That gives you leverage if a client uses the work before paying, and it clarifies that anything you brought to the engagement, existing tools, templates, or code, stays yours.

A kill fee or cancellation policy is fifth. Projects get cancelled for reasons unrelated to your performance. A kill fee sets what the client owes if they cancel mid-project, usually a percentage of the remaining contract value scaled to how far the work has progressed. Without it you carry all the risk of a client changing their mind after you turned down other work for theirs.

Dispute resolution is sixth. Name the governing law, your county or country, and say whether disputes go to arbitration or small claims court before any legal action. It is rarely invoked, and it signals professionalism and sets expectations before anything goes wrong.

Getting the contract signed

Once the sections are filled in with the Contract / SOW Generator, signing does not mean printing and scanning. Drawing your signature and embedding it in the PDF through Digital Signature takes about two minutes. Send the signed copy and ask the client to countersign and return it before work begins.

How you send it matters as much as what is in it. Most clients will not push back if you frame it well. "I've put together a simple agreement covering the project scope and timeline, happy to answer any questions before we get started" is ordinary professional communication, not an accusation. Sending a contract says you are organised and take the engagement seriously, and clients used to working with experienced professionals expect to sign something.

After signing, the Proposal / Quote Generator can document the agreed scope in a format that doubles as your own project brief. Set a reminder with the Follow-up Reminder Scheduler for the first milestone check-in or payment due date. The administrative side of freelancing is not glamorous, and it is what separates projects that run smoothly from the ones that do not.