How to Review a Consultancy Agreement in India

A consultancy agreement looks simple: one side pays, the other side advises. In practice it has to do three jobs at once, fix the commercial deal, keep the consultant from being treated as an employee, and settle who owns what the consultant creates. Get any of those wrong and the fallout shows up years later, not on signing day. The single biggest mistake is treating the "independent contractor" line as a formality. It is not. Indian labour authorities and courts look past that line at what actually happens day to day. (Adira, which publishes this guide, makes contract review and CLM software; this page is written to be useful on its own, whether or not you ever use it.)

This guide walks a typical Indian consultancy agreement in order: scope and deliverables, fees and payment, independent-contractor status and misclassification risk, IP assignment, confidentiality, non-solicitation, termination, indemnity and liability, and the "no employer benefits" clause almost every one carries. To mark up a contract yourself first, drop it into Weave, Adira's free browser-based contract tool, and flag the clauses this guide points to.

The business deal first

Strip the legal language away and the contract decides four things: what the consultant must actually deliver, how and when they get paid, who owns the output, and how easily either side can exit. Read for those answers first.

The label "consultant" does quiet work. It signals a contract for service, an engagement to deliver an outcome, not a contract of service, which is employment. Indian law does not accept that label at face value. PF and ESI authorities, and courts, look at how the engagement actually runs, who controls the manner of the work, whether it is exclusive, whether pay looks like a salary or an invoice. A consultancy agreement that reads like an employment contract with "employee" swapped for "consultant" fixes nothing; it creates a paper trail that works against the company later.

Clause by clause

Scope and deliverables. Check that the scope is defined, checkable output, a report, a set number of advisory hours, working software, with acceptance criteria, not open-ended language like "such other services as the Client may require from time to time." Vague scope invites scope creep for the client and payment disputes for the consultant, since neither side can point to what was actually promised.

Fees and payment. Check whether the fee is a fixed retainer, a per-project fee, or time-and-materials. A schedule tied to milestones, not just "monthly," protects the consultant from months of unbilled work. Two statutory points apply. Professional fees attract TDS, historically under Section 194J of the Income Tax Act, 1961 at 10 percent (2 percent for purely technical services) once payments cross Rs 50,000 in a year; from 1 April 2026 this sits under Section 393(1) of the Income-tax Act, 2025, carrying the same rates and threshold forward. And if the consultant holds Udyam registration as a micro or small enterprise, the MSMED Act's 45-day cap applies regardless of the contract. See our guides on payment terms and the MSME 45-day rule.

Independent-contractor status and misclassification risk. India has no single misclassification statute. Each welfare law defines "employee" in its own broad, functional terms. Section 2(f) of the Employees' Provident Funds and Miscellaneous Provisions Act, 1952 defines "employee" as:

"any person who is employed for wages in any kind of work, manual or otherwise, in or in connection with the work of an establishment, and who gets his wages directly or indirectly from the employer."

Read it on Indian Kanoon. Nothing there turns on the contract's label. Under Section 7A, a Commissioner can hold an inquiry and find a "consultant" was really an employee, with contributions assessed retrospectively, plus interest, for the whole period. The core judicial test is control: not just what work gets done, but who controls how, when, and where, set out in Dharangadhara Chemical Works Ltd. v. State of Saurashtra (Supreme Court, AIR 1957 SC 264), on Indian Kanoon.

The case built specifically around a consultant is Sushilaben Indravadan Gandhi and Another v. New India Assurance Company Limited and Others (Supreme Court, 15 April 2020). An honorary hospital surgeon was killed travelling for work; liability turned on whether he was an employee or an independent professional. The Court held control alone is not a universal test, and looked at the full picture, he ran his own practice, was not on payroll, was not directed day to day, and was free to consult elsewhere, and held it a genuine contract for service. Read it on Indian Kanoon. A contract missing those facts, fixed hours, one client, daily supervision, looks closer to Dharangadhara than to Sushilaben, whatever it is titled. See our independent contractor guide.

IP assignment. A consultant's work does not automatically belong to the client. Section 17 of the Copyright Act, 1957 gives the employer first ownership only where a work is made "in the course of the author's employment under a contract of service." A contract for service is not covered; the output stays the consultant's unless the agreement explicitly assigns it. Even then, Section 19(5) says an assignment silent on duration "shall be deemed to be five years," and Section 19(6) presumes a silent territory extends only "within India." Read both on Indian Kanoon. An agreement assigning "all IP in the deliverables" without "in perpetuity, throughout the world" gives the client five years, India only, not permanent global ownership. See our IP assignment guide.

