Format, Template & How-To 2026

What is a freelancer agreement, and why every Indian freelancer needs one

A freelancer agreement is a written contract under the Indian Contract Act, 1872 between an independent contractor and a client that fixes scope of work, payment and TDS terms, intellectual-property ownership, confidentiality, termination and dispute resolution. To make one, identify the parties, define the deliverables, set payment milestones, assign IP on full payment, and have both sides e-sign.

Freelancer agreement vs independent contractor vs consultancy agreement

Before drafting anything, sort out which document you’re actually making. The labels get used interchangeably, and that loose usage is harmless until a tax officer or a labour inspector starts reading. The name on the cover page matters far less than the substance of the relationship, but picking the right framing keeps the clause emphasis correct from the first draft.

Freelancer vs independent contractor vs consultancy agreement: does the label matter?

In legal substance, all three are contracts “for service”, meaning the person doing the work is independent, not an employee. So what separates them? Mostly the flavour of the engagement and which clauses carry the weight.

The honest answer to “does the label matter?”: not as much as people think. A court applies a substance-over-form test. If you call it a “consultancy agreement” but the consultant works fixed hours, uses your laptop, reports to your manager, and can’t take other clients, you may have drafted an employment contract by accident. A common question freelancers raise is whether they should insist on the “consultant” label to look more senior. Frankly, this gets overlooked: the title buys you nothing if the working reality contradicts it.

Contract of service vs contract for service: which one are you on?

This is the distinction that governs almost everything downstream: misclassification, TDS section, benefits, and tax treatment. A contract of service is employment (you serve the employer). A contract for service is independent work (you provide a service to a client). One word flips the entire legal regime.

How to make a freelancer agreement in India: step by step

Drafting a freelance contract isn’t a legal-genius exercise. It’s a checklist, run in order, with India-specific judgement at a few key points. The reader who lands here usually wants the doing-it sequence, not theory, so here it is as ten concrete steps. Each maps to a clause shown in full in the specimen below and explained in depth in the clause-by-clause section.

1. Identify the parties accurately. Capture full legal names, addresses, and PAN or GSTIN for both sides, and note whether each party is an individual, a sole proprietor, or a registered entity. This decides who signs and how TDS and GST flow.
2. Define the scope of work and deliverables precisely. Specify format, quantity, platform or medium, and acceptance criteria, so that “done” is objective and not a matter of taste. Vague scope is where most disputes begin.
3. Add a change-order and revision-cap clause. Cap the included revisions (two or three is standard) and route anything beyond the agreed scope through a written, separately-priced change order. This is your shield against scope creep.
4. Set the payment structure. Fix the advance, the milestones or final payment, the currency, the invoice timing, and a late-payment interest rate. An advance of 30-50% is the working norm for project work.
5. State the TDS and GST position. Name the correct TDS section (194J for professional or technical services, 194C for works contracts, 194H for commission), the rate, and who bears it; address GST registration and the turnover threshold so neither side is surprised at invoice time.
6. Assign intellectual property on full payment. Use a work-for-hire or assignment clause that transfers IP to the client only after the client has paid in full. Until then, you retain leverage and ownership.
7. Add confidentiality and, where relevant, a DPDP data clause. Protect confidential information both ways, and where the freelancer handles personal data, add data-processing and breach-notification terms under the Digital Personal Data Protection Act, 2023.
8. Add termination and the independent-contractor clause. Allow termination for cause and for convenience, attach a kill fee for mid-project cancellation, and affirm independent-contractor status (own tools, own hours, own taxes, no benefits) to keep misclassification at bay.
9. Add dispute resolution. Choose governing law, jurisdiction, and an escalation path (negotiation, then mediation or arbitration) before any dispute exists, when both sides are still reasonable.
10. Execute and stamp correctly. Sign by wet-ink, Aadhaar e-Sign, or DSC, keep the audit trail as proof of execution, and pay stamp duty if your state requires it so the document stays admissible.

Run those ten in sequence and you have a complete, India-aware agreement. The order isn’t arbitrary: parties and scope come first because everything else references them, tax and IP sit in the middle because they’re the commercial heart, and execution closes it out. Which step do most people skip? Step 5 and step 10, and those are exactly the two that cost money later.

Freelancer agreement format and template: a complete, copy-paste annotated specimen

This is the section the “format and template” search actually wants, and it’s the one no competitor publishes properly. Templates online are either gated behind a paywall, downloadable files you can’t read on the page, or screenshots you can’t copy. What follows is a complete, copy-paste Freelance Services Agreement in full draft language, clause by clause, with a short annotation after each clause explaining what it does, the alternatives, and the trade-off.

How to use this template: copy the whole thing, then fill every bracketed field (such as [Freelancer Name], [Client Name], [₹ amount], [date]) with your specifics. Read the annotation under each clause before you change anything, because that’s where the trade-offs live. The clause text sits inside the boxed blocks; the commentary is the normal prose after each one. This is a specimen, not legal advice for your particular deal, so adapt it to your facts.

FREELANCE SERVICES AGREEMENT

This Freelance Services Agreement (“Agreement”) is made on [date] at [city], between:
(1) [Freelancer Name], [individual / sole proprietor / entity], PAN [_], GSTIN [_ or “not registered”], having address at [address] (the “Freelancer”); and
(2) [Client Name], [individual / entity], PAN/GSTIN [____], having address at [address] (the “Client”).
The Freelancer and the Client are together the “Parties”.

