Freelance Contract Clauses That Actually Protect You From Bad Clients

You finished the work, the client loves it, and now they're not replying to invoices. Or they are replying — asking for "just one more revision" for the fourth time. Bad clients rarely announce themselves upfront. A well-written contract is the only thing that draws a line before the relationship goes sideways.

Most contract templates you find online are either too vague to enforce or written for a corporate legal team, not a solo freelancer. This article cuts through both extremes and tells you exactly what to include and how to word it.

What you'll learn

• Which clauses stop scope creep before it starts
• How to word payment terms so late payers have no wiggle room
• What a kill fee is and how to set it correctly
• How to protect your intellectual property until you're paid
• What a change-order process looks like in plain language

The Scope of Work Clause

This is where most freelance disputes are born. A vague scope is an open invitation for a client to keep adding to your workload without paying for it. The fix is specificity.

Instead of writing "Design a website for the client," write something like: "Designer will deliver five (5) unique page designs in Figma, including Home, About, Services, Contact, and one interior page. Up to two rounds of revisions per page are included. Additional pages or revision rounds are billed separately at the hourly rate specified in Section 4."

The key elements are: a numbered deliverable count, a defined revision limit, and an explicit pointer to what happens when either boundary is crossed. If you leave those three things out, you will be asked for more and you'll have nothing to point to.

The Change Order Process

Even with a tight scope, clients change their minds. A change order clause establishes how that process works so extra work doesn't become free work.

A simple version looks like this:

Any work outside the scope defined in this agreement requires a written change order, signed by both parties, before work begins. Change orders will specify the additional deliverables, timeline impact, and additional fees. Work on the original scope will pause while changes are negotiated.

That last sentence matters. If work continues while the change order is being discussed, you've already done the work and lost your leverage. Putting a pause in the contract gives you a credible reason to stop without it feeling like a personal standoff.

Payment Terms That Have Teeth

"Net 30" is a default that mostly benefits clients. For most freelance engagements, you want something tighter, and you want late fees built in so the client knows you mean it.

A practical structure for a project under a few thousand dollars:

• 50% upfront before any work begins
• 50% on delivery of final files or at project completion
• Late fee of 1.5% per month on any outstanding balance after 7 days past the due date

For larger projects, break payments into three milestones: deposit, mid-project checkpoint, and final delivery. This keeps your cash flow steady and gives the client a natural point to raise concerns before you're fully invested.

Add this sentence explicitly: "Final deliverables, source files, and any transfer of intellectual property rights will not occur until payment is received in full." This is your enforcement mechanism. Without it, you have no practical leverage once the work is done.

The Kill Fee Clause

Clients cancel projects. Sometimes it's budget cuts, sometimes it's cold feet, sometimes it's just disorganization. A kill fee ensures you're compensated for the time you've already committed.

Here's a reasonable structure:

• If the client cancels before work begins: deposit is non-refundable
• If the client cancels after work has started: client owes the deposit plus a percentage of the remaining contract value based on how far along the project is
• If the client cancels after 50% of the work is complete: client owes 75% of the total contract value

The exact percentages are negotiable, but the logic is consistent: the further along you are, the more of your time is already spent. Some freelancers use a simpler rule — if cancelled at any point after work begins, the full contract value is due. That's harder to sell upfront but easier to enforce.

State clearly that the kill fee is not a penalty, but compensation for time allocated. Framing matters both for the contract and for the conversation if you ever have to invoke it.

Intellectual Property and Ownership Transfer

By default in most jurisdictions, the creator of a work owns it. Rights transfer to the client only when you explicitly assign them. Your contract needs to spell out exactly what transfers and when.

A minimal IP clause looks like this:

Upon receipt of full payment, Freelancer assigns to Client all rights, title, and interest in the final deliverables specified in this agreement. Freelancer retains ownership of all preliminary work, unused concepts, working files, and any tools, frameworks, or processes developed independently of this project.

