The Sherpa Guide Series
Data Center Development
India Edition · 2026
Forthcoming edition — not yet published
How to take a site from raw land to an energized, leased facility — what to do, in what order, and what it costs you when you get it wrong.
- Type
- Guide
- Extent
- ≈150 pages
- Status
- Forthcoming
- Geography
- India
- Publisher
- Global Infrastructure Sherpa / Sherpa Publishing
- Price
- $995 — single-user licence
Overview
A working guide for taking an Indian data center site from raw land to an energized, leased facility — what to do, in what order, and what it costs when the order is wrong.
The organising idea behind the series is simple: data center development used to be a real estate business with an electrical problem attached, and is now an electricity business with a real estate problem attached. Every sequencing recommendation follows from that inversion.
India bends it in a particular direction: the answer is almost never in one instrument, and it is almost never only central. A large load has a statutory right of open access above one megawatt, and a lower threshold of one hundred kilowatts for green open access. Whether that power arrives cheaply, though, turns on surcharges — and the surcharge a genuine captive structure escapes is usually the single largest difference in delivered cost. The tests for captive status are not in the Act. They sit in a rule, they turn on twenty-six per cent of the equity and fifty-one per cent of the output measured across a financial year, and that rule was substituted in March 2026 with part of the new text commencing on a separate date. Miss the consumption test in any single year and the whole plant's output is treated as ordinary third-party supply, retrospectively.
The transmission-charge waiver for renewables works the same way — the tables everyone quotes are not the whole instrument. The same amendment back-dates the commissioning date of projects delayed by force majeure, expressly including non-availability of transmission, which changes the answer for a large class of projects. It also puts the renewable-charging test for storage on self-declaration, with verification after the financial year and re-billing if it fails. A developer reading the tables alone gets the wrong number and never sees the retrospective exposure.
Incentives need the same care. Data centres carry infrastructure status, and a dedicated income-tax exemption now exists in statute. It is also, on the face of the amending Act, unusable: the relief turns on conditions "as may be prescribed", and no prescribing rule has been located. This edition says that plainly, because an adviser who reads the exemption as available today is wrong.
Then there is the state layer, which is where the money actually is — the tariff order, the wheeling charge, the surcharges and electricity duty are all state instruments, and choosing a state is choosing all of them. One state repealed its data centre policy in 2026, replaced it, and excluded captive facilities from the new one entirely.
The method is stated as carefully as the findings. This edition separates two questions that are usually run together: whether an instrument is in force, and whether the text quoted from it is current. The first was audited. The second was not audited systematically — and one row in the research was corrupted by exactly that failure, quoting language from inside a footnote that reproduced deleted text. That row was removed rather than repaired, and what it covered is declared a gap.
What this edition covers
Fifteen parts across the full development sequence — the map, choosing your game, site selection, securing power, the captive question, permitting and politics, design and delivery, the capital stack, offtake and leasing, exit, pitfalls, life after the building, tax and incentives, signing the build, physical security and the data layer — followed by a tear-out field checklist, an indicative Indian timeline, a glossary, a note on sources, a full index, the reference register and an India screening layer.
Who this is for
Developers, investors, lenders and operators taking an Indian data center site from raw land to an energized, leased facility.
What you get
- Practical development guidance, not market sizing
- Open access at one megawatt, green open access at one hundred kilowatts
- The captive tests that decide whether you escape cross-subsidy surcharge
- A captive rule substituted in March 2026, with part of it commencing separately
- A transmission-charge waiver whose tables are not the whole instrument
- A tax exemption for data centres that is in force and not yet usable
- Personal-data obligations commencing in tranches, the next in November 2026
- A state policy that repealed its predecessor and excluded captive facilities
- Every instrument separated into in-force, and text-verified-current
- A tear-out field checklist, an indicative Indian timeline and a screening layer
Table of contents
- How to use this guide: A working document for Indian sites, read in the order the decisions arrive.
- Part 0 — The Map: Union and state, and the standing rule that whichever one you forgot is the one that stops you.
- Part 1 — Choosing Your Game: Colocation, hyperscale or captive campus — and which one the captive tests will actually carry.
- Part 2 — Site Selection: Choosing a state is choosing a tariff order, a duty rate and a pollution board, not just a plot.
- Part 3 — Securing Power: Open access at one megawatt, green open access at a hundred kilowatts, and what each one costs in surcharges.
- Part 4 — The Captive Question: Twenty-six per cent of the equity, fifty-one per cent of the output, and the year that undoes both if you miss.
- Part 5 — Permitting and Politics: Consents, clearances and the state approvals that no central instrument will tell you about.
- Part 6 — Design and Delivery: Building where diesel is a regulated emission source and the backup fleet is its own permitting workstream.
- Part 7 — The Capital Stack: What a lender needs settled about land title and power before it will fund anything standing on it.
- Part 8 — Offtake and Leasing: Selling power to your own tenants, and the licensing question Indian colocation keeps litigating.
- Part 9 — Exit: What transfers when the plot came from a state industrial agency with conditions attached.
- Part 10 — Pitfalls: Twelve ways an Indian project goes wrong, starting with a tax exemption that is in force and unusable.
- Part 11 — After the Building: Operations and the compliance calendar, including a data-protection tranche that lands in November 2026.
- Part 12 — Tax and Incentives: Infrastructure status, state capital subsidies, and which of them are self-executing and which are not.
- Part 13 — Signing the Build: Delay, imported plant and duty exposure, and which party is left holding each one.
- Part 14 — Physical Security: What hyperscale tenants audit before they sign, and what cannot be added after the shell is closed.
- Part 15 — The Data Layer: Personal-data duties commencing in tranches, and incident reporting that binds the operator directly.
- The Field Checklist: Tear-out — every union and state consent in the order an Indian project actually needs them.
- Appendices — Timeline, glossary, sources, index, references and the India screening layer: An indicative Indian timeline, a glossary, a note on sources, a full index, the reference register, and the screening layer.
Research and sources
Every instrument named in this edition is cited to its own number, the dates on its face, and the database it was read at. Two questions are kept apart rather than blurred: whether an instrument is in force, and whether the text quoted from it is still current. In-force status is asserted only where a commencement clause or a separate commencement notification was actually read — Presidential assent is not commencement, and Indian statutes routinely commence in tranches years apart. Currency of quoted text was not audited systematically, and the edition says so, because consolidations reproduce superseded language and one row in the research was corrupted by precisely that. Instruments that could not be read at all are named rather than omitted, including the incident-reporting directions, whose issuing body was unreachable throughout. Negative findings are phrased as "not located" rather than "does not exist". No prices are asserted: no tariff order or charge was read, so every cost statement is structural. Nothing here was reviewed by an Indian-qualified lawyer, and anything intended to carry a decision should be re-read against its own instrument on the day it is relied on.
Licensing
Single-user licence. For use by the named licensee only. Redistribution, resale, posting to shared drives or internal circulation beyond the named licensee is a breach of licence. Team licences covering up to five named users are available.