proposal evaluation criteria
Clear proposal evaluation criteria connect a public-sector team’s stated need to the evidence suppliers provide. They give evaluators a shared basis for comparing responses and explaining a decision. The work begins before the RFP is issued: define what the procurement must achieve, then decide what evidence will show whether a proposal meets that need.
Key Takeaways
- Evaluation criteria act as the bridge between a project’s stated objectives and the evidence suppliers must present in their proposals.
- Defining criteria during the planning stage gives evaluators a shared reference point before any responses arrive, which keeps the process fair and focused.
- A consistent scoring approach allows evaluators to compare proposals objectively and to explain the final award decision with confidence.
- Real examples and a practical template help teams, especially those new to RFPs, write criteria that are clear, measurable and defensible.
- Thoughtful criteria work done before the RFP is issued saves time later and strengthens supplier trust in the procurement process.
In an RFP, requirements describe what a supplier must meet or provide. Evaluation criteria explain how the team will assess proposals against the stated need. Some requirements are pass or fail; rated criteria are scored using a method disclosed in the solicitation. Contract terms set out obligations that apply if an agreement is awarded.
What proposal evaluation criteria do and how they differ from requirements
Start with the procurement need and the RFP requirements
Begin with the service, outcome or capability the organization needs. Translate that need into RFP requirements and requests for evidence. If a team needs a service to start by a specified date, it could ask suppliers to describe their proposed start-up plans and identify the resources needed. The criterion then assesses the plan’s quality and feasibility, rather than relying on a general impression of the supplier.
Separate mandatory requirements, rated criteria and contract terms
These parts of a solicitation serve different purposes. A mandatory requirement is assessed on a pass-or-fail basis. A rated criterion is assessed using the published scoring method. Contract terms describe obligations that apply to the successful supplier. Keeping the distinctions clear helps suppliers understand what they must meet, what will be scored and what they would agree to if selected.
| RFP element | Purpose | Illustrative example |
|---|---|---|
| Mandatory requirement | Checks whether a stated condition is met | Confirm that the proposal includes a completed pricing form |
| Rated criterion | Assesses the strength of a response against a stated measure | Assess whether the work plan addresses each required project stage |
| Contract term | Sets an obligation for the resulting agreement | Describe the reporting obligations during the contract |
Choose criteria that assess relevant evidence, not general impressions
Each scored item should connect to the procurement need and the evidence requested in the RFP. Avoid broad labels such as “overall quality” unless the solicitation explains what quality means and how evaluators will assess it. A criterion should help evaluators compare like with like, using information suppliers were asked to provide. Requirements and processes can vary among Canadian public-sector organizations, so confirm applicable policy and obligations with the relevant organization before preparing a solicitation.
Build criteria that are clear, relevant and ready to publish
Select evaluation areas that fit the procurement
Choose areas based on the work and its risks, not on a standard list. Depending on the need, an RFP might assess technical approach, implementation, relevant experience, team qualifications, service and support, security or compliance, references, and price. A small, well-defined purchase may not need every area. Include a criterion only when it helps distinguish proposals in a way that matters to the stated requirement.
Write observable measures and request matching evidence
Move from need to measure, then specify the evidence suppliers should submit. For an implementation need, a criterion could assess whether the proposed schedule identifies key stages, dependencies and responsibilities. Request a schedule showing those details so evaluators can assess the same features in each response. This makes technical proposal evaluation criteria easier to apply and helps suppliers understand how to answer.
Set weights and scoring anchors before releasing the RFP
Set the relative weight of each scored area and define the scoring anchors before publication. An anchor describes what different levels of evidence mean under the chosen scoring scale. Explain the evaluation method and any weighting in the solicitation so suppliers know how proposals will be assessed. Weights should reflect the procurement’s priorities, and the method should follow the organization’s process. No single balance of technical and price assessment suits every procurement.
Check the evaluation plan before publication
Review the draft against the need, the requested evidence and the organization’s approval process. This can catch criteria that are vague, overlapping or difficult to assess consistently. A clear plan supports a fair comparison and helps the team explain its approach.
- Does each criterion relate to a stated procurement need?
- Can suppliers identify the evidence they should provide?
- Are measures and scoring anchors clear enough for consistent assessment?
- Are the weights and evaluation method stated in the RFP?
- Does the plan align with organizational policy and required approvals?
Plan the evaluation team and a consistent review process
Assign roles, gather stakeholder input and manage conflicts
Choose evaluators for their knowledge of the procurement need, then agree on each person’s role before submissions arrive. A technical lead might assess the proposed approach, while a finance or contract specialist reviews parts within their expertise. Stakeholders can help identify operational needs, but evaluation should follow the published criteria rather than personal preferences or supplier relationships.
Ask evaluators to disclose actual, potential or perceived conflicts of interest through the organization’s process. Confirm who will handle questions, protect confidential submissions and maintain the evaluation record. Check organizational policies and applicable official guidance for specific requirements; processes can differ among Canadian public-sector organizations.
Prepare for submission receipt and compliance screening
Plan the review schedule around evaluator availability and expected volume. Assign someone to coordinate secure access to submissions, track receipt and manage version control. Before scoring, identify who will check the stated mandatory requirements and how any issue will be handled under the solicitation and organizational process.
A shared workflow helps the team apply the same steps to each response:
- Confirm evaluator roles, conflict disclosures, confidentiality expectations and access arrangements.
- Receive and organize submissions using the established process.
- Screen against the stated pass-or-fail requirements and record the outcome.
- Have evaluators independently assess eligible proposals against the published rated criteria.
- Discuss differences, reach consensus using the stated method and record the reasons.
- Prepare an award recommendation based on the documented evaluation results.
Use independent scoring before evaluator discussion
Before meeting as a group, give evaluators the same instructions, scoring anchors and review materials. Independent assessment lets each person form a view from the supplier’s evidence before group discussion can shape individual opinions. Ask evaluators to note the proposal section or specific information that supports each score, including gaps against the published measure.
Allow enough review time for the complexity of the submissions, and avoid assigning more material than evaluators can assess carefully. A short calibration exercise using a sample response can help the team interpret scoring anchors consistently. It should prepare evaluators to apply the published method, not change criteria or introduce new expectations.
Reach and document consensus consistently
During consensus, compare the evidence and reasons behind individual assessments. Where scores differ, ask which part of the response supports each view and how that information meets the criterion.
The evaluation record should make the reasoning understandable to someone who did not take part in the discussion. It gives the award recommendation a traceable basis in the solicitation, submitted evidence and documented assessment.
Compare technical proposals and price with a worked scoring example
Assess technical submissions against the published evidence requests
Review technical submissions against the evidence the RFP requested, not an evaluator’s preferred approach or information that was never solicited. For each rated criterion, identify what the supplier proposed, how it addresses the stated measure and any relevant limitation. Comments are clearer when they point to specific evidence, such as a described project stage, staffing plan or support arrangement.
Keep technical review distinct from price review when the published method calls for separate assessments. This helps evaluators consider each part on its stated basis and reduces the risk that a price impression influences an earlier technical judgement.
Review pricing using the stated method and comparable information
Use the pricing method described in the solicitation. Check that required fields are complete and proposals are compared on the same stated basis, such as the requested period, quantities or cost components. Follow the organization’s process for clarifying omissions or addressing arithmetic discrepancies. Do not create a new adjustment, assumption or scoring approach during evaluation.
Price evaluation should reflect the information requested and the published weighting. A lower price alone does not establish the best overall result when the solicitation also assesses technical factors. The team’s record should show how the stated method was applied to the submitted pricing.
Illustrative RFP scoring example: record scores and reasons
The following hypothetical example shows how a team might document weighted results. The criteria, weights and scores are illustrative only; tailor them to the procurement, organizational policy and method published in the solicitation. Assume the RFP assigns a score from zero to five for each rated area, then multiplies each score by its weight. In this example, a score of four means the response addresses the requested elements with clear supporting detail.
| Published criterion | Weight | Supplier A consensus score | Weighted result | Evidence-based reason |
|---|---|---|---|---|
| Technical approach | Describes each requested project stage and identifies responsibilities; the response gives limited detail on managing one stated dependency. | |||
| Implementation plan | Provides a schedule and key milestones, but does not explain how the proposed team will address the requested hand-off. | |||
| Price | Required pricing fields are complete and align with the stated comparison basis. |
An evaluator comment could read: “The schedule identifies the requested milestones, but the response does not assign responsibility for the hand-off described in the criterion.” Evaluators would discuss the cited evidence and agree on a consensus score using the published anchors. Another procurement may use a different scale or calculation, so do not treat this example as a standard method.
Turn consensus results into a clear selection statement
When scores are settled, connect the recommendation to the published criteria and documented results. Identify the evaluated proposal, summarize the evidence supporting the outcome and explain how the stated price method was applied. The selection statement should match the evaluation record, including any required approvals under organizational policy.
A clear record lets the organization explain its reasoning without relying on recollection. It shows how the team moved from the solicitation’s published method to its recommendation.
Use an evaluation matrix template and keep a complete award record
A spreadsheet can help organize the evaluation, but it does not replace the RFP, formal evaluation plan or organizational procedures. Treat a proposal evaluation criteria template as a working tool: confirm its fields match the method published in the solicitation, then adapt it to the procurement and required approvals.
Set up spreadsheet-ready fields for each criterion and evaluator
Use one row for each criterion and enough fields to trace the assessment from requested evidence to the final record. Add evaluator-level fields when each person scores independently.
| Field | What to record |
|---|---|
| Criterion and type | Published criterion name and whether it is mandatory, rated or price-related |
| Weight and scoring anchors | Published weight and the applicable descriptions for each score level |
| Evidence requested | Information the RFP asked suppliers to provide |
| Evaluator and individual score | Evaluator name or identifier and their score |
| Evidence or comment | Proposal reference and a concise reason for the assessment |
| Consensus score and approval | Agreed result, rationale and required approval record |
| Record reference | Location or identifier for supporting evaluation documents |
Record scores, evidence, consensus and approval
For each score, note where supporting information appears in the submission and how it relates to the published measure. Preserve individual assessments, consensus rationale and approvals according to your organization’s process. Limit access to confidential submissions and evaluation records to authorized people.
Check the evaluation record before making a recommendation
Before submitting a recommendation, confirm that the record is complete: mandatory screening results are recorded; each score has an evidence-based comment; consensus and price calculations follow the stated method; conflicts and confidentiality steps are documented; and required approvals are present. Check that the recommendation agrees with the evaluation results and supporting records can be located.
For an RFP, include criteria that assess relevant technical evidence and price using the disclosed method. A requirement states what must be met or provided; a criterion explains how a response will be assessed. Make measures clear by naming the evidence and features evaluators will consider. Set technical and price weights to reflect the procurement’s needs, publish the method and follow organizational policy. Teams adapting an rfp evaluation criteria template excel should verify that formulas and fields match the approved process.
For a specific procurement, consult your organization’s policies and applicable official guidance. To continue building practical knowledge, explore The Procurement School’s training programs and review the course outlines.
Frequently Asked Questions
What are the six criteria of evaluation in an RFP?
There is no universal set of six proposal evaluation criteria for every RFP. Common areas include technical approach, implementation plan, relevant experience, team qualifications, service and support, and price. Choose criteria that match the procurement need, explain how each will be scored, and request evidence suppliers can provide.
What are five things all proposals should include?
A proposal should include the information and evidence requested in the RFP, which may cover the supplier’s approach, work plan, team qualifications, relevant experience and pricing. The required contents vary by procurement. A clear solicitation tells suppliers what to submit and how the evaluation team will assess their responses.
What are some examples of evaluation criteria for an RFP?
RFP evaluation criteria can assess a proposed technical approach, project schedule, implementation plan, team qualifications, relevant experience, service and support, security, compliance or price. Each criterion should relate to a stated procurement need. The RFP should also identify the evidence suppliers must provide and the scoring method evaluators will use.
What are some examples of proposal evaluation criteria?
Proposal evaluation criteria include measures such as whether a work plan addresses each required project stage or whether a schedule identifies key milestones, dependencies and responsibilities. For a service procurement, criteria might assess support arrangements or relevant experience. Observable measures help evaluators compare the same evidence across proposals.
What are the five basic types of evaluation?
For proposal evaluation, five common areas are technical approach, implementation, experience, team qualifications and price. These are possible evaluation areas, not a fixed universal framework. Public-sector teams should select areas that reflect the procurement’s needs, disclose the scoring method in the RFP, and follow their organization’s policies.