Freelance Contract Review: What to Check Before Signing

Read a freelance agreement as a working plan

A freelance, consultant, or independent-contractor agreement does more than set a price. It should make the work executable: what will be delivered, when the client must respond, what counts as approval, what happens when the brief changes, and when payment and ownership move.

Start by tracing one deliverable from the brief to the invoice. If the agreement cannot tell both parties what is included, who accepts it, and what happens when facts change, the gap can become scope creep, delayed payment, or a dispute about ownership. This guide helps you identify those practical questions; it does not decide what a court or regulator would require in a particular jurisdiction.

Build the project from the contract

Use the sections below to test whether the document gives each stage of the work a usable boundary.

Scope, deliverables, and exclusions

List each promised output: quantity, format, quality standard, milestones, deadline, and any handover material. Phrases such as “as requested,” “reasonable additional tasks,” or “support as needed” can leave the boundary open. An exclusions list is just as useful as a services list.

Ask: Could a person who did not join the sales call tell what is included—and what would require a new quote?

Acceptance and approval

Find the named approver, the acceptance criteria, the review period, and the effect of silence. A clause allowing rejection in the client’s “sole discretion” can make completion difficult to measure even if the work follows the brief.

Ask: Who can approve, by when, against which written criteria, and what happens if feedback does not arrive?

Timeline and dependencies

Separate the freelancer’s deadline from inputs the client controls: access, copy, assets, data, decisions, feedback, and approvals. A fixed date without an extension mechanism can place delay risk on the person waiting for those inputs.

Ask: Does the schedule move when a required client dependency arrives late?

Completion, handover, and sign-off

Check what happens at the final milestone: delivery method, source files, credentials, documentation, acceptance, final invoice, and any post-launch support. A project is not necessarily complete just because a file was sent.

Ask: What exact event releases the final payment and closes the engagement?

Fees and payment terms: identify what is actually payable

Do not treat a headline project fee as the whole payment promise. Read the amount together with the trigger, invoice process, approval wording, expenses, tax wording, currency, and late-payment provision.

Topic	What to check	What to clarify
Fixed fee	Is the fee tied to a defined package of deliverables, or to an open-ended promise to help until the client is satisfied?	Which work is included, what triggers each instalment, and what is priced separately?
Hourly or daily rate	Look for time recording, minimum commitments, approval of hours, rate changes, and any cap.	Who approves time, how often is it invoiced, and what happens when the cap is reached?
Milestones, deposit, and final invoice	A payment can be guaranteed on an invoice date, or conditional on delivery, acceptance, launch, funding, or another event.	Which conditions must be met before each payment is due, and is there a deposit for committed time?
Expenses, tools, and taxes	Identify software, subscriptions, travel, equipment, licences, external services, and whether expenses need prior written approval.	Who bears each cost, are caps or receipts required, and does the fee include or exclude taxes where mentioned?
Payment timing and currency	Find the invoice due date, currency, payment method, bank charges, and any late-payment language.	When does the payment clock start, and can an internal approval process delay it?

Revisions are not the same as new work

A clean agreement separates correcting a mistake, an included revision, and a change request. Without that distinction, “unlimited revisions” can quietly change a fixed-fee project into open-ended work.

Correction

Work needed to bring a deliverable into line with the agreed specification. It should be measured against the original brief, not a later preference.

Included revision

A defined number of rounds or hours to refine an agreed deliverable. Check whether consolidated feedback is required and whether a revision can change the approved direction.

Change request

A new feature, audience, format, integration, deliverable, or material change to an approved direction. A useful process records the new scope, fee, and timeline before work starts.

Client-caused delay

Late feedback or missing materials may require the delivery date to move. The agreement can state how notice is given and whether reserved time or restart costs apply.

Intellectual property: separate the deliverable from the freelancer’s toolkit

The contract may assign ownership, grant a licence, or combine both. Read the definition of “work product” carefully. A clause assigning all IP created during the relationship may reach beyond the commissioned deliverable unless it distinguishes pre-existing materials, reusable tools, templates, code, know-how, and third-party components.

Transfer timing	Practical effect	What to clarify
On creation	The client may receive ownership as work is made, even before the final invoice is paid, depending on the wording and applicable law.	Which deliverables are covered, and does the freelancer keep a licence or security for unpaid work?
On delivery	The handover event becomes important: draft files, source files, and final deliverables may be treated differently.	What qualifies as delivery, and may the client use drafts before acceptance?
After full payment	Payment and ownership are linked operationally: the client may receive a limited right to review work until the final amount is paid.	What use is allowed before payment, and does the clause address an unpaid but already launched deliverable?

Check whether the freelancer can retain and reuse pre-existing code, templates, methods, libraries, and general know-how. A client can still receive the rights it needs in the agreed deliverable without every tool becoming client-owned.
If subcontractors contribute, verify that confidentiality and IP obligations flow down so the promised rights can be delivered. For software or creative work, identify any third-party or open-source materials and the licence terms that apply.
Portfolio rights are separate from ownership. The agreement may permit a name, logo, screenshot, case study, or anonymised description—or prohibit them through confidentiality or publicity wording.