This is the parties block. It fixes who is bound, captures PAN/GSTIN so TDS and GST flow correctly, and records the relationship type. The trade-off: an individual freelancer can sign as themselves, but a registered entity must sign through an authorised signatory, so add a line confirming signing authority if either side is a company.

Recitals. (A) The Client wishes to engage the Freelancer to provide certain services described in Schedule A; (B) the Freelancer agrees to provide those services as an independent contractor on the terms below; (C) the Parties intend this to be a contract for service and not a contract of employment.

Recitals set the context and, importantly, state the intent that this is independent work, not employment. This isn’t decorative: recital (C) is the first line of defence in a misclassification dispute. Keep recitals short and factual; a court reads them to understand purpose, not to be persuaded.

1. Scope of work and deliverables. The Freelancer shall provide the services and deliverables set out in Schedule A (the “Deliverables”), in the formats, quantities and to the acceptance criteria stated there. Anything not expressly listed in Schedule A is out of scope and shall be handled under Clause 2.

This is the engine of the contract. Everything that follows (payment, IP, termination) references the Deliverables. The alternative is a loose “Freelancer shall provide design services”, which sounds fine until the client expects forty banners and you costed for four. The trade-off of tight scope: it takes longer to draft Schedule A, but it ends almost every “but I thought that was included” argument.

2. Change orders and revision cap. The fee in Schedule B includes up to [two] rounds of revisions per Deliverable. Additional revisions, or any work outside Schedule A, shall be agreed in writing as a change order, priced separately at [₹ rate], and form part of this Agreement once signed by both Parties by email or otherwise.

This clause controls scope creep, the single most common freelance frustration. The revision cap (two or three rounds) sets a hard limit; the change-order mechanism prices anything beyond it. The alternative, “reasonable revisions”, invites endless free rounds. Lower the cap only if your fee genuinely covers heavy iteration.

3. Term and timelines. This Agreement begins on [start date] and continues until the Deliverables are accepted or until terminated under Clause 11. The Freelancer shall deliver per the timeline in Schedule A. Delays caused by the Client (late inputs, late approvals) extend the Freelancer’s deadlines correspondingly.

The term clause ties duration to completion, not an open-ended calendar. The last sentence is the freelancer’s protection: a client who sits on approvals for three weeks cannot then demand the original deadline. The trade-off: clients sometimes push back on the auto-extension, so be ready to cap it (“extension up to [X] days”).

4. Fees, payment schedule, advance, late-payment interest and kill fee. The Client shall pay the Freelancer the fees in Schedule B. An advance of [30-50]% is payable before work begins; the balance is payable per the milestones in Schedule B. Each invoice is due within [15] days. Overdue amounts carry interest at [1.5]% per month from the due date until paid. If the Client cancels after work has begun, a kill fee equal to [the value of work completed plus 20% of the remaining fee] is payable.

The money clause. The advance funds your float and signals the client is serious; the milestone split de-risks both sides; the interest rate gives you a contractual right (not just a moral one) to recover for delay; the kill fee compensates you when a project dies mid-flight through no fault of yours. The alternative, full payment on completion, front-loads all the risk onto the freelancer. We’d recommend never starting substantial work on a zero-advance deal with a new client.

5. Taxes (TDS and GST). Fees are stated [exclusive] of GST. Where the Freelancer is GST-registered, the Freelancer shall raise a tax invoice and the Client shall pay GST in addition to the fee. The Client shall deduct tax at source under Section 194J of the Income-tax Act, 1961 (or such other section as applies) and shall furnish a TDS certificate (Form 16A) and reflect the deduction in Form 26AS.

This clause stops the most common payment fight: who absorbs GST and what the TDS treatment is. Stating fees as exclusive of GST means the client pays the 18% on top, not you. Naming Section 194J pre-empts a client who tries to deduct under the wrong section. The trade-off: if you’re below the GST threshold, drop the GST sentence and say so, to avoid implying you must charge it.

6. Intellectual property and work-for-hire (on full payment). All intellectual property in the Deliverables shall vest in the Client only upon receipt by the Freelancer of full payment. Until full payment, the Freelancer retains all rights, and the Client has no licence to use the Deliverables. Pre-existing materials and the Freelancer’s tools, methods and know-how remain the Freelancer’s property; the Freelancer may display the Deliverables in a portfolio unless Schedule A says otherwise.

The IP clause does two jobs: it transfers ownership to the client (which the client is paying for) and it conditions that transfer on full payment (which protects you). If the contract were silent, the freelancer would keep copyright by default under Indian law and the client would get, at best, an implied licence. The trade-off: the portfolio carve-out is freelancer-friendly; a client wanting confidentiality may strike it, which is a fair negotiation.

7. Confidentiality / NDA and data protection (DPDP). Each Party shall keep the other’s confidential information secret during and after the engagement. Where the Freelancer processes personal data on the Client’s behalf, the Freelancer shall process it only on the Client’s instructions, apply reasonable security safeguards, and notify the Client without undue delay of any personal-data breach, consistent with the Digital Personal Data Protection Act, 2023.

Confidentiality protects business secrets both ways; the DPDP layer matters because a freelancer handling customer lists, analytics, or user content is processing personal data and inherits obligations. The alternative, a confidentiality clause with no data sub-clause, leaves a modern gap. The trade-off: the DPDP language is only essential where personal data is actually touched, so scale it to the work.

