Telecom EPC — Engagement
How We Take Telecom Projects — Our Terms, Stated Plainly
Four conditions decide whether we can take a telecom project. Published here so a client finds out at first contact rather than after a tender cycle.
Four conditions
₹1 crore minimum.50 kilometres minimum.Awarded directly.Complete scope, or none.These are not negotiating positions. Each exists because taking work outside it produces a job we cannot deliver to the standard we describe elsewhere on this site, and a client is better served knowing that before a tender than after one.
Local underground utility work follows different terms entirely — ₹1 lakh minimum, single lines accepted
Quick AnswerMezux Touch accepts telecom projects on four conditions: a minimum order value of ₹1 crore, a minimum route length of 50 km, a direct award from the telecom operator or ISP rather than through another contractor, and the complete project scope rather than an individual activity within it. Local underground utility work is a separate service with a ₹1 lakh minimum where single lines are accepted.
Why ₹1 crore and 50 kilometres
Mobilising crews, plant, a survey team and a liaison desk onto a corridor carries a fixed overhead that does not shrink with the job. Below roughly 50 km that overhead becomes a large share of the contract, which produces one of two outcomes: a price the client finds unreasonable, or a margin we cannot deliver properly on.
Neither is a good result, so we set the threshold rather than quoting and disappointing. A client whose project sits below it is genuinely better served by a contractor built for that scale, and we say so instead of taking the work and managing the difference afterwards.
Why direct awards only
A corridor date can only be committed by whoever controls the sequence. Working beneath another contractor means our crew availability, rig allocation and permission pursuit all sit behind decisions taken elsewhere, while the client still holds us to a completion date.
That is accepting responsibility for a programme we do not run, and it is not a promise worth making. It also means our capacity stays available for direct clients rather than being committed to filling gaps in another contractor's schedule.
This is a commercial position rather than a comment on any contractor. Plenty of good firms work that way; we have chosen not to on telecom corridors.
Why complete scope rather than a part of it
A telecom corridor rarely fails on drilling. It fails at the joins — a survey that arrives after the gang is standing by, a permission clearing when the rig is committed elsewhere, an as-built nobody produced because the contract ended at commissioning.
Contracting for one activity within that sequence puts us on one side of exactly the interface that causes the failure, accountable for an outcome that depends on parties we have no authority over. So we do not take HDD-only, splicing-only, blowing-only or trenching-only packages on telecom projects.
We also do not hire out HDD machines. Our rigs work on our own contracted scope with our own crews, which is what keeps accountability with the party that gave the date.
What happens after you send us a route
Does the project fit these four conditions?
The first thing we check is whether the project sits inside our thresholds. If it does not, we say so within a day or two and, where we can, suggest who might be better placed. A quick honest no is more useful to a client than a slow polite maybe.
Alignment assessment before any figure
We assess the route for ground types, crossing count, jurisdiction changes and access. This is where a corridor's real difficulty shows, and it frequently differs substantially from the length-based assumption a plan was built on.
Establishing what we are pricing against
Where the programme allows, ground is surveyed before a rate is agreed. Where it does not, we quote a range and name which end applies to which conditions rather than quoting the low end and relying on a variation clause.
Mapping the permission workload
Every governing body along the route is identified and the long-lead items — rivers, railways, canals, cantonment and forest land — are flagged with realistic timelines rather than optimistic ones.
Itemised scope, sequence and exclusions
The proposal states what is included, what is excluded, what we will not commit to and why. Exclusions are written to be read rather than buried, because a client discovering one after award is a dispute we could have prevented.
Direct contract with named accountability
On award, one named person becomes accountable for the corridor with a status the client can see at any time, rather than a monthly summary that conceals which item is actually holding progress.
Sequenced against the items that wait
Crossings and multi-jurisdiction approvals open first because they wait rather than slip. Survey phases ahead of the construction front. Plant is allocated by ground segment rather than by contract length.
Handover, restoration and deposit recovery
Tested as-built records, splice and OTDR documentation, every restoration certificate closed and every deposit pursued to release — because an open obligation on this corridor delays the applicant's next application elsewhere.
What we do commit to
Plant and crew availability, because both are ours. A complete first permission submission with physical follow-up rather than correspondence. A visible per-corridor status rather than a blended monthly figure. And honest early reporting when something is not moving, because early bad news is cheaper than late bad news for everyone involved.
What we will not commit to is a sanction date, since the timeline belongs to the authority, or to ground we have not been allowed to survey. Any contractor guaranteeing either is either misinformed or misleading you.
The one place these terms do not apply
Local underground utility work — water, sewer, gas and fire-safety lines for buildings, colonies, societies and campuses — runs on entirely different terms. There the minimum order value is ₹1 lakh, a single line is a normal scope, and being brought in for one specific run is perfectly reasonable.
The two are separated deliberately. A builder needing one water line and an operator awarding a national backbone need different conversations, and mixing them serves neither.
Elsewhere in this section
Telecom EPC overview|NLD OFC projects|FTTH projects|Delhi–Mumbai corridor|Mumbai–Chennai corridor|Bengaluru–Kolkata corridor|Delhi–Patna corridor|Delhi–Indore corridor|Jammu–Patna corridor|Delhi NCR|Gurugram|Mumbai & MMR|Bihar|Jharkhand
Frequently asked questions
Rarely, and we would rather say so at first contact than after a tender cycle. Below them we cannot deliver to the standard described elsewhere on this site.
Because a corridor date can only be committed by whoever controls the sequence. Beneath another contractor we would be guaranteeing a programme we do not run.
Not on telecom projects. A bore is only as good as the survey before it and the permission that allowed it, and taking one stage means accepting risk created elsewhere.
No. Our rigs work on our own contracted scope with our own crews, which keeps accountability with the party that gave the date.
We will say so quickly and, where we can, suggest who might suit it better. A fast honest no is more useful than a slow maybe.
No. Underground water, sewer, gas and fire lines run from a ₹1 lakh minimum where a single line is a perfectly normal scope.
Does your project fit these terms?
Send the route and length — if it does not, we will tell you within a day or two rather than after a tender cycle.
Get A Quote +91 99100 10209Engagement terms — reasoning, exceptions and detailed questions
Published thresholds are unusual in this industry, and the reason we publish ours is practical rather than principled: most of the wasted effort on both sides of a tender happens before anyone discovers the project was never a fit. Stating the four conditions openly means a client whose project sits outside them finds out in a day rather than after preparing a submission, and it means the projects that do reach us are ones we can actually deliver well.
What each condition is protecting against
The order value and length minimums protect against a fixed overhead being spread too thin, which produces either an unreasonable price or an undeliverable margin. The direct-award condition protects against committing to a programme we do not sequence. The full-scope condition protects against being accountable for an outcome created at an interface we have no authority over. None of the four exists to make us look selective; each exists because taking work outside it produces a job that disappoints, and a disappointed client is more expensive than a declined enquiry.
What a proposal from us actually contains
An itemised scope by stage rather than a lump figure. A stated sequence showing which items open first and why, because on corridor work sequence carries more risk than rate. Explicit exclusions written to be read rather than buried in an annexure. Ground assumptions stated with the range that applies where survey has not yet happened. Named accountability from award. And a clear list of what we will not commit to — sanction dates, unsurveyed ground, access on sites we do not control — so nothing in the contract depends on something outside anyone's control.
Beyond the basics
Is publishing your minimums not bad for business? It removes enquiries we would have declined anyway, at the cost of some that might have grown. On balance it saves far more time than it loses.
What if a client insists on a fixed price without survey? We quote a range and explain which end applies to which ground. What we avoid is quoting the low end and recovering the difference through variations later.
Do you ever make exceptions? For a client we already work with, on a route adjacent to an existing corridor, occasionally. For a new enquiry well below the thresholds, honestly no.
How quickly will you tell us it does not fit? Within a day or two of receiving the route and length. Holding a client in a tender process we intend to decline helps nobody.
Why publish what you will not commit to? Because every one of those items causes disputes when it is discovered after award instead of read before it.
Terms used on this page
Order value — the contract value below which fixed mobilisation overhead becomes disproportionate. Direct award — a contract given by the operator or ISP itself rather than through another contractor. Partial scope — a contract for one activity within a sequence rather than the whole sequence. Interface — the handover point between two contracted parties, where corridor programmes are typically lost. Variation clause — a contract provision allowing a rate to be revised, often used to recover an under-priced bid.
Popular searches — telecom contractor engagement terms
Related searches
minimum order value telecom project|direct award vs EPC subcontract|owned HDD rig fleet|no subletting contractor
GPR survey by city
GPR survey Chennai|GPR survey Faridabad|GPR survey Indore|GPR survey Kochi
By sector
non revenue water survey|SUE survey to PAS 128|metro alignment utility clearance
