Freelance Terms and Conditions: The Boring Document That Quietly Runs Your Business
There is a specific sound a freelancer makes when a client says "oh, I assumed that was included." It is not quite a word. It lives somewhere between a sigh and the noise a tyre makes going flat, and every freelancer who has ever worked without written terms has made it at least once.
That sentence — I assumed that was included — is where money goes to die. So does its cousin, "we'll sort out payment at the end," and its more menacing uncle, "actually, can you send over the source files before we've paid the final invoice?" Every one of those conversations has the same root cause: nobody wrote down the rules before the work started.
The thing that prevents all of them is the least glamorous document in your entire business. Nobody frames their terms and conditions. Nobody posts them with a rocket emoji. And yet they are, quietly, the difference between a freelance business that runs on agreements and one that runs on hope and awkward emails.
Terms and conditions vs a contract — no, they are not the same thing
This trips up almost everyone, so let's kill the confusion first.
A contract is the agreement for this specific job: what you are building, for whom, for how much, and by when. It changes every time, because every project is different. That is the territory our guide on freelance contract basics covers — the scope, the deliverables, the deadline for one particular engagement.
Your terms and conditions are the standing rulebook that sits underneath every job, regardless of what the project is. How you get paid. What happens when payment is late. How many rounds of revisions come with the price. Who owns the work, and from which moment. What you are not on the hook for. How either side walks away. None of that changes from client to client, which is exactly the point.
Think of it like flying. The contract is your itinerary for one trip — these dates, this destination, this fare. The terms and conditions are the airline's conditions of carriage, the ones that apply to every passenger on every flight whether they read them or not. You negotiate the itinerary each time. The conditions of carriage you write once and stop thinking about.
Get this distinction right and your paperwork gets dramatically lighter, because your per-project contract only has to cover the handful of things that actually change. Everything permanent lives in your terms.
The whole point is that you write them once
The power of a good set of terms is not in any single clause. It is that you decide all the uncomfortable things in advance, in a calm moment, when there is no money on the table and nobody is annoyed — and then you never have to negotiate them mid-project again.
This is the part people miss. Every rule you do not write down is a rule you will end up settling later, in the worst possible conditions: mid-dispute, from the weakest position, with a client who is currently sitting on your unpaid work. "When do I get paid" is a very easy conversation to have before the project starts and a genuinely horrible one to have six weeks after delivery. The terms move that conversation to the calm end of the timeline, permanently.
Write them once. Attach them to everything. Stop re-litigating the same three arguments on every project. That is the entire pitch, and it is a very good one.
The clauses that earn their place
You do not need a fourteen-page document. You need a short set of clauses that each prevent a specific, recurring way freelancers lose money. Here are the ones that pull their weight.
Payment terms, and a late fee that has teeth. State when payment is due (net 14 and net 30 are the common ones), whether you take a deposit up front, and — this is the part people leave off — what happens when an invoice goes past due. A stated late fee, say 1.5% a month, is rarely about the interest. Its real job is to move "pay the freelancer" up the client's to-do list, above the forty other things competing for their attention.
A revision limit with an actual number. "Two rounds of revisions are included; further rounds are billed at your standard rate." Without a number, "just a few small tweaks" is infinite, free, and somehow always arriving at 6pm on a Friday. This one line is your first line of defence against scope creep, and it works precisely because it was agreed before anyone wanted anything.
Ownership transfers on final payment. You retain the rights to the work until the invoice clears. This single sentence quietly converts "please pay me" from a request into a condition of actually using the thing they hired you to make. Keep your own reusable tools, templates and frameworks yours, and reserve the right to show the finished work in your portfolio while you are at it.
A cancellation and kill fee. If the client pulls the plug halfway through, you keep the deposit and bill for the work completed to that point. This protects the single most expensive and least recoverable thing you own: the hours you have already spent and cannot get back.
A liability cap. Your total liability is limited to the fee for the project. It is a dull sentence that stops a $900 logo from turning into a claim for a client's disappointing quarter. Nobody thinks they need it until precisely the one time they do.
Client responsibilities. The client owes you materials, feedback and access on a reasonable schedule — and if they do not deliver them, the timeline and the deadline move accordingly. This is the clause that saves you when a project drifts three months late and every single day of that delay was the client sitting on your emails. It is also, not coincidentally, why a non-paying or ghosting client becomes so much easier to deal with when the delay was demonstrably theirs.
Which law applies. One line naming the governing jurisdiction. Boring ninety-nine times out of a hundred, and occasionally the only thing that matters.
The three most freelancers skip — and regret
Almost everyone leaves the same three out, and for the same three bad reasons.
The late-payment fee, because it feels rude. It is not rude. What is rude is a client treating your invoice as optional while you become their interest-free lender. The fee simply prices in the cost of being paid late, which is a real cost you are otherwise absorbing in silence.
The revision cap, because you want to seem generous. Generosity you never defined is not generosity. It is scope creep wearing a nicer coat. Define the number, then be genuinely warm and flexible within it — that reads as generous. Unlimited free tweaks read as a doormat.
Ownership-on-payment, because nobody ever taught it. This is the highest-leverage sentence available to a freelancer and it costs you exactly one line. If you add nothing else to your terms this year, add this one.
How to actually put them to work
Writing a beautiful set of terms and then never sending them is a surprisingly popular hobby. Terms only protect you if the client has seen them and agreed to them before the work begins. Terms produced for the first time during an argument are not terms; they are a wish.
Put them in three places. One: fold the two or three that matter into every proposal, in plain language, so accepting the proposal means accepting the terms. Two: reference them on every invoice — a simple "payment due within 14 days per our terms" is enough to make lateness a breach of something rather than a vibe. Three: keep a plain terms page on your own site you can link to, which has the quiet side benefit of being findable in search.
And do not email a client a wall of legalese with "please review the attached." They will not, and the ask makes the whole thing feel like a negotiation you are inviting. Instead, translate the handful of terms that actually matter into two or three friendly sentences inside the proposal, get them to say yes to the proposal, and the terms ride along with it. A signed-off proposal that references your terms is, in practice, agreement to them — with none of the ceremony that makes clients nervous.
How formal does this actually need to be?
Proportionate to the money. A $300 job does not need a fourteen-page document; it needs four clear lines in the proposal — price, payment terms, revision limit, and what happens if they cancel. A $15,000 retainer earns the full set, carefully written.
The mistake is almost never being too informal. It is having nothing — no written statement, anywhere, of when you get paid and what is included. Even a short, plain set of terms beats a handshake every time, because a handshake's memory is selective and it tends, remarkably often, to favour whoever currently owes money.
One honest caveat: what counts as enforceable, how much late-payment interest you can charge, and how intellectual property transfers all vary by country. Treat everything here as a practical checklist rather than legal advice, and have a local professional glance over your terms once. It is a one-time cost that pays for itself the first time a client reads them and quietly decides to behave.
None of this makes you a lawyer, and it is not supposed to. It makes you a freelancer who decided the rules on a calm afternoon instead of during a bad week — which, it turns out, is most of the battle.
Frequently asked questions
What are freelance terms and conditions? They are the standing set of rules you attach to all of your work, regardless of the specific project: how and when you get paid, late-payment fees, how many revisions are included, who owns the work and from which point, your liability limits, what the client is responsible for, and how either side can cancel. Unlike a contract, which covers one particular job, your terms are written once and applied to every client.
Do freelancers really need terms and conditions? Yes — and they matter more the smaller and less formal your business is, not less, because you have no legal or finance department absorbing the risk. Even a few plain lines in your proposal covering payment terms, revision limits and cancellation will prevent the large majority of the disputes freelancers actually run into. The full set simply covers more ground.
What is the difference between terms and conditions and a contract? A contract is specific to one project — the scope, price and deadline for that job. Terms and conditions are the reusable rulebook that applies to every job you take. In practice the two work together: you attach your standing terms to each project-specific contract or proposal, so you only ever have to write down the parts that change.
What should freelance terms and conditions include? At minimum: payment terms and a late-payment fee; a revision limit with a real number; ownership of the work transferring on final payment; a cancellation and kill-fee clause; a cap on your liability; the client's responsibilities for materials and feedback; and which jurisdiction's law applies. Scale the detail to the size of the work.