8. Independent-contractor status (no employment). The Freelancer is an independent contractor and not an employee, partner or agent of the Client. The Freelancer controls the manner and means of performing the services, uses the Freelancer’s own equipment, sets the Freelancer’s own hours, may work for other clients, and is solely responsible for the Freelancer’s own taxes and statutory obligations. Nothing in this Agreement creates an employment relationship or any entitlement to employee benefits.

This is the misclassification firewall. Every phrase is doing risk-management work: own equipment, own hours, other clients, own taxes, no benefits. If a court ever tests whether the “contractor” is really an employee, this clause and the working reality are what it weighs. The trade-off: the clause is only as strong as the conduct behind it, so don’t promise autonomy and then micromanage like an employer.

9. Representations and warranties. The Freelancer warrants that the Deliverables are original, do not infringe any third party’s rights, and will be performed with reasonable skill and care. The Client warrants that any materials it supplies are lawful to use and that it has authority to enter this Agreement.

Reps and warranties allocate basic risk: the freelancer stands behind originality and competence; the client stands behind the lawfulness of what it hands over. The alternative, no warranties, leaves both sides exposed to third-party claims with no contractual recourse. Keep the freelancer’s warranties tied to “reasonable skill and care”, not a guarantee of results.

10. Indemnity. Each Party shall indemnify the other against losses arising from its own breach of this Agreement or its warranties. The Freelancer’s total liability under this Agreement shall not exceed the total fees paid under it, except for liability arising from the Freelancer’s wilful misconduct or breach of confidentiality.

Indemnity decides who pays when a third party sues. A mutual, scoped indemnity is fair; a one-sided indemnity where the freelancer covers everything is not. The liability cap (capped at fees paid) is the freelancer’s most important protection: it stops a ₹50,000 project from generating a ₹50 lakh liability. The carve-outs for wilful misconduct and confidentiality are market-standard.

11. Termination. Either Party may terminate for material breach not cured within [15] days of written notice. Either Party may terminate for convenience on [30] days’ written notice, in which case the kill fee in Clause 4 applies and the Client shall pay for all work completed up to termination. IP transfers only for Deliverables fully paid for.

Termination needs two routes: for cause (breach) and for convenience (either side simply wants out). The cure period gives the breaching party a chance to fix things before the relationship ends. The for-convenience exit, paired with the kill fee, is what makes a freelancer whole when a client walks. The trade-off: a shorter notice period favours flexibility; a longer one favours income stability.

12. Dispute resolution, governing law and jurisdiction. This Agreement is governed by the laws of India. The Parties shall first attempt to resolve any dispute by good-faith negotiation, then by mediation. Any unresolved dispute shall be referred to arbitration by a sole arbitrator under the Arbitration and Conciliation Act, 1996, seated at [city], in English. Subject to arbitration, the courts at [city] have jurisdiction.

This clause routes disputes through a sensible escalation: talk first, mediate next, arbitrate as a last resort, with a named seat and language. The alternative, going straight to litigation, is slower and more public. The trade-off: arbitration is private and usually faster but can cost more for small claims, so for low-value deals some freelancers prefer to keep it to negotiation plus court jurisdiction.

13. Notices, assignment, force majeure, entire agreement. Notices shall be in writing to the addresses or emails above. Neither Party may assign this Agreement without the other’s written consent. Neither Party is liable for delay caused by events beyond its reasonable control. This Agreement, with its Schedules, is the entire agreement between the Parties and supersedes prior discussions; amendments must be in writing and signed by both Parties.

The boilerplate. It looks like filler, but each line closes a gap: notices fix how communication counts, the anti-assignment clause stops the contract being handed to a stranger, force majeure covers genuine acts-of-god delay, and the entire-agreement clause stops a stray WhatsApp message being treated as a binding promise. Don’t delete boilerplate just because it’s dull.

Signature and execution block.
Signed for and on behalf of the Freelancer: __ Name: [] Date: [_]
Signed for and on behalf of the Client: _ Name: [_] Date: [_]
Execution method: [wet-ink / Aadhaar e-Sign / DSC]. Both Parties confirm the e-signature audit trail (where applicable) is retained as proof of execution.

The execution block records who signed, when, and how. Naming the e-sign method and confirming the audit trail matters for proving execution if the deal is ever challenged. Wet-ink, Aadhaar e-Sign, and DSC are all valid in India; pick one and note it.

Schedule A: Deliverables. [List each deliverable with format, quantity, platform/medium, acceptance criteria, and timeline. Example: “1. Logo suite: 3 concepts, 2 revisions each, delivered as AI + PNG + SVG; accepted on Client’s written sign-off; due [date].”]

Schedule B: Fees and milestones. [State total fee, advance %, milestone splits, currency, invoice timing. Example: “Total fee ₹[____] plus GST. Advance 40% on signing; 30% on first-draft acceptance; 30% on final delivery. Invoices due within 15 days.”]

The two schedules carry the specifics so the body clauses stay reusable. Schedule A is your scope-and-acceptance bible; Schedule B is the money map. Keeping these in schedules means you can reuse the same body contract across many projects by swapping only the schedules. That’s how practitioners turn one good template into a hundred clean deals.

