Vendor Price Comparison & Selection Matrix | Supplier Evaluation & Award Form

1. Procurement Project Overview & Intake

This section captures the context of the procurement so that every vendor is measured against the same baseline. Complete it before reviewing any quotations. Fields marked as mandatory are essential for a valid, auditable comparison.

Procurement/project reference number

Project or requirement title

Requesting department, business unit or cost centre

Requestor name and job title

Requestor email address

Requestor phone number

Date this comparison exercise commenced

Decision deadline (date by which a vendor must be selected)

Required delivery, installation or go-live date and time

Provide the justification for single or sole source award and confirm any required approvals:

Describe the reverse auction platform, rules and duration used:

Approved budget ceiling for this requirement

Estimated total spend (before quotes received)

Is this a repeat purchase of a previously sourced item or service?

Yes

Provide details of the previous purchase (vendor, price paid, date, and any performance issues):

This is a first-time purchase — a full market scan has been completed

Is this requirement time-critical?

Yes

Explain the critical deadline and the operational impact of any delay:

Does this purchase require legal, regulatory or internal policy review before award?

Yes

2. Requirements, Specification & Evaluation Criteria Definition

A fair comparison is only possible when every vendor is scored against the same clearly defined requirement. Separate mandatory (must-have) criteria from desirable (nice-to-have) criteria before opening the quotations.

Business need and problem statement — what outcome must this purchase deliver?

Detailed technical or functional specification

List the specific certifications or standards required:

State the minimum annual capacity or volume required:

Describe the accessibility standards that must be met:

Desirable (nice-to-have) features or benefits

Which elements of the specification may be varied, and what are the non-negotiable elements?

Define the outcomes and success measures vendors must achieve:

Estimated annual quantity or volume required

Unit of measure for pricing

Are samples, trials, demonstrations or a proof-of-concept required before award?

Yes

Describe the trial scope, duration and the pass/fail criteria used to assess it:

Must vendors hold specific certifications, licences or accreditations to be eligible?

Yes

List each required certification, licence or accreditation and its validity requirement:

Are there minimum insurance or liability cover requirements?

Yes

Specify the types and levels of cover required:

Rank the following evaluation dimensions in order of importance for this purchase (most important first).


	Price/total cost
	Quality and reliability
	Delivery speed and lead time
	Technical fit to specification
	After-sales support and service levels
	Vendor experience and references
	Risk and financial stability
	Sustainability and ethics

Upload the formal specification or scope of work document

Choose a file or drop it here

Upload drawings, schematics or supporting technical documents

Choose a file or drop it here

I confirm the specification has been reviewed and approved by the technical owner before quotations were requested

3. Vendor Identification & Bidder Register

Record who was invited and who responded. A competitive comparison requires a sufficiently broad and appropriate vendor pool; document any vendors that declined or were excluded and the reason why.

Number of vendors invited to quote or tender

Number of quotations or bids received

Number of quotations excluded as non-compliant or incomplete

Vendor register — all invited and responding vendors

	Vendor Name	Contact Person	Email	Country or Region	Quote Reference	Date Received	Complete Submission
	A	B	C	D	E	F	G
1
2
3
4
5
6
7
8
9
10

Primary vendor under evaluation (Vendor A) — legal entity name

Vendor A — registration or company number

Vendor A — primary contact person and job title

Vendor A — contact email and telephone

Vendor A — website

Vendor A — company background, years in business and core capabilities

Vendor A — number of employees

Vendor A — annual revenue in the latest financial year

Has every vendor submitted all required documentation (quote, terms, certifications, financials)?

Yes

List which documents are outstanding, from which vendor, and the chase-up action taken:

Was any vendor excluded from the comparison?

Yes

Name the excluded vendor(s) and provide the documented reason for exclusion:

Upload the vendor quotations received

Choose a file or drop it here

Upload vendor financial statements or credit reports

Choose a file or drop it here

Upload an image of the quoted product, sample or prototype (if applicable)

Choose a file or drop it here

4. Price Comparison — Line-by-Line Cost Breakdown

Enter the quoted prices exactly as submitted. Line totals are calculated automatically from quantity, unit price and discount so that all vendors are compared on a like-for-like basis. Do not include costs that are not part of the vendor's written quotation.

Quoted price breakdown (per vendor)

	Item or Service Description	Unit	Quantity	Unit Price	Discount %	Line Total
	A	B	C	D	E	F
1	Industrial sensor module (high accuracy)	Each	120	$84.50	5	$9,633.00
2	Calibration and commissioning service	Day	4	$650.00	0	$2,600.00
3	Extended warranty (3 years)	Item	1	$1,800.00	10	$1,620.00
4	Operator training (per session)	Session	2	$480.00	0	$960.00
5						$0.00
6						$0.00
7						$0.00
8						$0.00
9						$0.00
10						$0.00

Sub-total of all quoted lines (before tax and additional charges)

Applicable tax rate (percent)

Shipping, freight or delivery charges

Installation, set-up or configuration charges

Total quoted price (all inclusive)

Currency in which the quotation was submitted

Was a currency conversion applied to make the quotations comparable?

Yes

Record the conversion rate used, its source and the date it was applied:

Quotation validity period

Payment terms (number of days)

List the milestones and the percentage payable at each stage:

State the retention percentage held until final acceptance:

Are volume-based, early-payment or multi-year discounts available?

Yes

Describe the discount structure, thresholds and how it is applied:

Is the quoted price fixed for the full contract term?

Yes

Describe the price adjustment or indexation mechanism, its cap and its review frequency:

Does the quotation include any optional or provisional sums?

Yes

List each optional or provisional sum, its value and the trigger for incurring it:

Describe any other excluded costs and estimate their value:

5. Total Cost of Ownership (TCO) & Hidden Cost Analysis

The lowest purchase price is rarely the lowest cost. Capture the full lifecycle cost of each vendor over the expected contract period so that the comparison reflects what the organisation will actually pay.

Total cost of ownership comparison across vendors

	Cost Component	Vendor A Cost	Vendor B Cost	Vendor C Cost	Expected Life (Years)	Assumptions and Notes
	A	B	C	D	E	F
1	Purchase price (all inclusive)	$14,813.00	$13,950.00	$16,400.00	5	As quoted, excluding tax
2	Installation and commissioning	$2,600.00	$3,100.00	$2,250.00	5	One-off cost at deployment
3	Annual maintenance and support	$1,450.00	$1,180.00	$1,900.00	5	Recurring annual fee
4	Consumables and spare parts (per year)	$620.00	$740.00	$510.00	5	Estimated from usage forecast
5	Training and change management	$960.00	$1,250.00	$800.00	3	Initial plus refresher sessions
6	Renewal or subscription fees (per year)	$0.00	$900.00	$0.00	5	Applies to subscription-based option
7
8
9
10

Estimate the exit or switching cost if the contract ends early:

Estimate the expected downtime duration (in hours) during transition:

Estimated total cost of ownership over 3 years

Estimated total cost of ownership over 5 years

Estimated annual recurring cost after year one

Estimated cost savings versus the current arrangement (percent)

List the assumptions used in the TCO calculation (volumes, growth rates, inflation, utilisation, exchange rates)

Does any vendor's pricing create a dependency or lock-in risk?

Yes

Describe the lock-in risk, its financial impact and how it could be mitigated in the contract:

6. Quality, Technical Fit & Compliance Assessment

Score each vendor's proposal against the specification and quality expectations. Use the full scale and record evidence for any score of 1 or 2. Scores feed directly into the weighted evaluation matrix later in this form.

Rate each vendor's proposal against the following quality and technical criteria (Vendor A shown — repeat for other vendors).

	Poor	Below expectations	Meets expectations	Exceeds expectations	Outstanding
Conformance to the technical specification
Quality of materials, components or deliverables
Reliability and expected failure rate
Performance against required benchmarks
Completeness and clarity of the proposal submitted
Innovation and value-added suggestions offered
Compatibility with existing systems and processes
Quality management processes and traceability

Compliance scorecard — rate each requirement from 0 (not met) to 5 (fully met with evidence).


Mandatory specification requirements met
Required certifications and accreditations held
Regulatory and standards compliance demonstrated
Insurance and liability cover meets requirements
Data security and privacy controls documented
Health and safety policies and record provided
Contract terms and conditions acceptable as submitted
Environmental and sustainability obligations met

Does the proposal fully meet every mandatory requirement?

Yes

List each unmet or partially met mandatory requirement and the vendor's proposed alternative:

Describe each deviation and the mitigation or workaround agreed:

Has any vendor been subject to litigation, regulatory sanctions, product recalls or major quality failures?

Yes

Describe the issue, its date, outcome and the risk it poses to this procurement:

Were products tested, inspected or independently verified?

Yes

Summarise the test method, results and who conducted the testing:

Rate the overall quality of the documentation submitted by the recommended vendor (1 = very poor, 10 = excellent)

scale_onescale_twoscale_threescale_fourscale_fivescale_sixscale_sevenscale_eightscale_ninescale_ten

Rate the overall build quality or deliverable quality of the recommended vendor's offering

starstarstarstarstar

Upload test reports, inspection certificates or compliance evidence

Choose a file or drop it here

7. Vendor Risk, Financial Stability & Due Diligence

Assess the risk of entering into a relationship with each vendor. A low price does not compensate for a vendor that may fail to deliver, become insolvent or expose the organisation to compliance or reputational damage.

Summarise the financial health indicators reviewed (revenue trend, profitability, credit rating, payment behaviour):

Describe the concentration risk and any alternative sourcing options considered:

Risk register and mitigation plan

	Risk Description	Likelihood	Impact	Risk Score	Mitigation Action	Risk Owner
	A	B	C	D	E	F
1	Delivery lead time extends beyond the required date			0	Contractual delivery milestone with liquidated damages; phased delivery agreed	Procurement Lead
2	Vendor sub-contracts critical work without approval			0	Contract clause requiring prior written approval of sub-contractors	Contract Manager
3	Price increases applied at renewal			0	Fixed pricing for 24 months with capped indexation thereafter	Finance Business Partner
4				0
5				0
6				0
7				0
8				0
9				0
10				0

Assess the following vendor risk statements.

	Strongly disagree	Disagree	Neutral	Agree	Strongly agree
The vendor demonstrates a stable and sustainable financial position
The vendor has sufficient capacity to meet our volume requirements
The vendor has robust business continuity and disaster recovery arrangements
The vendor's supply chain is transparent and resilient
The vendor has appropriate insurance and liability cover in place
The vendor has a clear escalation and governance structure
The vendor is unlikely to create an unacceptable dependency

Overall financial stability rating for the recommended vendor (1 = very high risk, 10 = very low risk)

scale_onescale_twoscale_threescale_fourscale_fivescale_sixscale_sevenscale_eightscale_ninescale_ten

Has a due diligence or background check been completed on the recommended vendor?

Yes

Summarise the due diligence findings, including ownership, sanctions screening and adverse media checks:

By when will due diligence be completed?

I confirm that no undisclosed conflict of interest exists between the evaluation team and any vendor under consideration

Upload credit reports, financial statements or due diligence evidence

Choose a file or drop it here

8. Service Levels, Support, Delivery & After-Sales

Evaluate what happens after the purchase order is raised. Support quality, response times and delivery reliability frequently determine the true success of a procurement decision.

Rate the following service and support statements for the recommended vendor.

	Strongly disagree	Disagree	Neutral	Agree	Strongly agree
Support is available through the channels we require (phone, email, portal, on-site)
Guaranteed response and resolution times meet our operational needs
The vendor provides a named account manager or service contact
Escalation procedures are clearly defined and documented
Spare parts and consumables are readily available
Training and knowledge transfer are included or affordable
The vendor demonstrates proactive communication and reporting
Service credits or penalties apply for missed service levels

What is the additional charge for out-of-hours or emergency call-out?

Where is the local support team based and what languages do they support?

Guaranteed support response time (hours)

