Blog · Published 2026-11-03

Freelance contract checklist

A freelance contract doesn't need to be long or full of legal language to be useful. It needs to answer the questions that cause most disputes: what exactly you're delivering, when, for how much, when you get paid, and what happens if things change. This checklist walks through the clauses worth covering, with plain-English notes on why each one matters.

Important: this is general information, not legal advice. Laws on contracts, intellectual property and late payment differ by country and state. For anything high-value or unusual, have a qualified professional review your agreement.

Why a written contract matters even for small jobs

Many freelancers start with a friendly email and a handshake. That often works until it doesn't: the client remembers the scope differently, the payment date slips, or the project is cancelled halfway. A written agreement isn't a sign of distrust. It's a shared reference that both sides can point to when memories differ. Even a one-page agreement, confirmed by email, is far better than nothing.

The freelance contract checklist

1. The parties

• Your legal name or business name, and address.
• The client's legal entity name (not just the contact person's name), and address.
• Who the main contact and approver are on the client side.

Getting the legal entity right matters if you ever need to chase payment. The person you email might leave; the company remains responsible.

2. Scope of work

• A clear description of the project and its goal.
• A list of specific deliverables (for example, "homepage design, two inner page templates, style guide").
• Formats and file types you will hand over.
• What is not included (exclusions).

The deliverables list is the heart of the contract. If it's vague, everything else becomes negotiable. Exclusions are just as important: they stop assumptions before they become arguments. If you've already written a solid proposal, you can reuse its scope section; see how to write a freelance proposal with AI.

3. Revisions and approvals

• How many revision rounds are included.
• What counts as a round (one consolidated set of feedback).
• How long the client has to give feedback, and what happens if they don't respond.
• What counts as final approval.

A simple line such as "If no feedback is received within ten business days, the deliverable is considered approved" can prevent projects from stalling forever. Choose a period that's fair for your type of work.

4. Timeline

• Start date, key milestones and the expected delivery date.
• A note that dates depend on the client providing materials and feedback on time.

The dependency clause protects you when the client sends content three weeks late and still expects the original launch date.

5. Fees

• The total fee (fixed price) or rate (hourly, daily) and any estimate of hours.
• Currency.
• Whether expenses (software, stock assets, travel) are included or billed separately, and whether they need prior approval.
• Taxes: whether prices include or exclude applicable tax.

6. Payment terms

• Deposit amount and when it's due (often before work starts).
• Payment schedule: milestones, monthly, or on completion.
• Invoice due date (for example, 14 days from invoice).
• Accepted payment methods.
• Late payment terms: reminders, any late fee or interest, and whether you may pause work.

Late fees and interest are regulated differently in different places, so check what's allowed where you and your client are based. Even without a fee, a clear due date makes follow-ups easier. Our invoice follow-up email templates are built around referring back to agreed terms.

7. Changes to scope

• How new requests are handled (written estimate and approval before work).
• How changes affect price and timeline.

This clause turns scope creep from an awkward conversation into a routine process. For the emails and a change order template, see how to handle scope creep.

8. Intellectual property and ownership

• Who owns the final deliverables, and when ownership transfers (commonly on full payment).
• What happens to drafts, unused concepts and source files.
• Any pre-existing tools, code, templates or materials you keep ownership of and license to the client.
• Third-party assets (fonts, stock images, plugins) and their licences.

Tying ownership transfer to final payment is a common approach and gives both sides a clear rule. Be explicit about source files: many disputes are about whether "the design" includes the editable working files.

9. Portfolio and credit

• Whether you can show the work in your portfolio, and when (some clients need you to wait until launch).
• Whether you'll be credited publicly.

10. Confidentiality

• What information you'll keep confidential, and for how long.
• Whether a separate NDA applies.

11. Termination and cancellation

• How either side can end the agreement (notice period, in writing).
• What the client pays for work done up to that point.
• Whether the deposit is refundable.
• What gets handed over if the project ends early.

This is the clause people skip and later wish they hadn't. A cancelled project without a termination clause often means unpaid work.

12. Liability and warranties

• A reasonable limit on your liability (often capped at the fees paid).
• What you do and don't guarantee (for example, you don't guarantee specific business results).
• Who is responsible for content and materials the client supplies.

This section is where professional advice is most valuable, because what's enforceable varies by jurisdiction.

13. Independent contractor status

• A statement that you are an independent business, not an employee.
• That you control how and when the work is done, and provide your own equipment.

14. Communication and support

• Main communication channel and expected response times.
• Working hours.
• Any post-launch support period, what it covers, and what it costs after it ends.

Defining the support window makes the end of the project much cleaner. See our guide to client offboarding and the wrap-up email.

15. Governing law and disputes

• Which country or state's law applies.
• How disputes will be handled first (for example, good-faith discussion, then mediation).

16. Signatures

• Names, titles, dates and signatures of both parties (an e-signature tool is fine in most places).

Before you send it: a five-minute review

1. Could a stranger read the scope and know exactly what you're delivering?
2. Are the price, deposit and due dates written as specific numbers and dates?
3. Is it clear what happens if the client asks for more, goes quiet, or cancels?
4. Does the ownership clause match what the client actually expects to receive?
5. Does the agreement match your proposal? Mismatches are a common source of confusion.

Using AI to review or draft a contract

AI assistants can help you check a draft for missing sections or rewrite a clause in plainer English. They can't tell you what is legally enforceable where you live, and they may invent clauses that sound official. Use them as a checklist partner, not a lawyer:

Here is my freelance agreement draft: [PASTE].
Compare it against this checklist: parties, scope and exclusions, revisions, timeline, fees, payment terms, change process, IP and ownership, portfolio rights, confidentiality, termination, liability, contractor status, communication and support, governing law, signatures.

List any sections that are missing or vague, and quote the unclear sentence. Do not rewrite legal terms or add new obligations. Where a decision is needed, write [DECIDE: …].

Then make the decisions yourself, and get professional review for anything significant.

After it's signed

Once the agreement is signed, move straight into onboarding: invoice the deposit, request access and materials, and send your kickoff email. Our client onboarding checklist picks up exactly where this list ends.