That’s the complete specimen. Copy it, fill the brackets, read the annotations, and you have a contract that beats almost everything else online for an Indian engagement. The next section goes deeper on the clauses that carry the most risk, because knowing why each one is worded this way is what lets you negotiate it.

Drafting each clause: scope, payment, IP, confidentiality, termination, dispute resolution, indemnity

The specimen showed you the language. This section explains the reasoning, clause by clause, with the India-specific judgement that separates a contract that holds from one that folds. Each subsection stands on its own, so you can jump to the clause you’re negotiating.

Scope of work, deliverables, and the change-order / revision-cap clause

A Bengaluru-based product designer delivers a full brand identity, sends the invoice, and then the client goes quiet. Two weeks later the reply lands: “Actually, can we also get the social media kit, the pitch deck template, and three more logo directions? Shouldn’t take long.” That’s the “delivered, then ghosted, then upsold for free” pattern, and it’s the most common freelance dispute in India. The fix is structural, not emotional.

Scope is the foundation because every other clause references it. The drafting goal is to make “done” objective: format, quantity, platform, and acceptance criteria, all written down. The moment scope is measurable, the conversation stops being “is this good enough?” and becomes “does this match Schedule A?” That single shift defuses most quality fights.

The change-order and revision-cap clause is scope’s enforcement arm. In practice, the strongest version does two things: it caps included revisions at a hard number (two or three rounds), and it routes anything beyond the agreed scope through a written, separately-priced change order. The mistake we see most often is freelancers relying on goodwill instead of a cap, then resenting the fourth “tiny tweak”. A common question freelancers raise is how to stop endless free revisions without seeming difficult; the answer is that a written cap depersonalises the no. You’re not refusing, the contract is.

The pitfall here is silent scope. If Schedule A says “design work” and nothing more, a court has nothing to measure against, and the client’s expansive reading tends to win because ambiguity in a contract often favours the party who didn’t draft it. Spell it out.

Payment clause: advance, milestones, late-payment interest, kill fee

Why is the payment clause where most contracts earn their keep? Because this is the clause that gets tested in every dispute about money, which is most disputes. A 2026 payment clause does four jobs at once: it structures the advance and milestones, it sets a currency and invoice timeline, it fixes a late-payment interest rate, and it attaches a kill fee for mid-project cancellation.

The advance is non-negotiable for new clients. An advance of 30-50% before work begins funds the freelancer’s float and filters out clients who never intended to pay. Milestones (say 40% on signing, 30% on first-draft acceptance, 30% on final delivery) de-risk both sides by tying money to progress. The late-payment interest clause, often 1.5% per month, converts a moral grievance into a contractual entitlement; under Sections 73 and 74 of the Indian Contract Act, 1872, a genuine pre-estimate of loss is recoverable, while a sum that’s really a penalty may be read down, so keep the rate commercially reasonable.

Here’s a non-obvious downstream shift worth flagging. As non-payment disputes get more visible, mid-value freelance deals (₹1 lakh and up) are starting to move toward milestone-locked escrow held by payment platforms such as RazorpayX, Cashfree, or Setu, where the client funds a milestone and the platform releases it on delivery. Contracts built for this need an “escrow release condition” clause that most templates today simply don’t have. If you’re working at that value, drafting for escrow now saves a rewrite later.

A common question is whether to charge per word or per project, and the payment clause changes shape accordingly: per-word work needs a defined unit and a count-acceptance mechanism, while per-project work needs tight scope and milestones. The pitfall across both: no kill fee. Without it, a client can cancel at 90% complete and you’ve funded their project. The kill fee (work completed plus a slice of the remaining fee) is what makes cancellation cost something.

IP ownership and the work-for-hire / assignment clause

Who owns the work after the project ends? Under Indian copyright law, the default answer surprises many clients: the author (the freelancer) owns the copyright unless there’s a valid written assignment. So if the contract is silent on IP, the client doesn’t automatically own the logo, the code, or the copy it paid for; it gets, at most, a limited implied licence to use it for the purpose it was commissioned.

That default is exactly why the IP clause matters and why it should be conditioned on payment. The work-for-hire or assignment language transfers ownership to the client, but the smart drafting move is to make that transfer trigger only on full payment. Until the client pays, the freelancer keeps the rights, which is enormous leverage. A client who hasn’t paid has no IP to use, and that fact tends to accelerate slow invoices.

In practice, the cleanest structure separates three things: the Deliverables (assigned on payment), the freelancer’s pre-existing tools, methods and know-how (always retained), and a portfolio right (retained unless confidentiality requires otherwise). A common pitfall is the client assuming silence equals ownership. It doesn’t. If the contract says nothing, the client may reuse the work narrowly but cannot claim full ownership, and certainly cannot resell it. Spell out the assignment, or expect a fight when the client later wants to license the work to a third party.

Confidentiality, NDA, and the DPDP data clause

Confidentiality is the clause everyone includes and few read closely. Its job is mutual: the freelancer keeps the client’s business secrets, and the client keeps the freelancer’s rates, methods, and other-client information confidential. The obligation should survive the engagement, because a secret doesn’t stop being a secret when the project ends.

The newer layer is data protection. If a freelancer handles personal data on the client’s behalf (customer lists, user analytics, contest entries, anything identifying real people), the Digital Personal Data Protection Act, 2023 puts obligations on that processing. Is data protected under DPDP if you’re a freelancer? Yes, where you’re processing personal data, you’re effectively acting as a processor and should process only on the client’s instructions, apply reasonable security safeguards, and notify the client of any breach without undue delay.