Guaranteed support resolution time (hours)

Guaranteed uptime or availability (percent)

Service credit or penalty applied for service level breaches (percent)

Describe the proposed phases, volumes and dates for the phased rollout:

Quoted lead time from order to delivery (days)

Quoted lead time for repeat or replenishment orders (days)

Warranty terms — duration, coverage, exclusions and claim process

Is training included in the quoted price?

Yes

Describe the training scope, format, duration and number of participants covered:

What is the additional cost of training?

Is on-site support or installation assistance available?

Yes

Where is the on-site team based, what are the response times and is travel charged separately?

Does the vendor offer a service level agreement (SLA) with measurable targets?

Yes

Upload the proposed service level agreement

Choose a file or drop it here

Rate the quality and responsiveness of the vendor's communication during the tender process

starstarstarstarstar

How confident are you in this vendor's ability to deliver reliable after-sales support?

sentiment_very_dissatisfiedsentiment_dissatisfiedsentiment_neutralsentiment_satisfiedsentiment_very_satisfied

Additional observations on service, support or delivery terms

9. Sustainability, Ethics & Social Responsibility

Consider the environmental, ethical and social impact of each vendor. These criteria are increasingly important to stakeholders and can carry weighting in the final selection decision.

State the reported carbon footprint of the quoted product or service (kg CO2e):

List the environmental certifications held and their expiry dates:

Assess the following sustainability and ethics statements for the recommended vendor.

	Strongly disagree	Disagree	Neutral	Agree	Strongly agree
The vendor publishes a credible sustainability policy or report
The vendor measures and reports its environmental impact
The vendor's labour practices meet recognised ethical standards
The vendor can evidence responsible sourcing in its supply chain
The vendor offers lower-impact alternatives where available
The vendor supports product end-of-life recovery or recycling
The vendor's sustainability claims are independently verified

Does the vendor have a published sustainability or environmental policy?

Yes

Upload the vendor's sustainability policy or latest sustainability report

Choose a file or drop it here

Does the vendor have a published supplier code of conduct or ethical sourcing policy?

Yes

Summarise the key commitments in the vendor's code of conduct:

I confirm the vendor's ethical, labour and environmental practices have been reviewed as part of this evaluation

Estimated carbon footprint of delivery and deployment (kg CO2e)

10. References, Track Record & Vendor Capability

Independent evidence of past performance is one of the strongest predictors of future delivery. Verify references directly rather than relying solely on written testimonials supplied by the vendor.

Number of years the vendor has supplied this category of goods or services

Number of comparable projects or contracts delivered in the last 3 years

Value of the largest comparable contract delivered by the vendor

Describe the vendor's funding position, track record and any mitigations for their early stage:

Client references provided by the vendor

	Client or Organisation	Contact Person	Email or Phone	Project Value	Year Delivered	Satisfaction	Would Recommend
	A	B	C	D	E	F	G
1
2
3
4
5
6
7
8
9
10

Have you personally contacted and verified the references?

Yes

Summarise the feedback received from each reference, including any concerns raised:

Who is responsible for verifying the references and by when?

Has the vendor worked with our organisation before?

Yes

Summarise the previous relationship, performance and any issues encountered:

Upload case studies, portfolio or evidence of comparable work

Choose a file or drop it here

11. Site Visit, Demonstration & Vendor Presentation

Where practical, verify the vendor's capability first-hand through a site visit, product demonstration or presentation. Record observations objectively and consistently across all vendors.

Was a site visit, vendor presentation or product demonstration conducted?

Yes

Provide the date, attendees, agenda and a summary of what was observed:

Date and time of the vendor presentation or demonstration

Observations on the vendor's facilities, equipment, workforce and working environment

Questions raised by the evaluation team and the vendor's responses

Did the demonstration or visit reveal any concerns?

Yes

Describe each concern and how it could be addressed or mitigated:

Overall impression of the vendor following the visit or demonstration

sentiment_very_dissatisfiedsentiment_dissatisfiedsentiment_neutralsentiment_satisfiedsentiment_very_satisfied

How did you feel about each aspect of the vendor presentation?


Professionalism of the vendor team
Depth of technical knowledge demonstrated
Understanding of our business needs
Quality of the proposed solution
Confidence in the vendor's ability to deliver

Upload evaluation notes, scorecards or photographs from the visit

Choose a file or drop it here

12. Weighted Evaluation & Selection Scoring Matrix

Apply the agreed weighting to each criterion and score every vendor consistently. The weighted score is calculated automatically. Ensure that the total weighting equals 100 percent before finalising the recommendation.

Weighted vendor scoring matrix

	Evaluation Criterion	Weight Percent	Vendor A Score	Vendor B Score	Vendor C Score	Vendor A Weighted	Vendor B Weighted	Vendor C Weighted
	A	B	C	D	E	F	G	H
1	Total cost of ownership	30				0	0	0
2	Technical fit to specification	20				0	0	0
3	Quality and reliability	15				0	0	0
4	Delivery and lead time	10				0	0	0
5	Service and support levels	10				0	0	0
6	Vendor experience and references	8				0	0	0
7	Risk and financial stability	5				0	0	0
8	Sustainability and ethics	2				0	0	0
9						0	0	0
10						0	0	0

Total weighting applied (must equal 100)

Total weighted score — Vendor A

Total weighted score — Vendor B

Total weighted score — Vendor C

Comparative assessment — rate each vendor on the following dimensions (1 to 5 stars).


Value for money
Confidence in delivery
Quality of the proposal
Strength of the partnership potential
Overall recommendation

Score each vendor's responsiveness throughout the tender process (1 = poor, 10 = excellent).


Speed of response to the request for quotation
Willingness to clarify and answer questions
Flexibility on terms and commercial conditions
Accuracy and completeness of the submitted quotation
Professionalism of the account team

Rank the vendors in order of overall preference (best first).


	Vendor A — Northbridge Industrial Supply
	Vendor B — Vertex Systems Group
	Vendor C — Solstice Technical Partners
	No suitable vendor — re-tender required

Explain any score that differs significantly from the other evaluators and the evidence supporting it

13. Final Recommendation, Award & Approvals

Document the outcome of the comparison, the rationale for the recommendation and the approvals obtained. This record may be required for audit, governance or dispute resolution, so it must be complete and objective.

Describe the proposed split of the award between vendors and the rationale:

Explain why no vendor is suitable and what action is recommended next:

Total award value (excluding tax)

Total award value (including tax)

Confirm that the lowest-priced vendor also met all mandatory requirements:

Rationale for the recommendation — summarise the key evidence supporting this decision

Key risks of the recommended vendor and the agreed mitigation measures

Conditions, caveats or contract clauses to be included before award

Have all unsuccessful vendors been notified of the outcome?

Yes

What action is required and by when?

Will feedback be provided to unsuccessful vendors?

Yes

What level of feedback will be provided?

Outcome notification only

Summary score against criteria

Detailed comparative feedback

Feedback meeting offered

Other

Is there any actual, potential or perceived conflict of interest involving any member of the evaluation team?

Yes

Describe the conflict, the individuals involved and the mitigation or recusal applied:

Approval and sign-off record

	Approver Name	Role or Title	Approved	Date of Decision	Comments or Conditions
	A	B	C	D	E
1
2
3
4
5
6
7
8
9
10

Authorised signature of the approving manager

Name of the signatory

Position or title of the signatory

Date signed

14. Declarations, Data Handling & Record Retention

By submitting this form you confirm that the evaluation has been carried out objectively, that the information recorded is accurate and complete, and that all supporting evidence is retained in accordance with your organisation's records management policy.

I confirm the information provided in this form is accurate and complete to the best of my knowledge

I confirm that no confidential pricing or commercially sensitive information has been shared between competing vendors

I confirm that all vendors were given equal access to information and an equal opportunity to respond

I agree to this evaluation record being retained and made available for audit or governance review

I confirm that supporting evidence (quotations, correspondence, scorecards) has been filed and can be retrieved on request

Does this evaluation involve the processing of personal data about identifiable individuals?

Yes

Describe the personal data involved and how it will be handled, protected and retained in line with your organisation's data protection policy:

Any final comments, lessons learned or recommendations for future sourcing exercises

Upload any additional supporting documentation

Choose a file or drop it here

Thank you for completing the Vendor Price Comparison & Selection Matrix. Submitting this form creates a clear, defensible record of how the vendor decision was reached and why.

Analysis for Vendor Price Comparison & Selection Matrix | Supplier Evaluation & Award Form

Important Note: This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes. Please remove this content before publishing the form to the public.

Overall Form Analysis — Vendor Price Comparison & Selection Matrix

The Vendor Price Comparison & Selection Matrix is an exceptionally comprehensive and meticulously structured procurement evaluation tool designed to facilitate defensible, value-based supplier selection decisions. Spanning twelve distinct sections—from initial project intake through weighted scoring, final recommendation, and formal declarations—the form provides an end-to-end framework that captures every dimension of a competitive procurement exercise. Its scope is ambitious yet coherent, ensuring that price, quality, risk, sustainability, service levels, and governance considerations are all systematically documented before a vendor is awarded. This level of detail is essential in organisations where procurement decisions must withstand scrutiny from auditors, regulators, or stakeholders.

The form's greatest strength lies in its auditability. Every section is designed to produce a clear, evidence-backed record that can withstand internal audit, external review, or dispute resolution. From the procurement reference number at the outset to the authorised signature and declarations at the close, the form creates a complete decision trail. The inclusion of weighted scoring matrices, TCO formulas, risk registers with calculated scores, and structured approval sign-offs elevates this from a simple comparison spreadsheet to a rigorous governance instrument. The conditional follow-up logic—where certain questions trigger mandatory detail fields—ensures depth without burdening users with irrelevant questions. The form also balances quantitative data (pricing tables, numeric ratings, calculated scores) with qualitative assessments (narrative rationales, observation notes, confidence ratings), producing a rich and multi-dimensional evaluation record that serves both operational and strategic decision-making needs.

Section: Procurement Project Overview & Intake

This opening section establishes the foundational context for the entire procurement exercise and is critical for ensuring that every subsequent comparison is grounded in a well-defined business need. The section captures who is requesting the purchase, what is being procured, how the quotations were obtained, and what budget constraints apply—all before any vendor data is entered. This sequencing is excellent design practice, as it prevents evaluators from being swayed by vendor proposals before the evaluation framework is established.

Question: Procurement/project reference number

The Procurement/project reference number serves as the unique identifier for the entire procurement exercise and is fundamental to creating a traceable, auditable record. In any organisation that manages multiple concurrent procurement projects, this reference number is the primary key that links this comparison matrix to purchase orders, contracts, budget approvals, and correspondence files. Without it, the evaluation record becomes an orphan document that is difficult to locate, cross-reference, or defend during an audit.

From a design perspective, making this field mandatory is absolutely correct. A procurement reference number is typically generated at the point of requisition or project initiation, so it should always be available to the person completing the form. The placeholder example (e.g. PROC-2026-0148) is helpful as it suggests a standardised naming convention, which encourages consistency across the organisation's procurement records. This small design choice significantly improves data quality by guiding users toward a structured format rather than free-text entries that vary wildly.

The data collection implications are straightforward: this field produces a short, structured alphanumeric string that can be easily indexed, searched, and linked to other systems. It raises no privacy concerns and is essential for any downstream reporting, spend analytics, or compliance monitoring. From a user experience perspective, this is a low-effort, high-value field that sets the tone for the rest of the form—structured, purposeful, and designed for professional use.

Question: Project or requirement title

The Project or requirement title provides a human-readable descriptor for the procurement exercise and is essential for anyone reviewing the form to quickly understand what is being purchased. While the reference number provides the unique key, the title provides the semantic context. Together, they form the two most important identifiers for the evaluation record. This question's purpose is to ensure that the form is self-documenting—anyone picking it up months or years later should immediately understand the subject matter.

