10.3 Scoring, Consensus and Price Formulas

Qualitative Scoring Methodologies

In competitive sealed proposals, evaluation factors are qualitative and multi-dimensional. Public agencies utilize three primary scoring systems to capture evaluator assessments:

1. Numerical Scoring Systems (0–100 Point Scale)

Numerical scoring assigns discrete point values to each published evaluation criterion based on its established percentage weight. For example, an RFP may allocate 40 points to Technical Methodology, 25 points to Personnel & Qualifications, 15 points to Past Performance, and 20 points to Cost. Evaluators assign points to each criterion using structured numerical scoring rubrics (such as 1–5 or 1–10 point multipliers):

• 90–100% of Available Points: Outstanding; proposal significantly exceeds specifications with comprehensive detail and measurable value-added enhancements.
• 75–89% of Available Points: Good; proposal fully satisfies specifications with minor, non-critical omissions easily clarified.
• 60–74% of Available Points: Satisfactory / Minimum Acceptable; proposal meets baseline minimum requirements but lacks depth or innovation.
• Below 60% of Available Points: Unsatisfactory; proposal fails to satisfy core technical requirements or presents unacceptable operational risk.

2. Adjectival Rating Systems

Adjectival rating replaces raw numerical points with standardized qualitative descriptive terms. Adjectival systems are widely favored in complex enterprise and federal acquisitions because they compel evaluators to focus on the substantive merits of the proposal rather than debating arbitrary decimal fractions:

• Exceptional / Superior: The proposal substantially exceeds solicitation requirements in all material aspects. Demonstrates innovative methodologies, exceptional personnel qualifications, robust risk mitigation, and superior technical capability. The proposal contains multiple significant strengths and no weaknesses or deficiencies. Risk of unsuccessful performance is negligible.
• Acceptable / Proficient: The proposal satisfies all mandatory requirements of the RFP. Demonstrates a sound, practical technical approach and competent personnel. The proposal contains minor weaknesses that can be readily clarified or mitigated. Risk of unsuccessful performance is low to moderate.
• Marginal / Susceptible to Being Made Acceptable: The proposal fails to satisfy certain baseline requirements or provides insufficient operational detail. Contains substantial weaknesses, omissions, or ambiguities. Requires extensive discussions, clarifications, or revisions to become viable. Risk of unsuccessful performance is moderate to high.
• Unacceptable / Deficient: The proposal fails to satisfy critical mandatory requirements. Contains fatal omissions, unworkable methodologies, or severe technical flaws that cannot be cured without a wholesale rewrite of the proposal. Risk of unsuccessful performance is extreme.

3. Color-Coded Evaluation Systems

Color-coded systems assign standardized colors to performance tiers (e.g., Blue = Exceptional; Green = Acceptable; Yellow = Marginal; Red = Unacceptable). Color systems are almost always paired with adjectival rating definitions. They provide procurement officers, evaluation committees, and governing boards with an immediate visual dashboard comparing offeror strengths and vulnerabilities across distinct technical domains.

The Mandatory Requirement for Contemporaneous Narrative Justifications

A defensible evaluation connects ratings to the published criteria and proposal evidence. The approved plan should require evaluators to record contemporaneous, written narrative justifications documenting:

• Strengths: Specific attributes of the proposal that exceed requirements or provide tangible public operational benefits, citing specific proposal sections and page numbers.
• Weaknesses: Flaws, omissions, or ambiguities where the proposal fails to provide required detail or introduces operational risk.
• Deficiencies: Material failures to satisfy mandatory statutory or technical specifications.

---

Consensus Scoring vs. Mathematical Averaging

Once evaluators complete their initial reviews, the committee must reconcile individual evaluations into an institutional evaluation record. Public procurement utilizes two fundamentally different approaches: Consensus Scoring and Mathematical Averaging.

Mathematical Averaging (Vulnerable to Outlier Skewing):
[ Evaluator 1: 95 ] ──┐
[ Evaluator 2: 90 ] ──┼──> [ Arithmetic Mean: 63.75 ] ──> Unreconciled Conflicts in Audit File
[ Evaluator 3: 40 ] ──┤     (Evaluator 4 Outlier Distorts Rank)
[ Evaluator 4: 30 ] ──┘

Consensus Scoring (Facilitated Committee Deliberation):
[ Independent Preliminary Reviews ] ──>
  [ Facilitated Committee Meeting Led by Procurement Officer ] ──>
    [ Collaborative Technical Debate & Specification Reconciliation ] ──>
      [ Single Unified Consensus Score & Bulletproof Narrative Record ]

