Key takeaways
- Lead with one concrete workflow problem; it turns the demo into a fit test.
- Invite a special education lead, a school administrator, a teacher lead, and a technology or privacy contact.
- The 30 minutes runs on sample data: rollup, director view, privacy and procurement, pricing, and Q&A.
- Bring rough numbers: schools, case managers, students on plans, and your data agreement template.
- The usual next step is a scoped pilot, a privacy review, and a pricing conversation sized to your district.
To prepare for an Evident district demo, pick the one workflow problem you most want solved, invite the three or four people who can judge fit, and bring rough counts and your data agreement template. The walkthrough is 30 minutes on anonymized sample data, so the value comes from asking questions about your own workflow in each segment.
Bring one concrete problem
The most useful demos start from a specific pain: IEP progress notes scattered across paper and spreadsheets, progress reports rebuilt every quarter, family communication in several languages, FBA and BIP documentation, packet prep before meetings, or no view across schools. Pick the one that costs your staff the most time and lead with it. A focused problem turns the walkthrough into a test of fit rather than a feature tour.
Who to invite
| Person | What they judge |
|---|---|
| Special education director or coordinator | Caseload view, IEP dates, and whether packets would be ready before meetings |
| School administrator | Building rollups and what leaders can and cannot see |
| Teacher lead, case manager, or MTSS lead | Whether daily logging fits a real class period |
| Technology or procurement contact | Roles, sign-in, data agreements, and purchasing steps |
Missing one of these usually means a second call to answer a question someone could have answered live.
What the 30 minutes covers, and what to ask
| Time | Segment | Questions worth bringing |
|---|---|---|
| 00:00 | Evidence-readiness rollup with anonymized sample students | How is readiness defined? What does a school with thin records look like here? |
| 00:08 | Special education director view: caseload, IEP dates, and packet readiness | How far ahead do meeting reminders go? Can a coordinator see which students are missing recent goal data? |
| 00:15 | Privacy and procurement: DPA or NDPA, roles, and your state addendum | Will you sign our agreement? What can each role see? How are family links revoked? |
| 00:22 | Pricing for your district size and procurement options | How are school licenses sized? Do you accept purchase orders? What does a pilot cost? |
| 00:27 | Q&A | Anything the segments above did not reach. Bring your tech director if helpful. |
What to prepare
- Rough numbers. Schools, case managers, and students on IEP or 504 plans. Pricing and pilot scoping both depend on them.
- Your current tools. Where teachers log data now, and where progress reports and packets get built.
- Your data agreement. The district DPA, NDPA, or state addendum, if you have one, so the privacy segment can be specific.
- A look at the output. Review the sample evidence packet beforehand so you arrive knowing what you are evaluating.
- A staff-time baseline, optional. The ROI estimate gives a starting number for how much time the current workflow takes.
After the demo
If the workflow fits, the usual sequence is a scoped pilot, a privacy and procurement review, and a seat or pricing conversation sized to your district. Knowing that going in lets you ask pilot and procurement questions during the call instead of starting over afterward. The district pilot plan covers how to run the pilot, the compliance review questions cover the privacy review, and the procurement and ROI checklist covers the purchasing side. Book the walkthrough from the district demo page.
Common questions
Who should attend an Evident district demo?
A special education director or coordinator, a school administrator, an MTSS lead or teacher lead who knows the daily workflow, and a technology or procurement contact who can ask about access, sign-in, and data agreements.
Do we need real student data for the demo?
No. The demo uses anonymized sample district data. Bring your workflow questions, not student records.
What happens after the demo?
If the workflow fits, the usual next step is a scoped pilot, a privacy and procurement review, and a seat or pricing conversation based on your district size.
What should we prepare beforehand?
One workflow problem you want solved, rough counts of schools, case managers, and students on plans, the tools you use today, and your data privacy agreement or state addendum if you have one. Looking at the sample evidence packet first saves time on the call.