The ₹94 crore bid that was right on paper
A planning director at a mid-size highway contractor in Punjab once described a project that still came up in internal reviews years later. His company had won an NHAI package worth ₹94 crore, competitively bid at L1. The project was in Gujarat. His key site team was committed to an active package in Rajasthan. The work required design-build capability for river bridge structures, which the company had done once before on a smaller project in a different state. The relationship with the NHAI regional office was new.
He knew, when they submitted the bid, that the resource picture was thin. But the package size was right. The financial model worked. And there was internal pressure to maintain the order book.
Eighteen months later, the project was 8 months behind schedule. The bridge subcontractor had a measurement dispute with the Independent Engineer. The contractor's most experienced PM had been reassigned from head office to the Gujarat site, which meant the Rajasthan project was also in trouble.
The problem was not the project. The problem was the bid decision.
The real cost of a wrong bid
Contractors who calculate the cost of a bad bid usually count the direct costs: bid preparation (₹3 to ₹8 lakh for a large NHAI package), technical submission costs, EMD tied up during evaluation. These are real but they are not the main exposure.
The main cost is opportunity. The site team deployed on a project they were not suited for could have been deployed on one they were. The BD time that went into preparing the tender could have gone to a better-fit opportunity. The management attention consumed by a struggling project for 24 months does not show up as a line item anywhere.
On a ₹100 crore package where the contractor was underprepared for the specific project conditions, the combined cost of under-performance, penalty exposure, and management distraction can reach ₹8 to ₹15 crore over the project lifecycle. The bid preparation cost is a rounding error by comparison.
Why gut feel fails at scale
When a contractor manages 3 to 5 projects, the principal knows every site by instinct. She knows which PMs can handle a complex bridge package and which cannot. She knows which NHAI regional offices run clean programmes with predictable payment cycles and which have systemic IE-appointment delays. Go/no-go is intuitive because the entire portfolio fits inside one person's head.
At 15 to 25 active projects, it does not. The planning team is evaluating 40 to 60 tenders annually. The principal does not have the time for each one. And the instinct that worked at smaller scale produces errors at larger scale, because it is pattern-matching from 5 years ago on projects that are now significantly bigger and more complex.
A structured framework does not replace judgement. It structures judgement so the same quality of assessment can be applied consistently by a planning team, across 60 bid evaluations per year, without needing the principal in every room.
The 6 axes of the go/no-go decision
Every bid decision involves six questions. Most contractors answer them informally, in whatever order the RFP prompts them. A structured framework assigns a score to each axis and aggregates them into a decision.
Technical fit. Does the scope match what you have built before, at comparable scale and complexity? A contractor who has built 60 km of two-lane highway has not built a 15 km six-lane urban expressway. The go/no-go question is tighter than the qualification question. Not "do we meet NHAI's QR thresholds?" but "do we have enough relevant experience to execute this without material risk of underperformance?"
Financial capacity. Solvency is a floor, not a score. The question is whether you can fund the mobilisation advance shortfall, carry the float during payment cycles that routinely run 60 to 90 days, and deploy bank guarantees of 5 to 10% of contract value without stressing your credit lines. A contractor who wins a ₹150 crore package while already guaranteeing ₹300 crore of active work has a financial exposure that may not become visible until the project is 6 months old.
Experience match. Relevant prior work matters, but the specificity matters more. NHAI evaluators notice when a contractor lists BOT Toll projects on an EPC bid, or cites a state PWD package against an NHAI-specific technical threshold. Your experience ledger for go/no-go purposes should be maintained at the contract-mode level: which GCC forms have you operated under, how many times, and at what project sizes?
Resource availability. The two scarcest resources in any highway contractor are experienced PMs and quality plant. Not whether they exist in the company, but whether they are deployable on this specific project from the NTP date. A PM who will be available "after Q2" is not available for a project with a NTP in Q1. Be precise. Go/no-go decisions that assume resource availability they do not actually have are the ones that produce the Punjab scenario above.
Authority relationship. Some NHAI regional offices run structured, well-administered programmes with predictable IE appointment timelines and payment cycles in the 45 to 60-day range. Others have systemic measurement disputes, slow IE appointments, and payment delays that routinely run to 6 months. A contractor new to an authority relationship is pricing in an unknown, not a quantified risk. The score here should reflect both the quality of the authority relationship and how much historical data you have to base that assessment on.
Competitive landscape. Who else is likely to bid this package, at what price levels, and what does that imply for your win probability at a reasonable margin? A tender with 12 likely qualified bidders and an authority with a strong L1 orientation is a different calculation from a tender with 4 likely bidders where technical quality carries real weight at evaluation. Public tender data from CPPP and NHAI's portal gives you bidder history on similar packages in the same region.
Scoring and thresholds
Each axis scores on a 1-to-5 scale. 5 means full alignment. 1 means a known gap that requires mitigation before you can proceed.
A score of 5 looks like: you have done exactly this kind of project for this authority, at this contract value, and the team is ready from day one.
A score of 1 looks like: this is a new contract mode, the PM you want is committed to another site until the end of Q2, and three of your likely competitors have active relationships with this regional office.
The aggregate score maps to three decisions:
- - 24 to 30: Go. Assign resources and proceed with full bid preparation.
- 18 to 23: Conditional go. Submit only if specific named conditions are resolved before bid submission.
- Below 18: No-go. The opportunity cost of the resources required exceeds the realistic upside of winning.
The threshold is calibrated, not universal. A contractor who bids exclusively within familiar authority relationships may find 24 too conservative for their risk profile. A contractor expanding into new geographies or contract modes should consider a higher floor. Calibrate against your own bid win rate and post-award performance over the past 3 years.
The more important discipline: when you score "conditional go," someone needs to own each condition. Conditions without owners become assumptions. Assumptions become surprises at the 6-month review.
This is where the reading pays off
If you have read the tender using the 7-section reading order and identified the SCC modifications, BOQ gaps, and risk flags, you already have the raw material for a go/no-go score. The SCC reading tells you about authority-specific risk allocation. The BOQ cross-check tells you about technical scope fit. The qualification criteria check tells you where you stand on the experience axis.
And if you have drafted pre-bid queries, you already know which ambiguities in the NIT are genuine risks rather than drafting conventions. Some of those ambiguities affect your score on the competitive landscape axis: if your team caught an SCC modification that three other bidders missed, your pricing is tighter and your win probability is better than the raw bidder count suggests.
The go/no-go framework is not a separate exercise from tender reading. It is the output of the tender reading process, formalised into a decision.
CivilBolt's Go/No-Go scoring runs the 6-axis assessment against your company's qualification profile and project history. The analysis that takes a planning lead half a day to assemble takes about 20 minutes. The decision still belongs to the BD head. The supporting data is there before the meeting starts.
What's the worst-fit bid your company has submitted in the last three years? If you can answer that in one sentence, you can probably also describe which of the 6 axes would have flagged it first.