rated bid criteria
Before scoring a proposal, check whether each bid covers the same work. Rated bid criteria help evaluators compare qualities such as an organization’s approach or experience. Those scores are meaningful only when offers have been reviewed on a consistent basis.
Key Takeaways
- Rated bid criteria allow evaluators to score qualities like approach and experience in a structured way.
- Scores are only meaningful when every bid is reviewed against the same consistent standard.
- Evaluators should confirm that all bids cover the same scope of work before assigning any ratings.
- Consistency in evaluation builds fairness and confidence in the procurement process.
This guide explains the difference between pass/fail requirements and scored factors, then shows how to level bids by examining scope, exclusions and assumptions. The examples are hypothetical and intended for learning, not advice for a specific procurement.
What rated bid criteria are (and how they differ from mandatory criteria)
Rated criteria are factors evaluators score to compare how well compliant bids meet a procurement’s stated needs. Mandatory criteria are requirements a bid must meet to proceed. The solicitation documents should explain both types, including the scoring method and how price fits into the evaluation.
A plain-language definition of rated bid criteria
These criteria let an evaluation team assess proposal quality against requirements published in advance. A buyer might assess whether a proposed work plan explains key tasks, identifies dependencies and sets out a practical schedule. Evaluators use the stated scale to record how well each response addresses the requirement, rather than relying on general impressions.
Mandatory (pass/fail) criteria versus rated (scored) criteria
A mandatory requirement is a threshold: a bid either meets it or does not, based on the solicitation’s instructions. A rated factor distinguishes among bids that have passed the mandatory stage. Keeping these roles clear helps prevent evaluators from awarding points for a requirement meant to be pass/fail or treating a scored preference as an unstated condition.
| Evaluation element | How it is assessed | Example |
|---|---|---|
| Mandatory requirement | Pass or fail against the published instruction | Submit a required form by the stated deadline |
| Rated factor | Scored using the published scale | Explain how the proposed schedule addresses project dependencies |
| Price | Evaluated using the method set out in the solicitation | Compare prices on the specified basis and for the defined scope |
Why price matters but is rarely the only factor
Price is a key part of value for money, but a low figure alone does not show whether a proposal meets the requirement or presents a workable delivery plan. Depending on the procurement, evaluation may also consider experience, technical approach, capacity or sustainability. The solicitation should state which factors apply and how each contributes to the result.
Common non-price criteria: experience, approach, capacity, sustainability
Experience criteria can ask for relevant examples; approach criteria can assess the proposed method; and capacity criteria can examine whether the bidder has described the resources needed. Sustainability factors may address environmental or social considerations when relevant to the requirement and clearly defined. Each factor needs a connection to the work, a consistent assessment method and evidence evaluators can identify in the bid.
How weights and scoring scales work in Canadian public procurement
A weight represents a criterion’s relative importance, while a scoring scale describes how evaluators distinguish stronger and weaker responses. Set both before bids are evaluated, and explain the method in the solicitation. The World Bank’s Rated Criteria guidance describes non-price factors carrying 20 to 70 per cent of total evaluation weight in different procurement contexts. That range is not a Canadian rule; the appropriate method depends on the procurement and applicable requirements. For federal procurements, consult the Treasury Board of Canada Secretariat’s Contracting Policy and the relevant solicitation and organizational procedures.
Bid levelling first: getting to a true apples-to-apples comparison before scoring
What bid levelling means and why practitioners insist on it before ranking
Bid levelling is a structured review of what each offer includes, excludes and assumes, so the team can understand scope differences before comparing price or applying scored factors. It is not a way to rewrite a bid or give one bidder an unannounced opportunity to improve its offer. It is a comparison against the published requirement. When evaluators rank proposals before checking scope, a price difference may reflect different assumptions rather than better value.
Comparing exclusions, assumptions, allowances and scope across bids
Start with the requirement and review each bid against the same list. Record exclusions, dependencies, allowances, quantities, service periods and stated assumptions. Note where a bidder has included an item, omitted it or described it differently. Keep the original bid language and identify questions for the procurement lead to consider under the solicitation’s rules. This record makes scope gaps visible without treating an evaluator’s guess as a bidder commitment.
Why the lowest headline price can be misleading after levelling
A lower quoted amount may leave out work another bidder has priced or depend on an assumption that does not match the requested scope. That does not automatically make the bid non-compliant or establish what the bidder would charge for omitted work. The team should understand the difference and follow the stated evaluation and clarification process before drawing conclusions. A consistent scope review supports a defensible comparison.
Worked example: two bids, one fair comparison
Suppose a hypothetical municipality seeks a service package that includes setup and staff orientation. Bid A lists a lower total but excludes orientation. Bid B includes both activities in its price. The team records the exclusion and inclusion against the same requirement, then checks the solicitation for how such differences must be handled. It does not invent a cost for Bid A’s excluded work or adjust the offer without authority. Evaluators apply the stated scoring approach only after resolving the comparison in accordance with the published process.
An Excel bid-levelling matrix you can adapt
To create a working matrix in Excel, use one row for each requirement or scope item and columns for the requirement reference, Bid A response, Bid B response, inclusion status, exclusion or assumption, evidence location, clarification status and evaluator note. Add a separate field for any price difference, but do not calculate an adjusted total unless the solicitation and authorized process support that treatment. This layout can be copied into a workbook and adapted to your organization’s procedures. It is a practical starting structure, not a downloadable file.
Running a fair and transparent evaluation process
A fair evaluation follows the process set out in the solicitation and applies it consistently to every bid. Clear roles, advance preparation and careful records help the team explain its decision. In Canadian federal procurement, the Treasury Board of Canada Secretariat’s Contracting Policy sets out principles and requirements for contracting. Teams should also consult the rules, trade agreements and procedures that apply to their procurement, along with their organization’s policies. This section is educational, not advice for a specific process.
The evaluation committee’s roles and responsibilities
Before evaluation begins, confirm who is responsible for each task. The procurement lead can coordinate the process, answer procedural questions and maintain records. Subject-matter evaluators can assess responses against published requirements, while an authorized decision-maker carries out the approval role established by the organization. The committee assesses submitted evidence; it should not fill gaps with assumptions or introduce new preferences. When an issue is unclear, record it and refer it through the established process rather than resolving it informally.
Conflict of interest declarations and confidentiality habits
Ask evaluators to declare actual, potential or perceived conflicts before they receive or review bid information, following the organization’s process. A connection does not automatically determine the outcome; it should be disclosed so the appropriate person can assess and document next steps. Keep bids, scoring notes and committee discussions within authorized channels. Evaluators should not discuss submissions with people outside the process or use bid information for another purpose. These practices protect bidder confidentiality and help the committee work with care.
Setting a consistent scoring approach before bids open
Prepare the evaluation method before submissions arrive. Review the criteria, weights, scoring scale and evidence needed for each assessment. If the solicitation describes performance levels, evaluators should understand what evidence supports each level and apply that description consistently. A short practice exercise using a fictional response can expose unclear wording or differing interpretations before real bids are assessed. Changes to the published method must be handled through the applicable procurement process, not made informally during evaluation.
Common reasons bids are disqualified at the mandatory stage
A bid may fail a mandatory requirement when it does not meet a condition stated as pass/fail in the solicitation. Examples could include a missing required submission, an incomplete mandatory form or a response that does not meet a clearly stated technical requirement. The evaluator should identify the exact requirement and relevant evidence in the bid, then follow the solicitation’s rules for review or clarification. Check the stated requirement and the organization’s process before treating an omission as grounds for rejection.
Handling no-bid or single-bid scenarios
If no bids arrive, or only one bid is received, the outcome itself does not prove a problem. Record what occurred and follow the organization’s procedures for deciding next steps. The procurement lead may need to review the schedule, outreach, requirement wording and applicable approvals, while keeping any later action within the procurement rules. For a single submission, assess it against the published requirements rather than changing the standard because there are no competing offers. Document the basis for any decision to proceed, pause or take another permitted step.
Documentation and the audit trail: recording why you scored as you did
Notes should show the path from requirement to evidence to assessment. Record the criterion, relevant part of the bid, evaluator’s reasoning and any agreed committee outcome. If evaluators initially differ, preserve individual assessments where required and explain how the final result was reached under the established process. Clear records support internal review and help answer later questions about the decision.
Use this preparation checklist before evaluation starts:
- Confirm committee roles, access permissions and approval responsibilities.
- Complete conflict declarations and agree on confidentiality practices.
- Review the published criteria, weights, scoring scale and mandatory requirements.
- Confirm how questions, clarifications and disagreements will be recorded and handled.
- Set up a consistent record for evidence, evaluator notes and decisions.
Common mistakes in bid evaluation (and how thoughtful preparation prevents them)
Evaluation mistakes often begin when a team moves too quickly from receiving bids to ranking them. A consistent review takes time, but preparation can make the work clearer and more manageable. Treat differences as items to examine against the solicitation, not as invitations to fill gaps with assumptions or change the evaluation method.
Scoring bids before levelling them
Applying scores before checking whether offers cover comparable work can distort the evaluation. A response may appear stronger or less costly because it addresses a different scope. Before assigning points, confirm that evaluators understand the relevant differences and have followed the solicitation’s process. If a difference could affect an assessment, raise it through the established review process rather than resolving it informally.
Letting unexamined exclusions and assumptions drive the price swing
An exclusion or assumption can make a quoted price look more favourable without showing the full cost of meeting the requirement. Record the bidder’s wording and compare it with the stated scope. Do not invent a price for omitted work or treat an assumption as a commitment. When the evaluation method does not explain how to address a difference, refer the question to the procurement lead and follow the organization’s authorized process.
Inconsistent interpretation of criteria between evaluators
Evaluators may read the same response differently if a criterion or scoring scale is open to interpretation. Before scoring, agree on what evidence relates to each published criterion and how the scale will be applied. During review, assess each bid against that shared understanding. If an evaluator identifies ambiguity, document it and use the established process to address it consistently, rather than creating a new interpretation for one submission.
Weak records that cannot explain the award decision
A score without a reason is difficult to review later. Keep concise notes connecting the published criterion to specific evidence in the bid and the evaluator’s assessment. Record material questions and how they were handled under the process. These records help explain the decision and support accountability without relying on memory.
Your next step in building evaluation confidence
A careful evaluation depends on using the published method, making comparisons on a sound basis and keeping records that explain the team’s reasoning. The following checklist can help a team identify a sensible next step without replacing its procurement procedures.
Quick recap: level first, then score
Before applying rated bid criteria, confirm that evaluators share an understanding of each offer’s scope and any material differences. Then use the stated criteria and scoring method, and keep a record of the evidence supporting each assessment. If an issue falls outside the documented process, pause and seek direction through the appropriate organizational channel.
Where to find official Canadian guidance
Start with the procurement policy and procedures that apply to your organization and the specific process. For federal contracting, consult the Treasury Board of Canada Secretariat’s Contracting Policy and relevant federal procurement resources. Depending on the procurement, applicable trade agreements and provincial, territorial, municipal or local requirements may also matter. Check current official government publications rather than relying on a summary or an older template.
Learning options for public procurement professionals
To build foundational knowledge, choose a learning goal such as evaluation planning, bid analysis or contract management, then review the course outline against that goal. The Procurement School offers training programs for people developing public procurement knowledge. Explore the published program information to decide whether a course fits your learning needs.
Next-step checklist: Review your organization’s procedures; identify one evaluation skill to practise; and consult the applicable official guidance before a live procurement.
Frequently Asked Questions
What are rated bid criteria and how do they differ from mandatory criteria?
Rated bid criteria are factors evaluators score to compare how well compliant bids meet a procurement’s stated needs, while mandatory criteria are pass/fail requirements a bid must meet to proceed. Mandatory requirements act as thresholds, and rated factors distinguish among bids that have already passed that stage.
How do I set weights for non-price criteria in a bid evaluation?
Weights represent each criterion’s relative importance and should be set before bids are evaluated and explained in the solicitation documents. The World Bank’s Rated Criteria guidance describes non-price factors carrying 20 to 70 per cent of total weight in different contexts, but the right approach depends on the procurement and applicable requirements.
What is bid levelling and why does it matter before ranking bids?
Bid levelling is a structured review of what each offer includes, excludes and assumes, so evaluators understand scope differences before comparing prices or applying scored factors. Without this step, a price difference may reflect different assumptions rather than better value, making rankings hard to defend.
Why can the lowest headline price be misleading in a bid comparison?
The lowest quoted amount may leave out work another bidder has priced or rely on assumptions that do not match the requested scope. Evaluators should record the difference, follow the stated evaluation and clarification process, and avoid inventing costs for excluded work before drawing conclusions.
What non-price criteria are commonly used to evaluate bids?
Common non-price criteria include experience, technical approach, capacity and sustainability. Experience criteria ask for relevant examples, approach criteria assess the proposed method, capacity criteria examine described resources, and sustainability factors address environmental or social considerations when relevant and clearly defined.
How can I make my bid evaluation fair and transparent?
Publish the rated criteria, weights and scoring method in the solicitation before bids are received, then apply them consistently to every compliant offer. Level bids on scope first, keep the original bid language in your records, and route any clarification questions through the procurement lead under the solicitation’s rules.
What are common mistakes evaluators make when scoring bids?
Frequent mistakes include awarding points for a requirement meant to be pass/fail, ranking proposals before checking scope differences, and treating a scored preference as an unstated condition. Evaluators should also avoid relying on general impressions instead of the published scoring scale and stated requirements.