What to Check in a Client Contract: A Freelancer's Review Guide

When a client sends you their contract, the document has one job: to protect the client. That is not suspicious — it is how commercial agreements work. Every clause has been drafted (or copied from a template) to give the client maximum flexibility and minimum liability. Your job is to read the document from your own perspective and understand what you are actually agreeing to.

Most freelancers do not do this. They skim the contract, note the payment amount, and sign. Then scope creep sets in, an invoice gets delayed to Net-60, or a dispute about IP ownership emerges — and they discover the contract they signed does not protect them at all.

This guide walks you through the clauses that matter most when a client sends you their standard terms.

Why Client-Supplied Contracts Favour Clients

Client contracts are usually drafted (or reviewed) by the client's legal team, procurement department, or a template copied from a previous engagement. They reflect what the client wants: ownership of all deliverables, maximum payment flexibility, the right to terminate without penalty, and unlimited protection from freelancer errors.

This is not unusual or dishonest. But it means the baseline terms of a client-supplied contract are almost always tilted in the client's favour. The question is how far you are willing to accept those terms and which provisions you should push back on.

The good news is that most clauses in a client contract are negotiable. Clients expect freelancers to raise reasonable concerns — particularly established professionals. The key is to raise concerns before the project starts, in writing, and to focus on the provisions that matter most.

IP and Ownership: The Highest-Risk Clause

The intellectual property clause is the single most important provision to review in any client-supplied contract. Read our full guide on the intellectual property clause in freelance contracts before accepting any IP assignment provision.

Client contracts typically include broad IP assignment language: all work product, deliverables, and materials created in connection with the project are assigned to the client on creation or payment. The risk areas are:

Pre-existing IP inclusion. If the clause covers “all materials created in connection with the services” without carving out your pre-existing tools, frameworks, or methodologies, you may be assigning ownership of tools you use across multiple projects — not just what you create for this client.

Future work capture. Some contracts include language assigning IP not just for this project but for any future work done under the agreement. This is particularly problematic in MSAs and retainer arrangements.

Moral rights waiver. UK contracts sometimes include waiver of moral rights for creative work. Understand whether this applies to your work type and whether the waiver is appropriate.

Always negotiate a carve-out for pre-existing IP. The clause should assign only what you specifically create for this project — not your background tools, methodologies, or reusable components.

Payment Terms: Net-60 and Beyond

Check the payment terms carefully. Client-supplied contracts often include payment terms that are standard for large organisations but create real cash flow problems for freelancers.

Long payment periods. Net-30 is standard. Net-45 and Net-60 are common in larger organisations. Some corporate clients specify Net-90. For a freelancer who has already delivered work and incurred costs, waiting three months for payment is a significant burden.

Acceptance triggers. Some contracts tie payment to “client acceptance” rather than delivery. If the acceptance process is undefined or subject to the client's sole discretion, payment can be delayed indefinitely.

No late payment provisions. If the contract does not include a late payment clause, you are relying on the client's goodwill. Add one: a daily interest rate (8% above base rate is standard in the UK) provides both a deterrent and a remedy.

Scope and Change Requests

The scope of work is the foundation of the project. In client-supplied contracts, it is often defined vaguely, which gives the client room to expand what they expect from you without additional payment.

What to check:

• Is the deliverable described with enough specificity that both parties would agree on what “done” means?
• Is there an explicit change request clause requiring written agreement before any scope changes begin?
• Does the change request process include a mechanism for agreeing additional fees for changes?
• Are revision rounds defined and capped?

If the scope is vague, propose specific language before signing or attach a detailed scope document that is incorporated by reference into the contract.

Termination and Kill Fees

Client contracts almost always include a right to terminate for convenience — ending the project without cause, with notice. For the client, this is sensible risk management. For a freelancer who has already invested time in scoping and early deliverables, termination without compensation is a real financial risk.

What to check:

• What is the notice period for termination for convenience? Less than 14 days is very short for any substantial project.
• Is there a kill fee or compensation for work completed up to termination? Without one, you may work for nothing if the client terminates early.
• Is compensation tied to milestones, hours logged, or a flat percentage of the total fee?
• Can you also terminate the agreement, and on what terms?