The practical drafting tip is to scale the data clause to the work. A logo designer who never sees a customer record needs a light touch; a developer building a CRM integration needs a full data-processing addendum with breach-notification timelines. The pitfall is a one-size NDA that’s silent on data entirely, which leaves a gap exactly where modern regulators are looking.

Termination, kill fee, and the final-payment-vs-quality dispute

Termination needs two doors. The for-cause door opens on material breach not cured within a notice window (15 days is typical). The for-convenience door lets either side exit on notice, paired with a kill fee so the freelancer isn’t left funding an abandoned project. Both doors should make IP transfer conditional on payment, so a client can’t terminate, refuse to pay, and still walk off with the work.

The hardest termination scenario is the quality dispute: the client withholds final payment claiming the work is “not good enough”. Can a client do that? Only if the work genuinely fails the acceptance criteria in Schedule A, which is exactly why objective acceptance criteria matter so much. If the deliverable meets the written spec, “I don’t like it” is a taste preference, not a contractual ground to withhold payment. This is where tight scope drafting pays off twice: once to define the work, and again to defend the invoice.

What experienced practitioners know is that the kill fee and the late-interest clause work together. The kill fee compensates for cancellation; the interest clause compensates for delay; together they make walking away or stalling expensive enough that most clients simply pay. The pitfall is treating termination as an afterthought. A contract with no for-convenience exit and no kill fee is a contract that can be abandoned for free.

Dispute resolution and indemnity: one-sided vs mutual

Dispute resolution decides what happens when negotiation fails. The sensible structure escalates: good-faith negotiation first, then mediation, then arbitration under the Arbitration and Conciliation Act, 1996 as the binding last resort, with a named seat, language, and a sole arbitrator to keep costs proportionate. So which should you pick: litigation, arbitration, or mediation? For a low-value freelance payment dispute, mediation or a summary court route may be cheaper than full arbitration; for higher-value or cross-border deals, arbitration’s privacy and enforceability usually win.

Indemnity is the other half of risk allocation, and it’s where freelancers get squeezed. A one-sided indemnity makes the freelancer cover every conceivable claim while the client carries nothing; a mutual indemnity has each side cover losses from its own breach. Mutual is fair, and the freelancer should also insist on a liability cap (capped at the fees paid) so a small project can’t trigger an unlimited claim. The carve-outs for wilful misconduct and confidentiality breaches are standard and reasonable.

A common drafting question is what’s actually fair on indemnity. The practical reality is that a mutual, capped indemnity with narrow carve-outs is the market norm for freelance work, and a freelancer who’s handed an uncapped, one-sided indemnity should treat it as the single biggest red flag in the document. Push back on it before anything else.

Tax in your freelancer agreement: TDS, GST, and Section 44ADA

Tax is where Indian freelance contracts quietly fall apart, because the clause language is easy but the India-specific judgement is not. A contract that names the wrong TDS section, ignores the GST threshold, or misses Section 44ADA leaves both sides exposed to disputes that have nothing to do with the actual work. This is the gap no competitor fills well, so it’s worth getting right.

The historical context explains why this clause exists at all. Before 1 July 2017, freelance invoicing was simpler and largely informal. The arrival of GST that year (with the ₹20 lakh registration threshold and zero-rated export treatment) and the spread of Section 194J as the routine TDS section for professional fees together reshaped what a freelancer’s tax clause has to say. A 2026 tax clause carries weight that a 2015 one never did.

TDS: 194J vs 194C vs 194H, and what the contract should say

Tax deducted at source is the freelancer’s most-misunderstood deduction. The contract should name the correct section, the rate, and who bears it, because the wrong section is a dispute waiting to happen. Here’s the matrix.

For most freelance work (design, writing, development, consulting), Section 194J at 10% is the correct match, because it’s a professional or technical service. Section 194C applies only where the engagement is genuinely a works contract, and most freelance deals aren’t. The mistake we see most often is a client deducting under 194C (1-2%) for what is plainly a 194J professional service (10%), which leaves a shortfall the deductor ends up answering for.

GST for freelancers: the Rs 20 lakh threshold and the OIDAR / RCM trap

Do you need GST registration as a freelancer? The threshold answer: registration is required once your aggregate turnover crosses ₹20 lakh in a financial year (₹10 lakh in special-category states). Below that, registration is optional. Above it, you must register, charge GST, and the contract should state whether the fee is inclusive or exclusive of it. The GST decision is rarely about the contract language and almost always about your numbers.

The trap most freelancers miss is OIDAR and reverse charge. Do you have to charge GST even below ₹20 lakh? Generally no for ordinary domestic supply, but the OIDAR (online information and database access or retrieval) rules and reverse-charge mechanism can still pull you in through certain platform or import-of-service scenarios, for example when you pay for services from an overseas platform. The practical reality is that you should check the specific facts before assuming you’re exempt. The pitfall is treating “under ₹20 lakh” as a blanket exemption; it usually is, but not always.

Section 44ADA presumptive tax vs ITR-3 books, and how it shapes your tax clause

Section 44ADA of the Income-tax Act, 1961 is the structuring tool most freelancers should know and many don’t. Under presumptive taxation, an eligible professional can declare 50% of gross receipts as deemed income and pay tax on that, without maintaining full books of account, filing through ITR-4. The eligibility limit is ₹50 lakh, extended to ₹75 lakh where at least 95% of receipts come through banking channels (so cash receipts above 5% knock you out of the higher limit).

