Freelance Contract Guide: What Every Agreement Should Include

A clear freelance contract turns a promising conversation into a workable agreement. It tells the freelancer what to deliver, tells the client what they are paying for, and gives both sides a plan for handling delays, revisions, and changing priorities. The best contracts are not simply protective documents: they are practical project instructions that you can refer to throughout the work.

This guide explains what a freelance agreement should include, how to structure milestones, and how to discuss terms before work begins. Rules vary by country, and this is general information, not professional legal, tax, or insurance advice. Have important contracts reviewed by a qualified professional in your country, particularly when substantial liability, sensitive data, or cross-border work is involved.

What is a freelance contract?

A freelance contract is an agreement between an independent service provider and a client. It records the services, responsibilities, payment arrangements, and other conditions governing their work together.

For a small project, one document may cover everything. An ongoing relationship might use a main services agreement for general terms and separate statements of work for individual assignments.

Whatever the format, the documents should agree with one another. If your proposal promises something different from your contract, resolve the inconsistency before signing. Our freelance proposal guide can help you turn an initial pitch into a clearly defined project.

A useful test is simple: could someone who missed your sales call understand what happens next by reading the agreement?

What every freelance contract should include

Use this checklist to review a draft before either side commits.

Section	What to specify	Problem it helps prevent
Parties	Legal names, business details, authorized signers	Uncertainty about who owes what
Scope	Deliverables, formats, exclusions	Unpaid additional work
Timeline	Milestones, deadlines, dependencies	Unrealistic delivery expectations
Payment	Fees, currency, due dates, triggers	Arguments about when payment is due
Revisions	Included rounds and feedback process	Endless rework
Ownership	Rights transferred and retained	Disputes over files and reuse
Confidentiality	Protected information and permitted access	Unwanted disclosure
Cancellation	Notice, payments, handover	Confusion when work ends early
Communication	Channels, contacts, response expectations	Missed decisions and delays

Parties and authority

Identify the freelancer and the client using the appropriate legal names, not just brand names or social handles. Include relevant business addresses and contact details.

Confirm that the person signing is authorized to commit the client. Also distinguish between the person who approves creative work and the person who processes invoices; they may not be the same.

If subcontractors will contribute, explain whether client approval is required and how confidentiality and ownership obligations will apply to them.

Scope of work and exclusions

Avoid descriptions such as “website support” or “complete branding.” Define the actual outputs, their quantity, format, and intended use.

For example, a copywriting scope might include:

• One homepage draft delivered in an editable document.
• A kickoff interview and review of existing brand materials.
• Two consolidated revision rounds.
• Final copy organized by page section.

It might explicitly exclude design, development, customer interviews, translation, and additional pages.

For design or development projects, specify whether editable source files, repositories, documentation, installation, and training are included. A finished output and the materials used to create it are not necessarily the same deliverable.

Timeline and client responsibilities

Set deadlines alongside their dependencies. A delivery date may depend on receiving a brief, account access, product information, or approval of an earlier milestone.

Name what the client must supply and when. Explain what happens if it arrives late: dates might move by mutual agreement, or the freelancer may need to reschedule work around existing commitments.

Avoid promising that every client delay produces an identical extension. Availability may change. A rescheduling process is often more realistic than an automatic formula.

Price and payment terms

State the pricing model: fixed fee, hourly, daily, retainer, or milestone-based. Then specify:

• Amounts or rates and currency.
• Any deposit or advance funding requirement.
• Invoice timing and payment deadlines.
• Whether expenses require advance approval.
• How applicable taxes and processing costs are handled.
• Any agreed late-payment measures or right to pause work.

For hourly work, explain how time is recorded and whether there is a spending cap. For fixed-fee work, tie the fee to the defined scope.

If you are still deciding your pricing structure, consult the guide to how much to charge as a freelancer. Invoice requirements and tax obligations vary by country; our freelance invoice and taxes guide provides general context, not professional tax advice.

Revisions and change requests

Define a revision round as one consolidated set of feedback from the designated client contact. Otherwise, comments from different stakeholders can turn one round into several overlapping assignments.

Distinguish between:

• Corrections: Bringing work into line with the agreed requirements.
• Revisions: Adjustments within the approved direction.
• Scope changes: New deliverables, a different direction, or changed requirements.

A client asking a developer to fix an agreed feature is different from asking for a new integration. Your contract should explain how each situation is handled, including any correction period.

Intellectual property and usage rights

Specify whether the client receives ownership, a license, or another defined set of rights. State when those rights take effect—often after full payment for the relevant work.

Address separately:

• Final deliverables.
• Drafts and unused concepts.
• Pre-existing templates, tools, and reusable code.
• Third-party fonts, images, software, and other licensed assets.
• Portfolio display and attribution permissions.

Do not promise to transfer rights you do not own. Third-party assets may remain subject to their own licenses. Ownership rules vary by country, so seek professional legal advice on important transfers.

Confidentiality, data, and AI tools

Explain what information is confidential, who may access it, and how long the obligation lasts. Include appropriate exceptions, such as information already publicly available, and a process for returning or deleting materials.

If AI tools may be used, agree on boundaries before uploading client information. Specify whether confidential material can enter external tools, whether approval is required, and what human review is expected.

Projects involving personal data may require separate privacy or data-processing terms. Do not assume a standard confidentiality paragraph covers every obligation.

Cancellation, liability, and disputes

Explain how either party can end the agreement, what notice is required, and what happens to completed work, work in progress, approved expenses, and advance payments.

Distinguish cancellation for convenience from termination after a serious breach. Where appropriate, include an opportunity to resolve the breach first.

