How to Review a Freelance Contract in 10–15 Minutes

A freelance contract does not need to be thirty pages long to create expensive problems.

A short agreement can still leave you unclear about what you have to deliver, when you get paid, who owns the work, how many revisions are included, or what happens if the client ends the project early.

The useful question is not:

“Have I understood every line of legal wording?”

It is:

“Have I found the terms that could materially change my workload, payment, rights or risk?”

A repeatable review workflow helps you answer that quickly.

Use this as a first-pass checklist

In 10–15 minutes, aim to locate the relevant clauses and write down the questions you need answered. The aim is not to certify that the contract is safe to sign.

Follow the sections below in order, or search within this page for the numbered step you need. The timed routine later in the guide is a suggested way to organise the first pass, not a deadline for understanding every issue.

For each concern, record:

• the clause or schedule it appears in;
• what it could change about your work, payment, rights or exposure;
• the specific question you want the client to answer.

If the wording refers to another schedule or set of terms, obtain and read those too before deciding. Missing documents can leave the apparent deal incomplete.

What is a freelance contract review workflow?

A contract review workflow is simply a consistent order for checking the parts of an agreement that matter most to you commercially.

Instead of reading from page one to the signature block and hoping the important clauses stand out, you deliberately look for the terms that affect:

• what work is included;

• when and how you get paid;

• how revisions and approval work;

• who owns the finished work;

• whether you can reuse or show any of it;

• what must remain confidential;

• whether you are restricted from taking other work;

• how either side can end the agreement;

• how much liability you could face;

• which law, court or dispute process applies.

That does not turn a quick review into legal advice.

It gives you a structured first pass so you know what deserves a closer look.

Start with the commercial shape of the deal

Before getting into individual clauses, make sure you can answer five basic questions.

What exactly am I being paid to deliver?

You should be able to describe the deliverables without relying on vague phrases such as “support as required”, “reasonable revisions” or “other services requested by the client”.

What has to happen before I get paid?

Check whether payment depends only on sending a valid invoice or also on:

• client approval;

• project completion;

• a milestone;

• timesheet approval;

• another customer paying your client;

• a purchase order or other administrative step.

The difference can materially change when money actually reaches you.

What rights am I giving the client?

Look beyond a heading labelled “Intellectual Property”.

The contract may deal with:

• ownership of final deliverables;

• pre-existing tools and templates;

• source files;

• reusable code or components;

• portfolio use;

• moral rights;

• licences rather than outright ownership.

How can the project end?

Check whether either side can terminate on notice, whether there are immediate termination rights, and what happens to money already earned or work already completed.

What is the downside if something goes wrong?

This is where liability, indemnity, warranties, insurance and dispute clauses matter.

A £3,000 project can look very different if the contract exposes you to financial claims far beyond £3,000.

Step 1: check scope and deliverables

Start with the work itself.

A clear scope should make it reasonably easy to tell when you have completed what you were hired to do.

Look for:

• specific deliverables;

• quantities;

• formats;

• deadlines;

• included meetings;

• included support;

• dependencies on the client;

• anything explicitly excluded;

• how extra work is approved and priced.

Vague wording creates room for two people to remember the deal differently.

For example:

The Contractor will provide design support as reasonably requested by the Client.

That may be perfectly workable in a day-rate engagement.

It is much less comfortable if you agreed a fixed price for a defined project.

The useful question is:

“Could I tell from this contract whether a new request is included in the agreed price?”

A question you can send to the client

Could we list the agreed deliverables and anything outside scope, with additional work handled through a separate written change request?

For more detail, read our guide to scope and deliverables.

Step 2: check payment timing and triggers

Do not stop when you find the project fee.

You need to know what starts the payment clock.

Check:

• the total fee or rate;

• any upfront payment;

• milestone payments;

• when invoices can be issued;

• the payment period;

• whether approval is required before invoicing;

• expenses;

• VAT wording where relevant;

• disputed invoice procedures;

• rights to pause work if payment is overdue;

• whether payment depends on money arriving from somebody else.

There is no universal deposit percentage or payment period that is right for every freelancer.

A two-day piece of work for an established client creates a different cash-flow risk from a three-month project for a new business.

The important point is that the trigger should be clear.

“30 days from invoice” is different from “30 days from final acceptance”, particularly if final acceptance has no deadline.

A question you can send to the client

Could we make payment due 14 days from a valid invoice, rather than linking the payment date to final approval?

For more detail, read our guide to payment terms.

Step 3: check revisions and acceptance together

Revisions and acceptance are often treated as separate clauses, but commercially they are closely connected.

Check:

• how many revision rounds are included;

• what counts as a revision;

• what counts as new work;

• who can request changes;

• whether feedback must be consolidated;

• what makes a deliverable accepted;

• how long the client has to review it;

• what happens if the client does not respond.

The useful question is:

“Can this project remain unfinished indefinitely because the client never formally approves the work?”

