Most failed implementations trace to two causes — underestimating data quality in the outgoing system, and buying modules that are never adopted. Both are identifiable at evaluation if the right questions are asked before the demonstration rather than after the contract.
Start with workflows, not the feature matrix
Every vendor’s feature list is long and substantially identical. Scoring them produces a spreadsheet in which everyone passes and no decision follows.
The comparison that discriminates is narrower: identify the six processes consuming the most staff time in your buildings, and require each vendor to run those six live, on your data, in the demonstration. For most schools they are enrollment and registration, daily attendance, grading and report cards, family communication, scheduling, and whichever state report causes the most pain. A product that handles those six well is worth negotiating over.
The evaluation framework
1. Workflow fit
- Can it model your actual grading scale, credit structure and calendar, or does it assume a structure you would have to adopt?
- Does report card output match what families currently receive, including the parts board policy will not let you change?
- How many clicks is taking attendance? Multiply by teachers, by periods, by 180 days.
- What does the first day of school look like in this system?
2. Standards, evaluation and reporting coverage
- Is your state standard mapped — the current version, not Common Core as a proxy? States that revised away from Common Core need the revision.
- When your state updates standards, who does the remapping and how fast?
- Does it run your teacher evaluation framework, or only Danielson?
- Can it produce your state reports from operational data, or does it require parallel entry?
- Is ESSA subgroup disaggregation continuous, or an annual export?
3. Total cost of ownership over three years
| Cost | Question to ask |
|---|---|
| License | Per student, per module, or per site? What happens as enrollment changes mid-year? |
| Implementation | Is data migration included, and to what quality standard? |
| Training | Included, or per session? What about staff hired later? |
| Integration | Cost to connect to your SIS, finance system, identity provider and assessment vendor? |
| Messaging | Are text, voice and translation charges included or metered? |
| Support tier | What is included, and what does the tier that answers the phone in August cost? |
| Exit | Cost of full data export in a usable format at termination? |
The license is rarely the largest line in year one.
4. Migration risk
This is where implementations fail. Outgoing data is almost always worse than anyone believes: duplicate student records, inconsistent guardian data, historical grades on unmapped scales, discipline records in a separate system that never merged. Require the vendor to run a data quality assessment on a real export before contract. A vendor unwilling to do that has told you something useful.
5. Privacy, ownership and exit
- Will they sign your state’s standard data privacy agreement without amendment?
- Show me the contract clause on AI model training — the clause, not the marketing page.
- Who owns the data? The answer should be your district, in writing.
- What does export cost at termination, and in what format?
- What is their incident notification window, and does it fit inside your state breach obligation?
Detail on all of these: FERPA and student data privacy.
Product categories
| Category | Best suited to | Watch for |
|---|---|---|
| Record-only SIS | Districts with strong existing instructional systems | The gap between records and classroom stays unfilled |
| LMS-first platform | Schools prioritizing content delivery and submissions | Weak state reporting and scheduling |
| Assessment specialist | Districts with a specific benchmark or item-bank need | Another silo to reconcile |
| Evaluation-only tool | Districts fixing observation alone | Observation disconnected from what was actually planned and taught |
| Integrated platform | Schools wanting records, instruction, observation and assessment on one record | Breadth can mean a module is shallower than a specialist |
Where Edves fits — and where it does not
Edves is an integrated platform whose distinguishing strength is the instructional layer: standards-aligned lesson design, evidence-anchored teaching observation and objective-level assessment sitting on the same record as attendance and grades. Schools choose it when the gap they are closing is between administration and classroom practice, or when observation and instruction are currently disconnected.
It is a weaker fit in three situations, and saying so is more useful than not:
- A district needing a narrow, deep specialist in one function that already has everything else working.
- A district whose SIS is state-mandated or contractually locked, where integration rather than replacement is the only option — supported via LTI, but it is a partial deployment.
- A district whose primary pain is finance, HR or transportation, which is not what this platform is for.
Market context: all 50 states. Company data for due diligence: Edves facts.
Questions worth asking every vendor
- Show me a district of my size and type using this, and let me speak to them without you on the call.
- Run my six highest-volume workflows on my data in the demo.
- How many districts left you last year, and why?
- Which module do customers buy and never use?
- What is your published uptime, and what is the remedy when you miss it?
- What does support look like at 7am on the first day of school?
- Who is on my implementation team, and are they employees or subcontractors?