Skip to main content
Guides·7 min read

The Freelance Contract Clauses That Protect Your Money

Most freelance contracts protect the client, not you. These are the clauses that shift the balance — and the exact language to use.

M

Mitch Reise

April 12, 2026

freelance contractkill feescope creeppayment termsIP ownershipfreelancecontractor
Share

This article is for informational purposes only and does not constitute legal advice. For contracts involving significant money or complex IP, consult an attorney.

Most freelance contracts are written by clients or by freelancers who copied a template from the internet. Both sources tend to produce contracts that protect the client's flexibility at the expense of the freelancer's income. A few specific clauses make a significant difference. Here's what to include and why.

The Kill Fee Clause

A kill fee (also called a cancellation fee or early termination fee) is what you're owed if the client cancels a project mid-stream. Without one, a client can cancel after you've completed 60% of the work and owe you nothing for the completed portion.

Standard language:

If Client cancels this project after work has commenced, Client agrees to pay a kill fee equal to: 25% of the project total if cancelled before 25% completion; 50% if cancelled between 25–50% completion; 75% if cancelled between 50–75% completion; and 100% if cancelled after 75% completion or within 7 days of the final delivery date.

The exact percentages are negotiable, but the principle is non-negotiable: you need compensation for work already done and for the opportunity cost of having held time for this project.

A simpler version: a flat 25–50% kill fee on any cancellation, regardless of completion stage. This is easier to administer and common for ongoing retainer relationships.

If a client objects to a kill fee, that's a meaningful signal. A client confident in their commitment to the project shouldn't have a problem with it.

Payment Terms: Net 15, Not Net 30

The default in many industries is net-30 — payment due within 30 days of invoice. For freelancers, net-30 is a working capital problem. You've delivered work, you're waiting 30 days to be paid, and you may be 30–60 days out before you actually receive funds (invoices often take time to get approved internally on the client side).

Push for net-15 as your standard. It's reasonable and most clients will accept it. Language:

Invoices are due and payable within fifteen (15) calendar days of the invoice date.

For ongoing retainer clients, consider requesting payment in advance — billing on the 1st of the month for work performed that month, or billing mid-month for the second half. Monthly retainer clients who pay in arrears are effectively borrowing your services for 30+ days interest-free.

Use the Invoice Due Date Calculator to model the cash flow difference between net-15 and net-30 on your specific invoice volume. The working capital difference over a year is usually in the thousands.

Late Fee Language

Without a late fee clause, you have no formal recourse for slow payment beyond sending a politely worded reminder. With one, you have a financial incentive structure that encourages on-time payment.

Standard language:

Invoices not paid within the payment period will accrue a late fee of 1.5% per month (18% APR) on the unpaid balance, beginning the day after the due date. A grace period of 5 calendar days is provided before fees begin accruing.

The 1.5%/month (18% APR) rate is standard and widely accepted. Some freelancers use 2%/month; anything above 2% may run into state usury law complications depending on your jurisdiction.

Important: you must include this language in your contract before doing the work. You can't add a late fee clause retroactively. And in practice, even if you don't enforce the fee every time, its presence in the contract changes how seriously clients treat your payment deadlines.

The Invoice Late Fee Calculator shows you the accrued amount at any rate and time period, and includes contract language templates you can copy directly.

Scope Change Orders

Scope creep is the single biggest margin killer for freelancers. It's the accumulation of "just one more thing" requests that push a project 20–40% past its original scope with no corresponding increase in payment.

The fix is a written change order process:

Any work requested beyond the scope defined in this agreement (including additional features, deliverables, design directions, or revision rounds beyond the number specified) will be treated as a change order. Change orders require written approval from both parties before work commences and will be billed at Freelancer's standard hourly rate of $[X]/hr or at an agreed project rate.

Key details:

  • "Written approval" means email is fine — it doesn't need to be a formal document, but it needs to be documented
  • Specify what "beyond scope" means — if the contract specifies 2 revision rounds, a third revision is a change order
  • Make clear that change order work begins only after approval — not as a good-faith gesture while you wait for the client to decide

For ongoing clients, the Scope Creep Calculator quantifies what uncompensated scope additions are costing you annually. The number is usually surprising.

Revision Limits

Unlimited revisions are unlimited liability. Define them explicitly.

This agreement includes [X] rounds of revisions on each major deliverable. A revision round is defined as a single consolidated set of feedback submitted by Client. Additional revision rounds will be billed at Freelancer's hourly rate.

Two to three revision rounds is standard for most creative and technical work. One round is appropriate for highly scoped, well-defined deliverables.

The key mechanic is "consolidated feedback" — the client gets one round of revisions when they review and submit all feedback at once, not a drip of individual requests over two weeks. This prevents revision rounds from becoming indefinite ping-pong.

IP Ownership: Work for Hire vs. Licensed

Intellectual property ownership is often unaddressed in freelance contracts, which creates ambiguity that defaults to the freelancer's advantage under copyright law — but which clients may dispute.

There are two standard structures:

Work for hire: The client owns all IP upon full payment. The freelancer retains no rights to the work.

Upon receipt of full payment, Freelancer assigns all intellectual property rights, including copyright, to Client. All work produced under this agreement is considered a work made for hire under 17 U.S.C. § 101 to the maximum extent applicable.

License: The freelancer retains ownership; the client receives a license to use the work. This is appropriate when the freelancer wants to retain portfolio rights, reuse components, or maintain ownership of underlying code/assets.

Upon receipt of full payment, Freelancer grants Client a perpetual, non-exclusive, worldwide license to use the deliverables for [specified purposes]. Freelancer retains all copyright and may use the work in portfolio, case studies, and marketing materials.

For most client work, work-for-hire is standard and expected. For tools, components, or code that you'll reuse across multiple clients, a license structure makes more sense — but discuss it explicitly rather than leaving it ambiguous.

Retainer Scope and Expiration

If the engagement is a monthly retainer rather than a fixed project, add explicit terms for unused capacity:

Unused hours or deliverables from any given month expire at month end and do not roll over. Client may not bank capacity for use in future months.

Without this clause, a client who uses only 10 of their 20 monthly retainer hours in March can theoretically demand 30 hours in April. Explicit expiration prevents this. Some freelancers allow one-month rollover as a goodwill provision — include it if you want, but put it in writing.

See the Retainer Calculator for modeling what different retainer structures mean for your income and capacity utilization.

The Practical Reality

You won't win every negotiation on every clause. Large enterprise clients will have their own contract templates and legal teams. But with small and mid-size clients — which is where most freelancers do most of their business — these terms are standard professional practice, and most reasonable clients will accept them.

Start from a position of having these clauses in your template. If a client pushes back, negotiate from there. The worst outcome is you end up at net-30 instead of net-15, or at a 25% kill fee instead of 50%. The best outcome is you never have to think about it again because the contract already covers you.

The clients who object strongly to standard professional terms — kill fees, defined revision rounds, scope change orders — are the ones most likely to need those protections later. That's useful information.

Share
M

Mitchell Reise

Founder of Reise Tools · Contractor finance nerd. Building tools that help freelancers and 1099 contractors understand their money.