Consensus Scoring (Facilitated Committee Discussion)

Under consensus scoring, committee members conduct independent preliminary reviews to familiarize themselves with proposals and record initial observations. The procurement officer then convenes the committee in a facilitated, structured session:

1. Collaborative Deliberation: For each evaluation criterion of each proposal, evaluators present their observations. Evaluators debate technical merits, compare identified strengths and weaknesses, and resolve differing interpretations of specifications.
2. Resolving Misconceptions: Often, an evaluator who assigned a low rating simply misread a technical diagram or missed an appendix. Deliberation ensures that factual misunderstandings are corrected based on the actual proposal text.
3. Single Unified Score: Through facilitated dialogue, the committee arrives at a single, agreed-upon consensus score and drafts a single authoritative narrative evaluation summary per proposal.
4. Strengths and Governance Discipline: Consensus scoring eliminates outlier distortion, harmonizes institutional judgment, and produces an airtight audit trail. However, it requires an assertive, skilled procurement facilitator to prevent groupthink or the intimidation of junior evaluators by dominant personalities (e.g., a department director coercing subordinate staff).

Mathematical Averaging (Arithmetic Aggregation)

Under mathematical averaging, evaluators score proposals in isolation. The procurement officer collects the individual scorecards, enters the raw numbers into a spreadsheet, and calculates the arithmetic mean to establish the ranking.

While mathematically simple, this methodology carries severe legal and audit vulnerabilities:

• Outlier Distortion / Scoring Hijacking: A single uncalibrated or biased evaluator assigning an extreme score (e.g., scoring an excellent proposal 10 out of 100 or a poor proposal 100 out of 100) can materially affect the average and ranking.
• Fatal File Contradictions: Mathematical averaging leaves conflicting evaluator observations unresolved. For example, if Evaluator A rates a vendor's project plan as an "outstanding strength" while Evaluator B rates the exact same plan as an "unacceptable fatal flaw," averaging their scores (e.g., [100 + 20] / 2 = 60) creates an irrational record. Averaging is a legitimate method when authorized and applied consistently. Review factual contradictions and scoring errors using the approved process; do not switch to consensus after seeing which vendor benefits.

---

Weighting Criteria and Cost/Price Scoring Formulas

Disclose evaluation factors and their relative importance as the applicable law requires; not every jurisdiction requires numeric percentage weights. If percentages are published, use them consistently. Evaluating proposals against unannounced factors or modifying weights after proposal opening violates the fundamental legal principle of open and fair competition.

Structuring Evaluation Weights

A balanced RFP evaluation structure aligns criterion weights with project risk:

• Technical Methodology & Operational Approach: 30% to 40%
• Key Personnel Qualifications & Management Plan: 20% to 30%
• Organizational Experience & Verified Past Performance: 10% to 20%
• Cost / Price: 20% to 30%

The Two-Envelope System: Independent Cost Evaluation

To ensure that cost does not bias qualitative technical evaluations, public agencies employ the Two-Envelope System. Proposers submit their technical proposals and cost proposals in separate sealed envelopes or separate encrypted electronic vaults. The evaluation committee evaluates, discusses, and scores all technical criteria without knowledge of proposed prices. Only after technical scoring is finalized and locked by the procurement officer are cost proposals opened and evaluated.

The Standard Low-Bid Price Scoring Formula

One disclosed method of assigning cost points uses the inverse mathematical proportionality formula, where the lowest responsive proposed price receives 100% of the available cost points, and higher prices receive proportionally fewer points:

Standard Cost Formula:
Points Assigned = (Lowest Proposed Price / Offeror's Proposed Price) * Maximum Available Cost Points

Concrete Worked Numerical Example

An agency issues an RFP for enterprise asset management software with 30 maximum available cost points. Three responsive proposals are submitted:

• Offeror Alpha: $800,000 (Lowest Proposed Price)
  • Points = (\$800,000 / \$800,000) * 30 = 30.00 Points
• Offeror Beta: $1,000,000
  • Points = (\$800,000 / \$1,000,000) * 30 = 24.00 Points
• Offeror Gamma: $1,200,000
  • Points = (\$800,000 / \$1,200,000) * 30 = 20.00 Points

Notice the mathematical behavior of this formula: Offeror Beta's price is 25% higher than Alpha's, resulting in a 20% point reduction. Offeror Gamma's price is 50% higher than Alpha's, resulting in a 33.3% point reduction. This formula ensures that cost differentials are evaluated objectively and proportionately without subjective evaluator bias.

---

Comparison Table: Proposal Scoring Methodologies