Is My Freelance Contract Fair? A Pre-Signing Checklist for Independent Workers
A client contract is almost always drafted by the client, for the client. That does not make it evil — it makes it one-sided by default, and your job before signing is to spot the terms that quietly shift all the risk onto you. We review freelance and contractor agreements constantly, and the same few clauses cause the same expensive problems: getting paid, owning your work, and controlling how much work you actually have to do. Here is the checklist, in plain English, so you can sign with your eyes open.
Payment terms: when, how much, and what can hold it up
Start with the money, because this is where freelancers get hurt most. Look for a clear amount, a clear schedule, and a clear trigger for each payment. A deposit up front (often 25 to 50 percent) protects you if the client disappears. Watch the net terms: "Net 30" means you wait a month after invoicing, "Net 60" or "Net 90" can wreck your cash flow. And read carefully for what the client must do before payment is due — if it says payment is owed "upon final approval" or "upon acceptance" with no definition, the client can withhold your money indefinitely simply by never approving. Push for objective triggers (delivery, or a fixed number of days after delivery) instead of subjective ones.
The kill fee: getting paid if the project dies
A kill fee is compensation you receive if the client cancels partway through. Without one, a client can pull the plug after you have done most of the work and owe you nothing for it. Every freelance contract should address what happens on cancellation: ideally, you keep the deposit and are paid for work completed to date. If the contract lets the client terminate "for convenience" at any time with no compensation, that is a one-sided clause worth negotiating before you sign.
Who owns the work — and when
Intellectual property is where freelancers unknowingly give away the most. Many contracts say all work is "work made for hire" and assign everything to the client. Two things to understand. First, for independent contractors, "work made for hire" under the US Copyright Act is not automatic — it only applies to certain categories and only with a signed written agreement, so the exact language matters. Second, watch for clauses that hand over more than the final deliverable: your pre-existing tools, templates, and processes, or even unused concepts and rejected drafts. A fair contract transfers the specific deliverable on full payment and lets you keep your reusable tools and methods.
Ownership should follow payment
A small but important point: ownership of the work should transfer only when you have actually been paid in full. If the contract assigns all rights to the client on signing, and the client then fails to pay, you have handed over your work and lost your leverage. Look for, or ask to add, language that IP transfers "upon receipt of full payment." It is a standard, reasonable request and it keeps your strongest bargaining chip in your hands until the invoice clears.
Scope and the revision trap
Scope creep is how a profitable project turns into unpaid overtime. The contract should define the deliverables specifically, and it should cap revisions. A clause promising "unlimited revisions" or revisions "until the client is satisfied" is an open-ended commitment to work for free — subjective satisfaction has no finish line. Aim for a defined number of revision rounds, with additional rounds billed at your rate. Also look for a change-order process so that new requests beyond the original scope are priced and agreed, not just absorbed.
Non-solicitation and non-compete clauses
Some client contracts try to stop you from working with the client’s competitors, or from soliciting their other vendors and contacts, for a period after the project. A narrow, time-limited non-solicit can be reasonable. A broad clause that bars you from an entire industry, or from working with anyone the client has ever dealt with, can choke your business — and as an independent contractor, an overbroad non-compete is often unenforceable anyway. Read these closely and negotiate them down to something that does not threaten your livelihood.
Indemnification and liability
Buried in the back, you will often find an indemnification clause making you responsible if the client gets sued over your work, and sometimes a clause with no cap on your liability. For a solo freelancer, unlimited liability is a serious risk — a single dispute could exceed everything you earned on the project many times over. Look for a mutual indemnity (each side covers claims arising from its own fault) and a liability cap, commonly tied to the fees you were paid. These are normal, reasonable protections to request.
The 1099 misclassification angle
If a contract controls how, when, and where you work — set hours, requires you to use the client’s equipment, bars you from other clients — it starts to look like employment rather than an independent engagement. That creates IRS and state misclassification risk for both sides, and it can also mean you are giving up independence you are not being compensated for. You want a contract that defines the outcome and deadlines, not one that manages you like an employee.
Green flags: what a fair freelance contract looks like
Plenty of clients write fair agreements. Good signs include: a deposit and clear payment schedule, objective payment triggers, a kill fee or payment for work completed on cancellation, IP transferring on full payment, a defined scope with capped revisions and a change-order process, a mutual indemnity, and a liability cap. When you see these, the client has thought about a balanced relationship — which usually means they will be reasonable to work with, too.
How to ask for changes without losing the client
Negotiating a contract is normal and professional, and good clients expect it. Keep it collaborative and specific: "I am excited to work on this — a couple of small adjustments before I sign. Could we cap revisions at three rounds, and have IP transfer on final payment?" Most clients agree to reasonable, clearly-explained requests. A client who reacts badly to a polite, professional ask about payment and ownership is showing you how the project will go.
Can you show the work in your portfolio?
This one surprises people. If the contract includes a broad confidentiality clause and assigns all rights to the client, you may technically be barred from showing the work you did — in your portfolio, on your website, or in a case study — without the client’s permission. For designers, developers, writers, and other creatives, your portfolio is how you get the next job, so losing the right to display your work has real career cost. If displaying the work matters to you, ask for a portfolio carve-out: a sentence confirming you may show the deliverables as samples of your work, perhaps after the project is public or after a set time. Most clients agree, but only if you ask before signing.
Late payment: what recourse do you actually have?
Even a fair-looking contract can leave you powerless when an invoice goes unpaid. Look for, or negotiate in, real remedies: interest or a late fee on overdue invoices (a common figure is 1 to 1.5 percent per month), and the right to suspend or stop work until you are paid. Without these, a slow-paying client faces no consequence for dragging things out, and you are left financing their project. A clause letting you pause work on late payment is one of the most useful protections a freelancer can have, because it puts the pressure back where it belongs.
Whose law, whose courts?
Near the end you will find a governing-law and venue clause naming which state’s law applies and where any dispute must be filed. If the client is across the country and the contract requires you to litigate in their home state, a dispute over even a modest invoice can become impractical to pursue — the cost of fighting it where they are may exceed what you are owed. It is reasonable to ask for your own state, a neutral venue, or at least a low-cost dispute path like mediation before litigation. For small projects this rarely comes up, but for larger engagements it can decide whether you can realistically enforce the contract at all.
Get it in writing before you start work
The most common and most avoidable freelance disaster is starting work on a handshake and a "we will sort out the paperwork later." Later rarely comes, and when a dispute arises there is nothing to point to. Never begin paid work until the contract is signed and the deposit, if any, has cleared. Verbal agreements and email threads can sometimes be enforced, but they are far weaker and messier than a signed document, and proving the terms after the fact is its own expensive headache. A short, clear, signed agreement before day one protects both sides and sets a professional tone — and any client who resists putting basic terms in writing is telling you how the rest of the engagement is likely to go.
The bottom line
A fair freelance contract protects your payment, keeps your reusable work yours, and caps how much you can be asked to do and to risk. Read past the scope description, run the checklist, and negotiate the two or three terms that matter most for your situation. If you want a fast second opinion on the actual agreement, ClauseAudit reviews your freelance contract in about a minute, maps exactly who owns what, flags payment and revision traps, and drafts the email asking for changes. It is the difference between hoping a client is fair and knowing it before you start.
Don't guess — check your actual contract
Upload your freelance contract and our AI will flag the risky clauses in plain English, tuned to your state, with a downloadable report and redline.
This guide is general information from ClauseAudit, not legal advice. Laws vary by state and change — consult a qualified attorney for your situation.