What belongs in a freelance service agreement, clause by clause

Almost every freelance horror story — the project that ballooned to triple the size, the client who vanished before paying, the fight over who owns the work — traces back to the same root cause. Something that should have been written down wasn't. The contract isn't there to win lawsuits; most freelance disputes never reach a lawyer. It's there to make expectations explicit before money and ego are on the line, so that when a question comes up, the answer already exists in writing.

This is a tour of the clauses that actually earn their place in a freelance service agreement — what each one does and the specific pain it prevents. None of this is legal advice; it's the working knowledge of what to make sure is covered before you start.

Scope: the clause that prevents the most fights

If you get one clause right, make it this. The scope defines exactly what you'll deliver — and, just as importantly, what you won't. Vague scope is how a logo becomes a logo plus a brand guide plus business cards plus three rounds of website mockups, all for the original price.

Write deliverables as a concrete list, not a vibe. "A 5-page marketing website" beats "a website." "Two homepage concepts, one taken to completion" beats "design options." And pair the scope with an explicit out-of-scope line — "copywriting, photography, and ongoing maintenance are not included" — because naming what's excluded is what gives you a clean place to say "happy to, that's a change order."

Payment: amount, schedule, and what happens when it's late

State the total, the currency, and the schedule. For anything beyond a small project, get a deposit up front — a 30–50% deposit before work begins is standard and self-selecting: clients who balk at a deposit are often the ones who'd balk at the final invoice. Tie remaining payments to milestones, not vague time, so each release is anchored to something delivered.

Then write the part freelancers skip: what happens when payment is late. Spell out the due window (net 14 is friendlier than net 30 for solo work), any late fee, and your right to pause work on overdue accounts. You won't enjoy invoking it, but naming it upfront makes payment feel non-negotiable rather than optional.

Intellectual property: who owns what, and when

Be explicit about who owns the final work and at what moment ownership transfers. The crucial detail most contracts miss: tie the IP transfer to final payment. Until the client has paid in full, you retain ownership. This is the single most powerful protection a freelancer has — it means an unpaid client doesn't legally own the deliverables they're using.

Decide too whether you keep the right to show the work in your portfolio (usually yes, unless there's a specific confidentiality reason), and whether you retain ownership of underlying tools, components, or processes you reuse across clients. A dedicated IP transfer agreement can sit alongside the service agreement when the stakes warrant it.

Revisions: bound the loop before it opens

"Unlimited revisions" is a promise to work for free indefinitely. Define how many rounds are included — two is a sane default — what counts as a round (consolidated feedback, not a trickle of one-off requests), and what additional rounds cost. This isn't being rigid; it's giving the client a clear, fair structure so feedback converges instead of spiraling.

A good contract doesn't make you adversarial. It makes you predictable — and predictable is exactly what a nervous client is paying for.

Termination and the kill fee

Projects end early sometimes — priorities shift, budgets get cut, the relationship sours. Your agreement should say how either side can exit (usually written notice) and what's owed when they do. Include a kill fee or a clause that all work completed to the termination date is billable. Without it, a client can cancel at 80% done and argue they owe nothing because the final deliverable never shipped.

The boilerplate that quietly matters

A few clauses look like filler but do real work:

• Confidentiality — what client information you'll protect, and for how long. Pair with a separate NDA when a client requires one.

• Independent contractor status — you're not an employee; you control how and when you work and you handle your own taxes.

• Liability cap — limit your total liability, often to the amount paid under the contract, so one bad outcome can't be catastrophic.

• Governing law — which jurisdiction's rules apply, which matters more than ever when you and your client are in different countries.

From clause to signature

Knowing the clauses is half the job; the other half is making the contract effortless to send, sign, and prove. You shouldn't be redrafting these clauses from scratch each time, and you shouldn't be chasing a printed page through a scanner. Start from a vetted service agreement template, let it auto-fill the client and project details, and send it for signature with a few clicks.

In Kliently, every signature is backed by an append-only audit trail that records each open, scroll, and sign with IP and timestamp, and the final PDF carries a signature certificate — meeting the US ESIGN Act and the eIDAS simple-electronic-signature standard. Better still, when a client accepts a proposal, the matching contract can generate itself automatically, so the document with all these clauses is on the client's screen the moment they say yes. Write the clauses once; let the system handle the rest.