SYSTEM // LOADING
BIDQUEST // 2026
GRID // 1280px
BIDQUEST // 2026
Zero manual search • 100% Free
Compare QCBS and least-cost selection, interpret the tender's scoring method, and prepare technical evidence and pricing with a worked example.

The practical difference is how the team should organise its evidence and pricing review. Read the actual thresholds, criteria, formula and award provisions before treating a familiar acronym as a complete evaluation rule.
The Department of Expenditure's 2025 Consultancy Services Manual discusses both methods. This article's worksheet and numbers are original illustrations, not a prescribed model for every service procurement. Official reference: sections 4.2 and 8.5.

Write the sequence on one page: mandatory eligibility, technical evaluation, financial evaluation, combined ranking where applicable, and subsequent award requirements.
Ask which stage uses pass/fail checks and which awards marks. A mandatory condition cannot be treated as optional merely because the proposal can earn a strong score elsewhere.
Record what happens to a proposal below the technical threshold. Then identify whether financial ranking uses submitted price or an evaluated cost that includes specified adjustments or components.
Keep the clause reference beside every assumption. If the formula is absent or inconsistent, raise a clarification before using it to set price.

| Published criterion | Proposed evidence | Reviewer question |
|---|---|---|
| Relevant assignment | Permitted project and performance records | Does the evidence meet the definition? |
| Proposed team | Required qualifications and role plan | Are people genuinely available? |
| Methodology | Assignment-specific delivery approach | Does it answer the buyer's task? |
| Schedule | Milestones, dependencies and responsibilities | Is the programme feasible? |
| Quality management | Verifiable review and control process | Can it be applied during delivery? |
Replace these examples with the actual criteria. Do not award yourself marks for material the tender does not evaluate.

A polished brochure may describe the company well and still answer little of the procurement. Build the narrative around the stated deliverables, evidence and scoring requirements.
If the buyer asks for a risk approach, describe risks specific to the assignment and how the team would manage them. If it asks for a staffing plan, show roles and availability rather than listing every employee in the business.
Have the technical reviewer identify unsupported claims. Credentials, capacity and proposed personnel should be verifiable. Do not present someone as committed to the assignment without an actual arrangement.

