Most freelancers who've been burned can trace it to one of two things: no contract, or a contract that was vague in exactly the wrong place. A solid contract doesn't guarantee you'll never have a difficult client — but it converts disagreements into resolvable disputes instead of unresolvable ones, and it settles the most common conflicts before they happen.
Here's what every freelance contract needs, and why each element earns its place.
The purpose of a contract isn't to signal distrust — it's to make sure both parties have the same expectations before work begins. Disputes almost always stem from mismatched assumptions: the client thought three revisions meant unlimited iterations, the freelancer thought "one round" meant one set of comments on one draft. A contract forces both sides to be explicit about what they agreed to, when, and under what conditions.
A signed contract also creates a baseline for every subsequent conversation. When a client asks for something outside the original scope, you're not pushing back on a preference — you're referring to a document you both signed. That changes the dynamic entirely.
§1 The scope of work is the single most important clause in a freelance contract. It should describe, specifically and completely, what you are delivering. Not "a website" — a website with X pages, built in Y technology, with Z specific features, excluding A and B. Not "a logo" — a primary logo mark, two color variations, delivered as vector files in these formats.
The test: if a reasonable person read this section without talking to either party, would they know exactly what's included and what's not? If not, add more specificity.
Also define what's explicitly out of scope. If you're building a web app but not handling hosting or ongoing maintenance, say so. The most expensive scope creep comes from implicit inclusions — things neither side thought to specify that one side assumed were included.
§2 Specify: the total amount, the payment schedule, the payment method, and the late payment consequence.
Schedule: For project work, a deposit on signing (typically 25–50%) and the remainder on delivery is the standard structure. For longer projects, milestone-based payments reduce your risk — you get paid for each phase rather than front-loading all the risk to completion.
Net terms: Be explicit about when payment is due. "Net 15" means 15 days after invoice. "Due on receipt" means immediately. Leaving this vague means the client decides.
Late fees: A 1.5–2% monthly fee on overdue invoices is standard and worth including. You may never enforce it, but having it in the contract changes the client's behavior. It also gives you something to waive as a goodwill gesture if you choose to.
Deposit as non-refundable: State explicitly that the deposit is non-refundable if the project is cancelled by the client after work has begun. This is your kill fee protection.
§3 Define what counts as a revision and how many rounds are included. The word "revision" should mean a set of consolidated feedback on a deliverable — not an ongoing back-and-forth. Make clear that revisions are submitted together, not piecemeal.
Specify what happens when a client requests changes that go beyond the original scope. The standard approach: changes outside the original scope are quoted and billed separately, and work doesn't begin on them until a change order is signed. This is not bureaucracy — it's protecting you from the project that quietly grows by 40% while the budget stays flat.
Revisions that change the fundamental direction of the project (e.g., moving from a mobile-first to desktop-first design after mobile designs have been approved) are considered a new scope of work, not a revision.
§4 By default under U.S. copyright law, the creator owns the work — not the person who paid for it. If you want your client to own what you create for them, you need a written agreement transferring that ownership. If you want to retain rights, you need to say so explicitly.
Common approaches:
The IP clause is often where freelancers get into trouble by saying nothing. If a client later claims ownership of something you intended to retain, your silence works against you.
Upload, place signature fields, send — your client signs from any device. No account needed on their end.
Try GoSignHere Free§5 A kill fee is compensation paid when a client cancels a project after it's underway. It's not punitive — it's recognition that you've allocated time, turned down other work, and incurred costs that you can't recover when a project is cancelled.
Common structures: a flat percentage of the remaining contract value (25–50%), or payment for all work completed plus a percentage of the remaining work. The right amount depends on your business model, but the important thing is having something defined.
Also define what happens to the work product if the project is cancelled before completion. Typically: the client owns what they've paid for, and ownership of the remaining deliverables transfers when and if the kill fee is paid.
§6 Specify when you'll deliver, and what you need from the client to hit that date. If your delivery depends on the client providing content, access, or feedback by a certain date, say so — and make explicit that delays caused by the client's failure to deliver their inputs will push the project timeline accordingly.
This protects you from a situation where the project runs six months over because the client was slow at every review, and then they complain that you missed the deadline.
§7 For most freelance engagements, a brief mutual confidentiality clause is appropriate. You agree not to disclose the client's non-public business information. They agree not to disclose your pricing, proprietary processes, or other information you'd consider confidential. Define what counts as confidential and how long the obligation lasts (1–3 years is typical for commercial work).
If the client insists on a more comprehensive NDA, that's a separate document. For a standard freelance contract, a short confidentiality clause is sufficient for most situations.
§8 Specify the governing law (which state's laws apply) and the dispute resolution process. For most freelancers, the practical options are:
At minimum, specify the governing state. This matters if you're in California and your client is in Texas — each state has different court procedures and contract enforcement approaches.
A contract that sits in your drafts folder doesn't protect you. Get it signed before any work begins — not after the kickoff call, not after the first deliverable, before any work starts. Sending the contract for signature is also a professional signal that you take your business seriously.
For a two-party freelance contract (you and one client), the simplest approach is to send it via e-signature tool with a countersignature. Your client signs first, then you countersign — or you both sign in parallel. Either way, both parties get a copy of the signed document and the audit trail that proves when it was signed and by whom.
With GoSignHere, you can upload your contract, place signature and date fields for both parties, and have it signed in under 5 minutes — no account required for your client. The completed package includes a certificate of completion with timestamps and IP addresses, so if the contract is ever disputed, you have clear evidence of exactly when and how it was signed.
Create your free account. No credit card, no commitment.
Get Started Free