Drafting for foreign clients: FEMA, forex invoicing, export of services, GST LUT and e-FIRA

Working for an overseas client changes the contract in specific, learnable ways, and almost no competitor maps the full picture. Can you sign with a foreign client in USD, and is that legal under FEMA? Yes. Receiving foreign currency for services you export from India is squarely permitted under the Foreign Exchange Management Act, 1999, and is exactly the inward remittance the framework is built for. The contract can be denominated in USD (or any currency) so long as the payment mechanics respect the forex rules.

The independent-contractor clause and misclassification: contractor vs employee

This is the single biggest legal risk in a freelance relationship, and every competitor ignores it. Misclassification means a person labelled a “contractor” is, in substance, an employee, and the consequences fall mainly on the client: exposure to provident fund (PF), employees’ state insurance (ESI), gratuity, and the rest of the employment-law apparatus, plus the tax fallout of deemed employment. The contract is the first thing a court or authority reads, but it’s the working reality that decides.

How does the law decide? Through the control test, often expanded into a four-fold test: who controls how the work is done, who provides the tools and workplace, who bears the financial risk, and how integrated the worker is into the organisation. An employee is directed on method, uses the employer’s resources, draws a fixed wage, and is woven into the org chart. An independent contractor agrees on a result, uses their own tools, carries their own risk, and stands apart. Substance beats label every time.

So how do you draft the independent-contractor clause to survive scrutiny? Affirm every factor that points to independence: own tools, own hours, no exclusivity by default, own taxes, no benefits, and control over the manner and means of the work. Connect it back to the contract-of-service-versus-for-service distinction, because the clause is just that concept in operative language. What experienced practitioners know is that the drafting tells that flip a contractor into a deemed employee are subtle: a clause requiring fixed office hours, a clause barring other clients, a clause giving the client step-by-step control. Those read like employment, and a clause that contradicts the rest of the contract’s “independent” framing is worse than no clause.

A common question is whether the client will have to pay PF, ESI, or gratuity if the contract merely looks like employment. The honest answer: if the relationship is in substance employment, the label won’t save the client, and the statutory liabilities can be claimed regardless of what the document says. This is why misclassification is a second-order risk that’s rising: as the gig framework matures and authorities get a clearer template for testing these relationships, the independent-contractor clause moves from boilerplate to risk-critical. The pitfall is copying an “independent contractor” clause into a contract whose other terms describe an employee; the inconsistency is exactly what gets noticed.

Non-compete, non-solicit and confidentiality under Section 27: what is actually enforceable

Can a client stop you from working with their competitors after the project ends? Almost never in India, and this is one of the most misunderstood clauses in any freelance contract. Section 27 of the Indian Contract Act, 1872 voids agreements in restraint of trade, which means a post-termination non-compete (a clause barring you from competing or serving competitors after the engagement ends) is largely unenforceable. Clients copy these from foreign templates all the time; they’re mostly decorative here.

Stamp duty, registration and the unstamped-agreement problem

Does a freelance agreement need stamp paper, registration, or notarisation? Short answer: it’s valid without any of them, but stamping affects whether you can use it in court. This is absent everywhere in the competitor field, and it’s the kind of gap that surfaces only when you’re trying to enforce.

The key rule lives in Section 35 of the Indian Stamp Act, 1899: an insufficiently stamped instrument is inadmissible in evidence until you pay the deficit duty plus penalty. So an unstamped freelance agreement isn’t void, and the underlying contract is still valid, but if you need to produce it in court to recover payment, you’ll first have to regularise the stamping. Can you enforce an unstamped freelance agreement? Yes, once you’ve paid the deficit duty and penalty, after which the document becomes admissible. Pay it and proceed.

Registration is not required for a freelance services agreement under the Registration Act, 1908, and notarisation is optional rather than mandatory. The practical complication is that stamp duty is a state subject, so the value and rules differ by state, and the cleanest modern route is an e-stamp obtained through the state’s e-stamping facility. When should you stamp, and on what value? The practical reality is that for any contract you might need to enforce (anything material), stamping it correctly in the relevant state before a dispute arises is cheap insurance, far cheaper than the penalty later. The pitfall is assuming “unstamped means invalid” (it doesn’t) or “I’ll stamp it if there’s ever a problem” (by then it costs more).

E-signature validity: wet-ink vs Aadhaar e-Sign vs DSC, and email-only agreements

Are e-signatures valid on a freelance agreement? Yes, and the law on this is settled, even if most templates barely mention it. The Information Technology Act, 2000 gives electronic signatures legal recognition: Section 5 recognises electronic signatures, Section 10A confirms that contracts formed electronically are valid, and Section 3A read with Schedule 2 covers recognised techniques such as Aadhaar e-Sign and DSC. The Schedule 1 exclusions matter (certain instruments, like negotiable instruments and wills, can’t be executed electronically), but an ordinary freelance services agreement is firmly inside the permitted zone.

So which method should you pick? All three are valid, and the choice is about convenience and risk. Wet-ink suits the cautious or low-tech deal; Aadhaar e-Sign suits fast remote execution and is increasingly the default; DSC suits high-value or recurring relationships where a stronger cryptographic signature is worth the setup. Whatever you choose, name the method in the execution block and retain the audit trail, because the audit trail is your proof of who signed and when.

