RFP Evaluation Criteria: How to Score Supplier Proposals Fairly

Choosing a supplier through an RFP should not come down to who gave the slickest presentation or the cheapest headline price. A fair evaluation process helps your team compare proposals consistently, defend the final decision internally, and reduce the risk of selecting a supplier that looks good on paper but performs poorly after award.

Quick answer

To score supplier proposals fairly, start by defining clear evaluation criteria before you issue the RFP, then assign weightings based on business priorities such as technical fit, total cost, service capability, compliance, and implementation risk. Use a standard scoring matrix, involve the right cross-functional evaluators, require evidence for every score, and separate mandatory pass/fail requirements from weighted criteria. The goal is not just to find the lowest bid, but the supplier that offers the best overall value with the least delivery and operational risk.

Why fair RFP scoring matters

A structured evaluation process does more than make procurement look organised. It protects the business in practical ways:

• It reduces personal bias and inconsistent judgement.
• It gives finance, operations, users and procurement a shared basis for decision-making.
• It makes it easier to explain why one supplier was selected over another.
• It helps identify hidden costs, service gaps and implementation risks early.
• It creates an audit trail that is useful for governance and internal review.

For Malaysian businesses, this is especially important when purchases must satisfy internal approval thresholds, vendor onboarding checks, budget controls, and tax documentation requirements. If a decision is challenged later, a documented scoring model is far easier to defend than a vague statement that one proposal simply "felt better".

Start with evaluation principles before you build the scorecard

Before listing criteria, align your team on a few ground rules.

1. Score against business outcomes, not supplier popularity

Your criteria should reflect what the business actually needs:

• reliable supply
• acceptable quality
• operational fit
• manageable implementation
• commercial value
• compliance with internal and external requirements

This sounds obvious, but many RFPs still overweight presentation style or underweight fulfilment capability.

2. Separate mandatory requirements from scored criteria

Not everything should be weighted. Some items are non-negotiable and should be treated as pass/fail, such as:

• required licences or registrations
• ability to issue compliant invoices
• acceptance of key contract terms
• minimum technical or service requirements
• required insurance or safety documentation, where relevant
• onboarding documents such as company registration and tax details

In some categories, teams may also check whether the supplier is MOF-registered or meets other category-specific compliance expectations. If something is truly mandatory, do not bury it inside a weighted score.

3. Define scoring rules before proposals arrive

If the team decides what matters only after seeing supplier responses, bias can easily creep in. Set the criteria, weightings and scoring scale in advance and circulate them to evaluators before submissions are reviewed.

The core RFP evaluation criteria most teams should consider

The exact mix depends on the category, but most RFPs benefit from evaluating suppliers across these areas.

Technical and functional fit

This measures whether the proposal actually meets your specification.

Consider:

• compliance with required specifications
• ability to meet performance standards
• product or service suitability for your use case
• compatibility with existing systems or processes
• quality assurance approach

For services, this may include methodology, staffing model or deliverables. For goods, it may include technical specifications, approved brands, packaging requirements or substitutions policy.

Commercial value and total cost

Price matters, but fair scoring should go beyond the cheapest quoted unit rate.

Look at:

• quoted price
• total cost of ownership
• delivery charges
• implementation or setup costs
• maintenance or support fees
• payment terms
• rebate or volume pricing structures, if relevant

A supplier with a lower quote may still cost more over time if the service model is weak or delivery charges are high. In Malaysia, make sure your commercial comparison is consistent on SST treatment and any other applicable taxes or fees.

Service capability and operational support

A proposal may look attractive commercially but fail in day-to-day execution.

Evaluate:

• service coverage and support model
• order fulfilment process
• lead times
• escalation handling
• account management approach
• reporting capability
• training or user support

This area is often critical for indirect procurement categories where internal users depend on easy reordering, responsive support and predictable delivery.

Supplier capability and capacity

You are not only buying a product or service. You are buying the supplier's ability to deliver consistently.

Assess:

