Freelance Contract Clauses That Protect Your Pay

A freelance contract earns its keep in the moments a project goes sideways. Clients pause budgets, priorities shift, and invoices sit unpaid. Six clauses decide whether those moments cost you a week of income or a month of it. I learned that lesson the hard way early in my freelance work, and the contract I use now carries all six.

TL;DR: The Six Clauses That Protect Your Pay

Put these six clauses in your next freelance agreement: a payment schedule with an upfront deposit, a kill fee for canceled work, a late fee for overdue invoices, a tight scope definition, a revision cap, and an intellectual property transfer that takes effect on full payment. Each clause answers one question before a dispute asks it. Payment terms fix the amount and the date. A kill fee prices a canceled project. A late fee prices slow payment. Scope and revision clauses stop unpaid extra work. An IP clause keeps your leverage until the invoice clears.

Read the rest of this article for drafting language you can adapt, plus the state laws that already back you up. Treat the examples as starting points, not legal advice. A local attorney can tune the wording to your state and your type of work.

Also Read:

Freelance Retainers: Turn One-Off Gigs Into Steady Income

The Law Sets a Floor, Not a Contract

Two state laws give freelancers a baseline, and both point to the same lesson: get the terms in writing. California’s Freelance Worker Protection Act, known as SB 988, requires a written contract for freelance work valued at $250 or more, counting work for the same hiring party aggregated across 120 days. The written contract must name each party with a mailing address, list services with their value plus the rate and method of compensation, state the payment date or the mechanism that sets it, and state the date for submitting completed work or invoices for timely payment processing. The hiring party must keep the contract for at least four years. Payment falls due on the contract date, or within 30 days after completion where the contract names no date. Once work starts, the hiring party cannot make timely payment conditional on accepting less money or delivering extra work or rights beyond the agreement.

New York runs a similar regime under its Freelance Isn’t Free Act. The city version requires a written contract for services worth $800 or more, again aggregated across 120 days, with payment due on the contract date or within 30 days after completion. The state version extends the same idea statewide and requires the hiring party to keep the contract for six years. Freelancers who go unpaid can recover double the unpaid amount under the New York law. California’s statute also bars retaliation against freelancers who assert their rights. Read the California statute text for the exact requirements, and see this SB 988 summary for a plain-language breakdown. For New York, this client alert on both New York laws and this Freelance Isn’t Free Act guide cover the thresholds and remedies.

These laws help after a dispute starts. A contract helps before one starts. The statute sets a payment deadline. Your contract sets the deposit, the kill fee, the late fee, and the scope. Write those yourself, because no statute writes them for you.

Also Read:

How to Price Freelance Work Without Undercharging

Payment Terms: Schedule, Deposit, and Due Date

Payment terms answer three questions: how much arrives before work starts, how much arrives at each milestone, and the date each balance falls due. Name all three in the contract, with calendar dates or a clear formula such as a fixed number of days after delivery. Vague terms invite slow payment. A line that reads “payment due within 30 days of invoice” beats a line that reads “payment on completion” by a wide margin, because the second line starts an argument about the date completion happened.

An upfront deposit changes the power balance of a project. Deposits filter out clients who were never serious, and deposits cover the first stretch of work even where the project stalls. A common structure splits a fixed-fee project into three parts: a deposit before work starts, a payment at an agreed midpoint such as approved draft delivery, and a final payment on delivery. For a $3,000 project, that structure might mean $1,000 upfront, $1,000 at draft approval, and $1,000 on final delivery. Treat those numbers as an illustration, not a rule. Set the split that fits your cash flow and the client’s procurement process. Tie each payment to a concrete event the client can verify, such as delivery of files or written approval, so no payment depends on a subjective judgment call.

Put the payment schedule in your proposal as well as your contract, so the client sees the terms before the relationship starts. Our guide on how to write a freelance proposal that wins clients shows where terms belong in the pitch. Price the work itself with care, since a deposit percentage means little on a fee that was too low to begin with. See how to price freelance work without undercharging for a method that anchors fees to value delivered rather than hours spent.

Also Read:

Freelance Portfolio Mistakes That Cost You Clients

Kill Fee: Payment When a Project Ends Early

Projects die for reasons that have nothing to do with your work. Budgets freeze, stakeholders change direction, and internal champions leave. A kill fee clause states what the client owes when they cancel after work has started. Without one, a canceled project pays only for hours logged or milestones reached, and the gap between those milestones can swallow days of unbillable effort such as research, calls, and revisions already in progress.

