Do freelancers legally need a written contract?

In most places, no, but the map is changing. New York State has required one since August 2024 for any freelance engagement worth $800 or more, and Illinois has required one since July 2024 at a lower threshold measured across a 120-day window; both attach double damages to late payment. Elsewhere a written agreement remains a matter of practice rather than statute. Check your own jurisdiction rather than assuming either way, because the trend is towards more of these laws, not fewer.

When should the client own the work?

On final payment, stated explicitly, with a licence to nothing before that point. The clause worth adding underneath is the one covering what happens if the project is abandoned midway: without it, you have delivered files whose ownership is genuinely ambiguous, and ambiguity favours whoever is more willing to litigate. Note that ownership and usage are separable — a client can own a mark outright while your right to show it in a portfolio survives, if you write that down.

What is a kill fee and what should it be?

Compensation owed when a client ends a project early, and the reason it exists is that you turned other work away to hold the slot. Structure it by stage rather than as a flat figure — work completed to date, plus the balance of the current phase, is the version clients accept without argument. A calendar-based version, protecting a booked window you can no longer refill, is fairer for retained or scheduled work and much harder to negotiate.

Is a contract enough to make sure I get paid?

No, and treating it as a payment guarantee is the expensive mistake. A contract wins you a judgment; a judgment is a piece of paper that says you are owed money, and collecting on it is a separate project with its own costs and its own low success rate. Money already in your bank account has none of those problems. Sequence accordingly: deposit first, contract second, optimism last.

Freelance contracts and getting paid: the complete guide

Since 28 August 2024, a written contract has not been a matter of professional preference in New York. Under the state's Freelance Isn't Free Act, any freelance engagement worth $800 or more — in one job, or added up across the previous 120 days — legally requires one, and a hiring party who pays late can be made to pay double.

That is the answer to "do I really need a contract," at least in one state, and it reframes the rest of this. What protects a freelance project is three things in a specific order: money banked before you start, a scope defined in writing that both sides read the same way, and terms saying who owns what and when. The contract is the container for the second and third. It is not the thing that gets you paid, and the last section here is about why.

What the law now requires, and where

Most guides on this subject open with a paragraph about how contracts show professionalism. That paragraph is now out of date in at least two American jurisdictions, and the specifics are worth having exactly rather than approximately.

New York State. The Freelance Isn't Free Act added Article 44-A to the General Business Law and took effect on 28 August 2024. Where the work is worth $800 or more, alone or aggregated over the preceding 120 days, the hiring party must put it in writing, and the writing has to name both parties, itemise the services, state the rate and method of compensation, and give the payment date or the mechanism for working it out. If the contract fails to name a payment date, the law supplies one: 30 days after the work is complete. Remedies for non-payment are the sum owed plus double damages and legal fees. The hiring party has to keep the contract for six years. (New York Department of Labor; Venable LLP's 2024 summary of the Act.)

