Freelance Contract Checklist: What to Include

Introduction

A contract does not need to be ten pages of legal language. For most freelance projects, a clear one-page agreement prevents the majority of disputes: what you will deliver, what it costs, when it is due, how many revisions are included, when you get paid, and who owns the finished work.

This freelance contract checklist covers every item to agree before you start work, in plain language you can copy into an email or a simple document. It is not legal advice — for large projects, get proper advice — but for everyday work, a written agreement built from it will prevent the most common and expensive misunderstandings.

Why a One-Page Agreement Beats a Handshake

Most freelance disputes are not about bad faith. They are about two people remembering the same conversation differently. The client remembers "a website with everything." You remember "a five-page website." Both of you are sure you are right, because nothing was written down.

A short written agreement fixes this in three ways. First, it forces both sides to agree the scope before work starts, when changes are cheap. Second, it gives you something to point to when the project drifts — "this is outside the agreed scope, here is the extra cost." Third, it makes you look professional. Clients who see clear terms trust you more, not less.

The agreement does not need stamps and signatures. For most small projects, an email listing the agreed points plus a reply saying "Agreed" is a strong, practical record. What matters is that it is written, specific, and confirmed by both sides before work begins.

The Freelance Contract Checklist

Go through this checklist before every project. If an item does not apply, note that it does not apply — do not just skip it in silence.

1. Names and Contact Details

Write down your name or business name and the client's name, plus an email address for each side. This sounds obvious, but disputes often start with "I was dealing with the manager, not the company" or "I sent it to the wrong person." One named contact on each side avoids that.

2. Scope: Exactly What You Will Deliver

Describe the deliverable in concrete terms. Not "a website" but "one landing page, five sections, mobile-friendly, with contact form." Not "a logo" but "two logo concepts, one final logo, delivered as PNG and SVG."

Be specific about quantity, format, and quality bar. If the client expects something that is not in this section, it is not included — which is exactly why the next item matters.

3. What Is NOT Included

List the things that are out of scope: logo design, copywriting, hosting, photography, ongoing maintenance, or anything else the client might assume is part of the job. This single item prevents more arguments than any other. Clients rarely read a scope list and notice what is missing; spelling it out saves both sides a painful conversation later.

4. Timeline: Start, Draft, Final, Feedback

Agree four dates: the start date, the draft delivery date, the final delivery date, and the deadline for the client's feedback. Add one sentence that matters enormously: "If feedback arrives after the feedback deadline, the final date moves by the same number of days." Without that line, a client who replies three weeks late can still expect the original final date.

Also agree what counts as a working day if you do not work weekends — say so in the agreement rather than assuming it.

5. Price: Total, Currency, and What It Covers

State the total price, the currency, and what the price includes. If part of the work is billed separately — for example, stock photos, fonts, or hosting — say so now. Surprise costs are the fastest way to lose a client's trust.

If you charge in a different currency from your own, state who bears any transfer fees. A short line such as "Client pays transfer fees" avoids an awkward deduction from your payment later.

6. Payment Terms: Upfront, Milestones, and Due Dates

Agree how and when you get paid. A common structure for freelancers is 50% upfront to start and 50% on delivery, with invoices due within seven days. For larger projects, split into milestones: a percentage at the start, a percentage at draft approval, and the remainder on final delivery.

State the payment method, the due period in days, and what happens if payment is late — for example, a late fee or a pause on further work. Agreeing this before work starts is far easier than negotiating it after a payment is overdue.

7. Revisions: How Many Rounds Are Included

State the number of revision rounds included in the price — two is a common number — and the cost of extra rounds. Be clear about what counts as a revision (adjustments to the agreed deliverable) versus a new request (something outside the agreed scope, priced separately).

Without a limit, a project priced for two rounds can quietly become ten rounds for the same fee. With a limit agreed upfront, extra revisions are a normal conversation: "That is outside the included rounds, so it will cost ₹X — shall I go ahead?"

8. Ownership: Who Owns the Final Work

State when ownership transfers. The standard freelance arrangement is: the client owns the final files after full payment, and you may show the work in your portfolio unless a non-disclosure agreement says otherwise. Put both halves in writing.