The design choice to include a descriptive placeholder (e.g. Replacement of plant monitoring sensors — Line 3) is effective because it demonstrates the expected level of specificity. A title like 'Sensors' would be too vague, while the example shows that a good title includes the item, the purpose, and the location or scope. This guidance improves data quality without adding friction. Making this field mandatory ensures that no evaluation record is left without a clear subject line.

From a data quality perspective, a well-crafted project title enables effective categorisation and searchability across a portfolio of procurement exercises. It supports spend analytics, category management, and benchmarking. From a user experience standpoint, this is a quick, intuitive field that most users can complete without hesitation. The only minor risk is inconsistency in naming conventions across different users or departments, but the placeholder example mitigates this effectively.

Question: Requesting department, business unit or cost centre

The Requesting department, business unit or cost centre field captures the organisational origin of the procurement request and is essential for budget allocation, cost tracking, and accountability. In any organisation with multiple departments, this field ensures that the cost of the purchase is attributed to the correct budget line and that the requesting function is clearly identified for follow-up queries or approval routing.

This question is well-designed in its flexibility—it accepts a department name, business unit, or cost centre code, recognising that different organisations use different structures. However, this flexibility could be a double-edged sword: without a standardised list or dropdown, data entry could be inconsistent. A future enhancement might consider a dropdown or auto-complete list of known departments and cost centres to improve data quality. Nevertheless, making this field mandatory is correct because it is foundational to financial governance.

The data collected here is operational and organisational, with no privacy implications. It enables cross-departmental spend analysis and helps procurement teams identify patterns, such as which departments are the heaviest users of a particular category. From a user experience perspective, this is a simple, low-friction field. The only potential issue is if a user is unsure which cost centre applies—in which case a brief help note could be beneficial.

Question: Requestor name and job title

The Requestor name and job title field identifies the individual who initiated the procurement and their role within the organisation. This is critical for accountability, communication, and approval workflows. In the event of a query, dispute, or audit, the requestor is the primary point of contact and the person who can explain the business need and justify the evaluation criteria. The job title adds important context about the seniority and authority of the requestor.

The design is effective: combining name and job title in a single field with a clear placeholder (e.g. Jordan Reyes, Operations Manager) reduces the number of fields while capturing all necessary information. This is a good example of efficient form design—fewer fields, same data quality. Making this field mandatory is essential because an anonymous procurement request would be indefensible in any governance framework.

From a data collection perspective, this field produces personal data (name and role), which means it falls within the scope of data protection regulations. The form does address this later in the Declarations section, which is commendable. From a user experience standpoint, this is a quick and familiar field that most users will complete without friction. The placeholder example is helpful in guiding the expected format.

Question: Requestor email address

The Requestor email address provides the primary communication channel for the procurement exercise. It is essential for sending notifications, requesting clarifications, sharing evaluation outcomes, and routing approvals. Without a valid email address, the procurement process could stall at multiple points. This question's purpose is purely functional—it enables the digital workflow that modern procurement depends upon.

The design is straightforward and appropriate: a single-line text field with a placeholder that shows the expected format. Making this field mandatory is correct because email is the default communication method in virtually all organisations. A validation rule (e.g. regex check for @ symbol) would further improve data quality, though this is likely handled by the form platform.

From a privacy perspective, the email address is personal data and should be handled in accordance with the organisation's data protection policy. The form's later section on data handling addresses this. From a user experience standpoint, this is a zero-friction field—everyone knows their email address and can enter it instantly. The only minor consideration is whether a work email or personal email is expected; the placeholder (name@organisation.com) clarifies that a work email is preferred.

Question: Date this comparison exercise commenced

The Date this comparison exercise commenced establishes the timeline anchor for the entire procurement evaluation. This date is essential for measuring the duration of the evaluation process, identifying bottlenecks, and ensuring compliance with procurement policies that may impose time limits on how long quotations remain valid or how quickly decisions must be made. It also provides context for the decision deadline field that follows.

The design is clean and appropriate—a date picker field that ensures consistent formatting. Making this field mandatory is correct because the start date is a fundamental reference point for the entire exercise. Without it, it would be impossible to assess whether the evaluation was conducted within acceptable timeframes or whether quotation validity periods have expired.

From a data quality perspective, the date field produces structured, machine-readable data that can be used for process analytics—average evaluation duration, time-to-award metrics, and compliance with SLAs. From a user experience standpoint, this is a quick field, though users may need to recall or look up the exact date. The field is well-placed at the beginning of the form, where temporal context is being established.

Question: Procurement category

The Procurement category question classifies the type of goods or services being procured and is one of the most strategically important fields in the form. The category determines which evaluation criteria are most relevant, which regulatory frameworks apply, and how the procurement should be managed. For example, software procurement involves licensing models and data security, while construction involves schedule of rates and safety compliance. This question's purpose is to route the evaluation along the appropriate analytical path.

The design is excellent: a comprehensive single-choice list covering the major procurement categories (goods, services, software, construction, professional services, logistics, raw materials, facilities, marketing, and other). The inclusion of conditional follow-up questions for specific categories—such as product families for goods, deployment models for software, delivery arrangements for construction, and shipping profiles for logistics—demonstrates sophisticated form logic that adapts to the user's context. This prevents irrelevant questions from being asked while ensuring that category-specific details are captured.

The data collected here enables powerful category-level analytics, spend segmentation, and benchmarking. It also helps procurement teams apply the right templates, policies, and evaluation frameworks to each exercise. From a user experience perspective, the single-choice format is fast and intuitive, and the conditional follow-ups feel relevant rather than burdensome. Making this field mandatory is essential because the entire evaluation framework depends on knowing what type of procurement is being conducted.

Question: Sourcing method used to obtain the quotations

The Sourcing method used to obtain the quotations documents how the competitive process was conducted and is essential for demonstrating that the procurement followed fair, transparent, and compliant procedures. Different sourcing methods carry different governance requirements: open tenders require public notices and minimum response periods, while direct awards require documented justification. This question's purpose is to establish the procedural legitimacy of the exercise.

The design is thorough, covering the full spectrum of sourcing methods from open tender through to reverse auction. The conditional follow-ups are particularly well-designed: selecting 'Direct award/sole source' triggers a mandatory justification field, which is exactly the kind of governance control that prevents misuse of non-competitive procurement. Similarly, the reverse auction option triggers a field for describing the platform and rules used. This demonstrates a deep understanding of procurement governance requirements.

From a data collection perspective, this field produces categorical data that is essential for compliance reporting and spend analysis. It enables the organisation to track the proportion of competitive versus non-competitive procurement and identify areas where competition could be increased. From a user experience standpoint, the single-choice format is quick, and the conditional follow-ups only appear when relevant, keeping the form efficient. Making this field mandatory is correct because the sourcing method is a fundamental governance parameter.

Question: Approved budget ceiling for this requirement

The Approved budget ceiling for this requirement captures the maximum authorised spend for the procurement and is a critical financial governance control. This field ensures that the evaluation is conducted within approved financial boundaries and that any recommendation that exceeds the budget is flagged and escalated. Without this field, there would be no benchmark against which to assess whether the quoted prices are acceptable.

The design uses a currency field, which is appropriate for financial data and ensures consistent formatting. Making this field mandatory is essential because budget approval is a prerequisite for any procurement exercise. The field is well-placed in the intake section, where financial parameters are being established. The optional 'Estimated total spend' field that follows provides useful context without being burdensome.

From a data collection perspective, this field produces structured financial data that feeds into budget tracking, spend analytics, and variance reporting. It is commercially sensitive but not personally identifiable. From a user experience standpoint, this is a straightforward field for anyone who has obtained budget approval, though it may require a quick lookup. The currency field type reduces formatting errors and ensures consistency.

Question: Is this a repeat purchase of a previously sourced item or service?

The Is this a repeat purchase of a previously sourced item or service? question provides important context about the procurement's history and helps evaluators understand whether there is existing vendor performance data, historical pricing, or lessons learned from previous purchases. Repeat purchases may benefit from incumbent knowledge but also carry risks of complacency or lock-in. First-time purchases require more extensive market research. This question's purpose is to calibrate the depth and nature of the evaluation.

The design is effective: a simple yes/no question with conditional follow-ups that adapt to the response. If 'Yes', the form requests details of the previous purchase (vendor, price, date, performance issues), which is exactly the information needed to benchmark the current exercise. If 'No', a checkbox confirms that a full market scan has been completed, which is a reasonable governance control for first-time purchases. This conditional logic keeps the form efficient while capturing the right information in each scenario.

From a data collection perspective, this question produces binary data with rich conditional detail. The historical pricing data captured in the 'Yes' follow-up is particularly valuable for benchmarking and negotiation. From a user experience standpoint, this is a quick question that most users can answer instantly, and the follow-ups are only shown when relevant. The question is not mandatory, which is appropriate—its importance depends on the context of the specific procurement.

Question: Is this requirement time-critical?

The Is this requirement time-critical? question identifies whether the procurement has an urgent deadline and what the operational impact of delay would be. This is important for prioritising the evaluation, justifying expedited processes, and ensuring that delivery timelines are given appropriate weight in the vendor selection. Time-critical procurements may also justify direct awards or reduced competition periods.

The design is well-structured: a yes/no question with a mandatory follow-up when 'Yes' is selected. The follow-up asks for an explanation of the critical deadline and the operational impact of delay, which is exactly the kind of evidence needed to justify any deviations from standard procurement timelines. Making this follow-up mandatory is a strong governance control—it prevents users from claiming urgency without providing evidence.

From a data collection perspective, this question produces binary data with rich narrative context when time-criticality is confirmed. This narrative is valuable for audit trails and for justifying procurement decisions to stakeholders. From a user experience standpoint, the question is quick and the follow-up is only triggered when relevant. The question is not mandatory at the top level, which is appropriate—not every procurement is time-critical, and forcing this question would add unnecessary friction.

Section: Requirements, Specification & Evaluation Criteria Definition

This section is the intellectual core of the form—it defines what the organisation needs and how vendors will be assessed. A fair comparison is only possible when every vendor is scored against the same clearly defined requirement, and this section ensures that the specification, mandatory criteria, desirable features, and evaluation dimensions are all documented before quotations are reviewed. The separation of must-have from nice-to-have criteria is a best-practice approach that prevents evaluators from being distracted by vendor bells and whistles.

Question: Business need and problem statement — what outcome must this purchase deliver?

The Business need and problem statement is arguably the most important question in the entire form. It articulates the fundamental reason for the procurement and defines the outcome that the purchase must deliver. Every subsequent evaluation criterion, scoring decision, and vendor selection rationale flows from this statement. Without a clear problem statement, the evaluation becomes a price comparison exercise rather than a value-based decision.

The design is excellent: a multiline text field with a placeholder that demonstrates the expected level of specificity (e.g. Reduce unplanned downtime on Line 3 by improving sensor accuracy and shorten fault detection time). This example shows that a good problem statement includes the current pain point, the desired outcome, and the measurable impact. Making this field mandatory is absolutely essential—it is the foundation upon which the entire evaluation is built.

From a data collection perspective, this field produces rich qualitative data that provides context for every other field in the form. It is the narrative thread that connects the business need to the vendor selection. From a user experience standpoint, this is a thoughtful question that requires reflection, but the placeholder example makes it accessible. The multiline format gives users enough space to articulate their needs properly.

Question: Detailed technical or functional specification

The Detailed technical or functional specification defines the precise requirements that vendors must meet and is the benchmark against which all proposals are assessed. This field is essential for ensuring that the comparison is like-for-like—without a detailed specification, vendors may quote for different scopes, making price comparison meaningless. The specification also serves as the basis for contract terms and acceptance criteria.

The design uses a multiline text field, which provides sufficient space for detailed specifications. Making this field mandatory is correct because a procurement without a specification cannot be evaluated fairly. The field is well-placed immediately after the problem statement, creating a logical flow from 'what we need' to 'exactly how we need it'. The form also includes optional file upload fields for formal specification documents, which is a practical enhancement for complex procurements.