Draft the kill fee as a percentage of the remaining fee, with the percentage rising as the project advances. One workable shape: cancellation before work starts forfeits the deposit, cancellation after the first milestone pays 50 percent of the remaining fee, and cancellation after final delivery review pays the full fee. For a $4,000 project canceled after the first milestone with $2,000 still unpaid, a 50 percent kill fee on the remainder pays $1,000 for work the client will not use. Treat that arithmetic as an illustration of the mechanism, not a market standard. Your percentage should reflect how much of the project value sits in early-stage work that a client cannot reuse.

Pair the kill fee with a delivery clause. State that the client receives all work completed up to the cancellation date, and that the kill fee covers the canceled portion rather than buying rights to unfinished concepts. That pairing keeps the clause fair and keeps the client from treating cancellation as a cheap way to harvest ideas. A kill fee also protects your calendar. A canceled project frees your schedule, and the fee compensates the weeks you held open for a client who walked away.

Also Read:

How to Get Paid on Time as a Freelancer

Late Fees: A Price on Slow Payment

Slow payment is a loan you never agreed to give. A late fee clause puts a price on it. State the fee as a monthly percentage of the overdue balance plus a flat administrative charge for each reminder cycle, and state the date the fee starts accruing. A typical illustration: a 1.5 percent monthly fee on a $2,000 invoice adds $30 for each month overdue. Treat that rate as an example. Check your state rules before fixing a rate, since some jurisdictions cap interest on commercial debts or require specific disclosure language.

A late fee works best beside a work-pause clause. The work-pause clause says you may pause further deliverables while an invoice sits past its due date, with the project timeline shifting by the same number of days. Pausing work costs the client momentum, and momentum is often worth more to them than the invoice amount. Send the first reminder on the due date itself, not a week later. Early reminders signal that your payment terms are real terms rather than decoration. For tactics that keep invoices moving, read how to get paid on time as a freelancer.

Enforcement matters more than the fee size. A 1.5 percent monthly fee that you actually charge beats a 5 percent fee that you waive to stay friendly. Clients learn your payment behavior from your first invoice. Charge the fee once, politely, and future invoices tend to arrive on time.

Scope, Revisions, and IP Transfer, Compared

Scope, revisions, and intellectual property form the second half of pay protection. Scope defines what the fee buys. A revision cap defines how many rounds of changes the fee includes. An IP transfer clause defines the moment ownership moves from you to the client. Each clause prevents a distinct form of unpaid work, and the table below shows the failure each one stops.

Scope language should name deliverables as concrete nouns: pages, screens, files, formats, and word counts. Avoid adjectives as scope definitions. A line that promises “a landing page” invites argument about what a landing page includes. A line that promises “one landing page design, desktop and mobile, delivered as editable source files plus exported images” leaves little room for argument. Anything outside the named deliverables becomes a change order with its own price and timeline. How to handle scope creep without losing clients covers the conversation side of holding that line.

Revision caps need the same concreteness. State the number of included rounds, what counts as a round, and the rate for rounds beyond the cap. Two rounds of consolidated feedback from one decision maker differ sharply from two rounds of scattered comments from five stakeholders. Name the feedback format in the contract, and the cap becomes enforceable instead of aspirational.

IP transfer on full payment is the clause that gives the rest of the contract teeth. Under this clause, you license the work for the client’s review during the project, and full ownership transfers only after the final invoice clears. The client can review, comment, and approve, but cannot publish or resell the work while payment is outstanding. This structure also clarifies the difference between assignment and licensing. Read IP assignment versus licensing for freelancers before choosing which model fits a given project. Keep portfolio rights explicit as well. State that you may show the work in your portfolio after launch, unless the client pays a separate confidentiality fee for a defined period.

Conclusion: Build One Standard Contract

Draft one standard contract that carries all six clauses, then adapt it per project instead of writing terms from scratch each time. Start with the payment schedule and deposit, add the kill fee and late fee, then close with scope, revision cap, and IP transfer on full payment. Check the result against the two state laws above, and have a local attorney review the template once before you reuse it across clients. That single review costs less than one unpaid invoice.

Your next step is small: open your current agreement, find the missing clause, and add it before your next proposal goes out. Clients who respect your work rarely object to clear terms. Clients who object to clear terms are telling you something worth hearing before work starts. This article is general information, not legal advice, and the law in your state may differ from the examples here.