procurement evaluation plan
A fair procurement decision begins before a solicitation reaches suppliers. A procurement evaluation plan connects organizational objectives to clear requirements, disclosed criteria, scoring instructions, and an evidence-based recommendation. It gives the procurement team a common reference and helps evaluators apply the same process to every compliant submission.
Key Takeaways
- A procurement evaluation plan establishes fairness by defining criteria and scoring methods before suppliers submit their bids.
- Clear evaluation criteria help every evaluator assess all compliant submissions using the same consistent process.
- The plan translates organizational goals into measurable requirements that guide the entire evaluation from start to finish.
- Including detailed scoring instructions in the evaluation plan supports an evidence-based recommendation for the winning supplier.
- Building the evaluation plan early gives the procurement team a shared reference that reduces confusion and bias during assessments.
Build the framework in stages: define the outcome, separate mandatory requirements from rated criteria, decide how price will be assessed, and document the method before approaching the market. Teams seeking structured learning may consider Procurement Training for Teams, which provides a Canadian-focused public sector procurement curriculum.
What a Procurement Evaluation Plan Is and Why You Need One
A procurement evaluation plan is an internal working document explaining how the organization will assess supplier submissions. It normally identifies the evaluation team, roles, mandatory requirements, rated criteria, weighting approach, price or cost method, scoring scale, conflict-of-interest controls, approval points, and record-keeping expectations. Complete and approve it before issuing the solicitation, so the approach is settled before supplier responses are seen.
Defining the evaluation plan’s role in the procurement lifecycle
The plan sits between procurement planning and contract award. The business owner identifies the service, deliverable, operational need, budget context, and risks. The procurement professional converts those needs into requirements and criteria suppliers can understand and evaluators can apply. After closing, evaluators use the approved framework rather than personal preferences or new considerations. This supports fairness, transparency, consistency, value for money, and public confidence.
The timeline: when to prepare and approve the plan
Prepare the framework while the statement of work, specifications, and procurement strategy are being developed. Confirm that every criterion relates to a genuine requirement and that the planned evidence can be found in a supplier response. Complete internal review and obtain approval required by organizational policy, delegation, funding authority, and applicable legislation before releasing the solicitation. Check local rules, trade agreements, accessibility obligations, privacy requirements, and records policies for the relevant jurisdiction.
How the plan differs from the evaluation methodology, strategy, and report
Define overlapping terms for the project. The procurement strategy covers the market process, contract structure, and sourcing route. The evaluation methodology covers assessment mechanics, including scoring, verification, and price treatment. The evaluation plan brings those decisions together as committee instructions. The evaluation report is prepared after assessment and records the evidence considered, scores, discussions, approvals, and award recommendation. A plan sets the method in advance; a report records how it was applied.
For shared capability, Procurement Training for Teams offers a progressive certification pathway from essentials to procurement expert level, with.
Building the Framework: From Objectives to Defensible Criteria
Connecting procurement objectives, requirements, risks, and evaluation criteria
Begin with the desired contract outcome rather than a list of supplier features. State what the organization must achieve, identify operational and delivery risks, and determine which supplier capabilities address them. Translate each need into a requirement, then decide how the response will be assessed. Requirements may concern service availability, implementation, staffing, security, reporting, sustainability, or continuity. Each criterion needs a clear purpose, evidence source, and connection to the successful supplier’s work.
Mandatory vs. rated requirements: how to decide what belongs in each category
A mandatory requirement is a pass-fail condition. A submission that does not meet it may be considered non-compliant, subject to the solicitation wording and rules. Use mandatory requirements only for genuine necessities, such as a required licence, form, minimum technical capability, or acceptance of essential contract terms. Rated criteria distinguish compliant proposals by awarding points for quality, capacity, approach, experience, or value. Avoid making every preference mandatory: excessive pass-fail screening can reduce comparison and exclude capable suppliers without a sound procurement reason.
Writing clear, measurable, and non-overlapping criteria
Good wording tells suppliers what to address and evaluators what evidence to consider. Criteria should support consistent judgment while allowing an appropriate solution. Keep them separate so the same strength is not rewarded twice. Where useful, specify a page limit, workplan, implementation schedule, sample, reference, or service-level commitment.
| Weak wording | Improved wording | Evidence evaluators can review |
|---|---|---|
| Strong project team | Describe the proposed project manager’s experience delivering comparable public-sector implementations and identify their responsibilities. | Named personnel, relevant project summaries, roles, and availability. |
| Good transition plan | Provide a transition schedule showing activities, accountabilities, dependencies, risks, and service-continuity measures for the first 90 days. | Schedule, milestones, risk controls, and escalation process. |
| Quality reporting | Explain the monthly performance report, including measures, data sources, exception reporting, and corrective-action timelines. | Report sample, measures, reporting frequency, and response process. |
Including price or cost evaluation in the framework
Decide how price will be assessed before release. Define pricing components, contract term, options, assumptions, taxes, travel, implementation costs, and other evaluated amounts. A low price should not receive credit for an item treated as mandatory, and technical quality should not be scored again through a vague value statement. State whether the method uses a formula, comparison, or another disclosed approach, and confirm policy alignment.
Test the framework against sample responses. Ask whether evaluators could identify the same evidence, suppliers could understand the expectation, and each criterion could be defended as contract-relevant. This review can reveal hidden preferences, duplicated criteria, unclear pass-fail wording, or missing costs. Correct them before release.
Assigning Weights and Designing the Scoring Model
Principles for weighting technical criteria and price
Weighting communicates relative importance. Consider which outcomes carry the greatest operational, financial, safety, service, or implementation risk. Criteria tied to those outcomes may deserve more weight than helpful but less significant features. Price should have a meaningful weight, but should not automatically dominate when quality, continuity, accessibility, privacy, or implementation capability determine contract success.
Use a total of 100 points and test the distribution against realistic scenarios. Would a materially stronger technical solution still be recognized if it were not the lowest price? Would an inexpensive submission with serious delivery weaknesses rank too highly? Record the rationale for every weight and disclose criteria, relative weights, and the price method as required by policy and procurement rules.
Choosing a scoring scale and writing descriptive anchors
A scoring scale gives evaluators shared terms. A five-point scale can work for many procurements if each point has a defined meaning. Anchors should describe evidence quality and completeness, not general impressions. A high score might require a complete, credible approach addressing every stated element with relevant evidence; a middle score might describe an acceptable response with minor gaps; a low score might indicate missing, unclear, or unsupported information.
Avoid false precision. Evaluators should record evidence supporting each score, including the response location and material strengths or weaknesses. If subcriteria exist, explain how they contribute to the score. This supports arithmetic, consistency, and rationale checks.
Worked example: weighted-scoring calculation using illustrative numbers
The following hypothetical RFP uses illustrative numbers only. Mandatory compliance has already been checked, and technical quality is compared with evaluated price. Technical weighted points equal the score multiplied by the criterion weight and divided by the maximum score. The price score uses a disclosed comparative formula, such as lowest evaluated price divided by the supplier’s evaluated price, multiplied by available price points.
| Evaluation component | Weight | Supplier A score | Supplier A weighted points | Supplier B score | Supplier B weighted points |
|---|---|---|---|---|---|
| Service delivery approach | 30 | 4 of 5 | 24 | 5 of 5 | 30 |
| Implementation and transition | 20 | 5 of 5 | 20 | 3 of 5 | 12 |
| Team experience and capacity | 20 | 4 of 5 | 16 | 4 of 5 | 16 |
| Evaluated price | 30 | 25 of 30 | 25 | 30 of 30 | 30 |
| Total | 100 | 85 | 88 | ||
Supplier B has the higher total because its price score offsets its weaker transition response. That outcome is acceptable only if weights, anchors, price formula, and assumptions were set before review and disclosed where required. The record should show calculations, evidence, evaluator comments, and approved moderation.
Proportionality for small municipalities and agencies
A smaller organization can use a short set of relevant criteria, a plain scoring scale, and a small committee with assigned roles. The plan should match contract value, risk, complexity, and market conditions. Do not copy a large organization’s template without checking whether each step improves decision quality or only adds administration.
A lean process still needs approval, conflict declarations, scoring instructions, price treatment, evidence notes, and a secure file location. Confirm legislation, trade agreements, council or board authority, and delegation requirements. Proportionality means applying appropriate control, not removing accountability.
Guiding the Evaluation Committee and Managing the Process
Forming the committee: roles, responsibilities, and the chair’s duties
Choose evaluators who understand the need, can assess assigned evidence, and have time to participate. The procurement lead manages the process and confirms compliance with approved instructions. Subject-matter evaluators assess technical responses. A financial or operational representative may review price assumptions or implementation implications. The chair coordinates meetings, keeps discussion within disclosed criteria, confirms decisions, and escalates uncertainty rather than resolving it through preference.
Put responsibilities in the internal plan and briefing materials. The solicitation should explain supplier-facing requirements and the evaluation method, not private deliberations, internal prompts, or administrative instructions.
Conflicts of interest and code of conduct
Before receiving submissions, evaluators should disclose actual, potential, or perceived conflicts and confirm confidentiality and conduct obligations. A conflict may involve a personal relationship, prior business connection, financial interest, or another circumstance affecting confidence in the assessment. Follow policy: options may include removal, restricted access, independent review, or documented approval of another control.
Pre-evaluation calibration: aligning evaluators before scoring
Brief evaluators before scoring. Review objectives, mandatory screening, rated criteria, anchors, price process, conflict declarations, confidentiality, and note-taking. Use a sample response or neutral exercise to discuss how evidence maps to a score. Calibration identifies inconsistent interpretations; it is not agreement on a preferred supplier.
Handling clarifications, consensus scoring, and moderation after submissions arrive
Have evaluators score independently before group discussion, referring to the response and criterion. During consensus, invite evidence, record the rationale, and refer unresolved issues for procurement review. Clarifications must follow the solicitation rules and must not give one supplier an unfair chance to improve its proposal. Record the question, response, authorization, timing, and assessment effect.
| Good process practice | Process risk to avoid |
|---|---|
| Independent scoring followed by evidence-based discussion | Letting the first speaker set the committee’s view |
| Recording criterion-specific reasons and response references | Using general comments such as “good fit” without evidence |
| Routing supplier questions through the procurement lead | Allowing informal evaluator contact with a supplier |
| Documenting approved score changes during moderation | Changing marks privately or without a recorded reason |
Committee readiness checklist
- Confirm each evaluator’s role, availability, and conflict declaration.
- Provide the solicitation, evaluation worksheet, scoring anchors, and confidentiality instructions.
- Explain how mandatory requirements, rated criteria, price, and clarifications will be handled.
- Set deadlines for individual scoring, consensus, moderation, and approval.
- Store notes, worksheets, questions, decisions, and calculations in the authorized procurement record.
These controls keep the plan usable under pressure after closing. A committee that understands its boundaries can make a consistent recommendation while preserving fairness, accountability, and public trust.
Documenting the Plan, Getting Approval, and Preparing for Audit
What must appear in the solicitation vs. what stays internal
The solicitation should give suppliers enough information to understand assessment. Depending on applicable rules, this normally includes mandatory requirements, rated criteria, weights, scoring method, price or cost formula, submission instructions, and eligibility or award conditions. Suppliers should not need private committee notes to understand comparison.
Internal material may include evaluator assignments, briefing notes, conflict declarations, meeting schedules, moderation instructions, approval routing, and secure record locations. Internal guidance may explain application of disclosed criteria, but must not introduce a new factor, hidden preference, or undisclosed threshold after closing. Check legislation, trade agreements, policy, delegation, privacy, and records requirements.
Approval workflow and sign-off steps
Approve before market release. The business owner confirms the outcome and resources. Procurement checks the sourcing process, supplier instructions, evaluation method, pricing, and policy alignment. Finance, legal, information technology, privacy, accessibility, or senior management review may be required according to risk and authority.
Record reviewers, approved version, approval date, and conditions. Version control prevents outdated worksheets. If correction is needed before closing, issue it through the authorized amendment process and preserve both versions.
Linking evaluation criteria to contract management deliverables
Criteria should describe capabilities that matter after award. A transition criterion can become an implementation schedule; reporting can become a monthly deliverable with data fields, review dates, and corrective-action expectations; staffing commitments can become key-personnel provisions, service levels, or change-control requirements.
This supports continuity from selection to contract administration and helps the contract manager identify monitored evidence and escalation points. Do not copy every proposal statement into the agreement. Confirm which commitments are material, measurable, and suitable for the contract.
Building a complete, auditable record
An auditable file should trace the decision from need identification through approval and award. Preserve the business need, strategy, approved criteria, solicitation and amendments, evaluator declarations, worksheets, consensus notes, clarification records, price calculations, approvals, recommendation, award notice, and contract. Use consistent file names, access controls, version dates, and retention practices in the authorized system, not personal email or local drives.
Template prompt: Ask the drafting team to complete this sentence for every criterion: “We are assessing this because the contract requires it; the supplier must provide this evidence; evaluators will apply this scale; and successful performance will be monitored through this deliverable or measure.” If it cannot be completed clearly, revise the criterion before approval.
Frequently Asked Questions
Can you provide an example of a procurement evaluation plan?
A procurement evaluation plan example includes the evaluation team, mandatory requirements, rated criteria, point weightings, price method, scoring scale, conflict-of-interest controls, approvals, and records to retain. For a technology purchase, criteria might cover implementation approach, relevant experience, security, service support, and total cost, with each area linked to evidence suppliers must provide.
What are the 5 P's of procurement?
The five P’s of procurement are purpose, planning, process, people, and performance. Purpose defines the business outcome, planning sets requirements and evaluation criteria, process establishes fair sourcing steps, people assigns roles and controls conflicts, and performance checks whether the contract delivers the expected results.
Can you provide an example of a procurement plan?
A procurement plan example identifies the business need, scope, estimated value, budget, market approach, risks, schedule, contract type, approvals, and evaluation method. A plan for consulting services could specify the required deliverables, procurement timeline, supplier outreach, rated criteria, pricing approach, contract controls, and award authority.
What are the 5 criteria of evaluation?
Five common procurement evaluation criteria are technical quality, supplier experience, project approach, service capacity, and price. Criteria should reflect genuine contract needs, use clear evidence, and avoid rewarding the same strength twice. Mandatory conditions, such as a required licence, are usually assessed separately on a pass or fail basis.
What are the four main types of evaluation?
The four main types of procurement evaluation are compliance evaluation, technical evaluation, financial evaluation, and overall value evaluation. Compliance evaluation checks mandatory requirements, technical evaluation assesses the proposed solution, financial evaluation examines price or cost, and overall value evaluation combines approved results to support the award recommendation.
How should price be evaluated in a procurement evaluation plan?
A procurement evaluation plan should state the price formula, cost elements, weighting, assumptions, and treatment of unusual or incomplete pricing. Common approaches include lowest compliant price, weighted price scoring, total cost of ownership, or best-value assessment. The chosen method should match the procurement objective and be disclosed in the solicitation.