From a data collection perspective, this field produces detailed technical data that is essential for vendor evaluation and contract management. It may contain commercially sensitive information about the organisation's operations. From a user experience standpoint, this is a demanding field that requires technical knowledge and effort to complete well. However, for a professional procurement tool, this level of detail is expected and appropriate.

Question: Which mandatory (must-have) requirements apply?

The Which mandatory (must-have) requirements apply? question establishes the pass/fail criteria that vendors must meet to be considered eligible. This is a critical governance control—it prevents evaluators from selecting a vendor that fails to meet fundamental requirements simply because they offered the lowest price. The distinction between mandatory and desirable criteria is one of the most important principles in procurement evaluation.

The design is comprehensive: a multiple-choice list covering the major categories of mandatory requirements (quality certifications, delivery lead time, capacity, warranty, data security, accessibility, environmental standards, local support, interoperability, financial stability). The conditional follow-ups for specific options—such as listing required certifications, stating minimum capacity, and describing accessibility standards—ensure that the mandatory criteria are defined with sufficient precision to be objectively assessed. Making this field mandatory is essential because it defines the eligibility threshold.

From a data collection perspective, this field produces structured categorical data with conditional detail that feeds directly into the compliance scorecard later in the form. It enables objective pass/fail assessment of each vendor. From a user experience standpoint, the multiple-choice format is efficient, and the conditional follow-ups only appear when relevant. The field is well-designed for its purpose.

Question: Rank the following evaluation dimensions in order of importance

The Rank the following evaluation dimensions in order of importance question captures the relative priority of different evaluation criteria and directly informs the weighting applied in the final scoring matrix. This question is strategically important because it ensures that the evaluation reflects the organisation's actual priorities rather than an arbitrary weighting. The dimensions listed (price, quality, delivery, technical fit, support, experience, risk, sustainability) cover the full spectrum of procurement considerations.

The design uses a ranking question type, which is the most appropriate format for capturing relative priority. Users must order the dimensions from most to least important, which forces them to make deliberate trade-offs. This is more informative than a simple rating scale because it reveals the priority hierarchy. The question is not mandatory, which is a reasonable choice—some organisations may have standard weightings that don't need to be re-ranked for every procurement.

From a data collection perspective, this produces ordinal data that directly feeds into the weighted scoring matrix. It ensures consistency between the stated priorities and the actual scoring. From a user experience standpoint, ranking questions can be slightly more effortful than single-choice questions, but the payoff in data quality is significant. The list of dimensions is comprehensive and covers all the key procurement evaluation factors.

Question: I confirm the specification has been reviewed and approved by the technical owner

The I confirm the specification has been reviewed and approved by the technical owner before quotations were requested checkbox is a governance control that ensures the specification has been validated by the appropriate technical authority before the procurement process began. This prevents situations where vendors are invited to quote against an unreviewed or incorrect specification, which would waste time and potentially lead to an unsuitable award.

The design is simple but effective: a single checkbox with a clear, unambiguous statement. Making this field mandatory is a strong governance control—it creates a formal attestation that the specification is fit for purpose. This kind of confirmation checkbox is a best practice in procurement forms because it creates accountability and a clear audit trail.

From a data collection perspective, this produces a binary attestation that is valuable for compliance and audit purposes. From a user experience standpoint, this is a zero-effort field—a simple click. However, its importance is significant because it formalises the review process and creates accountability.

Section: Vendor Identification & Bidder Register

This section documents the competitive landscape of the procurement—who was invited, who responded, and who was excluded. A fair and defensible comparison requires a sufficiently broad and appropriate vendor pool, and this section provides the evidence that competition was genuine. The vendor register table is a particularly strong design element that captures the essential details of each bidder in a structured format.

Question: Number of vendors invited to quote or tender

The Number of vendors invited to quote or tender field captures the breadth of the competitive process and is essential for demonstrating that the procurement achieved adequate market coverage. Most procurement policies require a minimum number of invitations (typically three or more) to ensure genuine competition. This field provides the evidence that this threshold was met.

The design uses a numeric field, which is appropriate and ensures structured data. Making this field mandatory is correct because the level of competition is a fundamental governance parameter. Without it, there would be no way to assess whether the procurement was genuinely competitive or whether it was effectively a sole-source exercise dressed up as a competition.

From a data collection perspective, this produces a simple numeric value that is easy to analyse and report on. It enables the organisation to track competition levels across different categories and identify areas where market engagement could be improved. From a user experience standpoint, this is a quick field that most users can answer instantly.

Question: Number of quotations or bids received

The Number of quotations or bids received field captures the actual level of competition and, when compared with the number invited, provides a response rate that indicates market interest and the attractiveness of the requirement. A low response rate may indicate that the specification is too restrictive, the budget is unrealistic, or the market is concentrated. This field is essential for assessing the quality of the competitive process.

The design is consistent with the previous field—a simple numeric input. Making this field mandatory is correct because the number of responses received is a key indicator of procurement health. Together with the number invited, it provides a complete picture of the competitive landscape.

From a data collection perspective, this produces a numeric value that enables response rate calculations and market analysis. From a user experience standpoint, this is a trivial field to complete. The pairing of invited and received numbers is a simple but powerful design choice that provides immediate insight into the procurement's competitive health.

Question: Vendor register — all invited and responding vendors

The Vendor register table is one of the strongest structural elements in the form. It captures the essential details of every vendor involved in the process—name, contact, email, region, quote reference, date received, and submission completeness—in a single, structured table. This is far more efficient and analytically useful than asking separate questions for each vendor. The table format also makes it easy to identify gaps, such as vendors who were invited but did not respond.

The design is exemplary: the columns cover all the key data points needed to manage and track vendor submissions. The inclusion of a 'Complete Submission' yes/no column is particularly valuable because it immediately identifies which vendors have provided full documentation and which have gaps. The sample data rows demonstrate the expected level of detail and provide a useful reference for users.

From a data collection perspective, this table produces structured, tabular data that can be directly imported into procurement systems or analysis tools. It captures personal data (contact names and emails) which requires appropriate data protection handling. From a user experience standpoint, the table format is familiar and efficient for this type of data. The sample rows reduce cognitive load by showing exactly what is expected.

Question: Primary vendor under evaluation (Vendor A) — legal entity name

The Primary vendor under evaluation (Vendor A) — legal entity name field identifies the leading candidate for award and begins the detailed vendor profile section. This is important for clarity and focus—while the form supports comparison across multiple vendors, the detailed profile section concentrates on the primary candidate. The legal entity name (as opposed to a trading name) is essential for contract purposes and due diligence.

The design is straightforward: a single-line text field for the legal entity name. Making this field mandatory is correct because the form cannot proceed with a detailed evaluation without knowing which vendor is being assessed. The subsequent fields (registration number, contact, website, background, employees, revenue) build a comprehensive vendor profile that supports due diligence and risk assessment.

From a data collection perspective, this produces structured company data that is essential for contract execution and vendor management. From a user experience standpoint, this is a quick field, though users may need to verify the exact legal entity name. The placeholder guidance is helpful.

Question: Has every vendor submitted all required documentation?

The Has every vendor submitted all required documentation (quote, terms, certifications, financials)? question is a completeness check that ensures the evaluation is based on complete information. Incomplete submissions can lead to unfair comparisons—vendors who provide more documentation may appear stronger simply because they were more thorough, not because their offering is better. This question's purpose is to identify and address documentation gaps before the evaluation proceeds.

The design is effective: a yes/no question with a mandatory follow-up when 'No' is selected. The follow-up asks for a list of outstanding documents, the vendor affected, and the chase-up action taken. This is a strong governance control—it ensures that missing documentation is identified, tracked, and resolved. Making both the question and the follow-up mandatory is appropriate because documentation completeness is a prerequisite for a fair comparison.

From a data collection perspective, this produces binary data with rich conditional detail about documentation gaps. This is valuable for audit trails and for ensuring that the evaluation is based on complete information. From a user experience standpoint, the question is quick, and the follow-up only appears when needed.

Question: Was any vendor excluded from the comparison?

The Was any vendor excluded from the comparison? question documents any vendors that were removed from the evaluation and the reasons why. This is essential for transparency and fairness—exclusions must be justified and documented to prevent accusations of bias or manipulation. The question also helps identify patterns, such as recurring exclusion reasons that might indicate issues with the specification or the invitation process.

The design is well-structured: a yes/no question with a mandatory follow-up when 'Yes' is selected. The follow-up requires the name of the excluded vendor(s) and a documented reason for exclusion. Making this follow-up mandatory is a strong governance control—it ensures that every exclusion is justified and recorded. This is consistent with procurement best practice and regulatory requirements in many jurisdictions.

From a data collection perspective, this produces binary data with conditional narrative detail that is essential for audit and compliance purposes. From a user experience standpoint, the question is quick and the follow-up is only triggered when relevant. The design effectively balances efficiency with governance.

Section: Price Comparison — Line-by-Line Cost Breakdown

This section captures the detailed pricing from each vendor in a structured, comparable format. The line-by-line breakdown table with automatic calculation of line totals is a powerful design element that ensures like-for-like comparison. The section also captures important commercial terms such as currency, validity period, payment terms, and price fixity, which are essential for a complete financial assessment.

Question: Quoted price breakdown (per vendor)

The Quoted price breakdown (per vendor) table is the heart of the price comparison and one of the most important structural elements in the form. It captures each line item with its description, unit, quantity, unit price, discount percentage, and calculated line total. The automatic calculation of line totals (Quantity × Unit Price × (1 − Discount%/100)) eliminates arithmetic errors and ensures consistency across all vendors. This is a significant improvement over manual calculations in spreadsheets.

The design is exemplary: the columns cover all the key pricing dimensions, and the formula-based line total ensures accuracy. The sample data rows demonstrate the expected level of detail and provide a useful reference. The instruction to enter prices exactly as submitted and not to include costs outside the written quotation is an important governance control that prevents manipulation.

From a data collection perspective, this table produces structured financial data that can be directly analysed, compared, and reported on. The formula-based calculations ensure data integrity. From a user experience standpoint, the table format is familiar and efficient, and the automatic calculations reduce effort and errors. This is one of the strongest design elements in the entire form.

Question: Total quoted price (all inclusive)

The Total quoted price (all inclusive) field captures the bottom-line price that each vendor is offering, including all additional charges such as tax, shipping, and installation. This is the single most important number in the price comparison and the primary input for the weighted scoring matrix. It must be accurate and complete to ensure a fair comparison.

The design uses a currency field, which is appropriate and ensures consistent formatting. Making this field mandatory is essential because the total price is the primary basis for the financial comparison. The field is well-placed after the line-by-line breakdown and the additional cost fields (tax, shipping, installation), ensuring that it reflects the true all-inclusive cost.

From a data collection perspective, this produces a structured financial value that feeds directly into the TCO calculation and the weighted scoring matrix. From a user experience standpoint, this is a straightforward field, though it requires the user to have completed the preceding pricing fields. The mandatory status ensures that no vendor comparison proceeds without a complete price picture.

Question: Is the quoted price fixed for the full contract term?

The Is the quoted price fixed for the full contract term? question is critical for understanding the true cost of the procurement over time. A low initial price with aggressive indexation can end up costing more than a higher fixed price. This question's purpose is to surface price volatility risk and ensure that the comparison accounts for the full contract duration, not just the initial purchase price.

The design is strong: a yes/no question with a mandatory follow-up when 'No' is selected. The follow-up asks for the price adjustment mechanism, its cap, and review frequency—exactly the information needed to model future cost exposure. Making both the question and the follow-up mandatory is a strong governance control that prevents hidden price escalation from being overlooked.

From a data collection perspective, this produces binary data with conditional detail about price adjustment mechanisms. This is essential for TCO modelling and contract negotiation. From a user experience standpoint, the question is quick and the follow-up is only triggered when relevant. The design effectively surfaces a critical risk factor.

