ISO 9001:2015 · ISO 45001:2018

RoW & Compliance

Right-of-Way (RoW) in India: Why Projects Stall and How They Get Cleared

RoW is where most telecom projects lose time. A practical look at the approvals maze — and what it takes to keep a file moving.

Quick AnswerRight-of-Way (RoW) is the legal permission to lay infrastructure along or across a route, coordinated with authorities such as MCD, NHAI, PWD and municipal bodies. It is where most telecom projects stall, and a dedicated in-house liaison team is the most reliable way to keep files moving.

The real bottleneck is rarely the engineering

Ask any experienced telecom contractor where projects lose the most time, and the answer is almost never the drilling — it is the paperwork. Right-of-Way (RoW) is the permission to lay infrastructure along or across a route, and securing it means dealing with a patchwork of authorities, each with its own process, fees and timelines.

Who has to say yes

A single urban route can touch many bodies: municipal corporations, development authorities, the PWD, NHAI for highways, rail authorities for crossings, traffic police for road works, and sometimes utility owners and private landholders. Each approval is a separate workstream, and a delay in any one can hold up the entire route.

Why files stall

  • Incomplete applications: missing surveys, unclear alignments or absent documents send a file back to the start.
  • No follow-up: applications that are filed and forgotten simply sit.
  • Fragmented responsibility: when RoW is sub-contracted or split, no one owns the outcome.
  • Poor design: a route that clashes with existing utilities invites objections and revisions.

What actually clears them

The projects that move are the ones treated as a managed process, not a formality. That means an accurate survey and a clash-free design that authorities can approve with confidence; complete, correct applications the first time; and — crucially — persistent, informed follow-up with each body until the permission is in hand. This is relationship and process work as much as it is technical.

Why in-house liaison beats sub-contracting

When a contractor keeps a dedicated liaison team on its own payroll, RoW becomes a single accountable workstream. The team knows how each authority works, spots problems early, and pushes files forward daily. When RoW is handed to a sub-contractor, accountability blurs and files drift — which is exactly why long-pending projects so often turn out to be stuck on approvals, not construction.

The bottom line

RoW is the discipline that decides whether a telecom project finishes on time. Treated as an afterthought, it becomes the reason for months of delay. Treated as a managed, in-house process backed by good survey and design, it turns from the biggest risk into a solved problem.

Related insights

More on why files stall, and the topics that sit next to it:

Terrain & Monsoon|Trenchless vs Open-Trench|Choosing a Telecom EPC Contractor

Permission file not moving?

Tell us which office holds it — most stalls are a missing annexure, not a decision.

Get A Quote +91 99100 10209

Why RoW files stall — causes, remedies and detailed questions

Permission delay is the largest single cause of programme slip on Indian underground projects, and very little of it is caused by decisions against applications. Files stall for administrative reasons that are almost entirely preventable: a missing annexure, a misdirected submission, an unclosed obligation from earlier work, or simply that nobody followed up. The distinction matters because each has a different remedy.

The four reasons files actually stop

First, incomplete first submission — a file returned for a missing document rejoins the queue at the back rather than resuming where it stopped. Second, wrong jurisdiction, where the receiving body has no power over that metre and the file simply sits. Third, an unclosed restoration obligation from earlier work, sometimes by a different contractor, which departments check against the applicant even when applicants do not. Fourth, submission without pursuit: a file that belongs to everyone belongs to nobody, and those sit for months.

What actually moves a file

Jurisdiction mapped before drafting, so nothing is sent to an office that cannot act on it. A genuinely complete first submission, because the cost of one missing annexure is measured in weeks. Restoration history audited against the applicant before filing rather than discovered afterwards. One named person accountable per corridor with a dated log of every contact, which is the difference between pursuit and submission. And physical follow-up, because on a queue-driven process presence achieves what correspondence does not.

Beyond the basics

Can any contractor guarantee a sanction date? No, and one who does is either misinformed or misleading you. The timeline belongs to the authority; what can be committed to is completeness and pursuit.

What is the single most expensive mistake? An incomplete first submission. The file returns and rejoins the queue at the back, which costs far more than the missing document was worth.

Can an earlier project block a new application? Yes. An unclosed restoration obligation attaches to the applicant rather than the project, and departments check it routinely.

Does a survey help the application? Materially, particularly on roads opened recently. It demonstrates the excavation is targeted rather than exploratory.

Is following up really that important? It is usually decisive. Files move because someone is at the department asking, not because they were submitted correctly.

Terms used on this page

Annexure — a supporting document whose absence returns the entire application. Jurisdiction — the authority with legal power over a particular stretch of road. Restoration obligation — an outstanding duty to reinstate, which follows the applicant into later files. Queue position — a file's place in processing order, lost entirely when it is returned. Named accountability — one identified person responsible for a corridor's permission status.

Trusted by India’s telecom & infrastructure leaders

Bharti Airtel
Tata Communications
TCIL
Reliance Jio
Gigatel Networks
RailTel
MTNL
BSNL
Vodafone Idea
P2P Networks
Bharti Airtel
Tata Communications
TCIL
Reliance Jio
Gigatel Networks
RailTel
MTNL
BSNL
Vodafone Idea
P2P Networks