The query that changed the outcome
A contracts manager at an EPC contractor in Hyderabad was reviewing a 420-page NIT for an NHAI four-laning package in Andhra Pradesh. Buried on page 287 (in the Special Conditions of Contract, not the standard GCC) was a clause that modified the force majeure definition to exclude monsoon-related delays entirely. Three other bidders missed it. Her team submitted a pre-bid query referencing the specific clause, noting the conflict with GCC Clause 19, and asking for NHAI's position.
NHAI's written response at the pre-bid conference acknowledged the clause, clarified that the standard GCC definition would apply, and issued a corrigendum.
The three bidders who missed it carried that risk unpriced in their financial bids.
Pre-bid queries are not a formality. Done correctly, they are one of the few tools a contractor has to reduce risk before committing to a price.
What evaluators actually do with pre-bid queries
The NHAI pre-bid process follows a standard sequence: queries are submitted in writing before the pre-bid conference, responses are issued at the conference or within 7 days, and responses that modify the tender become part of the bid document via corrigendum.
Evaluators (typically the Independent Engineer or authority's technical team) read every query before the conference. They categorise them roughly into three buckets:
Genuine technical ambiguities. These get serious consideration. If the NIT specifies material requirements that conflict with the referenced IRC code, or if the payment terms are ambiguous about what constitutes a "milestone" for interim payment, the evaluator knows it needs resolution before bids are opened.
Requests for commercial relief. A query that says "can the bid validity period be reduced from 120 days to 90 days" is noted, usually declined, and signals that the bidder is optimising for convenience rather than understanding the project. These queries are not harmful, but they consume goodwill.
Questions already answered in the document. When a contractor asks something that is clearly covered in the NIT, it signals one of two things: the team didn't read the full document, or the team is fishing for a more favourable interpretation. Neither impression helps at bid evaluation.
What a weak pre-bid query looks like
Here is a real category of weak query, paraphrased from pre-bid meetings:
*"Please clarify the completion period for this project."*
The completion period is stated in the NIT. This query tells the evaluator that the bidder either didn't read it or is hoping for a different answer. It is not a question. It is a request for the evaluator's time.
A stronger version of the same concern:
*"Section 3.2 states the scheduled completion period as 30 months from the Appointed Date. Section 7.1 (Special Conditions) states that PCOD must be achieved within 24 months for the HAM annuity calculation to commence. Please confirm whether the 24-month PCOD obligation applies to all lanes, or to the first set of lanes as defined in Clause 4.3 of the concession agreement."*
The second query is referencing specific sections, identifying a genuine ambiguity between two parts of the document, and asking for a precise clarification. This is worth the evaluator's time to resolve.
Where to find genuine ambiguities
A 400-page NHAI NIT has hundreds of clauses. You are not trying to read all of them in the same depth. You are looking for specific types of conflict.
SCC vs. GCC conflicts. The Special Conditions of Contract modify or override the GCC. The modifications are intentional, but they are sometimes drafted in a way that creates ambiguity when read against the standard clause. Read the SCC against the relevant GCC clauses, not in isolation.
Scope definition and the BOQ. What is listed in the BOQ scope and what is described in the technical specifications sometimes don't match. If a bridge design refers to a specific IRC code for pile foundations and the BOQ doesn't include a separate item for pile testing, ask whether the testing is to be included in the rates or billed separately.
Milestone and payment trigger definitions. HAM projects with PCOD-based annuity payments often leave ambiguity about what physical completion means at the PCOD stage. Is it all four lanes? Is it the main carriageway? Are structures included? This is worth clarifying in writing before you price the construction period float.
Qualification criteria and NHAI Project Book. If the technical qualification criteria reference the NHAI Project Book and the project is in a category that is partially defined, ask for the specific qualifying project list. Evaluators have discretion in assessing whether a prior project qualifies — getting this in writing before bid submission removes the ambiguity.
Force majeure and risk allocation in SCCs. As illustrated above, SCCs sometimes narrow the GCC's risk allocation in ways that have significant financial implications. Read all force majeure, relief event, and delay compensation clauses against the GCC baseline.
How to format and reference clauses
Format matters less than content, but a consistent structure helps evaluators process queries quickly and respond precisely.
A query that is easy to answer gets answered well. A query that requires the evaluator to work out what you're actually asking risks a generic response that doesn't resolve the underlying issue.
A functional format:
Query [number] Reference: [Document section] / [Clause number] Issue: [One or two sentences describing the specific ambiguity or conflict] Question: [The specific clarification you need]
Example:
Query 7 Reference: SCC Clause 12.3 / GCC Clause 43.2 Issue: SCC Clause 12.3 states that running account bills will be processed within 21 days of measurement. GCC Clause 43.2 states the standard period as 28 days. The SCC is silent on whether the 21-day period includes the Independent Engineer's certification step. Question: Please confirm whether the 21-day period in SCC Clause 12.3 runs from measurement or from receipt of the IE's certificate.
This query takes 90 seconds to answer and produces a written record that protects both parties.
How many queries to submit
There is no universal right number. In practice, a well-reviewed 400-page NIT generates between 8 and 20 meaningful queries. Fewer than 5 usually means the team hasn't reviewed the document thoroughly enough. More than 40 usually means the team is asking questions that are already answered.
The quality filter: each query should resolve a specific risk or ambiguity that changes your pricing or your post-bid contractual position. If you can answer it from the document without interpretation, don't submit it as a query. If the answer would change how you price the bid, it belongs in the query list.
One practical approach: identify the top 10 clauses that create financial or timeline risk for the contractor. For each one, check whether the NIT is clear on how the risk is allocated. If it isn't, that's a query.
What happens after the conference
NHAI issues written responses within 7 days of the pre-bid conference. Any response that changes the tender document is formalised as a corrigendum and becomes part of the bid package. These corrigenda supersede the original NIT.
Read every corrigendum before finalising your bid. A corrigendum that revises a milestone definition or changes a payment trigger clause is more commercially significant than the original NIT clause it replaces. It reflects a deliberate position taken after contractor queries.
If NHAI's response to your query is ambiguous, submit a follow-up query through the official channel before the query cut-off date. An oral clarification at the pre-bid conference is not sufficient. Only written responses are binding.
The part most contractors don't do
After the pre-bid conference, update your risk register with the responses received. Each written response that narrows risk (or confirms a risk allocation you had assumed) should be noted, with the corrigendum reference and the original query number.
At the point of contract signing, the responses become part of the contract documents. A contract administrator who knows that SCC Clause 12.3 means the 21-day period runs from IE certification (per Query 7 response) is in a fundamentally different position at the first RA bill dispute from one who didn't ask.
Pre-bid queries are not tender housekeeping. They are the first step in building a paper trail that follows the project through construction, claims, and final account.
CivilBolt's Pre-Bid Query module reads your NIT, identifies clause conflicts and ambiguities across the document, and drafts queries in the structured format evaluators expect. The analysis that takes a contracts manager three days takes about 20 minutes.