Confidentiality. Standard, since a consultant often sees financials, strategy, or product plans well beyond the deliverable. Check it defines what counts as confidential, carries reasonable exclusions, and, unlike a non-compete, validly survives termination. See our confidentiality guide.

Non-solicitation. Many agreements stop the consultant soliciting the client's customers or staff, or vice versa, after the engagement ends. Section 27 of the Indian Contract Act, 1872 says: "Every agreement by which any one is restrained from exercising a lawful profession, trade or business of any kind, is to that extent void." Read it on Indian Kanoon. A clause with a defined period, limited to people actually dealt with, active solicitation only, usually survives; one broad enough to bar serving any client the company has ever dealt with reads as a non-compete. See our non-solicitation guide.

Termination. Check the notice period (commonly 15 to 30 days either way), whether termination is for convenience or only for cause, and what happens to fees for delivered-but-unbilled work and work in progress. A client who can terminate for convenience with no notice and no payment for part-done milestones is a red flag for the consultant; no cause-based path at all is a red flag for the client.

Indemnity and liability cap. Check what the consultant indemnifies against, typically IP infringement and confidentiality breach, and whether total liability is capped, and at what. A cap tied to fees paid in the preceding six to twelve months is standard; an uncapped indemnity is a serious exposure for an individual or small firm, since one claim can exceed the entire engagement fee many times over. See our guides on indemnity clauses and limitation of liability.

No employer-benefit representation. Almost every agreement states the consultant is not entitled to PF, ESI, gratuity, or leave, and handles their own taxes. Fine to include, but it settles nothing on its own; it is exactly the clause a PF or ESI authority looks past when the working reality, fixed hours, one client, daily supervision, says otherwise.

Red flags table

Normal	Red flag	Why it matters
Deliverables defined with acceptance criteria	"Such other services as required," no defined output	Nothing to point to if a dispute starts over what was promised
Non-exclusive, consultant free to take other clients	Exclusivity required, in the contract or in practice	A factor courts weigh toward employment
Paid against invoices for milestones or a defined period	Fixed "monthly salary" language, paid on a payroll date	Wage-like, calendar-fixed pay fits the EPF/ESI "wages" pattern
Consultant decides method, tools, and hours	Client assigns daily tasks, fixed hours, issues a laptop and email ID	Control over manner of work is the test since Dharangadhara
IP assignment states "in perpetuity, worldwide"	Silent on duration and territory	Defaults to 5 years, India only, under Section 19(5) and 19(6)
Liability capped, commonly at 6-12 months' fees	No cap on indemnity or liability	A single claim can exceed the entire engagement fee
Termination states notice and treatment of part-done milestones	Client can terminate for convenience, no notice, no payment for work in progress	Consultant absorbs the client's cancellation risk for free
MSME status checked, 45-day cap applied if Udyam-registered	No process to check status before agreeing payment terms	Section 15 caps agreed payment at 45 days regardless of the contract
Non-solicit limited to clients or staff actually dealt with	Bars serving any client of the company at all	Reads as a disguised non-compete, risks being void under Section 27

Bad clause, better clause

Bad: "The Consultant shall provide such advisory and other services as the Client may require from time to time, and shall be available during the Client's business hours. The Consultant shall be paid Rs 1,50,000 per month. The Consultant is an independent contractor and is not entitled to any employee benefits. All work product created by the Consultant during the engagement shall belong to the Client."

What is wrong: open-ended scope and fixed monthly pay tied to business-hours availability look like a salary. The IP line does not say "assign," and states no duration or territory, so it defaults to a five-year, India-only reading at best. The label sits next to language that argues against it.

Better: "The Consultant shall deliver the services in Schedule A, against the milestones and acceptance criteria set out there, on a non-exclusive basis. The Consultant shall determine the method, tools, and schedule of delivering the Services, and may engage other clients during the term. Fees of Rs 1,50,000 per milestone shall be paid within 15 days of the Client's written acceptance. The Consultant hereby irrevocably assigns to the Client, in perpetuity and throughout the world, all right, title and interest, including copyright, in the Work Product. The Consultant is responsible for its own tax filings and statutory compliance, and the Client shall have no obligation to make contributions under the EPF Act, 1952 or the ESI Act, 1948 in respect of the Consultant."