Notice two things: rights transfer upon full payment, not upon delivery. And you're explicitly keeping your working files and any reusable code or design assets you brought to the project. If you built a custom component library for one client and you don't carve it out, you may not be able to use it for anyone else.

If the client wants source files or editable formats, list that explicitly as a separate deliverable. It's common to charge extra for source file handoff, and your contract should reflect that.

Revision Limits and What Counts as a Revision

"Unlimited revisions" is a phrase you'll see in some freelancer pitches as a selling point. It is also a guaranteed path to burnout and unprofitable projects. Set a revision limit and define what a revision actually is.

A workable definition: "A revision is a change to previously approved work. Feedback on work that has not yet been approved is not counted as a revision round."

This stops the situation where a client keeps requesting changes to something you sent them yesterday and calling it "feedback" rather than a revision. Once they've approved a direction, any change to that direction uses one of their allocated rounds.

Specify what "approval" means too. Written approval via email counts. Silence does not. Add: "Work is considered approved if the client does not provide written feedback within five (5) business days of delivery."

Client Responsibilities and Timely Feedback

Projects stall when clients go quiet. If they're slow to provide feedback, you still have other work to do — and you shouldn't be penalized for a project dragging on because of their delays.

Include a clause that sets a feedback window and what happens if it's missed:

Client agrees to provide feedback, approvals, and required materials within five (5) business days of each submission. If the client fails to respond within this window, Freelancer reserves the right to reschedule remaining work based on current availability. Rush fees may apply if a tight deadline is needed after a client-caused delay.

This does two things: it puts the responsibility for timeline on both parties, and it creates a legitimate basis to charge a rush fee if the client goes quiet for three weeks and then suddenly needs everything by Friday.

Dispute Resolution and Governing Law

If things go seriously wrong, you want to know ahead of time how you'll resolve it and under which jurisdiction's law. Keep this simple.

Specify your state or country as the governing jurisdiction. Specify that disputes will first go to mediation before any legal action. This isn't about being litigious — it's about having a process that both parties agreed to before tensions were high.

Add a clause for attorney's fees if you're in a jurisdiction where this is enforceable: "In any dispute arising from this agreement, the prevailing party shall be entitled to recover reasonable attorney's fees and costs." This discourages nuisance disputes from clients who assume you can't afford to fight.

Common Pitfalls When Writing Your Contract

The most common mistake is copy-pasting a template without reading it. Boilerplate contracts often include clauses that contradict each other or use jurisdiction-specific language that doesn't apply to where you operate.

A second common mistake is making the contract too long. A 20-page contract intimidates clients and buries the important clauses in noise. For most freelance projects, a solid contract fits on three to five pages. If it's longer than that, ask yourself what you're actually protecting versus what you copied from somewhere.

Don't try to cover every possible scenario. Contracts that attempt to address every hypothetical end up being unreadable and are no more enforceable than a clear, focused one. Cover scope, payment, IP, kill fees, revisions, and dispute resolution. That handles the vast majority of real disputes.

Finally, don't send a contract as an afterthought once the project starts. Send it before any work begins, before any prep calls beyond a brief intro, and certainly before you turn down other work to hold space for this client.

Wrapping Up

A good contract isn't about distrust. It's about clarity. When both sides know exactly what was agreed to, most problems resolve themselves before they become disputes.

Here are the concrete next steps to take this week:

1. Audit your current contract against the clauses listed here. Mark any that are missing or too vague to enforce.
2. Add a kill fee clause if you don't have one. This is the single clause most freelancers regret not having after a cancelled project.
3. Tighten your scope language by converting any general descriptions into numbered deliverables with explicit revision limits.
4. Add the IP transfer trigger so rights transfer on payment, not on delivery.
5. Have a contract attorney review your draft once — even a single one-hour consultation can catch jurisdiction-specific problems that templates miss entirely.