What Belongs in a Freelance Contract (and What Doesn't).

You did the work. You sent the invoice. And then the client went quiet. No reply, no payment, no paper trail that says they owe you a dime.

Or maybe this version: the project was supposed to be a logo and a brand guide. Three months later, you're on your fifteenth round of "small tweaks" because the contract said "revisions until client satisfaction" and the client is never satisfied. Your freelance contract was supposed to be the lock on the door. Instead, you left it wide open.

Most freelancers learn this the hard way. You either get stiffed, scope-crept, or stuck with terms that quietly hand over your rights, your time, or your ability to take on other work. A freelance contract fixes that, but only if the right clauses are in it and the wrong ones aren't.

Key Takeaways

• Written freelance contracts are now legally required in California ($250+), New York ($800+), and Illinois for qualifying work.
• Every freelance contract needs seven clauses: scope of work with specifications, payment structure with late fees, IP assignment tied to payment, revision limits, a kill fee, AI usage terms, and a dispute resolution process.
• Five clauses to strike or refuse: non-competes, blanket work-for-hire language, unlimited exclusivity without extra pay, open-ended retainer rollover, and "all work product" IP grabs.
• Paying for work doesn't transfer copyright. Under U.S. law, the creator owns it by default unless a written IP assignment says otherwise.
• Retainer agreements need different contract language than project contracts, especially around unused hours, overage rates, and termination notice.

A Written Freelance Contract Isn't Optional Anymore

A freelance contract is a signed agreement between you and a client that defines the work, the pay, the timeline, and what happens when things go sideways. Without one, you're working on trust. Trust doesn't hold up in court.

This used to be a "best practice" conversation. Now it's a legal one.

California's Freelance Worker Protection Act, effective January 2025, requires a written contract for any freelance work valued at $250 or more. New York's Freelance Isn't Free Act sets the threshold at $800. Illinois passed its own version in July 2024. These laws have teeth — NYC alone has helped freelancers recover over $3.5 million through enforcement actions.

Even in states without freelance-specific legislation, a verbal agreement dissolves the moment a client decides your invoice isn't worth paying.

Seven Clauses That Belong in Every Freelance Contract

Scope of Work: Write Specifications, Not Outputs

"A website redesign" is an output. It's also the opening line of every scope dispute you'll ever have. Compare it with: "A five-page site built in Webflow, mobile-responsive, with three revision rounds included, delivered to a staging environment by March 15."

Your scope section should name the deliverables, the technical or quality standards, and the number of revision rounds included. Just as important: state what's not included. Without that boundary, every new request slides in as an assumption rather than a negotiation.

A client asking for "one more page" feels casual in a Slack message, but if there's no contractual line between in-scope and out-of-scope, you've got nothing to push back with. Add a change-order process: a short clause that says any work outside the agreed scope triggers a separate written agreement and a separate fee.

On our platform, standardized contracts prompt you for these specifications instead of vague descriptions.

Payment Structure and Late Fees

Get paid before you start. A deposit of 25–50% of the total project fee filters out clients who aren't serious and gives you a financial cushion if things go wrong later. For projects longer than four weeks, break the remaining balance into milestone payments tied to specific deliverables, not arbitrary calendar dates.

Your payment clause should also cover:

• A net-30 payment window (or shorter) with a specific late fee. 1.5% per month is standard. "Late fees may apply" is a suggestion; "1.5% monthly interest on unpaid balances beginning 31 days after invoice date" is enforceable.
• Which payment methods you accept and who covers transaction fees (wire transfer costs, platform percentages, currency conversion charges).
• A flat statement that the client can't demand a lower rate as a condition for paying on time. California's FWPA explicitly prohibits this practice, and your contract should too.

We built escrow and milestone payments into our platform for this reason. Funds are held before work begins, then released at agreed checkpoints.

Intellectual Property and Copyright

A common assumption: once a client pays for work, the client owns it. That's wrong. Under U.S. copyright law, the person who creates the work owns it by default.

The phrase "work for hire" shows up in contracts everywhere, but its legal reach is narrow. It applies to employees working within the scope of their jobs, or to independent contractors only when the work falls into one of nine specific categories listed in the Copyright Act of 1976: contributions to a collective work, translations, parts of an audiovisual project, and a few others. A logo, a blog post, a marketing strategy, a custom app? Those rarely qualify.

The fix is an IP assignment clause that transfers ownership to the client after full payment clears. Not before, not at delivery, not upon "acceptance."

Two carve-outs to negotiate into every freelance contract:

• Portfolio display rights. Your past projects are how you win future ones, and most clients won't object if you ask.
• Pre-existing tools exclusion. Templates, frameworks, and code libraries you bring to a project shouldn't become the client's property just because you used them on their job.

Revision Limits

"Unlimited revisions" is a blank check drawn on your time. Your contract should set a number of included rounds (two or three is standard), define what counts as a revision versus a new direction, and state a per-round fee for anything beyond the limit.

A revision modifies existing approved work: tweaking a headline, adjusting a color palette, tightening a paragraph. Scrapping an approved concept and starting over is new creative direction. That's new scope, and it triggers the change-order clause at your out-of-scope rate. Name this boundary in the contract and you'll stop arguing about it in email threads.

Kill Fee and Termination

A client cancels three weeks into a six-week project. You turned down other work to hold that time. Without a kill fee clause, you eat the loss.

Kill fees are pre-agreed compensation if the client pulls the plug after work has started. The standard range is 25–50% of the total project fee, and a tiered structure works well: 25% if the client cancels during the first phase, 50% in the middle stages, 75% near completion. The non-refundable deposit you collected up front serves as the floor. If the kill fee owed is less than the deposit, the client has already covered it. If it's more, they owe the difference.

A kill fee covers cancellations after work has begun. A cancellation fee covers the client backing out before work starts, compensating you for blocked calendar time. Both belong in your contract.

Your termination clause should require written notice (14 to 30 days) and specify that all completed work through the termination date is owed in full.

AI Usage and Disclosure

Most contract templates were written before AI was part of anyone's daily workflow. If you use AI tools for research, drafting, code generation, or image editing, the contract should address it before a client discovers it the wrong way.

Three things to put in writing:

1. Permitted use. Whether AI-assisted work is allowed and for which tasks. Some clients will be fine with AI-powered research but draw the line at AI-generated copy.
2. Ownership of AI outputs. The U.S. Copyright Office has ruled that works produced solely by AI without meaningful human authorship can't receive copyright registration. If a deliverable can't be copyrighted, the client can't own exclusive rights to it in the traditional sense.
3. Disclosure requirements. Whether you need to tell the client about AI use, and at what level of detail.

From the client's direction: specify that you won't input confidential client materials into public AI models without written consent. Designers, photographers, and illustrators are already writing these clauses into standard agreements. Every other freelance discipline should catch up.

Dispute Resolution and Governing Law

Specify how disagreements get resolved (mediation first, then arbitration or small claims) and which jurisdiction's laws govern the contract. Skip this clause and you could wind up litigating in the client's state under rules you've never read.

For international work, governing law determines everything from how IP ownership transfers to whether your late fee is enforceable. On our platform, built-in dispute resolution handles most disagreements without either side needing a lawyer.

Five Clauses That Don't Belong in a Freelance Contract

1. Non-Compete Clauses. In Chavez-DeRemer v. Medical Staffing of America, the Fourth Circuit flagged non-competes as evidence that workers were employees, not contractors, and upheld a $9 million judgment. If a client has confidentiality concerns, a non-disclosure agreement or non-solicitation clause covers it without blocking half your pipeline.
2. Blanket Work-for-Hire Language. "All work created during this engagement is work for hire" strips your ownership before you've been paid and often isn't legally valid for contractors. Push for the payment-conditional IP assignment clause described above instead.
3. Unlimited Exclusivity Without Separate Compensation. If a client wants you off-limits to their competitors, they're buying your capacity, not just your deliverables. That costs extra. Any exclusivity clause should name specific competitors (not "the entire industry"), expire when the contract does, and carry a separate fee.
4. Open-Ended Retainer Rollover. Letting unused hours pile up creates a growing work-debt that will come due at the worst time. A client who uses 8 of 20 hours for three months straight shouldn't show up in month four expecting 56 hours of work for the regular monthly rate. Cap rollover at 25% of the monthly allocation, or go use-it-or-lose-it.
5. "All Work Product" IP Grabs. Contracts that claim "all work product created during the engagement" can sweep up your side projects, pre-existing code libraries, and deliverables you're producing for other clients at the same time. Limit IP transfer to the specific deliverables listed in the scope of work.

How Retainer Contracts Differ from Project Agreements

Nearly every freelance contract guide treats projects and retainers the same. Retainers need different language.

The biggest retainer-specific trap: skipping the overage clause. Define your hourly or per-deliverable rate for work beyond the monthly allocation, and require written approval before you start any out-of-scope tasks.

We support both project and retainer payment workflows matched to each structure.

Frequently Asked Questions

Do I Need a Freelance Contract for Small Jobs?

In California, any freelance work over $250 requires one by law. New York sets the line at $800. Even where no statute demands it, writing a short scope-and-payment agreement takes ten minutes. Chasing an unpaid invoice without one takes months.

Should I Use My Own Contract or the Client's?

Yours, whenever possible. You wrote the terms, so the terms protect you. If a client insists on theirs, compare it against your baseline. Check the IP clause, payment timing, revision limits, and termination terms. Negotiate anything that's missing or one-sided before you sign. A client's template was written to protect the client.

Can a Freelance Contract Be an Email?

In some states, yes. Illinois's Freelance Worker Protection Act recognizes emails and texts as valid contracts if they describe the work and payment terms both parties agreed to. But a signed document is harder to challenge and easier to enforce. Use email confirmations as supporting evidence, not as the agreement itself.

What If a Client Refuses to Sign a Contract?

Walk. A client who won't put terms in writing wants flexibility, and that flexibility always tightens around the person doing the work, not the person paying for it.