How to evaluate technology vendors for your district
A repeatable way to compare technology providers: write requirements first, score against them, and read the contract as carefully as the proposal.
Most vendor decisions go wrong before the first demo. A district sees an impressive presentation, then writes requirements that happen to match it. The result is a contract that fits the vendor’s strengths rather than the district’s needs.
A repeatable evaluation process fixes that. It also gives the board and auditors a clear record of why a decision was made.
Write requirements before you talk to vendors
Start by describing the problem, not the product. A good requirements document covers:
- what is not working today, in the words of the people affected;
- the outcomes you need, such as coverage, response times you will hold the provider to, or reporting;
- constraints, including budget, timeline, existing systems it must work with, and staff capacity to run it;
- must-haves versus nice-to-haves, decided in advance.
Share the draft with the people who will use the system. Teachers, front-office staff and technicians often know what matters better than anyone else.
Build the scorecard before the proposals arrive
Decide how you will score before you see any bids. A simple scorecard weights a handful of criteria, for example:
| Criterion | Example weight |
|---|---|
| Meets must-have requirements | Pass or fail |
| Total cost over the full term | 30% |
| Fit with existing systems and staff | 25% |
| Implementation plan and timeline | 20% |
| Support model and references | 15% |
| Contract terms | 10% |
Your weights will differ, and funding programs may require particular scoring rules. E-Rate, for example, requires cost of eligible services to be the primary factor. The point is to decide in advance and apply the same scorecard to everyone.
Compare capabilities side by side
Proposals are written to look complete. A side-by-side comparison of the capabilities you actually need makes gaps visible quickly. Tools like our Vendor Matrix can help you build a shortlist before you invest time in demos.
Ask for references that look like you
A reference from a large enterprise tells you little about how a provider works with a district. Ask for references from organizations with a similar number of buildings, similar staff and similar systems. Then ask them:
- What went wrong during implementation, and how was it handled?
- How quickly does support respond in practice?
- Would you choose them again?
Read the contract as carefully as the proposal
The contract is what you will live with for years. Pay particular attention to:
- term and renewal, including automatic renewals and how much notice you must give to leave;
- price changes during the term and at renewal;
- termination rights if service does not meet the agreement;
- service levels and what happens when they are missed;
- data ownership and exit, including how you get your data back;
- student data privacy, including a data privacy agreement that meets your state’s requirements.
Many states and consortia publish standard student data privacy agreements. Using one saves time and sets a consistent bar for every provider.
Use the purchasing options you already have
Cooperative purchasing contracts and state contracts can shorten procurement considerably, where your policies allow them. Check which ones your district can use before starting a full RFP, and confirm that the specific products and terms meet your requirements.
Keep a record
Write down the requirements, the scorecard, the scores and the reason for the final choice. When the contract comes up for renewal, that record is the starting point for deciding whether the provider delivered what they promised.
A process like this takes a little more time at the start. It saves far more over the life of the contract.