A defined review period can make the process much clearer.

So can objective acceptance criteria.

“Accepted when it meets the specification in Schedule 1” gives both sides something to work with.

“Accepted when the Client is completely satisfied” leaves much more room for disagreement.

A question you can send to the client

Could we add a defined review period, with any rejection identifying the specific agreed requirement that has not been met?

If appropriate for the project, you might also discuss what happens when the client does not respond within that period.

For more detail, read our guide to acceptance and delayed approval.

Step 4: check intellectual property and portfolio rights

Do not assume that delivering work and transferring ownership are the same thing.

Read the actual wording.

A contract may say rights transfer:

• as the work is created;

• when it is delivered;

• when the client accepts it;

• when the relevant invoice is paid;

• on some other stated event.

Those positions can have different commercial effects.

Also distinguish the work created specifically for the client from material you already owned or use across multiple projects.

That might include:

• templates;

• code libraries;

• frameworks;

• design systems;

• processes;

• scripts;

• stock assets;

• reusable documents;

• know-how.

A broad assignment can sometimes appear to capture more than the client actually needs.

Portfolio rights are a separate issue again.

Even if you created the work, confidentiality or publicity wording may restrict your ability to show it publicly.

Questions you can send to the client

Could ownership of the agreed final deliverables transfer once the related invoices have been paid?

Can we exclude my pre-existing tools, templates and reusable components from the transfer, while giving you the rights needed to use them as part of the finished work?

Once the project is public, may I show the finished work in my portfolio?

For more detail, read our guide to intellectual-property ownership.

Step 5: check confidentiality and work restrictions

Confidentiality clauses are common and often sensible.

The issue is usually scope.

Check:

• what information is confidential;

• whether public or previously known information is excluded;

• how long confidentiality lasts;

• whether you can disclose information to professional advisers or approved subcontractors;

• what happens to confidential material after the engagement.

Then check for restrictions that go beyond confidentiality.

Search for:

• exclusivity;

• non-compete;

• non-solicitation;

• conflicts of interest;

• restrictions on working with particular businesses or sectors.

A restriction can have a direct financial cost if it prevents you accepting other work.

The useful question is:

“What future work could this wording realistically stop me taking?”

A question you can send to the client

Could we narrow this restriction to the specific competitors, customers or activities the client actually needs to protect?

For more detail, read our guide to restrictions on future work.

Step 6: check termination and what remains payable

A termination clause tells you how the relationship can end.

It should also make you ask what happens next.

Check:

• notice periods;

• immediate termination rights;

• termination for convenience;

• payment for completed work;

• payment for work in progress;

• committed third-party costs;

• deposits;

• final handover obligations;

• IP treatment;

• confidentiality after termination.

A client right to cancel the project may be commercially acceptable.

The more important question is whether the contract explains what happens to work and money when they do.

A question you can send to the client

If the project is ended early for convenience, can the agreement confirm how completed work, work in progress and non-cancellable costs will be paid?

For more detail, read our guide to termination and payment on exit.

Step 7: check liability, indemnities and warranties

These clauses deserve a slower read because they can create risk far beyond the amount you are being paid.

Liability

Check whether the agreement contains an overall cap.

Also check whether certain types of claim sit outside that cap.

Do not look only at the number. Look at what the cap actually applies to.

Indemnities

An indemnity may require one party to cover particular losses, claims or costs.

Check:

• what triggers it;

• whose conduct is covered;

• which losses are included;

• whether third-party claims are involved;

• whether the obligation is capped.

Warranties

Make sure you understand what you are promising.

There is a significant difference between promising to perform work with reasonable skill and promising that a project will achieve a specific commercial result.

The useful question is:

“Could this clause expose me to losses that are disproportionate to the value of the project?”

Questions you can send to the client

Could we add an overall liability cap that is proportionate to the value and risk of the engagement?

Can we narrow this indemnity so it applies only to claims arising from matters within my responsibility?

For more detail, read our guide to indemnity obligations.

Step 8: check governing law, disputes and insurance

These sections are easy to skim because they often appear near the end of the agreement.

They can still matter.

Check:

• governing law;

• court jurisdiction;

• arbitration;

• mediation requirements;

• where proceedings must take place;

• insurance requirements.

A foreign governing-law clause is not automatically a reason to reject a contract.

But it may make a dispute more expensive or difficult to deal with.

Insurance wording also deserves attention.

If the contract requires professional indemnity, cyber, public liability or another policy, check:

• whether you already have it;

• the required level of cover;

• how long it must be maintained;

• whether the requirement is proportionate to the project.

For more detail, read our guide to dispute-resolution terms.

A 10–15 minute first-pass workflow

You can turn all of the above into a repeatable routine.

Minutes 0–2: map the agreement

Search for terms such as:

• payment;

• invoice;

• accept;

• revision;

• intellectual property;

• copyright;

• confidential;

• exclusive;

• terminate;

• liability;

