Most freelancers write a contract after the project that went wrong. The client kept adding “small tweaks”, the invoice went unpaid for ninety days, and somewhere around week six it became clear nobody had agreed what “finished” meant.

A contract is not there to win a court case. It is there to make both people agree, in writing, before anything goes wrong. That is almost the whole of its value.

This covers the clauses that actually matter. It is general information rather than legal advice — contract law varies considerably by country, so have anything important reviewed locally.

Scope: what is included, and what is not

This single clause prevents more trouble than everything else combined. Scope creep is rarely malicious — it happens because two people had different pictures in their heads and never compared them.

Be specific in a way that feels almost excessive. “A website” means nothing. “A five-page WordPress site using an existing theme, with a contact form and basic on-page SEO” is a scope.

Then add the part most contracts omit: an explicit exclusions list. Writing “content and images supplied by the client; hosting, domain and ongoing maintenance not included” costs one line and settles arguments before they start.

State how changes are handled too. Not refusing changes — every project has them — just naming the process. “Work outside this scope will be quoted separately before proceeding.” Saying that upfront is easy. Saying it in week three is a confrontation.

Payment terms with actual consequences

Vague payment terms are an invitation to be paid late, and late payment is the single most common financial problem freelancers face.

• A deposit before starting. Fifty percent is standard for new clients. It filters out people who were never going to pay and covers you if the project stalls.
• A named due date. “Net 14” or “due on receipt” — not “on completion”, which is undefined.
• Staged payments on longer work. Tie them to milestones so you are never carrying more than a few weeks of unpaid work.
• A late fee. You may never charge it. Its presence changes how your invoice is prioritized in an accounts queue.
• The right to pause work. State plainly that work stops if an invoice passes a certain age. This is your only real leverage, and it only exists if you wrote it down.

Interest and late-fee rules on commercial debts differ by jurisdiction, and some countries cap what you may charge. Check your local position rather than copying a figure from a template.

Revisions: a number, not a feeling

“Revisions until you are satisfied” sounds generous and is the fastest route to an unprofitable project. Satisfaction has no definition and no end point.

Name a number. Two rounds is typical for design work. Then define what a round is, because that is where the ambiguity hides: one consolidated set of feedback, delivered at once, not fourteen separate messages over a fortnight.

Say what happens after the included rounds — additional revisions at your hourly rate. This is rarely enforced, and it reliably stops the endless drip of small changes simply by existing.

Intellectual property transfers on payment

The default position on who owns commissioned work varies by country, and assuming the wrong default causes real problems.

The clause worth having is straightforward: ownership of the delivered work transfers to the client on receipt of full payment. Before that, it remains yours. This is fair to both sides and gives you a concrete position if an invoice goes unpaid.

Two things to carve out. Retain the right to show the work in your portfolio unless the client specifically buys that right. And keep ownership of any reusable components, libraries or templates you brought to the project — you are licensing those, not selling them, or you cannot use your own tools on the next job.

Termination and the kill fee

Projects get cancelled. Budgets vanish, priorities shift, the person who hired you leaves. Without a termination clause you may have done six weeks of work and be owed nothing beyond the deposit.

Cover three things: how much notice either side gives, what is owed for work completed up to that point, and whether the deposit is refundable. A common arrangement is that the deposit is non-refundable and completed work is billed pro rata.

Give yourself an exit too. You should be able to walk away from a client who is abusive, unresponsive, or repeatedly late paying, without breaching your own agreement.

Smaller clauses worth including

• Client responsibilities. Content, access, approvals and feedback deadlines. Most delays are caused by the client, and this clause makes that visible rather than arguable.
• Limitation of liability. Capping your liability at the project fee is standard practice and worth having.
• Confidentiality. Mutual, and usually enough without a separate agreement for ordinary work.
• Governing law. Which country’s law applies. Matters more than people expect with international clients.
• Independent contractor status. Confirms you are not an employee, which has tax implications in many jurisdictions.

Getting it signed without friction

A contract nobody signs protects nobody. The practical obstacles are usually about process rather than terms.

• Send it early. With the proposal, not after they have said yes. It reads as standard procedure rather than a sudden demand.
• Keep it short. Two pages in plain language gets signed. Fifteen pages of legalese gets forwarded to someone who is busy.
• Use e-signature. Print, sign, scan is where agreements go to die.
• Summarize the key terms in the email. Price, timeline, what is included, payment schedule. Most clients will read the summary and sign on that basis.
• Do not start work before it is signed. The moment you begin, your leverage is gone.

Red flags in a client’s contract

When a client sends their own agreement, a few specific terms are worth catching before you sign.

• Unlimited revisions or “to the client’s satisfaction”. An open-ended obligation with no defined end.
• Payment on final approval. If approval is undefined, so is your payment date.
• Uncapped liability or broad indemnity. Exposure far beyond what the project pays you.
• Ownership of everything you create, including pre-existing tools. This can prevent you reusing your own libraries.
• Non-compete clauses covering a whole industry. Reasonable confidentiality is normal; being barred from an entire sector is not.
• Payment terms of 60 or 90 days. Common with large companies and negotiable more often than people assume.

None of these mean walk away. They mean ask for an amendment. Clients who send contracts expect redlines, and the ones who refuse any change at all have told you how the rest of the project will go.

International clients

Working across borders adds a few considerations worth settling in writing rather than discovering later.

Specify the currency and who absorbs conversion and transfer costs, because a payment that looks correct can arrive noticeably short — our fee calculator shows how much those deductions take. Name the governing law and where disputes would be handled. And be aware that pursuing a small unpaid invoice across jurisdictions is usually impractical, which makes deposits and staged payments your real protection rather than the contract itself.

Frequently asked questions

Do I need a lawyer to write one?

For routine project work, a solid template adapted to your situation is usually enough. It is worth paying for a review once, then reusing it. For high-value contracts or unusual terms, get proper advice.

Is an email agreement legally binding?

In many jurisdictions a clear written exchange showing agreement on the essential terms can be enforceable. It is far weaker than a proper contract and easier to dispute, but it is dramatically better than nothing. If you take one thing from this article, get the scope and price confirmed in writing.

What if the client sends their own contract?

Read it properly. Watch for unlimited revisions, unlimited liability, payment terms beyond 30 days, and clauses claiming ownership of everything you produce including your reusable tools. You are allowed to negotiate. Clients expect it.

Will asking for a contract lose me the client?

Serious clients expect one and it makes you look more professional, not less. A client who refuses to sign anything is telling you something important, and it is worth listening to.

The point is the conversation

Almost no freelancer ever enforces a contract in court. The value is entirely in what happens before the work starts — walking through scope, payments and revisions forces both people to say out loud what they were assuming.

That conversation is where the misunderstandings surface, while they are still cheap to fix. The document is just the record of it.

Once the terms are agreed, our free invoice generator produces a clean invoice with the payment terms you have just set.