Also state what happens to source files and drafts. If the client expects editable source files, agree that now — some freelancers include them, others charge extra. Either is fine, as long as it is agreed before delivery, not argued about afterwards.

9. Cancellation: What Happens If Either Side Stops

Agree what happens if the project is cancelled: the client pays for work completed up to that point, plus any agreed cancellation fee (sometimes called a kill fee) if you turned down other work for the project. Also agree how cancellation is communicated — in writing, by email — so there is no confusion about whether the project is paused or ended.

10. Communication: Where and How Often

Agree where you will communicate — email, WhatsApp, or a project tool — and how often you will update the client. "Weekly update by email every Friday" is enough. This prevents the two classic failures: the client who expects daily updates, and the freelancer who goes silent for three weeks.

11. Signatures or Written Agreement

Finish with confirmation. Both sides reply "Agreed" with the date, or sign a PDF if the project is larger. The format matters less than the fact that both sides confirmed the same document.

Example Agreement in Plain Language

Here is how the checklist looks as a short agreement you could send by email:

Project: Logo design for [Client Name].
Scope: Two logo concepts, two revision rounds, final logo delivered as PNG and SVG files. Logo usage guide not included.
Timeline: Draft by 24 October 2026, final by 30 October 2026 if feedback arrives within 48 hours of the draft.
Price: ₹8,000 total. 50% upfront to start, 50% on delivery. Invoice due within 7 days.
Revisions: Two rounds included. Extra revisions ₹800 each.
Ownership: Client owns the final logo files after full payment. Designer may show the work in their portfolio.
Cancellation: If cancelled, client pays for work completed to date.
Communication: Email updates, once a week or when a draft is ready.
Please reply "Agreed" to confirm, and I will begin.

That is the whole agreement — under two hundred words, and it covers scope, price, timeline, revisions, payment, ownership, cancellation, and communication.

Related: How to Calculate Your Freelance Hourly Rate | 5 AI Tools to Automate Invoicing and Follow-ups

Common Mistakes to Avoid

• Starting without written scope. "Just do a website" leads to endless changes, because nobody agreed what "a website" means.
• No revision limit. Ten revisions for the price of two is the fastest way to turn a profitable project into a loss.
• No payment terms. A client who was never told when payment is due will not feel late when they pay two months later.
• No ownership line. Disputes over who owns the files — and whether you can show the work in your portfolio — are painful and avoidable.
• Sending a template with another client's name in it. Personalise every agreement. A leftover name from a previous client destroys trust instantly.
• Agreeing scope changes verbally. When the project changes mid-way, pause, agree the new scope and price in writing, and then continue. A short email — "Confirming the extra page will cost ₹X and add three days" — is enough.

What If the Client Will Not Sign?

Offer a lighter version first: send the checklist by email and ask the client to reply "Agreed." Most reasonable clients will do this without hesitation, because it protects them too.

If a client will not even agree by email, treat that as a red flag. It usually means they want the freedom to change the scope, delay payment, or dispute the deliverable later. Politely decline and move on — the projects you refuse are often the ones that would have cost you the most time and stress.

For larger projects, or anything involving unusual intellectual property, liability, or employment terms, get proper legal advice rather than relying on a template.

FAQ

Do I need a lawyer for every freelance project?

For most small projects, a clear written agreement between you and the client is enough. For large, high-value, or unusual projects, get legal advice.

Can I use a template contract?

Yes, but personalise the scope, price, and timeline for each project. A template is a starting point, not a finished agreement. Check every line before you send it, and remove anything that does not apply to this project.

What if the project changes mid-way?

Pause, agree the new scope and price in writing, then continue. Never start extra work on a verbal promise — if the client genuinely wants it, they will confirm it in writing.

What if the client asks me to start before agreeing terms?

Politely decline. A short message works: "I am happy to start as soon as we confirm the scope and payment terms — here is a one-page summary for you to approve." Clients who respect your process are usually the clients worth keeping.

This post is educational information, not legal advice. For large or high-value projects, consult a qualified lawyer.