Question: Which cost elements are INCLUDED/EXCLUDED from the quoted price?

The Which cost elements are INCLUDED/EXCLUDED from the quoted price? questions are essential for understanding the scope of each vendor's quotation and ensuring that the comparison is truly like-for-like. One vendor may include training and warranty while another excludes them, making the headline prices misleading. These questions surface the scope differences that could significantly affect the total cost.

The design uses parallel multiple-choice lists for included and excluded cost elements, which is an effective way to capture scope boundaries. The comprehensive list of cost elements (materials, labour, delivery, packaging, insurance, training, documentation, warranty, support, taxes, disposal) covers the major cost categories. The conditional follow-up for 'Other' excluded costs ensures that unusual exclusions are documented.

From a data collection perspective, these questions produce structured categorical data that enables scope normalisation across vendors. This is essential for fair price comparison. From a user experience standpoint, the multiple-choice format is efficient, and the parallel structure of included/excluded makes it easy to identify scope gaps.

Section: Total Cost of Ownership (TCO) & Hidden Cost Analysis

This section elevates the analysis from purchase price to lifecycle cost, recognising that the lowest bid is rarely the lowest cost. The TCO comparison table, hidden cost identification, and TCO formula provide a rigorous framework for assessing the true financial impact of each vendor over the expected contract period. This section is a significant differentiator of this form compared to simpler price comparison tools.

Question: Total cost of ownership comparison across vendors

The Total cost of ownership comparison across vendors table is a sophisticated analytical tool that captures the full lifecycle cost of each vendor across multiple cost components. The table includes purchase price, installation, annual maintenance, consumables, training, and renewal fees, with expected life and assumptions for each component. This holistic view is essential for making a value-based decision rather than a price-based one.

The design is excellent: the columns capture cost for each vendor (A, B, C) alongside the expected life and assumptions, enabling direct comparison. The sample data rows demonstrate the expected level of detail and show how different vendors may have different cost profiles—Vendor B has lower purchase price but higher installation and renewal costs. This kind of insight is exactly what the TCO analysis is designed to surface.

From a data collection perspective, this table produces structured financial data that feeds into the TCO calculation and the weighted scoring matrix. The assumptions column is particularly valuable because it documents the basis for the estimates, making the analysis auditable. From a user experience standpoint, the table format is efficient and the sample rows provide clear guidance.

Question: Estimated total cost of ownership over 3 years

The Estimated total cost of ownership over 3 years field captures the headline TCO figure that summarises the full lifecycle cost of the recommended vendor. This is the single most important financial metric in the form and the primary input for the 'Total cost of ownership' criterion in the weighted scoring matrix. A 3-year horizon is a common benchmark that balances short-term affordability with long-term value.

The design uses a currency field, which is appropriate and ensures consistent formatting. Making this field mandatory is essential because TCO is the basis for the value-based comparison that this form is designed to support. The field is well-placed after the TCO comparison table and the hidden cost analysis, ensuring that it reflects a comprehensive cost picture.

From a data collection perspective, this produces a structured financial value that is the key output of the TCO analysis. It enables comparison against the budget ceiling and the estimated spend. From a user experience standpoint, this field requires the user to have completed the preceding TCO fields, but the payoff is a single, powerful metric that drives the final decision.

Question: List the assumptions used in the TCO calculation

The List the assumptions used in the TCO calculation field documents the basis for the TCO estimates, including volumes, growth rates, inflation, utilisation, and exchange rates. This is essential for auditability—without documented assumptions, the TCO figure is just a number with no context. If the assumptions change (e.g. higher volumes than expected), the TCO can be recalculated and the decision re-evaluated.

The design uses a multiline text field, which provides sufficient space for detailed assumptions. Making this field mandatory is a strong governance control that ensures the TCO analysis is transparent and defensible. The field is well-placed immediately after the TCO figures, creating a logical connection between the numbers and their basis.

From a data collection perspective, this produces rich qualitative data that provides context for the quantitative TCO figures. It is essential for audit and for future re-evaluation if circumstances change. From a user experience standpoint, this is a demanding field that requires careful thought, but it is essential for the integrity of the TCO analysis.

Question: Does any vendor's pricing create a dependency or lock-in risk?

The Does any vendor's pricing create a dependency or lock-in risk? question identifies a critical strategic risk that is often overlooked in price comparisons. A vendor with proprietary technology, high switching costs, or escalating renewal fees can create a dependency that erodes value over time. This question's purpose is to surface these risks before the award decision is made.

The design is effective: a yes/no question with a mandatory follow-up when 'Yes' is selected. The follow-up asks for a description of the lock-in risk, its financial impact, and how it could be mitigated in the contract. This is exactly the kind of forward-looking risk assessment that distinguishes a strategic procurement tool from a simple price comparison. Making the follow-up mandatory ensures that identified risks are documented and addressed.

From a data collection perspective, this produces binary data with conditional narrative detail about strategic risks. This is valuable for contract negotiation and risk management. From a user experience standpoint, the question is quick and the follow-up is only triggered when relevant.

Section: Quality, Technical Fit & Compliance Assessment

This section provides a structured framework for assessing each vendor's proposal against the specification and quality expectations. The use of matrix rating scales, compliance scorecards, and evidence-based scoring ensures that the assessment is objective and consistent. The section also captures important due diligence information such as litigation history and product testing.

Question: Rate each vendor's proposal against quality and technical criteria

The Rate each vendor's proposal against the following quality and technical criteria matrix rating question provides a structured, multi-dimensional assessment of each vendor's proposal quality. The eight sub-questions (conformance, quality, reliability, performance, completeness, innovation, compatibility, and quality management) cover the key dimensions of technical excellence. The five-point scale (Poor to Outstanding) provides sufficient granularity for meaningful differentiation.

The design is strong: the matrix format enables efficient assessment across multiple criteria, and the consistent scale ensures comparability. The instruction to use the full scale and record evidence for scores of 1 or 2 is a best practice that prevents score inflation and ensures that low scores are justified. This question feeds directly into the weighted scoring matrix, creating a clear link between assessment and decision.

From a data collection perspective, this produces structured ordinal data across multiple dimensions that enables detailed vendor comparison. From a user experience standpoint, the matrix format is efficient—users can assess all criteria in a single view. The scale labels are clear and intuitive.

Question: Does the proposal fully meet every mandatory requirement?

The Does the proposal fully meet every mandatory requirement? question is a critical pass/fail gate that determines whether a vendor is eligible for award. If a vendor fails to meet a mandatory requirement, they should normally be excluded regardless of their price or other strengths. This question's purpose is to enforce the mandatory criteria defined earlier in the form.

The design is effective: a yes/no question with a mandatory follow-up when 'No' is selected. The follow-up asks for a list of each unmet or partially met mandatory requirement and the vendor's proposed alternative. This is essential for transparent decision-making—if a mandatory requirement is waived, the waiver must be documented and justified. Making both the question and the follow-up mandatory is a strong governance control.

From a data collection perspective, this produces binary data with conditional detail about compliance gaps. This is essential for audit and for ensuring that the evaluation is conducted against the defined criteria. From a user experience standpoint, the question is quick and the follow-up is only triggered when needed.

Question: Has any vendor been subject to litigation, regulatory sanctions, product recalls or major quality failures?

The Has any vendor been subject to litigation, regulatory sanctions, product recalls or major quality failures? question is a due diligence check that surfaces reputational and operational risks associated with each vendor. A vendor with a history of quality failures or regulatory sanctions may pose a significant risk to the organisation, regardless of their price or technical capability. This question's purpose is to ensure that these risks are identified and assessed before the award decision.

The design is well-structured: a yes/no question with a mandatory follow-up when 'Yes' is selected. The follow-up asks for a description of the issue, its date, outcome, and the risk it poses to the procurement. Making this follow-up mandatory ensures that identified risks are documented and can be weighed in the decision. This is consistent with best practice in vendor risk management.

From a data collection perspective, this produces binary data with conditional narrative detail about vendor risk history. This is valuable for risk assessment and audit. From a user experience standpoint, the question is quick and the follow-up is only triggered when relevant.

Section: Vendor Risk, Financial Stability & Due Diligence

This section assesses the risk of entering into a relationship with each vendor, recognising that a low price does not compensate for a vendor that may fail to deliver or expose the organisation to compliance or reputational damage. The risk register with calculated scores, the risk matrix, and the due diligence checklist provide a comprehensive risk assessment framework.

Question: Risk register and mitigation plan

The Risk register and mitigation plan table is a powerful risk management tool that captures identified risks along with their likelihood, impact, calculated risk score, mitigation actions, and risk owner. The automatic calculation of risk scores (Likelihood × Impact) ensures consistency and enables prioritisation. The sample data rows demonstrate the expected level of detail and show how different risks are assessed and mitigated.

The design is exemplary: the columns cover all the key dimensions of risk management, and the formula-based scoring eliminates subjectivity in the risk assessment. The inclusion of a risk owner column ensures accountability. This table transforms the form from a comparison tool into a risk management instrument.

From a data collection perspective, this produces structured risk data that can be tracked over time and used for portfolio-level risk analysis. From a user experience standpoint, the table format is efficient and the sample rows provide clear guidance. The calculated risk scores reduce effort and improve consistency.

Question: Has a due diligence or background check been completed on the recommended vendor?

The Has a due diligence or background check been completed on the recommended vendor? question is a critical governance control that ensures the recommended vendor has been properly vetted before award. Due diligence typically includes ownership verification, sanctions screening, adverse media checks, and financial assessment. This question's purpose is to confirm that these checks have been completed or to identify when they are still outstanding.

The design is effective: a yes/no question with conditional follow-ups for both responses. If 'Yes', a summary of findings is requested. If 'No', a deadline for completion is required. This ensures that due diligence is either completed or scheduled, with no gaps. Making the question mandatory is essential because awarding a contract without due diligence is a significant governance failure.

From a data collection perspective, this produces binary data with conditional detail about due diligence status and findings. This is essential for compliance and audit. From a user experience standpoint, the question is quick and the follow-ups are contextually appropriate.

Question: I confirm that no undisclosed conflict of interest exists

The I confirm that no undisclosed conflict of interest exists between the evaluation team and any vendor under consideration checkbox is an ethical governance control that formalises the evaluator's declaration of impartiality. Conflicts of interest can undermine the integrity of the evaluation and expose the organisation to legal and reputational risk. This question's purpose is to create a formal attestation that can be referenced in the event of a challenge.

The design is simple but powerful: a single checkbox with a clear, unambiguous statement. Making this field mandatory is a strong governance control that creates accountability. The related question in the Final Recommendation section (about actual, potential, or perceived conflicts) provides an opportunity to disclose any conflicts that do exist.

From a data collection perspective, this produces a binary attestation that is essential for ethical compliance. From a user experience standpoint, this is a zero-effort field—a simple click—but its significance is substantial.

Section: Service Levels, Support, Delivery & After-Sales

This section evaluates what happens after the purchase order is raised—support quality, response times, delivery reliability, and warranty terms. These factors frequently determine the true success of a procurement decision and are often overlooked in price-focused evaluations. The section provides a comprehensive framework for assessing the ongoing relationship with the vendor.

Question: Support model offered by the recommended vendor

The Support model offered by the recommended vendor question captures the level of support the vendor will provide and is essential for assessing whether the vendor can meet the organisation's operational needs. A 24/7 support model is very different from a self-service portal, and the choice has significant implications for both cost and risk. This question's purpose is to document the support commitment and ensure it aligns with the organisation's requirements.

The design is comprehensive: a single-choice list covering the full spectrum of support models (24/7, business hours, on-call, regional, local partner, self-service, other). The conditional follow-ups for on-call and regional options capture additional details such as out-of-hours charges and support team locations. Making this field mandatory is appropriate because support capability is a critical factor in vendor selection.