The Code on Social Security, 2020 and freelancers: what changed on 21 November 2025

Here’s the freshness signal nobody in the competitor field has. The Code on Social Security, 2020 came into force on 21 November 2025, after Parliament passed it back in September 2020. For the first time, Indian law gives statutory definitions of “gig worker”, “platform worker” and “aggregator”, and under Sections 113-114 it requires aggregators (the platforms) to contribute 1-2% of their annual turnover (capped at 5% of payouts to workers) to a Social Security Fund. This is a genuine milestone: the workforce is finally recognised in statute.

But who’s actually covered? This is where the detail matters for a freelancer. The Code’s framing is aggregator-centric, built around platform and gig workers who earn through an aggregator. The ordinary project freelancer (non-platform, working directly for clients) still falls largely outside this safety net, which means the private contract remains their main protection. The takeaway from the section’s opening of the whole guide holds: for most freelancers, the contract is the safety net, and the Code doesn’t change that yet.

What to do when a client doesn’t pay: the enforcement path

This is the payoff section, the most-searched pain point in the whole topic. A client has the work, the deadline passed, and the invoice is unpaid. What now? The good news is that a well-drafted agreement turns a weak grievance into a recoverable claim, and the enforcement path is a ladder you climb one rung at a time.

Start with the documented reminder. Send the invoice again with the contractual late-payment interest already accruing (this is why the interest clause matters), a clear due date, and a record of delivery against Schedule A. Many payments arrive at this stage simply because the freelancer signalled they’re tracking it. If silence continues, escalate to a formal demand or legal notice setting out the contract, the amount due, the interest, and a deadline to pay before further action. How do you send a legal notice to a non-paying client? Through a lawyer, citing the agreement and the specific clauses breached, which converts a soft chase into a documented pre-litigation step.

If the notice doesn’t work, the dispute-resolution clause kicks in: mediation first, then arbitration under the Arbitration and Conciliation Act, 1996 if your contract provides for it, with damages recoverable under Section 73 of the Indian Contract Act, 1872. For registered businesses, the MSME route can offer a faster recovery mechanism. And here’s the part that ties back to the very start: can the client withhold final payment claiming the work is “not good enough”? Only if it genuinely fails the acceptance criteria in Schedule A, which is why objective acceptance criteria are worth the drafting effort.

What if there’s no written contract at all? Do you have any rights? Some, but you’re fighting uphill. You can still claim for work done, but proving the scope, the agreed fee, and the IP terms from scattered messages is hard, and the absence of a late-interest clause or a dispute mechanism weakens your hand. This is the strongest practical argument for the whole guide: the agreement (advance, milestones, IP-on-payment, late-interest, dispute clause) is what makes recovery realistic. The pitfall is starting enforcement from a position of no documentation; by then, the best protection was the contract you didn’t sign.

Quick comparison tables: payment models, tax, stamping, agreement types

For scannability, here’s the comparison the payment clause keeps gesturing at, plus pointers back to the other tables in this guide. Different payment models reshape the payment clause in specific ways, and choosing the right one upfront avoids a renegotiation later.

Charging per word versus per project changes the fixed-fee version specifically: per-word needs a defined unit and a count-acceptance step, while per-project needs tight scope and milestones. The other comparison tables in this guide live in their home sections: the agreement-types table sits in the agreement-types section near the top, the TDS and GST tables sit in the tax section, the employee-versus-contractor table sits in the misclassification section, the stamping table sits in the stamp-duty section, and the social-security coverage table sits in the Code on Social Security section. Which model should a new freelancer default to? Fixed fee with a solid advance and tight scope, because it’s the easiest to enforce and the hardest to dispute.

Frequently asked questions on making a freelancer agreement

How do I make a freelancer agreement in India step by step?
Identify the parties with PAN/GSTIN, define the scope and deliverables in Schedule A, add a change-order and revision cap, set the payment structure with advance and TDS/GST treatment, assign IP on full payment, add confidentiality and a DPDP clause, add termination and the independent-contractor clause, choose a dispute-resolution path, then e-sign and stamp if your state requires. The full copy-paste template is on this page.

What does a freelance contract look like, and what is the format?
The standard format runs: a title and parties block, recitals, then roughly thirteen numbered clauses (scope, change orders, term, fees, taxes, IP, confidentiality, independent-contractor status, warranties, indemnity, termination, dispute resolution, boilerplate), followed by two schedules (deliverables; fees and milestones) and a signature or e-sign block. The complete annotated specimen is published in full above.

Where can I download a free freelancer agreement template in India?
The complete, copy-paste annotated template is right here on this page, with no gated download or paywall. Copy it, fill the bracketed fields, read the annotation under each clause to understand the trade-offs, customise it to your deal, and execute it. That’s the whole template, on the page, free to use.

Who owns the IP or copyright of work created by a freelancer?
By default, the freelancer (the author) owns the copyright unless it’s validly assigned in writing. So the agreement must assign IP to the client, ideally on full payment, through a work-for-hire or assignment clause. If the contract is silent, the client gets only a limited implied licence at best, not full ownership, and certainly not the right to resell the work.

How is TDS deducted on freelancer payments, 194J or 194C?
Section 194J (10%) applies to professional or technical services, which covers most freelance work; Section 194C applies to genuine “works” contracts; Section 194H (2%) applies to commission or brokerage. The contract should state the correct section, the rate, the threshold, and that the client bears the deduction and furnishes Form 16A, so the credit is clean at filing time.