Also consider liability limits, warranties, dispute escalation, governing law, and the process or location for formal proceedings. These provisions deserve particular legal scrutiny; their enforceability varies by country.

How to structure freelance contract milestones

Milestones divide a project into reviewable stages. Each should connect a specific output to a payment arrangement and an approval process.

For a website project, a sensible sequence might be:

Milestone	Deliverable	Approval basis
Discovery	Requirements and page outline	Covers the agreed pages and functionality
Design	Layouts for agreed page types	Matches the approved brief
Build	Working site in a test environment	Agreed features meet documented checks
Handover	Final files, access, and documentation	Listed handover items are provided

“Halfway finished” is not a useful milestone because neither side knows exactly what to inspect.

Specify the review window, who approves the work, and how the client reports issues. Require feedback to identify departures from the agreed requirements. Also explain how unresolved feedback affects later stages.

Avoid treating silence as acceptance without careful discussion and legal review. An explicit approval process is usually clearer operationally.

Step by step: create and agree your contract

1. Confirm the business outcome

Ask what the client wants to achieve, who will use the work, and who has final approval. Separate the desired business result from the deliverable you can control.

A writer can promise agreed articles, for example, but should not casually guarantee sales outcomes.

2. Translate the brief into deliverables

List outputs, formats, exclusions, client inputs, and acceptance criteria. Use a concrete example when a requirement is subjective.

Instead of “modern design,” identify approved references, brand guidelines, and functional requirements.

3. Choose the payment structure

Match payment stages to meaningful progress. For open-ended work, define an hourly budget or recurring capacity rather than inventing a fixed scope.

For ongoing engagements, a freelance retainer agreement should clarify included services, availability, and what happens to unused capacity.

4. Discuss the difficult scenarios

Ask what happens if feedback is late, priorities change, work pauses, or the project ends early. Discussing these situations before signing is easier than negotiating them during a disagreement.

5. Review and sign the same version

Check names, amounts, dates, attachments, and references. Make sure both sides sign the final version and retain an accessible copy.

Document later changes in writing, including their effects on fees and deadlines.

6. Use the contract during delivery

Refer to it at kickoff and milestone reviews. Keep approvals, feedback, invoices, and scope changes organized.

A contract works best when it supports everyday project management rather than disappearing after signature.

Practical wording you can adapt

These are drafting prompts, not a complete contract or professionally reviewed legal clauses. Adapt them to your project and local requirements.

Scope and revision template

The freelancer will deliver [outputs] in [formats], based on the brief dated [date]. The fee includes [number] consolidated revision rounds within that brief. The client will provide feedback through [designated contact]. Additional outputs or changes to the approved direction require written agreement on fees and scheduling before work begins.

Dependency and scheduling template

The schedule depends on the client providing [materials or access] by [date] and feedback within [review period]. If those dependencies are delayed, the parties will confirm revised delivery dates in writing, taking account of the freelancer’s availability.

Change-request message

This request adds [new requirement] beyond the agreed scope. I can provide it for [additional fee], with delivery on [revised date]. Alternatively, we can retain the current scope and schedule. Please confirm your preferred option before I proceed.

These messages keep the conversation collaborative. The goal is not to reject changes, but to make their consequences visible.

Common freelance contract mistakes

• Starting before agreement: Enthusiasm is not a substitute for confirmed terms and any required funding.
• Offering unlimited revisions: This makes workload and completion difficult to define.
• Leaving approval authority unclear: Conflicting feedback can derail an otherwise straightforward project.
• Copying an unrelated template: Terms suited to photography may not fit software development.
• Ignoring handover: Specify files, access transfer, documentation, and any post-delivery support.
• Accepting broad liability without review: A small project fee does not necessarily mean small contractual exposure.
• Leaving promises in chat: Incorporate important commitments into the signed documents or an agreed written amendment.

How Scoutr helps

On Scoutr, contracts and milestones are created on the platform. Each milestone is funded by the client through Stripe before work on it starts, and approved deliverables release payment to the freelancer. There is also a dispute process if something goes wrong.

Scoutr charges freelancers 0% commission and clients a 5% platform fee. Its fair, deterministic matching, AI co-agent, and community feed support finding and organizing freelance work. However, platform workflows do not replace a clear scope, thoughtful approval criteria, or professional review where needed.

Clients preparing an engagement can also use the guide to how to hire freelancers to improve their brief and selection process.

FAQ

Do I need a freelance contract for a small project?

A written agreement is useful even for small assignments. Keep it proportionate, but still identify the deliverable, fee, deadline, revision allowance, ownership terms, and cancellation process.

Can an email count as a freelance contract?

In some circumstances, emails or other electronic communications may form a binding agreement. Rules vary by country and context. A clearly agreed document reduces uncertainty; obtain professional legal advice if enforceability is important.

Who should provide the contract?

Either party can provide it. What matters is that both review and agree to the terms. If a client supplies their standard agreement, check that it matches your actual scope, payment arrangement, and responsibilities.

What should I do when a client requests extra work?

Compare the request with the agreed scope. If it is additional work, explain the fee and scheduling impact, then obtain written approval before proceeding. Distinguish additions from corrections needed to meet your original commitments.

What happens if a client does not pay?

Check the payment deadline, follow up in writing, and use the contract’s escalation or pause process. Keep delivery and approval records. Formal recovery options vary by country; seek professional advice before taking legal action.

---

Ready to start? Create your free Scoutr profile — freelancers keep 100% of what they earn (0% commission), and payments run through Stripe.