From a data collection perspective, this produces categorical data that feeds into the service level assessment and the weighted scoring matrix. From a user experience standpoint, the single-choice format is quick and intuitive, and the conditional follow-ups are only shown when relevant.

Question: Warranty terms — duration, coverage, exclusions and claim process

The Warranty terms field captures the vendor's warranty commitment and is essential for understanding the post-purchase protection available to the organisation. Warranty terms vary significantly between vendors—one may offer a comprehensive 3-year warranty while another offers a limited 1-year warranty with numerous exclusions. This question's purpose is to document these differences and ensure they are factored into the evaluation.

The design uses a multiline text field, which provides sufficient space for detailed warranty terms. Making this field mandatory is appropriate because warranty is a significant value factor that affects the total cost of ownership. The field is well-placed in the service levels section, where post-purchase commitments are being assessed.

From a data collection perspective, this produces rich qualitative data about warranty coverage that is essential for TCO analysis and contract negotiation. From a user experience standpoint, this is a demanding field that requires careful review of the vendor's warranty documentation, but it is essential for a complete evaluation.

Section: Sustainability, Ethics & Social Responsibility

This section addresses the growing importance of environmental, ethical, and social considerations in procurement. The inclusion of sustainability criteria, ethics assessments, and carbon footprint tracking reflects modern procurement best practice and stakeholder expectations. The section is well-designed to capture both the criteria that are relevant to the procurement and the vendor's performance against them.

Question: Which sustainability criteria are relevant to this procurement?

The Which sustainability criteria are relevant to this procurement? question identifies the environmental and social factors that should be considered in the evaluation. Not all sustainability criteria are relevant to every procurement—for example, carbon footprint is more relevant for physical goods than for professional services. This question's purpose is to focus the sustainability assessment on the factors that matter most for the specific requirement.

The design is comprehensive: a multiple-choice list covering the major sustainability criteria (recycled content, carbon footprint, renewable energy, circular economy, ethical labour, local sourcing, packaging, certifications, take-back schemes, water/energy efficiency, ethical supply chain). The conditional follow-ups for carbon footprint and certifications capture specific quantitative data. This is well-designed for its purpose.

From a data collection perspective, this produces structured categorical data that enables targeted sustainability assessment. From a user experience standpoint, the multiple-choice format is efficient and the conditional follow-ups are only shown when relevant.

Question: Overall sustainability rating of the recommended vendor

The Overall sustainability rating of the recommended vendor question provides a summary assessment of the vendor's sustainability performance on a five-point scale from Leader to Poor. This single rating synthesises the detailed sustainability assessment into a clear, actionable indicator that can be used in the weighted scoring matrix. It is particularly useful for stakeholders who need a quick summary rather than detailed analysis.

The design is effective: a single-choice question with descriptive scale labels that clearly communicate the expected level of performance. The labels (Leader, Strong, Average, Developing, Poor) are intuitive and well-calibrated. This question is not mandatory, which is appropriate—sustainability may not be a primary criterion for every procurement.

From a data collection perspective, this produces ordinal data that feeds into the weighted scoring matrix. From a user experience standpoint, this is a quick question that summarises the preceding sustainability assessment.

Section: References, Track Record & Vendor Capability

This section captures independent evidence of past performance, which is one of the strongest predictors of future delivery. The client references table, the reference verification question, and the capability assessment provide a comprehensive view of the vendor's track record. The inclusion of a YouTube guidance video is a thoughtful touch that supports users in conducting effective reference checks.

Question: Client references provided by the vendor

The Client references provided by the vendor table captures the details of past clients who can vouch for the vendor's performance. The table includes client name, contact person, contact details, project value, year delivered, satisfaction rating, and whether they would recommend the vendor. This structured format enables efficient reference checking and provides a clear picture of the vendor's track record.

The design is excellent: the columns cover all the key data points needed for reference verification, and the sample rows demonstrate the expected level of detail. The inclusion of a satisfaction rating and a 'Would Recommend' column provides quick indicators of reference quality. The table format is efficient and enables easy comparison across references.

From a data collection perspective, this produces structured data about the vendor's past performance that is essential for risk assessment. It captures personal data (contact names and details) which requires appropriate data protection handling. From a user experience standpoint, the table format is familiar and the sample rows provide clear guidance.

Question: Have you personally contacted and verified the references?

The Have you personally contacted and verified the references? question is a critical governance control that ensures references are independently verified rather than taken at face value. Written testimonials supplied by the vendor may be selectively curated; direct contact with references provides more reliable evidence. This question's purpose is to confirm that independent verification has taken place.

The design is effective: a yes/no question with conditional follow-ups for both responses. If 'Yes', a summary of the feedback received is requested (and made mandatory). If 'No', the responsible person and deadline are captured. This ensures that reference verification is either completed or scheduled. Making the question mandatory is appropriate because unverified references should not be relied upon in a defensible evaluation.

From a data collection perspective, this produces binary data with conditional detail about reference verification. This is essential for audit and for ensuring the reliability of the reference evidence. From a user experience standpoint, the question is quick and the follow-ups are contextually appropriate.

Section: Site Visit, Demonstration & Vendor Presentation

This section captures first-hand observations from site visits, product demonstrations, or vendor presentations. While not always practical or necessary, these activities can provide valuable insights that are not available from written proposals alone. The section is well-designed to capture observations objectively and consistently across all vendors.

Question: Was a site visit, vendor presentation or product demonstration conducted?

The Was a site visit, vendor presentation or product demonstration conducted? question establishes whether first-hand verification was undertaken and provides context for the observations that follow. Site visits and demonstrations can reveal important information about the vendor's facilities, capabilities, and working practices that is not evident from written proposals.

The design is well-structured: a yes/no question with conditional follow-ups for both responses. If 'Yes', a detailed summary of the visit is requested (and made mandatory). If 'No', the reason is captured from a predefined list. This ensures that the absence of a site visit is justified and documented. The conditional logic keeps the form efficient while capturing the right information.

From a data collection perspective, this produces binary data with conditional narrative detail about site visits. This is valuable for audit and for providing context to the evaluation. From a user experience standpoint, the question is quick and the follow-ups are only shown when relevant.

Question: Did the demonstration or visit reveal any concerns?

The Did the demonstration or visit reveal any concerns? question surfaces any negative observations from the site visit or demonstration. This is important because first-hand observations may reveal risks or issues that are not apparent from written proposals. Identifying these concerns early allows them to be addressed through contract terms or mitigation measures.

The design is effective: a yes/no question with a mandatory follow-up when 'Yes' is selected. The follow-up asks for a description of each concern and how it could be addressed or mitigated. Making this follow-up mandatory ensures that identified concerns are documented and addressed. This is consistent with best practice in risk management.

From a data collection perspective, this produces binary data with conditional narrative detail about identified concerns. This is valuable for risk assessment and contract negotiation. From a user experience standpoint, the question is quick and the follow-up is only triggered when relevant.

Section: Weighted Evaluation & Selection Scoring Matrix

This section is the analytical engine of the form—it applies the agreed weighting to each criterion and scores every vendor consistently to produce a ranked outcome. The weighted scoring matrix with automatic calculations, the comparative assessment matrices, and the vendor preference ranking provide a rigorous, transparent framework for the final selection decision.

Question: Weighted vendor scoring matrix

The Weighted vendor scoring matrix table is the centrepiece of the evaluation and the mechanism by which all the preceding analysis is synthesised into a single, comparable score for each vendor. The table captures each evaluation criterion, its weight, the score for each vendor, and the calculated weighted score. The automatic calculation (Weight × Score) eliminates arithmetic errors and ensures consistency. The sample data rows demonstrate how different vendors perform across different criteria.

The design is exemplary: the columns cover all the key dimensions, and the formula-based calculations ensure accuracy and consistency. The inclusion of sustainability as a weighted criterion (even at a low weight) reflects modern procurement best practice. The total weighting must equal 100 percent, which is enforced by a mandatory field. This is one of the strongest analytical tools in the form.

From a data collection perspective, this table produces structured scoring data that directly drives the final selection decision. The weighted scores enable objective, transparent comparison across vendors. From a user experience standpoint, the table format is efficient and the automatic calculations reduce effort and errors. The sample rows provide clear guidance on expected input.

Question: Rank the vendors in order of overall preference

The Rank the vendors in order of overall preference (best first) question captures the evaluator's subjective overall preference, which may or may not align with the weighted scores. This is valuable because it can reveal discrepancies between the calculated outcome and the evaluator's professional judgement, prompting further discussion or investigation. The inclusion of a 'No suitable vendor — re-tender required' option is a thoughtful addition that provides an escape hatch if none of the vendors are acceptable.

The design uses a ranking question type, which is appropriate for capturing relative preference. The items include the three vendors and the re-tender option. This question is not mandatory, which is reasonable—the weighted scores should be the primary basis for the decision, with the ranking serving as a secondary check.

From a data collection perspective, this produces ordinal data that can be compared against the weighted scores to identify discrepancies. From a user experience standpoint, the ranking format is intuitive and quick.

Section: Final Recommendation, Award & Approvals

This section documents the outcome of the evaluation, the rationale for the recommendation, and the approvals obtained. It is the formal record of the decision and may be required for audit, governance, or dispute resolution. The section is well-designed to capture all the key elements of a defensible award decision.

Question: Recommended outcome of this evaluation

The Recommended outcome of this evaluation question captures the final decision—whether to award to a specific vendor, split the award, re-tender, or take other action. This is the culmination of the entire evaluation process and the single most important output of the form. The question's purpose is to formalise the recommendation in a clear, unambiguous format.

The design is comprehensive: a single-choice list covering the main outcomes (award to Vendor A, B, or C, split award, no award/re-tender, other). The conditional follow-ups for split award and no award capture the rationale for these less common outcomes. Making this field mandatory is essential because the form must produce a clear recommendation.

From a data collection perspective, this produces categorical data that is the primary output of the evaluation. It enables tracking of award decisions and outcomes. From a user experience standpoint, the single-choice format is quick and unambiguous.

Question: Rationale for the recommendation

The Rationale for the recommendation — summarise the key evidence supporting this decision field is the narrative justification for the award decision and is arguably the most important qualitative field in the form. It connects the quantitative analysis (weighted scores, TCO, pricing) with the qualitative assessment (quality, risk, references) to explain why the recommended vendor was chosen. This rationale is the primary evidence in the event of a challenge or audit.

The design uses a multiline text field, which provides sufficient space for a comprehensive rationale. Making this field mandatory is essential because a recommendation without a rationale is indefensible. The field is well-placed after the recommended outcome and award value, creating a logical flow from decision to justification.

From a data collection perspective, this produces rich qualitative data that is essential for audit, governance, and dispute resolution. It is the narrative thread that ties the entire evaluation together. From a user experience standpoint, this is a demanding field that requires careful thought and synthesis of the preceding analysis, but it is essential for a defensible decision.

Question: Approval and sign-off record

The Approval and sign-off record table captures the formal approvals obtained for the recommendation, including the approver's name, role, approval status, date, and any conditions. This is essential for governance—it demonstrates that the recommendation has been reviewed and approved by the appropriate authorities. The sample data rows show a multi-level approval process involving the requestor, procurement lead, and finance business partner.

The design is excellent: the columns capture all the key approval data points, and the sample rows demonstrate the expected level of detail. The inclusion of a 'Comments or Conditions' column allows approvers to record caveats or requirements, which is important for contract negotiation. The table format is efficient and enables easy tracking of the approval workflow.

From a data collection perspective, this produces structured approval data that is essential for governance and audit. From a user experience standpoint, the table format is familiar and efficient. The sample rows provide clear guidance.

Section: Declarations, Data Handling & Record Retention

This closing section captures the formal declarations that underpin the integrity of the evaluation, along with data handling and record retention arrangements. The declaration checkboxes create a formal attestation of accuracy, confidentiality, and fairness that is essential for governance and compliance. The data handling questions ensure that personal data is managed appropriately.