When evaluated cost drives selection after technical qualification, the team may feel pressure to cut the quote aggressively. First establish the cost of delivering the compliant offer.
Identify travel, staffing, project management, reporting, support and other required work. Keep tax and financial assumptions consistent with the tender's price format.
Then define the minimum acceptable internal price, subject to management approval. A technically qualified offer that cannot be delivered sustainably is a commercial risk even if its price is competitive.
Do not use expected post-award scope reductions as an unconfirmed way to make the estimate work.
Assume a made-up evaluation assigns 70% to a technical score and 30% to a financial score. For this example only, the financial score is the lowest price divided by the bidder's price, multiplied by 100.
Bidder A has a technical score of 90 and a price of ₹12 lakh. Bidder B has a technical score of 80 and a price of ₹10 lakh. Assume both meet all qualification requirements.
A's financial score is approximately 83.33. Its combined score is approximately 88: 0.70 × 90 plus 0.30 × 83.33. B's financial score is 100 and combined score is 86.
Under that specific invented method, A ranks higher despite its higher price. Under a least-cost comparison using those same prices and no other differences, B would rank lower in cost.
The example demonstrates why the evaluation method matters. It does not establish actual scores, a universal ratio or an award outcome for a real tender.
Use the formula to understand sensitivity, not to invent competitors' scores. You may model a range of technical scores and prices internally, but identify them as assumptions.
The bid team usually cannot know exactly how other offers will be scored. Do not claim a calculated win probability based on a few hypothetical numbers.
Ask instead whether improving a weak, evidenced part of your proposal is worth the preparation effort, and whether the proposed price supports that delivery approach.
Check currency, tax treatment, reimbursable items, lifecycle costs where specified, rounding, ties and the treatment of non-responsive offers. Ask a focused query if the documents are unclear.
For example, “The price schedule includes a reimbursable travel allowance, while the evaluation clause refers to total cost. Please confirm whether that allowance enters the financial comparison.”
The answer belongs in both the price model and proposal review. A clarification is not useful if finance continues using the older assumption.
For QCBS, verify that every scored criterion has a clear response and supporting evidence. For LCS, verify technical qualification and the completeness of the evaluated price.
For both, check mandatory forms, cover separation, authorised signatures where required, and the latest amendments. A strong technical score does not correct a misfiled financial bid.
Retain the evaluation map with the final offer so the team can later understand how it priced and positioned the proposal.
Suppose the proposal promises several workshops, specialist review and detailed reports because those activities address the published criteria. Finance should confirm that those commitments appear in the estimate.
Do not improve a technical response by adding unfunded work casually. The offer must remain deliverable at the submitted price if selected.
Create a short cross-reference: technical commitment, responsible resource, estimated time and cost line. This allows finance to identify where a proposal writer has expanded scope beyond the original plan.
The purpose is not to reduce every technical strength to a spreadsheet. It is to ensure the narrative and price describe the same assignment.
Ask the reviewer to identify the buyer's question, the evidence that answers it and the remaining weakness for every scored criterion.
A polished company description may be useful background but not evidence of a proposed methodology. A staff biography may be impressive but not show that the person is available for the required role.
Rate internal readiness as documented, partial or unsupported. These are review labels, not predicted buyer marks. Use them to focus preparation on missing evidence.
Where a criterion has a stated maximum or substructure, verify that the proposal responds to each relevant element without inventing extra scoring rules.
If the buyer asks for clarification during evaluation, identify exactly what is requested and the applicable response process. Preserve the original submitted proposal.
Have the bid owner review the response for consistency with the offer and the permitted scope. Do not treat a clarification as an unrestricted chance to rewrite price, staff or methodology.
If the requested explanation involves a calculation, show the basis clearly. If it concerns experience, provide authentic evidence relevant to the criterion rather than a new unsupported claim.
Retain the response and acknowledgement with the evaluation record.
For internal planning, hold your technical-score assumption constant and test several prices using the published formula. Then vary the assumed technical score separately.
This identifies which assumptions dominate the model. It does not reveal actual competitor offers or scores.
Label every scenario and make sure the team understands that the result is conditional. A table saying “we win” can mislead management when the inputs were merely guesses.
Use the exercise to ask better questions: is a proposed price reduction sustainable, does a technical weakness need real evidence, and is this assignment worth pursuing under the stated method?
Some price schedules include several cost elements. Read which ones enter the financial comparison and how any stated adjustment is applied.
Check whether the quote includes all required periods, sites and services. A low first-year number can be irrelevant if evaluation covers the full assignment.
Keep the submitted pricing form and the internal cost model separate but reconciled. If a form appears inconsistent with the evaluation description, clarify it before submission.
Do not redesign the price schedule to produce the comparison you prefer.
After official results are available, record what the documents actually show: qualification outcome, scores where disclosed, financial position and stated decision.
Distinguish observed information from your interpretation. If the buyer does not disclose detailed scoring, do not create a precise explanation of every lost mark.
Compare the available result with your internal evidence review. Did you overlook a mandatory form, underestimate a delivery cost or fail to substantiate a criterion?
Use that learning to improve the next bid. Avoid assuming the same strategy will work under a different method or buyer.
For the next opportunity, appoint one person to maintain the evaluation map, one to verify evidence and one to reconcile price. A small team can combine roles while retaining the checks.
Set deadlines for qualification, scored content and commercial approval. Identify which unresolved issue could invalidate participation or change the estimate.
Keep management review focused on the actual decision: readiness, price sustainability and preparation capacity under this tender's rules.
A familiar acronym becomes useful only when translated into concrete work. The map, evidence review and reconciled offer make that translation visible.
Before submission, confirm that the internal comparison uses the published method and clearly labelled assumptions. Remove unsupported competitor scores from any factual management summary. Preserve the formula, inputs and approval so the team can distinguish its planning scenario from the buyer's eventual official evaluation.
No. Use the actual published weighting and formula.
No. Establish the technical qualification requirements before comparing evaluated cost.
The published combination of quality and cost can produce that result. Follow the actual methodology.
Use assumptions only for clearly labelled internal scenarios, not as factual rankings or reliable predictions.
Do not assume so. Keep mandatory qualification separate from scored criteria.
Before approving a service bid, prepare its evaluation map, evidence table and price sensitivity model. Explore BidQuest for discovery, then verify the method in the buyer's current documents.
Department of Expenditure. Accessed 12 Oct 2026.

Learn how to read government tender documents in India: NIT, eligibility, technical specifications, BOQ, EMD, evaluation, corrigenda and submission checklist.
Read the guide
Learn how Indian MSMEs and contractors can find government tenders on CPPP, GeM and state portals, shortlist relevant notices and track corrigenda.
Read the guide
Provisional accounts are acceptable only if the applicable tender requirements permit them on the relevant basis.
Read the guide