Other operating clauses that change the risk

Confidentiality and client data

Confirm what is confidential, the permitted project use, who may access it, whether subcontractors need consent, and what return or deletion is practical. This guide does not replace a focused NDA review.

Independent contractor status

The contract may say there is no employment relationship and address taxes, benefits, equipment, and control over methods. That label does not by itself determine classification: the facts and applicable jurisdiction can matter.

Subcontracting

Check whether delegation is allowed, whether consent is needed, who remains responsible, and how confidentiality and IP obligations apply to contributors.

Liability, indemnity, and warranties

Identify a liability cap, whether it is linked to the contract value, any excluded categories, warranties, and indemnities for third-party claims. The practical concern is assuming losses that exceed the fee or sit outside the freelancer’s control.

Termination, cancellation, and handover

Read termination for convenience and for cause, notice, payment for completed work and committed time, any kill fee, return of materials, and the status of IP after termination. Cancellation is not just an exit right; it decides who absorbs work already reserved.

Exclusivity and non-solicitation

Treat a project exclusivity promise, post-project competitor restriction, client non-solicitation, and worker non-solicitation as separate restrictions. Read duration, territory, affected clients, prohibited activity, and stated exceptions rather than assuming a label answers the question.

A practical freelance contract checklist

Use this as a signing checklist. For each point, find the wording in the agreement and write down the answer—do not rely on a call or email that is not reflected in the contract.

1
Match the brief to the scope
Look for deliverables, formats, milestones, acceptance criteria, exclusions, and assumptions. Clarify anything a client could reasonably read more broadly.
2
Map every payment trigger
Identify the deposit, milestone invoices, due dates, approval conditions, expenses, currency, and late-payment wording. Ask which amount is due if the project stops halfway.
3
Put a boundary around revisions
Check the number of rounds, who provides consolidated feedback, how changes are priced, and when a deadline shifts.
4
Make dependencies visible
List client materials, access, decisions, and feedback that the freelancer needs. Clarify the notice and extension process when they arrive late.
5
Trace the ownership chain
Separate final deliverables from pre-existing tools, third-party assets, open-source components, portfolio use, and subcontractor contributions. Clarify when the transfer or licence begins.
6
Read the downside clauses together
Check liability caps, indemnities, warranties, confidentiality, termination, and restrictions on future clients. Clarify risks that are uncapped or disconnected from the fee.

Example clause, explained

Illustrative sample — not taken from a real contract

Client will review each Deliverable within five business days of receipt. If Client does not provide written notice identifying a material failure to meet the agreed acceptance criteria within that period, the Deliverable will be treated as accepted. Requests that change the agreed scope will be handled under a written change request.

Plain English

The clause gives the client a defined review window, requires feedback to identify a material mismatch with agreed criteria, and distinguishes a rejection from new work.

Potential concern

This structure only works if the acceptance criteria and the change-request process are concrete. “Material failure” and “agreed scope” can still become arguments when the brief is vague.

Question to ask

Who sends the approval notice, what criteria will they use, and what happens to the timeline and fee when the feedback changes the original brief?

Red flags you can recognise in the text

A red flag is a prompt to investigate, not an automatic conclusion that a clause is illegal or unenforceable.

“Unlimited revisions” or “all changes requested by Client.”

The promise may have no price, time, or scope limit.

Next step: Define revision rounds and route material changes through a written change request.

Payment only after “final approval” at the client’s sole discretion.

A subjective or open-ended approval step can delay the payment trigger.

Next step: Ask for named approvers, objective acceptance criteria, a review period, and a silence rule.

Assignment of all present and future intellectual property created during the relationship.

The language may sweep in reusable tools, unrelated work, or background materials.

Next step: Identify the commissioned deliverables and expressly reserve pre-existing materials and permitted reuse.

Unlimited liability or a broad indemnity with no stated cap.

The potential exposure may be out of proportion to the fee and may include risks the freelancer cannot control.

Next step: Ask what claims are covered, whether there is a cap, and which categories are carved out.

Immediate termination with no payment for completed work or committed time.

The freelancer may carry the cost of work already performed or time held open.

Next step: Clarify accrued fees, work in progress, cancellation payment, and handover obligations.

A vague exclusivity promise or ban on “competitors.”

It may restrict future work without identifying the clients, activity, duration, or territory.

Next step: Narrow the prohibited activity and list any known exceptions or existing clients.

Freelancer and client: the same clause, different operational needs

A useful agreement makes expectations visible for both sides. These are reading prompts, not a rule about which party should get a particular term.

Topic	Freelancer should check	Client should check
Scope	Can I price and schedule the requested outcome?	Does the scope identify the business result and handover I need?
Acceptance	Will I know when a milestone is complete and billable?	Do I have a clear, timely way to flag a genuine mismatch?
IP	Which tools and background materials can I keep using?	Do I receive the rights needed to use the paid-for deliverable?
Delays	Do deadlines move when inputs or feedback are late?	Will I be notified promptly when a dependency affects delivery?
Termination	What am I paid if reserved work is cancelled?	What work, files, access, and cooperation will I receive on exit?