• indemn;

• insurance;

• governing law.

You are not deciding anything yet.

You are finding where the commercial risk sits.

Minutes 2–5: scope, revisions and acceptance

Ask:

• What am I delivering?

• What is outside scope?

• How many changes are included?

• When is the work considered accepted?

If those answers are vague, note them.

Minutes 5–8: payment

Identify:

• when you can invoice;

• when payment becomes due;

• anything that can delay that trigger;

• what happens when payment is disputed or late.

Minutes 8–10: IP, confidentiality and restrictions

Ask:

• What does the client own?

• When do they own it?

• What do I retain?

• Can I show the work?

• Does anything restrict future clients?

Minutes 10–12: termination and downside risk

Read:

• termination;

• liability;

• indemnity;

• warranties;

• insurance;

• disputes.

These are the clauses most likely to change the downside if the relationship goes badly.

Minutes 12–15: turn flags into questions

Do not finish with a list saying:

• bad IP clause;

• bad payment;

• liability issue.

Turn each concern into something the client can answer.

For example:

Could payment be due from invoice rather than from final acceptance?

Could the liability cap apply to this indemnity as well?

Can existing clients be expressly excluded from this restriction?

Could the contract define how many revision rounds are included?

That gives you an actual negotiation list.

Which issues deserve more attention?

There is no universal list of clauses that should automatically make every freelancer walk away.

The same wording can have very different consequences depending on the project, fee, client, insurance and type of work.

However, pause and investigate carefully if you see:

• unlimited or very broad liability;

• personal guarantees;

• indemnities covering matters outside your control;

• an open-ended obligation to provide extra work for a fixed fee;

• no clear route to acceptance or payment;

• payment dependent on a third party paying your client;

• IP wording that appears to capture pre-existing materials;

• termination wording that leaves completed work unpaid;

• broad restrictions on future clients or sectors;

• insurance requirements far beyond the size of the engagement;

• a foreign dispute process you do not understand.

A red flag is not a legal conclusion.

It is a reason to understand the wording before you sign.

Example: turn a vague clause into practical questions

Consider this fictional clause:

The Contractor shall provide such additional services and revisions as the Client may reasonably request in connection with the Project, at no additional charge.

You do not need to decide immediately whether the clause is “good” or “bad”.

Start with what it could mean in practice.

What counts as an additional service?

The clause does not define it.

How many revisions are included?

There is no stated limit.

Could the client add new deliverables?

Possibly, depending on how “in connection with the Project” is interpreted.

What happens when a request is clearly outside the original scope?

The clause does not explain how additional fees are agreed.

Those questions point towards a useful commercial discussion:

Could we replace this with a defined number of revision rounds and confirm that additional deliverables or out-of-scope work require a separate written quote?

That is much more useful than simply labelling the clause a red flag.

Paste-ready questions for common contract issues

You do not need to write a legal essay when you negotiate.

Short questions are usually easier to answer.

Scope

Could we list the exact deliverables and confirm that additional work requires written agreement on scope and price?

Payment

Could payment run from the invoice date rather than from an open-ended approval process?

Acceptance

Could we add a defined review period and objective reasons for rejecting a deliverable?

Revisions

Could we state how many revision rounds are included and how further changes will be charged?

Intellectual property

Could ownership of the final deliverables transfer once the related invoices have been paid?

Background materials

Can we exclude my existing tools, templates and reusable components from the assignment?

Portfolio

Once the work is public, may I include the finished project in my portfolio?

Work restrictions

Could we narrow this restriction to the particular competitors, customers or activities the client needs to protect?

Termination

If the project ends early, can we confirm what remains payable for completed work and committed costs?

Liability

Could we add an overall liability cap proportionate to the engagement?

When a 15-minute review is not enough

A quick workflow is useful for triage.

It is not a substitute for proper advice where the stakes justify it.

Slow down or consider professional advice if the agreement involves:

• a high-value project relative to your business;

• a personal guarantee;

• unusually broad liability or indemnities;

• regulated work;

• valuable intellectual property;

• substantial data or security obligations;

• a jurisdiction you are unfamiliar with;

• restrictions that could materially affect future income;

• wording you still do not understand after asking the client.

The aim of the quick review is not to make every decision in fifteen minutes.

It is to identify where fifteen minutes is enough and where it is not.

Check what your contract actually says

Generic checklists can only take you so far.

The wording in your own agreement is what matters.

PactRivet checks freelance service agreements across ten commercial areas, including scope, payment, expenses and status, revisions and acceptance, intellectual property, confidentiality, work restrictions, termination, liability and disputes.

It highlights wording that may deserve attention and gives you plain-English questions you can take back to the client.

PactRivet does not decide whether a clause is legally valid or tell you whether you should sign. Its purpose is to make the first read clearer and help you identify the questions worth asking.

Check your freelance agreement and prepare questions for the client.

PactRivet provides general information and questions to consider. It is not legal advice.