Question: I confirm the information provided in this form is accurate and complete

The I confirm the information provided in this form is accurate and complete to the best of my knowledge checkbox is the foundational declaration that underpins the entire evaluation record. Without this attestation, the form is merely a collection of data points; with it, it becomes a formal, accountable document. This question's purpose is to create a clear statement of accuracy that can be referenced in the event of a challenge.

The design is simple but powerful: a single checkbox with a clear, unambiguous statement. Making this field mandatory is essential because it creates accountability and a formal audit trail. The phrase 'to the best of my knowledge' is appropriately qualified, recognising that absolute certainty is not always possible.

From a data collection perspective, this produces a binary attestation that is essential for governance and compliance. From a user experience standpoint, this is a zero-effort field—a simple click—but its significance is substantial.

Question: I confirm that no confidential pricing or commercially sensitive information has been shared between competing vendors

The I confirm that no confidential pricing or commercially sensitive information has been shared between competing vendors checkbox is an ethical and legal declaration that protects the integrity of the competitive process. Sharing confidential pricing between competitors can constitute collusion, which is illegal in many jurisdictions and can invalidate the procurement. This question's purpose is to create a formal attestation that the competitive process was conducted fairly.

The design is clear and unambiguous. Making this field mandatory is essential because price confidentiality is a fundamental principle of competitive procurement. This declaration protects both the organisation and the individual evaluator.

From a data collection perspective, this produces a binary attestation that is essential for legal compliance. From a user experience standpoint, this is a zero-effort field with significant legal significance.

Question: I confirm that all vendors were given equal access to information and an equal opportunity to respond

The I confirm that all vendors were given equal access to information and an equal opportunity to respond checkbox is a fairness declaration that ensures the competitive process was conducted on a level playing field. Unequal access to information can give certain vendors an unfair advantage and can be challenged by unsuccessful bidders. This question's purpose is to create a formal attestation of procedural fairness.

The design is clear and consistent with the other declaration checkboxes. Making this field mandatory is essential because fairness is a fundamental requirement of competitive procurement. Together with the other declarations, it creates a comprehensive attestation of the evaluation's integrity.

From a data collection perspective, this produces a binary attestation that is essential for governance and legal compliance. From a user experience standpoint, this is a zero-effort field with significant governance significance.

Overall Strengths and Weaknesses Summary

The Vendor Price Comparison & Selection Matrix is one of the most comprehensive and well-designed procurement evaluation tools available. Its strengths are numerous: end-to-end coverage from intake to declarations; sophisticated conditional logic that adapts to the user's context; automatic calculations in pricing tables, risk registers, and scoring matrices; strong governance controls through mandatory fields and attestation checkboxes; and a balanced approach that combines quantitative analysis with qualitative assessment. The form is designed for professional procurement use and reflects deep domain expertise in sourcing, evaluation, and vendor management. The inclusion of TCO analysis, risk registers, sustainability assessments, and weighted scoring matrices elevates it far beyond a simple price comparison tool.

The form's primary weakness is its sheer length and complexity. With over 200 fields across 12 sections, completing this form is a significant undertaking that could take several hours for a complex procurement. This could lead to user fatigue, incomplete responses, or abandonment—particularly for simpler procurements where the full depth of analysis may not be warranted. A potential improvement would be to introduce a tiered approach, where simpler procurements use a condensed version of the form and only complex or high-value procurements trigger the full analysis. Additionally, some sections (such as the vendor profile for Vendor A) could benefit from a multi-vendor approach that captures profiles for all vendors being compared, rather than focusing on a single primary candidate. Despite these considerations, the form is an outstanding tool for organisations that require rigorous, defensible procurement decisions.

Mandatory Question Analysis for Vendor Price Comparison & Selection Matrix | Supplier Evaluation & Award Form

Mandatory Question Justifications

Procurement/project reference number
Justification: This field is the unique identifier that links the entire evaluation record to the organisation's procurement system, purchase orders, and contract files. Without a reference number, the form becomes an orphan document that cannot be located, cross-referenced, or defended during an audit. It is essential for data integrity, traceability, and compliance with procurement governance policies. Making this field mandatory ensures that every evaluation record is properly indexed and retrievable.

Project or requirement title
Justification: The project title provides the human-readable context that makes the form self-documenting. It is essential for anyone reviewing the record to quickly understand the subject matter without having to read the entire form. A clear title also supports categorisation, searchability, and portfolio-level reporting. Making this field mandatory prevents the creation of evaluation records that are difficult to identify or understand.

Requesting department, business unit or cost centre
Justification: This field is essential for budget attribution, cost tracking, and organisational accountability. It ensures that the procurement cost is allocated to the correct budget line and that the requesting function is clearly identified for follow-up queries or approval routing. Without this field, financial governance and spend analytics would be compromised. Making this field mandatory is a fundamental financial control.

Requestor name and job title
Justification: Identifying the requestor is essential for accountability, communication, and approval workflows. In the event of a query, dispute, or audit, the requestor is the primary point of contact who can explain the business need and justify the evaluation criteria. The job title provides important context about the requestor's authority and seniority. Making this field mandatory ensures that no procurement request is anonymous or unaccountable.

Requestor email address
Justification: The email address is the primary communication channel for the entire procurement process, including notifications, clarifications, approval routing, and outcome communication. Without a valid email address, the digital workflow that modern procurement depends upon would stall at multiple points. Making this field mandatory is essential for process continuity and effective communication.

Date this comparison exercise commenced
Justification: The commencement date is the temporal anchor for the entire evaluation and is essential for measuring process duration, identifying bottlenecks, and ensuring compliance with quotation validity periods and procurement timelines. Without this date, it would be impossible to assess whether the evaluation was conducted within acceptable timeframes. Making this field mandatory ensures that the evaluation timeline is properly documented.

Procurement category
Justification: The procurement category determines which evaluation criteria are relevant, which regulatory frameworks apply, and how the procurement should be managed. It also triggers category-specific follow-up questions that capture essential details. Without this classification, the evaluation framework cannot be properly calibrated. Making this field mandatory is essential because the entire analytical approach depends on knowing the type of procurement.

Sourcing method used to obtain the quotations
Justification: The sourcing method documents how the competitive process was conducted and is essential for demonstrating compliance with procurement policies and regulations. Different methods carry different governance requirements—open tenders require public notices, while direct awards require documented justification. Making this field mandatory ensures that the procedural legitimacy of the exercise is established and that any non-competitive methods are properly justified.

Approved budget ceiling for this requirement
Justification: The budget ceiling is a critical financial governance control that defines the maximum authorised spend. It provides the benchmark against which quoted prices are assessed and ensures that the evaluation stays within approved financial boundaries. Without this field, there would be no way to assess whether the recommended award is affordable or requires escalation. Making this field mandatory is a fundamental budgetary control.

Business need and problem statement — what outcome must this purchase deliver?
Justification: This is the foundational question of the entire form—it articulates why the procurement exists and what outcome it must deliver. Every evaluation criterion, scoring decision, and vendor selection rationale flows from this statement. Without a clear problem statement, the evaluation becomes a price comparison exercise rather than a value-based decision. Making this field mandatory ensures that the evaluation is grounded in a well-defined business need.

Detailed technical or functional specification
Justification: The specification defines the precise requirements that vendors must meet and is the benchmark against which all proposals are assessed. Without a detailed specification, vendors may quote for different scopes, making price comparison meaningless. The specification also serves as the basis for contract terms and acceptance criteria. Making this field mandatory ensures that the comparison is like-for-like and that the evaluation is conducted against defined requirements.

Which mandatory (must-have) requirements apply?
Justification: This question establishes the pass/fail criteria that determine vendor eligibility and prevents evaluators from selecting a vendor that fails fundamental requirements simply because they offered the lowest price. The distinction between mandatory and desirable criteria is a cornerstone of fair procurement evaluation. Making this field mandatory ensures that eligibility thresholds are clearly defined and consistently applied.

I confirm the specification has been reviewed and approved by the technical owner before quotations were requested
Justification: This attestation ensures that the specification has been validated by the appropriate technical authority before the procurement process began. It prevents situations where vendors are invited to quote against an unreviewed or incorrect specification, which would waste time and potentially lead to an unsuitable award. Making this field mandatory creates formal accountability for the specification review process.

Number of vendors invited to quote or tender
Justification: The number of vendors invited is a fundamental indicator of the competitive breadth of the procurement. Most procurement policies require a minimum number of invitations to ensure genuine competition. Without this field, there would be no way to assess whether the procurement was genuinely competitive or effectively sole-source. Making this field mandatory ensures that competition levels are documented and auditable.

Number of quotations or bids received
Justification: The number of quotations received indicates actual market interest and, when compared with the number invited, provides a response rate that reveals the health of the competitive process. A low response rate may indicate issues with the specification, budget, or market. Making this field mandatory ensures that the level of actual competition is documented and can be assessed alongside the invitation count.

Primary vendor under evaluation (Vendor A) — legal entity name
Justification: The legal entity name of the primary vendor is essential for contract execution, due diligence, and vendor management. The form cannot proceed with a detailed evaluation without knowing which vendor is being assessed. Making this field mandatory ensures that the evaluation has a clear subject and that the vendor is properly identified for all downstream processes.

Has every vendor submitted all required documentation (quote, terms, certifications, financials)?
Justification: Documentation completeness is a prerequisite for a fair comparison—incomplete submissions can lead to biased evaluations where more thorough vendors appear stronger simply because they provided more information. This question identifies and addresses documentation gaps before the evaluation proceeds. Making this field mandatory ensures that the evaluation is based on complete information and that any gaps are tracked and resolved.

Sub-total of all quoted lines (before tax and additional charges)
Justification: The sub-total is the foundation of the price comparison and must be accurate and complete to ensure a fair like-for-like assessment. It feeds into the total quoted price and the TCO calculation. Without this field, the financial comparison would be incomplete. Making this field mandatory ensures that the pricing analysis has a solid numerical foundation.

Total quoted price (all inclusive)
Justification: The total quoted price is the single most important financial figure in the comparison and the primary input for the weighted scoring matrix. It must reflect the true all-inclusive cost to enable fair comparison across vendors. Without this field, the evaluation cannot proceed to the scoring stage. Making this field mandatory is essential for the integrity of the financial comparison.

Quotation validity period
Justification: The quotation validity period determines how long the quoted prices remain firm and is essential for managing the evaluation timeline. If the validity period expires before a decision is made, the prices may no longer be available, requiring re-negotiation or re-tendering. Making this field mandatory ensures that time constraints are known and managed.

Is the quoted price fixed for the full contract term?
Justification: Price fixity is a critical factor in the total cost of ownership—a low initial price with aggressive indexation can end up costing more than a higher fixed price. This question surfaces price volatility risk and ensures that the comparison accounts for the full contract duration. Making this field mandatory prevents hidden price escalation from being overlooked in the evaluation.

Estimated total cost of ownership over 3 years
Justification: The 3-year TCO is the headline metric that summarises the full lifecycle cost of the recommended vendor and is the primary input for the value-based comparison. It captures costs beyond the initial purchase price, including maintenance, consumables, training, and renewal fees. Making this field mandatory ensures that the evaluation reflects the true cost of the procurement, not just the purchase price.

List the assumptions used in the TCO calculation (volumes, growth rates, inflation, utilisation, exchange rates)
Justification: Documented assumptions are essential for the auditability and defensibility of the TCO analysis. Without them, the TCO figure is just a number with no context, and it cannot be re-evaluated if circumstances change. Making this field mandatory ensures that the TCO analysis is transparent, reproducible, and can withstand scrutiny during an audit or challenge.

Does the proposal fully meet every mandatory requirement?
Justification: This is a critical pass/fail gate that determines vendor eligibility. If a vendor fails to meet a mandatory requirement, they should normally be excluded regardless of price or other strengths. Making this field mandatory ensures that the mandatory criteria defined earlier in the form are actively enforced and that any waivers are documented and justified.