Do I need GST registration as a freelancer, and what’s the Rs 20 lakh threshold?
Registration is required once your aggregate turnover crosses ₹20 lakh in a financial year (₹10 lakh in special-category states); below that it’s optional. Above the threshold you must register and charge 18% GST, so state the fee as GST-exclusive in the contract. Watch the OIDAR and reverse-charge trap on platform collections, which can apply regardless of turnover.

Is a freelance agreement legally binding in India?
Yes. A valid contract under the Indian Contract Act, 1872 (offer, acceptance, consideration, lawful object, free consent, capacity) is binding whether it’s on paper or digitally signed. Writing doesn’t create the binding force; it makes the terms provable and the agreement enforceable, which is what matters when a dispute reaches a court or arbitrator.

Are e-signatures or digital signatures valid on a freelance agreement?
Yes. They’re recognised under the Information Technology Act, 2000: Section 5 recognises electronic signatures, Section 10A validates electronic contracts, and Section 3A with Schedule 2 covers techniques like Aadhaar e-Sign and DSC. The Schedule 1 exclusions (such as wills and negotiable instruments) don’t affect a freelance services agreement. Keep the audit trail as proof of execution.

Does a freelance agreement need stamp paper, registration or notarisation?
It’s valid without stamping, but an insufficiently stamped agreement is inadmissible in evidence under Section 35 of the Indian Stamp Act, 1899 until you pay the deficit duty plus penalty. Registration isn’t required, and notarisation is optional. Stamp value and rules vary by state, and an e-stamp through the state portal is the practical route.

What do I do if a client doesn’t pay after I deliver the work?
Escalate one rung at a time: a documented reminder with the contractual late-interest accruing, then a formal legal notice, then the dispute clause (mediation, then arbitration), then court, a summary suit, or the MSME route if you’re registered. A well-drafted contract (advance, milestones, IP-on-payment, late-interest) is what makes recovery realistic rather than wishful.

Is a verbal, WhatsApp or email-only freelance agreement enforceable?
Often yes. A concluded contract can arise from correspondence even without a formal signed document, so an email or WhatsApp exchange can bind. But proof is harder, terms are usually missing, and you’re exposed on IP, payment timing, and disputes. A signed written agreement is far safer; treat email-only as the fallback, not the plan.

Can I enforce an unstamped freelance agreement in court?
The contract is valid, but an insufficiently stamped instrument is inadmissible in evidence under Section 35 of the Indian Stamp Act, 1899 until you pay the deficit duty plus penalty. Pay the shortfall and the penalty, and the document becomes admissible. So the practical answer is yes, you can enforce it, after regularising the stamping.

Is a non-compete clause in my freelance contract enforceable in India?
Post-termination non-competes are largely void under Section 27 of the Indian Contract Act, 1872, which strikes down agreements in restraint of trade. What’s enforceable instead: in-term exclusivity (during the engagement), confidentiality (which survives), and narrow non-solicitation. So draft those substitutes rather than relying on a non-compete that probably won’t hold.

Am I an employee or a contractor, and what if I’m misclassified?
The control or four-fold test decides it on substance, not the label: who controls method, tools, hours, integration, and financial risk. Misclassification can trigger PF, ESI, and gratuity exposure plus deemed employment for the client. Draft a clear independent-contractor clause (own tools, own hours, own taxes, no benefits) and make sure the working reality matches it.

Do I have to charge GST even below Rs 20 lakh (the OIDAR / Upwork / Fiverr trap)?
Generally no for ordinary domestic supply below the threshold. But the OIDAR rules and reverse-charge mechanism can still pull you in through certain platform or import-of-service scenarios, for example paying for services from an overseas platform. So check the specific facts before assuming you’re exempt; the threshold exemption is the rule, not an absolute.

Why did my client deduct 10% TDS, and can I get it back?
That’s Section 194J TDS on professional fees. It isn’t a loss; it’s a prepayment of your income tax. Claim credit for it through Form 26AS or your Annual Information Statement when you file your return, and it adjusts against your final liability or comes back as a refund. Ask the client for Form 16A so your credit reconciles cleanly.

Section 194J vs 194C vs 194H, which TDS provision should the contract reference?
Section 194J for professional or technical services (10%), which fits most freelance work; Section 194C for genuine works contracts (1-2%); Section 194H for commission or brokerage (2%). Reference the correct one in the tax clause so the client doesn’t mis-deduct, because the wrong section creates a shortfall the deductor answers for and a reconciliation headache for you.

Wet-ink vs Aadhaar e-Sign vs DSC, which signing method?
All three are valid under the Information Technology Act, 2000. Wet-ink suits the cautious or low-tech deal; Aadhaar e-Sign suits fast remote execution and is increasingly the default; DSC suits high-value or recurring deals where a stronger cryptographic signature is worth the setup. Specify the chosen method in the execution block and retain the audit trail as proof.

References

Case Law

Statutes

Primary and regulatory sources

Disclaimer

This article is for informational and educational purposes only and does not constitute legal advice. The clause language and commentary above are illustrative drafting references; they are not tailored to any specific transaction, party, or jurisdiction. For specific legal guidance on drafting, negotiating, or executing a freelancer agreement, consult a qualified legal professional.