• operational capacity
• relevant category experience
• supply continuity planning
• subcontracting approach
• warehousing or stockholding model, if relevant
• financial stability indicators where appropriate
• key personnel and organisational capability

The right level of diligence depends on the size and criticality of the contract.

Risk and compliance

A fair process should account for supplier risk, not just promise quality.

This may include:

• regulatory compliance
• data handling and security, where relevant
• health, safety and environmental requirements
• anti-bribery or code-of-conduct acceptance
• ability to provide required business documents
• dispute history or material delivery issues, if documented

If the purchase involves recurring invoicing, check whether the supplier can support your documentation and finance controls, including the information your finance team needs for LHDN record-keeping.

Implementation and transition

If switching suppliers is disruptive, implementation quality deserves its own score.

Review:

• transition plan
• implementation timeline
• resource commitment
• risk mitigation approach
• user onboarding or training plan
• continuity during cutover

This criterion is especially useful for service contracts, managed supply arrangements and higher-value operational purchases.

A practical example of an RFP scoring matrix

Below is a simple structure that many procurement teams can adapt.

Evaluation areaTypical useExample weightingNotesMandatory compliancePass/fail screeningNot weightedRemove non-compliant bids before scoringTechnical fitSpecifications and scope match25-35%Define what "meets" versus "exceeds" meansCommercial valuePrice and total cost20-30%Compare on a like-for-like basisService capabilityDelivery, support, responsiveness15-25%Important for recurring purchasesSupplier capabilityCapacity, experience, continuity10-20%Useful for critical categoriesRisk and complianceOperational and regulatory risk5-15%May be weighted higher in sensitive categoriesImplementationTransition and rollout5-15%More relevant when switching is complex

The exact percentages should reflect business priorities. For a highly standard commodity item, commercial value may carry more weight. For a specialised service, technical fit and delivery capability may matter more than price.

How to assign weightings fairly

Weightings are where many evaluation models become distorted. A fair weighting model should reflect the consequences of getting a criterion wrong.

Ask these questions when weighting criteria

1. If this supplier fails in this area, what happens to the business?
2. Is the impact financial, operational, compliance-related, or reputational?
3. Can the weakness be fixed later, or is it hard to recover from?
4. Is this criterion genuinely important, or just nice to have?

For example:

• If delayed delivery would halt operations, service reliability should carry meaningful weight.
• If the item is highly standardised, technical fit may be simpler and less heavily weighted.
• If the contract touches sensitive systems or regulated processes, compliance and risk may need stronger weighting.

Avoid these common weighting mistakes

• giving price too much weight when service failure is costly
• assigning similar weights to criteria of very different importance
• including too many low-value criteria that clutter the model
• overweighting presentation performance
• adjusting weights after reading proposals

Choose a scoring scale and define it clearly

A scoring scale only works if evaluators interpret it the same way.

A simple 5-point scale works well

For many RFPs, use a scale such as:

• 1 = poor or does not meet requirement
• 2 = partially meets requirement with significant concerns
• 3 = meets requirement adequately
• 4 = exceeds requirement in a meaningful way
• 5 = clearly exceeds requirement with strong supporting evidence

You can also use a 10-point scale if your team is experienced, but more granularity does not automatically mean better judgement.

Define what good evidence looks like

Ask evaluators to score based on proof, not impression. Examples of evidence include:

• documented process descriptions
• sample service levels
• implementation plans
• product specifications
• referenceable case examples
• pricing schedules
• site visit findings
• demonstration results

If a supplier makes a claim without support, the score should reflect that uncertainty.

How to run the evaluation process step by step

A fair result depends as much on process discipline as on the scorecard itself.

1. Build the scorecard before issuing the RFP

Document:

• criteria
• sub-criteria
• weightings
• pass/fail requirements
• scoring scale
• evaluator roles

This should be approved internally before supplier responses come in.

2. Screen for mandatory compliance first

Before weighted scoring, remove proposals that fail essential requirements. This avoids wasting time and prevents a commercially attractive but non-compliant bid from distorting the discussion.