Has a due diligence or background check been completed on the recommended vendor?
Justification: Due diligence is a fundamental governance requirement before awarding a contract. It includes ownership verification, sanctions screening, adverse media checks, and financial assessment. Awarding a contract without due diligence exposes the organisation to significant legal, financial, and reputational risk. Making this field mandatory ensures that the recommended vendor has been properly vetted or that a clear plan for completion is in place.

I confirm that no undisclosed conflict of interest exists between the evaluation team and any vendor under consideration
Justification: This ethical declaration creates a formal attestation of evaluator impartiality and is essential for the integrity of the procurement process. Conflicts of interest can undermine the evaluation and expose the organisation to legal and reputational risk. Making this field mandatory creates accountability and provides a clear audit trail of the evaluator's declaration.

Support model offered by the recommended vendor
Justification: The support model is a critical factor in vendor selection because it determines the level of ongoing service the organisation will receive. A mismatch between the vendor's support model and the organisation's operational needs can lead to significant disruption and cost. Making this field mandatory ensures that support capability is explicitly assessed and documented as part of the evaluation.

Quoted lead time from order to delivery (days)
Justification: Lead time is a critical operational parameter that determines whether the vendor can meet the organisation's delivery requirements. A vendor with an excellent product but a 6-month lead time may be unsuitable for a time-critical procurement. Making this field mandatory ensures that delivery capability is explicitly assessed and factored into the weighted scoring matrix.

Warranty terms — duration, coverage, exclusions and claim process
Justification: Warranty terms significantly affect the total cost of ownership and the level of post-purchase protection available to the organisation. Warranty coverage varies widely between vendors and can be a major differentiator. Making this field mandatory ensures that warranty is explicitly assessed and that any differences between vendors are captured and considered in the evaluation.

Number of years the vendor has supplied this category of goods or services
Justification: The vendor's experience in the specific category is a strong predictor of their ability to deliver successfully. A vendor with deep category experience is more likely to understand the requirements, anticipate challenges, and deliver a high-quality outcome. Making this field mandatory ensures that vendor experience is explicitly assessed as part of the track record evaluation.

Have you personally contacted and verified the references?
Justification: Independent reference verification is essential for ensuring the reliability of the reference evidence. Written testimonials supplied by the vendor may be selectively curated, while direct contact provides more objective evidence of past performance. Making this field mandatory ensures that references are either independently verified or that a clear plan for verification is in place before the award decision.

Total weighting applied (must equal 100)
Justification: The total weighting must equal 100 percent to ensure that the weighted scoring matrix is mathematically valid and that the scores are comparable across vendors. An incorrect total would invalidate the entire scoring analysis. Making this field mandatory is a critical data integrity control that prevents mathematical errors in the evaluation.

Recommended outcome of this evaluation
Justification: The recommended outcome is the primary output of the entire evaluation process and must be clearly stated. Without a clear recommendation, the form fails in its fundamental purpose. Making this field mandatory ensures that the evaluation produces a definitive, actionable outcome that can be communicated to stakeholders and acted upon.

Total award value (excluding tax)
Justification: The award value is the financial commitment that the organisation is making and must be clearly documented for budget approval, contract execution, and financial reporting. It is the key figure that connects the evaluation to the organisation's financial systems. Making this field mandatory ensures that the financial commitment is explicitly stated and can be verified against the approved budget ceiling.

Rationale for the recommendation — summarise the key evidence supporting this decision
Justification: The rationale is the narrative justification that connects the quantitative analysis with the qualitative assessment to explain why the recommended vendor was chosen. It is the primary evidence in the event of a challenge, audit, or dispute. Without a clear rationale, the recommendation is indefensible. Making this field mandatory ensures that every award decision is supported by documented evidence and reasoning.

Authorised signature of the approving manager
Justification: The authorised signature is the formal act of approval that gives the recommendation legal and organisational authority. Without it, the evaluation is merely a recommendation with no binding effect. Making this field mandatory ensures that the award decision has been formally authorised by an individual with the appropriate authority.

Name of the signatory
Justification: The signatory's name identifies the individual who formally approved the recommendation and is essential for accountability and audit purposes. A signature without a name is incomplete and cannot be verified. Making this field mandatory ensures that the approval record is complete and traceable.

Position or title of the signatory
Justification: The signatory's position or title confirms that the individual who approved the recommendation had the appropriate authority to do so. This is essential for governance compliance—approvals must be given by individuals with delegated authority. Making this field mandatory ensures that the approval authority can be verified.

Date signed
Justification: The date of signature establishes when the approval was given and is essential for the audit trail. It enables the organisation to track the timeline of the approval process and to verify that the approval was given before any commitments were made. Making this field mandatory ensures that the approval record is temporally complete.

I confirm the information provided in this form is accurate and complete to the best of my knowledge
Justification: This foundational attestation creates formal accountability for the accuracy of the entire evaluation record. Without it, the form is merely a collection of data points with no assurance of reliability. Making this field mandatory ensures that the evaluator takes personal responsibility for the quality and integrity of the information provided.

I confirm that no confidential pricing or commercially sensitive information has been shared between competing vendors
Justification: Price confidentiality is a fundamental principle of competitive procurement, and sharing confidential pricing between competitors can constitute collusion, which is illegal in many jurisdictions. This declaration protects both the organisation and the individual evaluator from legal exposure. Making this field mandatory ensures that this critical ethical and legal standard is formally acknowledged.

I confirm that all vendors were given equal access to information and an equal opportunity to respond
Justification: Procedural fairness is a fundamental requirement of competitive procurement. Unequal access to information can give certain vendors an unfair advantage and can be challenged by unsuccessful bidders. This declaration creates a formal attestation that the competitive process was conducted on a level playing field. Making this field mandatory ensures that fairness is explicitly confirmed and documented.

Overall Mandatory Field Strategy Recommendation

The Vendor Price Comparison & Selection Matrix employs a robust mandatory field strategy that prioritises governance-critical data while allowing flexibility for supplementary information. With approximately 40 mandatory top-level fields and numerous conditional mandatory follow-ups, the form ensures that all essential data points are captured without requiring users to complete every field. The conditional mandatory logic is particularly effective—fields such as the sole-source justification, price adjustment mechanism, and conflict of interest description only become mandatory when the triggering condition is met. This approach maximises data quality for critical fields while minimising unnecessary friction for users. The mandatory fields are well-distributed across all sections, ensuring that no section is left without essential data. The attestation checkboxes in the Declarations section are appropriately mandatory because they create the formal accountability framework that underpins the entire evaluation record.

However, the sheer number of mandatory fields—particularly in the intake and specification sections—could present a barrier for simpler procurements where the full depth of analysis may not be warranted. A strategic improvement would be to introduce a tiered mandatory field approach, where the number of mandatory fields scales with the procurement value or complexity. For example, procurements below a certain threshold could use a condensed version with fewer mandatory fields, while high-value or high-risk procurements trigger the full set. Additionally, some fields that are currently mandatory could be made conditionally mandatory based on user input—for instance, the warranty terms field could be mandatory only for goods and physical products, not for professional services. The form would also benefit from a progress indicator that shows users how many mandatory fields remain, reducing the risk of abandonment near the end of the form. Overall, the mandatory field strategy is well-designed for a professional procurement tool, but a tiered approach would improve completion rates for simpler exercises while maintaining rigour for complex ones.

To configure an element, select it on the form.

To add a new question or element, click the Question & Element button in the vertical toolbar on the left.

Vendor Price Comparison & Selection Matrix | Supplier Evaluation & Award Form

1. Procurement Project Overview & Intake

2. Requirements, Specification & Evaluation Criteria Definition

3. Vendor Identification & Bidder Register

4. Price Comparison — Line-by-Line Cost Breakdown

5. Total Cost of Ownership (TCO) & Hidden Cost Analysis

6. Quality, Technical Fit & Compliance Assessment

7. Vendor Risk, Financial Stability & Due Diligence

8. Service Levels, Support, Delivery & After-Sales

9. Sustainability, Ethics & Social Responsibility

10. References, Track Record & Vendor Capability

11. Site Visit, Demonstration & Vendor Presentation

12. Weighted Evaluation & Selection Scoring Matrix

13. Final Recommendation, Award & Approvals

14. Declarations, Data Handling & Record Retention

Analysis for Vendor Price Comparison & Selection Matrix | Supplier Evaluation & Award Formkeyboard_arrow_down

Overall Form Analysis — Vendor Price Comparison & Selection Matrix

Section: Procurement Project Overview & Intake

Question: Procurement/project reference number

Question: Project or requirement title

Question: Requesting department, business unit or cost centre

Question: Requestor name and job title

Question: Requestor email address

Question: Date this comparison exercise commenced

Question: Procurement category

Question: Sourcing method used to obtain the quotations

Question: Approved budget ceiling for this requirement

Question: Is this a repeat purchase of a previously sourced item or service?

Question: Is this requirement time-critical?

Section: Requirements, Specification & Evaluation Criteria Definition

Question: Business need and problem statement — what outcome must this purchase deliver?

Question: Detailed technical or functional specification

Question: Which mandatory (must-have) requirements apply?

Question: Rank the following evaluation dimensions in order of importance

Question: I confirm the specification has been reviewed and approved by the technical owner

Section: Vendor Identification & Bidder Register

Question: Number of vendors invited to quote or tender

Question: Number of quotations or bids received

Question: Vendor register — all invited and responding vendors

Question: Primary vendor under evaluation (Vendor A) — legal entity name

Question: Has every vendor submitted all required documentation?

Question: Was any vendor excluded from the comparison?

Section: Price Comparison — Line-by-Line Cost Breakdown

Question: Quoted price breakdown (per vendor)

Question: Total quoted price (all inclusive)

Question: Is the quoted price fixed for the full contract term?

Question: Which cost elements are INCLUDED/EXCLUDED from the quoted price?

Section: Total Cost of Ownership (TCO) & Hidden Cost Analysis

Question: Total cost of ownership comparison across vendors

Question: Estimated total cost of ownership over 3 years

Question: List the assumptions used in the TCO calculation

Question: Does any vendor's pricing create a dependency or lock-in risk?

Section: Quality, Technical Fit & Compliance Assessment

Question: Rate each vendor's proposal against quality and technical criteria

Question: Does the proposal fully meet every mandatory requirement?

Question: Has any vendor been subject to litigation, regulatory sanctions, product recalls or major quality failures?

Section: Vendor Risk, Financial Stability & Due Diligence

Question: Risk register and mitigation plan

Question: Has a due diligence or background check been completed on the recommended vendor?

Question: I confirm that no undisclosed conflict of interest exists

Section: Service Levels, Support, Delivery & After-Sales

Question: Support model offered by the recommended vendor

Question: Warranty terms — duration, coverage, exclusions and claim process

Section: Sustainability, Ethics & Social Responsibility

Question: Which sustainability criteria are relevant to this procurement?

Question: Overall sustainability rating of the recommended vendor

Section: References, Track Record & Vendor Capability

Question: Client references provided by the vendor

Question: Have you personally contacted and verified the references?

Section: Site Visit, Demonstration & Vendor Presentation

Question: Was a site visit, vendor presentation or product demonstration conducted?

Question: Did the demonstration or visit reveal any concerns?

Section: Weighted Evaluation & Selection Scoring Matrix

Question: Weighted vendor scoring matrix

Question: Rank the vendors in order of overall preference

Section: Final Recommendation, Award & Approvals

Question: Recommended outcome of this evaluation

Question: Rationale for the recommendation

Question: Approval and sign-off record

Section: Declarations, Data Handling & Record Retention

Analysis for Vendor Price Comparison & Selection Matrix | Supplier Evaluation & Award Form

Mandatory Question Analysis for Vendor Price Comparison & Selection Matrix | Supplier Evaluation & Award Form