rating criteria for rfp1616 .pdf
Original filename: rating criteria for rfp1616.pdf
This PDF 1.4 document has been generated by / iTextSharp™ 5.4.1 ©2000-2012 1T3XT BVBA (AGPL-version), and has been sent on pdf-archive.com on 29/06/2016 at 04:43, from IP address 45.74.x.x.
The current document download page has been viewed 314 times.
File size: 3 KB (1 page).
Privacy: public file
Download original PDF file
rating criteria for rfp
An overview of rating criteria for evaluating software RFP's
You can use many different scoring schemes for rating criteria for rfp's. Whatever you use,
however, should be applied consistently across all proposals for evaluation.
Types of scorings
1. Simple Yes or No scores. Quick and easy to use, but omits how important specific features or
functionality are to you.
2. Combined weighting and scoring method to indicate to what degree your rfp requirements are
met by the vendor/software. Slower to do, but does take into consideration the importance of
different criteria within an RFP.
3. Scoring schemes and weighting, may be as elaborate as you require. They need to provide you
with sufficient analysis/evaluation, without being too complex, confusing or take too long. Our
preference is for something that is quick to use and provides the required information eg both
option 1's below - see the RFP Evaluation Template. However, ultimately the choice is yours. Just
ensure you have a written justification for your chosen scoring and weighting schemes.
Scoring schemes include
1. 0 to 3 range, where your requirements are: not met (0), partially met (1), fully met (2), exceeded
(3). Straightforward and easy to use.
2. -3 to +3 range, where your requirements are: not met (-3), fully met (0), exceeded (+3), with
points in between. More complex, more aggressive scoring, which will separate out the
software/vendor's scores. However, confusingly, a zero score is actually a good score!
3. 1 to 10 range, where your requirements are: not met (1) and exceeded (10), with points in
between. Again, will separate out software/vendor's scores more than with a ‘0 to 3' range. But
because of the wider range, it may be more difficult to agree a consensus scoring.
4. Percentage of points available overall (adding up to 100) eg software functionality (0 to 50%),
support and maintenance (0 to 20%), implementation assistance (0 to 15%) and price (0 to 15%).
5. Percentage of points available for each requirement eg exceptional (100%), exceeds
requirements (80%), meets minimum requirements (60%), not meeting minimum requirements
(30%), unacceptable (0%), with percentages in between.