How to Read and Respond to a BoQ on Etimad Tenders
The bill of quantities (BoQ) is the financial backbone of an Etimad tender. It sets out every deliverable, quantity, and unit of measurement the government expects you to price — and it is ruthlessly exact. A supplier who misreads a single unit or misses a line item may still win the technical evaluation, only to discover mid-contract that the financial model is fatally broken.
This guide explains how to read a BoQ correctly, how to use it during technical proposal drafting, and the most expensive mistakes to avoid.
Why the BoQ matters beyond the financial envelope
Most suppliers treat the BoQ as a finance team problem. That is the first mistake. The BoQ is also the most precise statement of scope in the entire tender package — more precise than the narrative sections of the booklet.
When the technical proposal describes your methodology, the BoQ is the document that tests whether your plan is coherent. If you propose 10 site visits but the BoQ has a unit rate for 30 visits, one of them is wrong — and the committee will notice.
The anatomy of an Etimad BoQ
Etimad BoQs follow a fairly consistent structure, though the exact format varies by ministry and sector.
| Column | What it contains | Your action |
|---|---|---|
| Item number | Sequential reference (e.g., 3.2.1) | Cross-reference to the booklet clause |
| Description | Full scope of the deliverable | Flag ambiguities for a clarification question |
| Unit | Measurement basis (each, m², day, lot) | Confirm your understanding is literal |
| Quantity | Government's estimated volume | Validate against the narrative scope |
| Unit rate | Your bid price per unit | Price carefully — not globally |
| Total | Unit rate × Quantity | Calculated; verify the formula is correct |
Step 1: Map every BoQ line to the booklet scope
Before you price a single line, build a cross-reference table. For every BoQ item, find its corresponding clause in the booklet's technical scope. This does three things:
- Reveals BoQ items with no matching booklet clause — possible scope additions you missed.
- Reveals booklet requirements with no BoQ line — deliverables the government may expect but forgot to quantify.
- Forces alignment between your technical proposal and your financial bid.
The second category is the most dangerous. If the booklet requires "monthly progress reports" but the BoQ has no line for them, you still have to deliver them. Either the cost is absorbed into another line or it eats your overhead.
Items in BoQ but not narrative
- — Likely a standardized clause from a template — read it carefully regardless.
- — May carry hidden volume risk if quantities are estimates only.
- — Technical proposal must address it even if the booklet narrative doesn't highlight it.
Items in narrative but not BoQ
- — Deliverable is expected but unpriced — cost must be absorbed somewhere.
- — Common for overhead items: PM meetings, reports, document management.
- — Flag in technical proposal that you will deliver this — don't ignore it.
Step 2: Validate every quantity estimate
Etimad BoQs state quantities as estimates. The contract language typically allows actual quantities to vary within a tolerance (often ±20–25%). If your cost model is linear, that variance is manageable. If you have high fixed costs embedded in unit rates, overruns will hurt you.
| Quantity risk | How to spot it | How to handle it |
|---|---|---|
| Volume too low for fixed setup cost | Your cost per unit rises sharply below the BoQ quantity | Price a mobilization/setup line separately |
| Volume too high for your capacity | Scaling to 2× the BoQ quantity would strain resources | State delivery assumptions in the technical proposal |
| Unit is ambiguous (m² vs. m³) | Two interpretations yield a 10× price difference | Submit a clarification question before the deadline |
| Phased delivery not reflected | All quantity in one line but delivery spans two years | Note your unit-rate assumptions explicitly |
Step 3: Price each line — not the total
The most common BoQ mistake is working backwards from a target total rather than pricing each line on its own merits. Spreading margin or discount unevenly across lines creates problems:
- Front-loading (high unit rates on early deliverables) can trigger an unbalanced-bid challenge from the evaluation committee.
- Back-loading (low rates on early items) means you are underfunded during the heaviest delivery period.
- Concentrating margin in low-volume lines creates volatility when volumes vary at contract.
Price each line to recover its true direct cost plus a proportional share of overhead and margin. Then test the overall total for competitiveness.
Higher-risk unit types require more validation before you lock in a rate.
Step 4: Use the BoQ to stress-test your technical proposal
Run this consistency check before you finalize either envelope:
- Every phase in your methodology corresponds to at least one BoQ line — or is explained as overhead.
- Team size in the technical proposal is consistent with person-day quantities in the BoQ.
- Site visits, workshops, training sessions, and reports in the narrative match the quantities in the BoQ.
- Your Gantt timeline delivers all BoQ quantities within the contract period.
- Optional items in the BoQ (priced separately) are reflected in your technical proposal as optional scope.
Common BoQ mistakes that cost suppliers the most
| Mistake | Consequence | Prevention |
|---|---|---|
| Leaving a line blank | Automatic disqualification in most Etimad tenders | Use a checklist — every line must have a rate |
| Unit misread (e.g., day vs. week) | Contract revenue 5× lower than expected | Read units aloud; confirm with the team before pricing |
| Ignoring provisional / contingency sums | Delivery obligation with no financial cover | Price them; note any assumptions in your technical proposal |
| Using last year's unit rates without inflation adjustment | Margin erosion on multi-year contracts | Apply an escalation factor for contracts over 12 months |
| Not checking the BoQ formula | Total column has a spreadsheet error from the government | Recalculate every total; note discrepancies in your bid |
What to do when the BoQ has errors
It is not uncommon for a government-issued BoQ to contain formula errors, mismatched units, or ambiguous descriptions. The correct response is a formal clarification question submitted through Etimad before the deadline — not a unilateral assumption embedded in your bid.
State the issue clearly: "Item 4.3.2 lists the unit as 'm²' but the description refers to a linear installation. Please confirm the correct unit of measurement."
If the clarification window has closed, document your assumption explicitly in your bid cover letter and in the relevant section of your technical proposal. An undocumented assumption that turns out to be wrong is a dispute; a documented one is a negotiation.
The BoQ is where good bids become profitable contracts or loss-making obligations. The suppliers who treat it as a secondary finance document consistently underperform those who make it the starting point of their entire bid analysis.