Questions worth asking before signing

What exactly counts as a completed deliverable, and where are the acceptance criteria written?
How many revision rounds are included, and what makes a request a change in scope?
When is each invoice payable: on issue, delivery, acceptance, or another condition?
Which client materials, access, and decisions are needed before work can progress?
When does ownership transfer, and can the client use the work before full payment?
Which pre-existing templates, code, tools, and third-party materials remain outside the transfer?
May I use the work in my portfolio, name the client, or show screenshots—and when?
If the project is cancelled halfway through, what is payable and what must be handed over?
Is liability capped, and do the indemnity or warranty clauses create a different exposure?
Can I work with competitors or use subcontractors, and what limits actually apply?

A realistic scenario: the fixed-fee MVP

A freelance developer accepts a fixed fee to build an MVP. The agreement says the developer will provide “features as requested,” includes unlimited revisions, and makes the final invoice payable only after “final approval.” The client also needs to provide brand assets and product decisions, but the timeline has no dependency clause. An IP assignment covers everything created during the relationship, and termination allows immediate cancellation without explaining payment for work in progress.

Before deciding what any clause would mean legally, the developer can turn this into concrete questions: which screens, integrations, tests, and handover items are included; who approves each milestone and within what period; what happens when client decisions arrive late; which requests are a priced change; whether the client can use the MVP before final payment; and what fee and handover apply if the project is stopped. Those answers make the commercial deal more legible for both parties.

What the contract says vs. what may depend on your jurisdiction

What the contract says

The text can identify scope, fees, payment triggers, deadlines, ownership language, confidentiality, liability, termination, and restrictions. Those are practical commitments to locate and compare before signing.

What may depend on your jurisdiction

Worker classification, IP ownership rules, tax treatment, enforceability of liability limits or restrictions, mandatory payment protections, remedies, and the effect of an assignment or indemnity can depend on governing law and the actual working relationship. The label “independent contractor” is not a universal answer.

When professional legal review may be appropriate

A professional review can be particularly useful when the stakes or the allocation of risk make a plain-language first pass insufficient.

The project value is substantial or the engagement is long term.
The work creates strategically important IP, software, data, or regulated materials.
Liability is uncapped, the indemnity is broad, or third-party claims are a meaningful risk.
The relationship is cross-border or the governing law and dispute forum are unfamiliar.
The agreement contains exclusivity, non-compete, non-solicitation, or complex subcontracting provisions.
A large enterprise client requires terms that materially differ from the commercial proposal.

Frequently asked questions

Can a client own my freelance work?

The agreement may assign ownership or grant the client a licence, but the effect and any default ownership rules can depend on the wording, facts, and applicable law. Identify the deliverables, timing, and any retained pre-existing materials.

When should I get paid?

The contract should show the amount, invoice process, due date, and conditions for each payment. A fee described in a proposal can operate very differently if the agreement makes it conditional on acceptance or another event.

Can I reuse my code or templates?

Look for a reservation of pre-existing materials, reusable tools, and general know-how, plus any client licence needed to use them within the deliverable. Third-party and open-source terms may also matter.

What if the client asks for extra work?

Compare the request with the written scope and revision terms. A useful agreement describes a change-request process that records the additional fee and timeline before the work proceeds.

Can I work for competitors?

Check for project exclusivity, non-compete, confidentiality, and non-solicitation wording. Read the specific activity, clients, duration, territory, and exceptions; legal effect can vary by jurisdiction.

What if the client cancels the project?

Read the termination and cancellation clauses for notice, payment for completed work or committed time, any kill fee, handover, and the status of work product and client materials.

Can Lawyerless review a freelance agreement?

You can paste or upload it for a plain-language first pass on scope, payment, ownership, liability, and clauses worth reviewing. Lawyerless provides informational support, not legal representation or jurisdiction-specific legal advice.

Explore related contract concepts

Freelance contract

A broader introduction to the core parts of a freelance agreement.

NDA Review

A deeper guide to reviewing standalone confidentiality obligations.

Confidentiality clause

How a contract defines and controls confidential information.

Termination clause

How agreements set out notice, cancellation, and exit obligations.

Non-compete clause

A focused explainer on restrictions affecting future work.

Review your freelance contract before you commit

Upload or paste the agreement to get a structured, plain-language first pass on the terms that govern the work, payment, and risk.

Analyze My Freelance Contract

Sources and methodology

This educational guide focuses on reading the commercial and operational language of a freelance agreement. It does not present national rules as universal. The institutional sources below help distinguish an IP assignment from a licence and explain why the legal effect of a working relationship can be fact- and jurisdiction-dependent.

WIPO: Technology Transfer Agreements
Explains the distinction between IP assignments and licences, including the importance of identifying what is transferred.
ILO: Employment relationship and labour contracts
Provides international context for why the characterisation of a working relationship should not rest on a contract label alone.