Freelance contract in India: a client agreement checklist
India-specific client contract checklist for women freelancers: scope, fees, revisions, IP, cancellation, confidentiality and disputes.
In this guide
What should a freelance contract say?
A useful freelance service agreement answers four questions before work starts: what will be delivered, when and how the client will pay, who can use the work, and what happens if the project changes or stops. A signed agreement is easier to rely on when it is specific, consistent with the proposal and invoice, and shared with every decision-maker. This checklist is general information for India, not a substitute for legal advice on a particular contract.
Name the parties and the person allowed to approve work
Use the legal name of the client or business, its address and a reliable contact. Identify your own legal or trade name and whether you contract as an individual, proprietorship, partnership, LLP or company. Ask who can approve a brief, sign off a milestone and authorise extra cost. A friendly contact may not have authority to bind the client organisation.
Write down deliverables, boundaries and acceptance
Describe the files, service, quantity, format, quality standard and delivery dates. State what is outside scope, such as printing, stock images, travel, source files, maintenance or extra research. Explain how the client accepts a milestone, how quickly they must send consolidated feedback and what happens if they do not respond. Attach the brief or proposal and identify its version so documents do not contradict each other.
Set a payment schedule that protects your working time
State the total fee or rate, currency, deposit if any, invoice milestones, due date, taxes where applicable, reimbursable expenses and payment method. Say when work begins and whether delivery or final file access depends on cleared payment. If a client asks for a free sample, define a small, watermarked or paid test with a clear limit instead of giving away usable work. Do not assume a late-fee clause is automatically enforceable; have unusual terms reviewed.
| Term | Agreed detail | Who confirms it and by when |
|---|---|---|
| Client and authorised contact | ||
| Deliverable, exclusions and acceptance test | ||
| Fee, tax, deposit and invoice dates | ||
| Included review rounds and change rate | ||
| IP licence or assignment and payment condition | ||
| Cancellation, handover and dispute route |
Prevent scope creep and late-payment disputes
Define revisions and what counts as a new request
Set a reasonable number of feedback rounds and ask the client to combine comments from their team. A correction to an agreed requirement can be treated differently from a new direction, added page, extra deliverable or missed deadline caused by late client material. Agree how you will price and reschedule a change before doing it; keep a short written change log and updated delivery date.
Agree what happens when the client or freelancer pauses
List dependencies such as access, product samples, data, approvals and subject-matter review. State how a delay affects the schedule and how long an inactive project can remain paused. For cancellation, explain payment for completed milestones, committed costs, work in progress and any refund calculation. Avoid a term that lets one side cancel without accounting for work already delivered or money already spent.
Keep an evidence trail that is useful if memories differ
Save the final proposal, signed terms, approved brief, change approvals, invoices, payment records, delivery links and acceptance messages in one dated project folder. Confirm important calls by email or another agreed written channel. Do not keep sensitive client or customer data longer than needed, and restrict folder access to people who need it.
Protect work, privacy and the freelancer's ability to earn
Separate ownership from permission to use the work
Say whether the client receives a licence or an assignment, which uses, territory and duration it covers, and when the permission starts. List your pre-existing templates, methods, fonts, code, portfolio pieces and third-party materials separately. Under Indian copyright law, a written assignment should identify the work and the rights assigned; duration and territory matter. If the contract is silent, the result may not match either party's expectation, so get the clause reviewed for valuable work.
Make confidentiality and portfolio terms workable
Define confidential information, permitted project use, who may receive it, how long confidentiality lasts and when copies must be deleted or returned. Exclude material already public or independently developed where appropriate. Ask for written permission before naming the client or displaying a deliverable in your portfolio. A client can have legitimate launch or privacy concerns, but a blanket ban on all future work in an industry may be too broad; have restrictive clauses reviewed.
Use a proportionate liability and dispute clause
Identify the governing law, a practical first escalation contact, negotiation or mediation steps, court or arbitration route, and the location for any proceeding. Define responsibility for third-party materials, client-supplied claims, data handling and rework. Liability caps, indemnities and exclusions can have major consequences; do not copy them from a template without understanding them. For an eligible micro or small supplier, check current Udyam and MSME Samadhaan/ODR requirements before relying on a delayed-payment remedy.
Freelance agreement questions
Do I need a lawyer to write every freelance contract?
A small, low-risk project may use a carefully checked proposal and standard terms, but legal review is sensible for high-value work, international clients, sensitive data, employment-like control, broad IP transfer, exclusivity, indemnity or a dispute already underway. Keep a standard template and ask a lawyer to review that template once, then update it when your work or risk changes.
Can an email or messaging approval form part of the agreement?
Written messages can help show what the parties discussed and approved, but an unclear thread may leave key terms uncertain. Put the final scope, price, dates and IP terms in one signed document or a clearly accepted proposal, and preserve the approval with its attachments. For a high-value or disputed deal, ask an Indian lawyer to assess the evidence and contract.
Should a client own my work before paying?
That depends on the agreed licence or assignment. State whether rights transfer or a licence begins only after full payment, and what the client may do with drafts while payment is pending. Do not assume an invoice alone resolves ownership; align the proposal, agreement and delivery process.
What if a client delays payment?
Send a calm written reminder with the invoice, due date, amount and a specific request for a payment date. Pause new work only as your contract allows, keep proof of delivery and communications, and seek advice before threatening legal action. A registered micro or small supplier may have additional remedies under MSME law, subject to current eligibility and registration conditions.
Related practical guides
Related issue guides
Sources and publication record
Draft prepared 26 September 2026; project-team editorial review pending · Sources checked .
- The Indian Contract Act, 1872India Code, Legislative Department, Government of India
- The Copyright Act, 1957India Code, Ministry of Law and Justice, Government of India
- Copyright Office: copyright scope, ownership and registration FAQsCopyright Office, Government of India
- MSME ODR Scheme for delayed-payment disputes: implementation guidelinesMinistry of Micro, Small and Medium Enterprises, Government of India
- Digital Personal Data Protection Act, 2023India Code, Legislative Department