Why Mezux Touch
Timely Completion Commitment
A date we can actually keep, because we control the plant, the crews and the permissions that decide it.
Quick AnswerWe commit to dates because we control the three things that normally break them: the plant, the crews and the permission programme. Where something is genuinely outside our control, we say so before signing rather than after slipping.
Programmes slip for three reasons
In our experience almost every underground project delay traces to one of three causes: plant unavailable when promised, crews reassigned to another job, or a permission that nobody opened early enough.
All three are structural rather than accidental. A contractor on hired plant, supplied labour and outsourced liaison has ceded control of all three and can only report on them.
We removed each one deliberately. That is the whole argument for owned fleet, in-house crews and an internal liaison desk, and it is why our dates behave differently.
What we will not promise
We will not promise an authority's sanction date, because that timeline belongs to the authority. What we commit to is a complete first submission, physical follow-up and an honest status you can see at any point.
We will not promise a fixed drilling rate through unknown ground either. Where rock or boulders are likely we quote a range and explain which end applies, rather than quoting the low end and relying on a variation clause.
Saying this at tender stage costs us some bids. It costs clients considerably less than the alternative.
Every market has one governing constraint
Maharashtra bans road cutting through the monsoon. Patna's water table shortens the year from the other direction. A metro package runs on possessions granted months ahead. A plant survey runs on a shutdown window nobody will move.
The first thing we establish on any job is which of these applies, because everything else in the programme is scheduled against it. Treating it as a detail is how a route that clears approvals a month late loses an entire season.
Where a client's own date cannot move, we say at tender which stretches are exposed rather than absorbing the risk into a schedule that will not hold.
Reporting that shows problems early
A weekly status that only reports progress is decoration. Ours reports what is at risk, why, and what decision would unblock it.
Clients occasionally find this uncomfortable in month one and useful by month three, because a problem surfaced early is still solvable.
The record behind the claim
700 KM of GPR survey delivered inside 30 days, a separate 250 KM month, and delivered corridors at Bawana, NDMC and Okhla completed under multi-authority compliance.
Those numbers exist because the constraints above were managed rather than reported, and we are willing to be measured against them.
Frequently asked questions
Almost always one of three causes — plant unavailable, crews reassigned, or a permission opened too late. All three are structural, and we removed each deliberately.
No, because that timeline belongs to the authority. We commit to a complete first submission, physical follow-up and an honest status you can see at any point.
We quote a range and explain which end applies to which ground. Quoting the low end and relying on a variation clause later is the practice we are trying to avoid.
By identifying the governing constraint at scoping and building backwards from it. A route clearing approvals a month late often loses a whole season, not a month.
What is at risk and what decision would unblock it, not just what was completed. A problem surfaced early is still solvable.
Have a date that genuinely cannot move?
Tell us the date first and the scope second — we will say honestly whether it is deliverable.
Get A Quote +91 99100 10209Delivery commitment — what we promise, what we do not, and detailed questions
Mezux Touch commits to dates on the basis that we control the things dates depend on: our own plant, our own crews and our own permission desk. What we do not control is an authority's processing time, seasonal ground conditions, or an operating client's site access, and we say so at quotation rather than promising and explaining later. A contractor who commits to everything has either not read the scope or intends to manage the gap through variations after award.
The three reasons programmes actually slip
Permissions, which stall administratively rather than through refusal. Ground worse than assumed, which happens when nobody surveyed before pricing. And plant that was not available when the window opened, which is the reason owning equipment matters more than it appears to. Two of those three are within our control, which is why our commitments are framed around them. The third — permission timing — we control the inputs to but not the outcome, and framing it otherwise would be dishonest.
How problems surface early rather than late
Every corridor has one accountable owner and a status the client can see rather than a monthly summary. Where a permission is not moving, that is reported when it becomes apparent rather than when it becomes critical. Where ground turns out worse than assumed we stop and reassess rather than forcing progress, because a forced bore becomes an abandoned bore. Where a seasonal window is at risk we say which stretches are exposed at scoping rather than absorbing it into a schedule that will quietly slip. Early bad news is cheaper than late bad news for everyone.
Beyond the basics
What will you not promise? A sanction date, ground you have not let us survey, or access on an operating site we do not control. Each is outside our control and saying otherwise is dishonest.
What do you actually commit to? Plant availability, crew availability, a complete permission submission with physical pursuit, and honest early reporting when something is not moving.
How is progress reported? Per corridor with a named owner and a visible status, not a blended monthly summary that hides which item is holding the programme.
What happens if ground is worse than assumed? We stop and reassess rather than forcing progress. A forced bore becomes an abandoned bore, which costs far more than the pause.
Is there evidence behind the record? Delivered corridors with names, clients and dates — 135 KM at Bawana, 225 KM for NDMC, 67 KM at Okhla — which can be asked about specifically.
Terms used on this page
Variation — a post-award change to scope or rate, often used to recover an under-priced commitment. Exposed stretch — a section whose delivery depends on a window or approval staying open. Blended status — a combined progress report that conceals which individual item is delayed. Reassessment point — a defined stage at which work stops if conditions differ from prediction. Accountable owner — one named person responsible for a corridor's progress and reporting.