Liability and Indemnification

Client contracts often include broad indemnification provisions requiring you to indemnify (compensate) the client for any losses arising from your services. Without a liability cap, this creates unlimited exposure. Read our guide on limitation of liability clauses for the full picture.

What to check:

• Is there a liability cap, and what is it set at? The project fee is a standard benchmark.
• Does the cap apply symmetrically to both parties?
• Are consequential losses (lost profits, reputational damage, third-party claims) excluded?
• Is the indemnification clause mutual, or does it only run in favour of the client?

Unlimited liability provisions are not standard even in corporate contracts. Push back on any indemnification clause that is not capped and mutual.

Confidentiality and Hidden Non-Competes

Confidentiality clauses are standard. What varies is whether the clause also functions as a non-compete by preventing you from working for similar clients or in the same sector.

Check whether the confidentiality clause:

• Covers only genuinely confidential information the client shares with you, not general industry knowledge
• Has a defined duration (2–5 years is standard; indefinite is not)
• Includes carve-outs for publicly available information and information you independently develop
• Prevents you from working with the client's competitors (if so, it is a non-compete and should be negotiated separately)

How to Push Back Without Losing the Client

Raising contract concerns does not damage the client relationship if done professionally. Most clients expect freelancers — particularly experienced ones — to review contracts and raise questions. Here is how to handle it well:

Do it in writing. Email is better than a call. It creates a record and allows you to be precise about which clauses you are questioning and what change you are proposing.

Prioritise your concerns. Do not redline every clause. Focus on the two or three provisions that create the most meaningful risk for you. Starting with everything looks like you are being difficult; starting with the highest-risk clauses looks professional.

Propose specific alternative language. Rather than saying “I am not happy with the IP clause”, propose the specific wording you want. This makes it easier for the client to accept your change and demonstrates that you understand what you are asking for.

Do it before starting work. Your negotiating position weakens significantly once you have started delivering. Raise concerns during the contract review stage, before any project work begins.

Client Contract Review Checklist

Before signing a client-supplied contract, confirm:

• IP assignment is limited to deliverables created for this project, with pre-existing IP excluded
• Payment terms are specified and commercially acceptable (Net-30 or better where possible)
• A late payment clause with defined interest or penalty is included
• Scope is described specifically, with a written change request process for additions
• Revision rounds are defined and capped
• Termination for convenience includes a kill fee or compensation for completed work
• Liability is capped at or near the project value, with consequential loss excluded
• Indemnification is mutual and subject to the liability cap
• Confidentiality has a defined duration and does not function as a hidden non-compete
• Dispute resolution and governing law are specified

FAQ

Is a client-supplied contract legally binding as-is?

Yes — once you sign, the contract binds you regardless of who drafted it. You can propose amendments before signing, but after signing, changes require the client's agreement. This is why reading and negotiating client contracts before signing is so important.

What clauses in a client contract are most often unfair to freelancers?

The five most problematic: broad IP assignment covering pre-existing tools; long payment terms (Net-45 to Net-90); client termination for convenience without a kill fee; unlimited indemnification obligations; and broad confidentiality provisions that function as hidden non-competes.

Can I negotiate a client-supplied contract?

Yes. Most contracts are negotiable, even those presented as standard terms. Raise concerns professionally and in writing before starting work. Focus on the highest-impact clauses rather than redlining everything. Most clients, even larger ones, will negotiate on IP, payment terms, and liability if concerns are raised clearly and early.

What should I do if a client refuses to negotiate?

Understand exactly what you are agreeing to and decide whether the project's commercial value justifies the contractual risk. Some terms — particularly broad IP assignment and unlimited liability — carry meaningful long-term risk that may not be worth accepting regardless of the project fee.

How do I identify a non-compete hidden in a confidentiality clause?

Look for confidentiality provisions covering not just specific information received from the client, but also business strategies, client lists, and future products. If the clause is so broad it would prevent you from working for the client's competitors or in the same sector, it is functioning as a non-compete and should be negotiated as one.

BeforeYouSign is an AI-powered educational tool. It does not provide legal advice. Always consult a qualified legal professional before making binding legal decisions.