Illinois. The Freelance Worker Protection Act came into force on 1 July 2024, on the same pattern with a lower bar: five hundred dollars of work across any 120-day window. Late payment is double the underpayment plus fees, and simply failing to produce a written contract carries statutory damages of the greater of that same threshold or the value of the contract. (Illinois Department of Labor; Jackson Lewis's 2024 summary.)

California, statewide since 1 January 2025 under SB 988, at a $250 threshold. And the City of Los Angeles has had its own ordinance since 1 July 2023, at $600, with a four-year record-retention rule of its own. You will see Minnesota listed in this company in a lot of articles; we went looking and could not confirm it, so treat that one as unverified until you have read the statute yourself.

What all of them share is the structure worth understanding even if you work nowhere near any of them: a dollar threshold, a written-contract requirement, a default payment clock when the contract is silent, and a penalty large enough that a client's finance department would rather pay you than test it.

Two things follow practically. First, in a covered jurisdiction the written contract is the cheapest insurance available to you, because the statute does the enforcement work your own drafting could never do. Second, the reason to send one everywhere else is unchanged and has nothing to do with law: it is the only way two people find out, before the money is spent, that they meant different things.

This is a description of what these statutes say, with dates and sources so you can check them. It is not advice about your situation, and every one of these laws is specific to a place — read yours, or ask somebody who has.

The clauses, written out

Every guide on this query lists the clauses. The best-ranked one names nine and gives sample wording for none of them, which is like a recipe that lists ingredients and omits quantities. So here they are as sentences, generic enough to adapt and specific enough to use.

Scope and deliverables. The clause that prevents the most arguments, and the one to spend the most time on:

The Contractor will provide: [itemised deliverables, with formats and quantities]. Work not listed above is not included, specifically: [the tempting adjacent things]. Additional work will be quoted separately and agreed in writing before it begins.

The naming of what is excluded is the part people leave out, and it is the part that works. The full treatment lives in the four sentences that stop scope creep; do not make this clause carry that whole job alone.

Payment. Amount, schedule, and what late means:

Total fee: [amount]. Half is payable before work begins and is non-refundable. The balance is payable on delivery of final files, within [number] days of invoice. Invoices unpaid after that period accrue interest at [rate] per month, and work on all active projects pauses until the account is current.

The pause clause matters more than the interest. Interest is a number a client can decide to absorb; a stopped project is a problem they have to solve today.

Intellectual property. Ownership transfers on final payment, and not before:

All rights in the deliverables remain with the Contractor until the final invoice is paid in full, at which point ownership transfers to the Client. Prior to that, the Client has no licence to use the work. The Contractor retains the right to display the work in a portfolio and in awards submissions unless agreed otherwise in writing.

That last sentence gets deleted from a lot of client-supplied contracts, and getting it back is usually a thirty-second conversation, because nobody actually cares until you have already given it away.

Revisions. A count, and a definition of what one is:

The fee includes [number] rounds of revisions. A round is one consolidated set of feedback from the Client, delivered in a single response. Feedback arriving after a round is closed will be gathered into the next round or quoted as additional work.

Without the definition, two rounds becomes six by way of email.

Termination and the kill fee. What is owed when it ends early:

Either party may end this agreement in writing. On termination the Client pays for all work completed to the date of notice, plus the remaining balance of the current phase. Deposits are not refundable. Work completed but unpaid remains the property of the Contractor.

You turned other work away to hold that slot. That is the thing the kill fee is for, and saying so out loud in the negotiation makes it much easier to keep.

A general note on drafting them yourself: shorter and plainer wins. A two-page agreement a client reads is worth more than a twelve-page one they sign without reading, because the value is in the shared understanding, and an unread clause produces none of it. A checklist to work through before you send one is a faster route than starting from a blank page.

The clauses you can leave out, and the two you should not

The lists you will find elsewhere run to nine or fifteen items, because a list is easy to lengthen and nobody is ever criticised for including too much. Somebody has to make the call about what earns its place on a job worth a few thousand, so here is mine.

Leave out the elaborate dispute-resolution ladder. Mediation, then arbitration, then a named venue, is a structure built for parties who will both still exist and both still be represented in three years. On a solo project it mostly guarantees that any dispute becomes too expensive for you to pursue, which discourages the wrong party. Leave out mutual indemnification boilerplate copied from a software agreement. Leave out confidentiality clauses that run longer than the scope section, unless the client asked, in which case sign theirs and move on.

Two are worth keeping. The first is a liability cap:

The Contractor's total liability under this agreement is limited to the total fees paid by the Client.

Without it your exposure on a two-thousand-dollar project is theoretically unlimited, which is an absurd position to be in, and this single sentence closes it. On a large or safety-adjacent job this is the clause where an actual lawyer earns their fee.

The second is a plain statement of status:

The Contractor is an independent contractor. Nothing in this agreement creates an employment relationship, partnership, or agency.

That protects the client more than you, which is exactly why including it makes the agreement easier for them to sign, and it saves you from the tax and classification arguments that occasionally follow long retainers.

The deposit does more work than the contract

There is a small exchange in the Clients From Hell archive that settles this better than any argument I could make. A software firm asked an insurance company for a deposit. The insurer refused. The salesperson asked: would you insure a company that did all their work upfront without getting paid?

Money in your account cannot be disputed, delayed, renegotiated, or lost to somebody deciding that your invoice is next quarter's problem. It is the only part of this whole apparatus that has already happened. Half up front is standard practice for creative project work — a norm, not a survey finding, and anyone quoting you a percentage as a statistic is guessing — and it does more for you than every clause above put together.

The new statutes do not change that ranking. They make the written contract cheap and, in some places, compulsory, which is a good reason to always have one. They do not make it faster than money you already hold. If a client will agree to only one of the two, take the deposit and write the scope down in an email, then go back for the signature.

Which is also a test for a client worth having. Read enough of these threads and the pattern is hard to miss: the client who treats a deposit request as an insult is very often the same client who later treats the invoice as an opening offer.

What a contract cannot do

A freelancer on Hacker News took a non-paying client to court and won a judgment for around $20K. Then, in his words: he never paid. Sent to a collection agency, who called back within a day to say they knew of him well.

That is the ceiling on paperwork. A contract gets you a strong position in a dispute, and a judgment confirms you were right. Neither one is money, and converting either into money is a separate project with its own cost, its own timeline and its own decent chance of ending with nothing. Contracts are still worth having. What is not worth having is the belief, very common in the guides, that owning one means you will be paid.

So use the contract for the thing it is genuinely excellent at, which is preventing the dispute rather than winning it. Almost everything expensive that happens to freelancers happens in the gap between two reasonable people who understood the same sentence differently, and written scope, terms and ownership all close that gap. None of them closes the other one, between a client who has your files and a client who has paid for them. For that the tools are the deposit, the delivery schedule, and what to do once an invoice has gone quiet.

The unexciting operational half

This section is boring and short because the work is boring and short, and skipping it is the most common way a well-drafted project still goes wrong.

Put an acceptance clause in: deliverables are deemed approved if the client does not respond within a stated number of working days. Without one, a project can stay technically unfinished forever, and an unfinished project is an unpayable invoice.

Invoice the day the milestone lands, not at the end of the month. Put the purchase-order number on it if they use them, because an invoice without one goes into a drawer rather than into a system. Name a due date rather than "net 30," since the two mean the same thing to you and only one of them means anything to the person in accounts payable.

And keep the signed copy somewhere you can find it in a hurry. In New York the client is legally obliged to keep it for six years. You should probably match them.

In North the contract is drafted alongside the proposal and shown to the client the moment they accept, so the terms arrive attached to the decision rather than as a separate hurdle a week later.

Deposit first. Scope in writing second. Signature third. In that order, on every job, including the small friendly one.