Nonprofit website RFP evaluation kit Prepared by Salt Technologies A nonprofit selection committee can use this scorecard to compare website proposals. Agree the criteria before opening bids, then give every eligible vendor the same tasks. Writing the brief Outcomes and audiences — Give each priority audience a task and a way to tell whether it succeeded. A participant can find a distribution site on a phone. A donor can complete a gift and see a receipt. An editor can correct both English and Spanish service hours before the office closes. Name the staff member who will accept each result. Inventory and ownership — List the CMS, page and document counts, language versions, forms, payment processor, CRM and membership tools. For each, say who owns the account, who can grant test access and who will approve migrated content. Ask bidders to price any unknown volume separately. Bid format and schedule — Give bidders the same response sheet. Request a fixed scope or stated estimate basis, exclusions, staffing locations, accessibility testing, launch support and recurring fees. Publish the question deadline, shared answers process, shortlist demonstration date and decision owner. Launch and continuity — Name campaign dates, giving days and program deadlines that constrain cutover. Ask for a sample redirect register, a trial content import and a rollback rehearsal. Agree who checks that a donation, volunteer registration or member renewal made during the switch is reconciled. Sample requirement “Our program manager must be able to update a food distribution location in both supported languages using an editor account. At the shortlist demonstration, use a sample location to show editing, preview, publication and reversal. In the proposal, identify who translates the update, which work requires a developer and whether training and licensing are included.” Set the rules - RFP [reference] · committee chair [name] · evaluators [names] · submission and question deadlines [date, time zone] · required procurement channel [details]. - Check mandatory eligibility, subcontractor disclosures, delivery location, accessibility obligations, insurance and required documents against the published RFP. Record pass, fail or clarification with a clause reference. Apply your published process before scoring. Score each eligible proposal - Use the suggested weights below or agree your own before review. Use 0 for missing evidence, 1 for a claim, 2 for a partial response, 3 for meeting the requirement, 4 for strong supporting evidence and 5 for a demonstrated, repeatable result. Leave unreviewed criteria blank. - Weighted points = rating ÷ 5 × weight. Sum all six weighted scores for a total out of 100. Each evaluator records the evidence and scores independently before the panel reconciles differences. Public journeys and accessibility (25%) — Demonstrate the donation, meeting-finder and keyboard journeys in the acceptance tests. | Rating [ ] | Evidence [ ] Content migration and search continuity (20%) — Provide a sample URL inventory, redirect map, exceptions list and post-launch check. | Rating [ ] | Evidence [ ] CMS editing and training (15%) — Show a staff editor updating a meeting, previewing it and reverting a mistake. | Rating [ ] | Evidence [ ] Integrations, data and security (15%) — Identify donation and membership integrations, data access, backups and incident ownership. | Rating [ ] | Evidence [ ] Delivery, handover and support (15%) — Name delivery roles, milestones, acceptance owner, training and support response commitments. | Rating [ ] | Evidence [ ] Three-year cost of ownership (10%) — Separate implementation from hosting, licenses, support, optional work and buyer staff time. | Rating [ ] | Evidence [ ] Run the same acceptance tests - Find a meeting — using only a keyboard, find the next meeting for a specified day and location. Verify the time, location and contact details are accessible and that focus stays visible. - Complete a mobile donation — use a test payment to donate, return to the website and see confirmation. Also test cancellation and retry. Check the transaction and receipt evidence with the finance owner. - Update a program — a staff editor changes a meeting time in staging, previews it, publishes it and corrects it without developer access. Verify the public listing reflects the correction. - Record for each test: vendor [name], environment [demo or staging], expected result [ ], observed result [ ], pass or issue [ ], evidence [ ], owner and retest date [ ]. Use sample records and test payments. Document the decision - For each vendor record the evidence behind the score, unanswered questions, three-year cost assumptions, reference checks and any conflicts of interest. Resolve tied scores using the process published in the RFP. - Before contract award, turn the selected tests into acceptance criteria. Name the staff sign-off owner, remediation period and handover deliverables. Worked example — fictional bids, ratings out of 5 Public journeys and accessibility (25%) — Bid A 4, Bid B 4 Content migration and search continuity (20%) — Bid A 3, Bid B 5 CMS editing and training (15%) — Bid A 3, Bid B 4 Integrations, data and security (15%) — Bid A 4, Bid B 3 Delivery, handover and support (15%) — Bid A 3, Bid B 4 Three-year cost of ownership (10%) — Bid A 3, Bid B 4 Weighted total out of 100 — Bid A 68, Bid B 81 In this fictional evaluation, both bidders pass the mandatory conditions. Bid B earns the higher migration score by demonstrating a trial import, resolving broken document links and handing over a redirect register. Bid A earns the higher integration score because its team demonstrates payment reconciliation after a failed CRM sync. If that sync is essential for launch, ask B to demonstrate recovery under the published clarification process before award. Implementation and training (USD) — Bid A 36000, Bid B 45000 Annual hosting, licenses and support (USD) — Bid A 9000, Bid B 5000 Three-year cost (USD) — Bid A 63000, Bid B 60000 These sample USD figures illustrate a budget comparison. Assume three full years of recurring fees at the quoted rate, with the same scope for both vendors. Add any separately priced translation, transaction fees at your donation volume, internal staff time and exit or data-export costs before taking the recommendation to the board. Manna Food Center asked for English and Spanish content, simpler access to programs, and connections to donation and volunteer tools. For a food-assistance site, give two vendors the same location update and ask a staff editor to publish it in both languages. Record who maintains translations and what a participant sees on a phone. Manna Food Center’s published website RFP (PDF) — https://www.mannafood.org/wp-content/uploads/2025/06/RFP_-Website-Redesign-Manna-Food-Center-003-1.pdf The Friends had already developed a site blueprint. Its RFP asks a vendor to build on that work, migrate the site and price ongoing support across multiple properties. If your organization has a discovery report, attach it. Ask bidders which decisions they accept, which need validation and how they price support for each property. That makes duplicated discovery and unequal support coverage visible. The Friends of the Saint Paul Public Library’s published website RFP — https://thefriends.org/2026/11/16/request-for-proposals-website-redesign/ Accessibility evaluation guidance — https://www.w3.org/WAI/test-evaluate/tools/selecting/ Source — https://www.salttechno.com/nonprofit-website-rfp#rfp-evaluation-kit Invite Salt to bid on your RFP — https://www.salttechno.com/contact-us?source=%2Fnonprofit-website-rfp&interest=Nonprofit+website+RFPs&resource=rfp-evaluation-kit