What changed: scope is tied to milestones instead of open-ended availability, non-exclusivity supports the label instead of just asserting it, payment tracks acceptance rather than a calendar date, and the IP clause names "assign," "in perpetuity," and "throughout the world" to defeat Sections 19(5) and 19(6) instead of relying on silence.

Printable checklist

1. Deliverables defined with acceptance criteria, not open-ended "such services as required"?
2. Engagement stated non-exclusive, and hours/tools/supervision actually support that label?
3. Fee schedule tied to milestones, not a fixed date resembling salary?
4. TDS treatment stated (Section 194J / Section 393(1) rates and threshold)?
5. If Udyam-registered, does the payment term respect the 45-day cap under Section 15?
6. IP assignment uses "assign," states "in perpetuity" and "throughout the world"?
7. Confidentiality defines what counts confidential, with exclusions, surviving termination?
8. Non-solicit, if any, limited to clients or staff actually dealt with, for a stated period?
9. Termination states notice period and treatment of part-done milestones and unpaid invoices?
10. Liability capped, with a stated figure, and indemnity naming specific risks?

How this interacts with related clauses

No single clause carries the whole risk. The independent-contractor and no-employer-benefit clauses only hold up if scope, exclusivity, and payment elsewhere describe an arrangement that genuinely looks independent; a strong label cannot rescue weak substance. IP assignment and confidentiality should be read together, since a client can own the deliverable outright and still need confidentiality to stop reuse of the know-how. Indemnity and the liability cap are a pair too: an indemnity naming real risks only matters if the cap does not swallow it.

US and global contrast

The US runs a similar substance-over-label enquiry through different machinery. The IRS and several states, most notably California's "ABC test," presume employee status unless the company proves the worker is free from control and runs an independently established trade. On IP, the US "work made for hire" doctrine can vest ownership in the payer automatically for certain commissioned work; India has no equivalent, so an Indian agreement always needs its own explicit assignment clause. India's difference is mechanism, not logic: no single misclassification statute, no ABC-style presumption. Each welfare law, EPF, ESI, and separately the Payment of Gratuity Act, 1972, applies its own definition, so a company can face a PF finding on one consultant while a separate ESI inquiry into the same person reaches a different conclusion.

When a lawyer is worth it

Pay for a review when the engagement is long-running or exclusive in practice, close to full-time, exactly the pattern PF and ESI authorities reclassify; when deliverables involve IP the client must own outright; when the indemnity is uncapped and the consultant cannot absorb a large claim; or when a dispute has already started.

FAQ

Can a company just call someone a "consultant" to avoid PF and ESI contributions? It can write the word, but Section 2(f) of the EPF Act and the parallel ESI definition turn on wages and control, not the label. A Commissioner can reclassify the relationship under Section 7A of the EPF Act, with retrospective liability.

Does a consultant automatically own the work they create for a client? Yes, unless the contract has an explicit assignment clause. Section 17(c)'s employer-ownership default applies only to a genuine employee under a contract of service, not a consultant.

Does the MSME 45-day payment rule apply to individual consultants? Yes, if the consultant holds valid Udyam registration as a micro or small enterprise when the contract is signed. Section 15 of the MSMED Act, 2006 caps agreed payment at 45 days, and Section 16 adds compound interest at three times the RBI-notified bank rate if that deadline is missed.

Should a consultancy agreement include a non-compete? It can be written, but Section 27 of the Indian Contract Act, 1872 voids agreements restraining a lawful profession, trade, or business once the restraint outlasts the engagement, whoever is restrained. A narrower non-solicit limited to actively approaching specific clients or staff has a better chance of holding up.

What is the single biggest thing a company can do to reduce misclassification risk? Make the contract match reality: non-exclusive engagement, consultant-controlled hours and methods, milestone invoicing instead of fixed monthly pay, and no daily task supervision. The strongest clause on paper cannot fix an arrangement that runs like full-time employment.

---

This guide explains how a typical Indian consultancy agreement is generally structured, and the statutory tests and defaults that apply to its contested clauses. It does not tell you whether your specific consultant would be reclassified as an employee if challenged, or whether your specific IP or indemnity clause is enforceable as written; that depends on the actual facts of control, exclusivity, and the exact wording in front of you. For that, especially before a PF or ESI inspection, or before signing an engagement involving valuable IP, talk to a lawyer who can look at your actual working arrangement, not just the contract.