Skip to content
iprocure

Glossary

Evaluation consensus

Evaluation consensus is the step in which a sourcing panel, having scored supplier responses independently, reviews where their scores differ and agrees one score per criterion, recording the reasons and keeping each individual score.

Most significant sourcing decisions are made by a panel: a buyer, a technical expert, a user representative, sometimes quality, legal or finance. Each brings a different view, which is the point. Consensus scoring turns those views into one defensible result. It normally runs in two stages. First, each evaluator scores their assigned sections alone, against the same criteria and rubric. Second, the panel compares the spread and agrees a score for each criterion.

The order matters. If evaluators see each other's scores before submitting their own, the first or most senior score anchors everyone else, and the panel loses its independent views. Scoring independently first, then discussing, surfaces real disagreements. A useful practice is to flag criteria where scores differ by more than a set margin and ask the outliers to explain, since they may have noticed something the others missed, or misread the response.

Consensus is not the same as averaging. An average hides a disagreement that the panel should resolve; a consensus score records a decision. The chair, or the panel together, sets the agreed score and notes why. Keeping every individual score alongside the agreed one matters for audit, for debriefing unsuccessful suppliers and for challenges in regulated or public tenders, where the buyer must show that the decision followed the published criteria.

How iProcure handles evaluation consensus

iProcure's evaluator workspace is built around this process, and it is shown on sample data today. Each evaluator scores only their assigned sections, without seeing colleagues' scores first. The panel then sees where scores diverge and agrees one score on the record, with every individual score kept. The evaluation model the workspace scores against is live.

FAQ

Evaluation consensus: common questions

Should consensus scores be averaged or agreed?

Agreed. An average is a useful starting point, but it can hide a real disagreement: one evaluator scoring 2 and another 5 average to 3.5, which neither believes. Discuss criteria with a wide spread, let the outliers explain, and record an agreed score with a short reason. Keep the individual scores so the discussion itself is on the record.

How many evaluators should an RFP panel have?

Enough to cover the expertise the criteria demand, and few enough to reach agreement. Three to five is common for significant events. Assign sections by expertise, so a technical expert scores the technical criteria and finance scores the commercial terms, rather than asking everyone to score everything. Each evaluator should declare any conflict of interest before seeing a response.

Next step

See it live in 10 minutes.

Pick your region and the two modules that hurt most. We run your own category through the RFx spine on sample data. No access, no commitment, no build decision required.

  • Supplier-blind RFx
  • Independent evaluation
  • Approvals from email
  • Global & modular

Design partner's seat

Pre-launch and honest about it: you get the mechanism now. Design partners get a free 60 to 90 day pilot, a preferential launch price, roadmap input and a direct line to the founders.

Call +91 70990 38346WhatsApp us