3. Use cross-functional evaluators

A balanced panel often includes:

• procurement for process and commercial comparison
• operations or end users for practical suitability
• finance for cost clarity and payment implications
• IT, legal, quality or HSE where relevant

Not every stakeholder needs to score every section. Some teams assign sections to subject-matter owners, then consolidate results through procurement.

4. Score independently before group discussion

Have evaluators review proposals individually first. This reduces groupthink and the risk that the most senior voice dominates the room.

5. Hold a moderation session

After independent scoring, discuss major scoring differences. The aim is not forced agreement, but alignment on evidence and interpretation.

Good moderation questions include:

• What evidence supports this score?
• Did we compare suppliers on the same basis?
• Are we scoring the written response or making assumptions?
• Is this concern already covered elsewhere in the matrix?

6. Clarify, but do not coach

If proposals are unclear, ask suppliers structured clarification questions. Give the same opportunity where needed and document responses. Avoid telling a supplier how to improve its bid in a way that creates unfair advantage.

7. Calculate weighted scores and test the outcome

Once scores are finalised, review the ranking critically:

• Does the top-ranked supplier also make sense qualitatively?
• Is one criterion overpowering the result unfairly?
• Did any supplier win largely on headline price while carrying obvious delivery risk?

If the outcome seems odd, check the model for design issues rather than changing scores casually.

Common mistakes that make RFP scoring unfair

Even experienced teams fall into avoidable traps.

Focusing only on the lowest price

Lowest price is not always lowest cost. Rework, delays, quality issues and weak support often surface later.

Scoring vague promises too highly

A polished proposal should not beat a well-supported one simply because it sounds more confident.

Letting incumbent familiarity sway the process

Existing suppliers may have an advantage because the team already knows them. That knowledge can be useful, but it should be documented and applied carefully.

Mixing past experience with proposal evaluation without rules

If prior supplier performance will affect scoring, say so in the methodology and apply it consistently.

Using too many criteria

A bloated matrix can create false precision. Keep the model focused on what truly drives value and risk.

Failing to document why scores were given

A number without rationale is weak governance. Short comments are usually enough if they explain the evidence behind the score.

A simple template for evaluator comments

To keep scoring disciplined, ask evaluators to write comments in a consistent format:

• Requirement: what was being assessed
• Evidence observed: what the supplier provided
• Strength or concern: what stood out
• Score reason: why the chosen score was justified

This makes moderation easier and creates a cleaner audit trail.

How to adapt criteria for different purchase types

Not every RFP should use the same model.

Purchase typeCriteria to emphasiseCriteria to keep lighterCommodity goodsCommercial value, fulfilment reliability, complianceComplex implementation scoringOperational servicesService capability, staffing, implementation, riskMinor feature differencesStrategic suppliersCapability, continuity, governance, total valueShort-term price aloneTechnology-related solutionsFunctional fit, integration, security, implementationSuperficial presentation quality

Tailoring the scorecard helps you avoid both overengineering and under-evaluating.

Final recommendations for a fair supplier proposal evaluation

If you want a process that is both practical and defensible, keep these principles in view:

• decide the rules before proposals arrive
• separate pass/fail from weighted criteria
• evaluate total value, not just headline price
• require evidence for scores
• involve the right stakeholders, but keep roles clear
• document rationale, not just numbers
• use moderation to challenge bias, not to override evidence

A fair RFP evaluation process is ultimately about consistency. Suppliers should feel they were assessed on the same basis, and your internal stakeholders should be able to see why the selected proposal best meets the organisation's needs.

For teams managing recurring indirect purchases or supplier consolidation, structured digital procurement workflows can make this process easier to standardise. Platforms such as Lapasar, a MOF-registered procurement platform with 10,000+ suppliers and 2M+ SKUs, can support more organised supplier comparison and purchasing workflows across Peninsular Malaysia, but the core discipline still starts with a well-designed evaluation model.