Some links in this post are affiliate links. We may earn a small commission if you sign up — at no extra cost to you.

Freelance Client Contract Checklist: 10 Points Before You Sign

Most freelancers who get burned by a client contract don't sign something obviously bad. They sign something incomplete — a document that looks professional but skips the clause that would have saved them three weeks of unpaid work or a costly revision spiral.

Before you sign anything, go through this 10-point checklist. If any of these items are missing or vague, ask for an amendment. A client who refuses to clarify basic terms before the project starts is telling you something important.

Why Contracts Fail Freelancers

Contracts typically fail at one of two points: the scope discussion or the payment discussion. Either the deliverables are vague enough that both parties can be technically correct during a dispute, or the payment terms leave the freelancer exposed to late payment, non-payment, or scope expansion without additional compensation.

The checklist below covers both failure points — and a few others that only show up after a project goes sideways.

The 10-Point Contract Checklist

1. Scope of Work Is Explicit

The contract should describe exactly what you're delivering — not categories of work, but specific deliverables. "Website design" is not a scope. "Five-page website including homepage, about, services, contact, and blog — desktop and mobile layouts, delivered as Figma files" is a scope.

If the scope is ambiguous, the client will fill in the gaps with assumptions. Those assumptions are usually more expansive than yours.

Check that the contract defines:

Number and type of deliverables
What's explicitly excluded
Format of final files
Number of revision rounds

If any of these are missing, add them before signing.

2. Revision Limits Are Defined

Unlimited revisions is not a policy — it's an income leak. Every round of revisions costs you time. Without a defined limit, clients will use as many as they want, and you'll feel too awkward to stop them mid-project.

A strong contract specifies:

Number of revision rounds included (typically 2–3)
What constitutes a revision vs. a new request
What happens when the client exceeds the included rounds (additional fee per round)

The change order process is part of this. If the client wants something outside the original scope, you need language that triggers a new agreement — not a free addition.

3. Payment Schedule Is Clear

The contract should spell out exactly when payment is due — not "upon completion" or "net 30 from invoice date" as the only terms. A professional payment structure typically includes:

Deposit upfront (25–50% of total project value)
Milestone payment at an agreed project point
Final payment upon delivery or approval

Deposits protect you from clients who disappear or cancel. Milestone payments protect you from scope creep. Final payment protects you from endless approval delays.

Check that the deposit is nonrefundable (within reason) and that the payment schedule is tied to deliverable milestones, not to subjective approval.

4. Late Payment Consequences Are Stated

A payment due date without a consequence is just a suggestion. Include a late fee clause — typically 1.5% per month on the outstanding balance — and a provision allowing you to pause work or withhold deliverables if payment is overdue beyond a set period (e.g., 10 business days).

Many freelancers never enforce late fees, but including the clause changes client behavior. It signals that you're running a real business with a real billing process.

Check that the contract specifies:

Late fee percentage and when it kicks in
What happens to deliverables during late payment
Whether you can stop work if invoice is overdue

5. Kill Fee Clause Is Included

Projects get cancelled. Clients get cold feet, budgets get cut, priorities shift. Without a kill fee clause, a cancelled project means unpaid work on your side.

A kill fee is a percentage of the total project fee paid to you if the client cancels after work has started. Common structures: 25–50% of remaining project value if cancelled past a certain milestone.

This protects you from the scenario where you've completed 60% of a project and the client suddenly decides not to proceed — and believes they don't owe you anything for the work done.

Check that the kill fee:

Applies at each project stage (not just at the start)
Is a clear dollar amount or percentage
Includes what happens to work already delivered

6. Intellectual Property Ownership Is Assigned

Who owns the work once it's complete? If the contract doesn't specify, IP ownership defaults to the creator — you — in most jurisdictions. But clients often assume they own everything they've commissioned.

If you're doing a work-for-hire arrangement (full IP transfer to the client), the contract should say so explicitly. If you're licensing the work (client can use it, you retain ownership), the usage rights need to be defined — scope of use, geographic restrictions, duration.

Beware of contracts that grant the client "unlimited, irrevocable, worldwide rights" without specifying the usage context. That language is appropriate for a full buyout, not a limited-use license.

7. Confidentiality Requirements Are Mutual

Many client contracts include NDAs or confidentiality clauses protecting the client's information. That's reasonable. What you should check is whether the NDA is one-sided (you can't discuss the project) or mutual (neither party discloses the other's confidential information).

Also check:

Whether the confidentiality clause prevents you from listing the client as a reference or including the work in your portfolio
Duration of the confidentiality obligation
Whether receiving publicly available information or reverse-engineered information is excluded

Overly broad NDAs can prevent you from getting future work by stopping you from referencing this engagement.

8. Dispute Resolution Is Defined

If something goes wrong and you can't resolve it directly, what happens? The contract should specify:

Which state or country's law governs the agreement
Whether disputes go to arbitration, mediation, or court
Who pays legal fees if the dispute escalates

"Binding arbitration" clauses are common in client contracts and generally favor large companies over individual contractors. If you see one, understand what it means before signing.

9. Termination Terms Are Explicit

Either party should be able to exit the contract under defined conditions. The contract should specify:

Notice period required for termination (e.g., 14 days written notice)
What happens to completed work upon termination
Whether you're paid for work in progress at termination
What triggers immediate termination (non-payment, breach of contract)

Contracts without termination clauses leave you legally bound to a project indefinitely — even a bad one.

10. Communication and Approval Process Is Outlined

Scope creep often comes through informal communication — a Slack message, an email, a verbal "can you just add this?" If the contract doesn't specify how changes get approved, verbal requests can spiral.

The contract should specify:

What communication channels are official (email, project management tool)
How approvals are given (written sign-off, not just silence = approval)
Who on the client side has authority to request changes

This is especially important for projects with multiple client stakeholders. You need to know whose approval counts.

Using a Contract Template

Writing contracts from scratch for every client is inefficient and risky. A professional contract template covers these 10 points in plain English, customizable for any project type. The Freelance Contract Template Pack includes multiple contract types — project, retainer, and hourly — each with all 10 clauses pre-written.

Going through this checklist takes about 10 minutes before any project starts. The time you spend reviewing a contract before signing is a fraction of the time you'd spend resolving a dispute afterward.

Red Flags to Watch For

Beyond the checklist, a few patterns should slow you down before signing:

Vague SOW with an eagerness to "figure it out as we go" — this almost always means scope creep
Payment on net 60 or net 90 — these are corporate payment terms pushed onto freelancers who have no AP department leverage
No kill fee and no deposit — the client is keeping all the risk on your side
"We own everything you produce for us" — check if this extends to work done on your own time
No revision limits — you'll be in an endless loop

A contract that passes this checklist doesn't need to be long. Some of the most airtight freelance contracts are one or two pages. What matters is clarity and coverage — not length.

👉 Get the Freelance Contract Template Pack — $25