Key takeaways
- Pick one use case; a pilot that tries to prove everything proves nothing.
- Write success thresholds before kickoff, such as 80 percent of teachers logging 4 days a week.
- Include at least one skeptical or stretched-thin teacher, not only enthusiasts.
- Run the privacy and data agreement review during the pilot, not after.
- Scope the decision to what six weeks can show: adoption, data quality, and workflow fit.
A district pilot plan answers five questions before anyone logs in: which one workflow the pilot tests, who does each job, what numbers count as success, how privacy is reviewed, and who decides what happens after. The checklist below runs a six-week pilot in four phases, each with a done-when standard, followed by example success thresholds and the pitfalls that most often sink a pilot.
Phase 1: before kickoff (two weeks out)
| Item | Done when |
|---|---|
| One primary use case chosen | Written in one sentence, for example "IEP goal data collection and quarterly progress reports for resource teachers" |
| Pilot group selected | 6 to 15 teachers across one to three schools, including at least one skeptical or stretched-thin teacher |
| Roles named | Named people for: roster setup, chart and goal setup, daily logging, report review, family questions, and pilot lead |
| Success thresholds written | Two or three signals, each with a number and a date (see examples below) |
| Privacy review started | The data agreement, role permissions, and data storage questions are with the technology or privacy lead |
| Decision meeting booked | Date, attendees, and decision owner on the calendar |
Phase 2: weeks 1 and 2
| Item | Done when |
|---|---|
| Accounts and rosters live | Every pilot teacher can sign in and sees only their own students |
| Setup session held | 30 minutes per school: one real student set up start to finish during the session |
| Logging moment chosen per teacher | Each teacher has written down when in the day they will log |
| First check-in done | Pilot lead has asked each teacher what got in the way, and fixed access or setup problems |
Phase 3: weeks 3 to 5
| Item | Done when |
|---|---|
| Logging consistency checked weekly | Share of teachers logging on most school days is recorded each Friday |
| Drop-off followed up | Any teacher whose logging fell off has had a conversation about friction, not compliance |
| Output tested in a real meeting | At least two teams have used an exported report or packet in an actual meeting |
| Privacy review closed | The data agreement is signed or the open items are listed with owners |
Phase 4: week 6, the decision
| Item | Done when |
|---|---|
| Results compared to thresholds | Each success signal is marked met, not met, or unclear, with the number |
| Teacher feedback collected | Every pilot teacher answered: would you keep using this if it were optional, and what would you change |
| Decision made | Expand, adjust and re-run, or stop, with the reason written down |
| Next steps owned | Rollout plan, procurement steps, or wind-down each have an owner and date |
Example success thresholds
Write the threshold, not just the metric. "Teachers are logging" is a hope; "80 percent of pilot teachers log at least 4 days a week in weeks 3 to 5" can be checked.
- Adoption: at least 80 percent of pilot teachers log goal data on 4 or more days a week in weeks 3 to 5.
- Output used: at least 3 IEP teams use an exported progress report in a real meeting without rebuilding the data by hand.
- Would keep it: at least 7 of 10 pilot teachers say they would keep using it if it were optional.
Be honest about what six weeks cannot show. A short pilot will not settle long-term student outcomes, and claiming it does weakens the case for the rollout. Scope the thresholds to adoption, data quality, workflow fit, and whether the output is usable in meetings.
Pitfalls that sink a pilot
Only enthusiasts. Volunteers who love new tools succeed with almost anything, so the pilot predicts nothing about the typical classroom.
Too many use cases. A pilot testing charts, IEP data, FBA records, and family communication at once produces feedback you cannot sort. One workflow, done well, is a clearer decision.
Ignoring early drop-off. If logging fades after week one, the cause is usually friction or unclear ownership. Catch it in week two and fix it; do not paper over it in the week six review.
Privacy review after the fact. Data agreements and role permissions take time. Start them before kickoff so a positive pilot is not stuck waiting on paperwork.
Running an Evident pilot
Evident's school plans include a Team Pilot tier sized for this kind of trial, and a district plan covers several schools under one agreement with cross-school rollups for leaders. A signed data agreement is available, and the security overview and help article on how Evident handles school data cover storage, access, and deletion for the privacy review. A district demo uses sample data only and is a reasonable first step before choosing pilot schools; the ROI estimate gives a starting number for the staff-time baseline. For setting the shared logging standard across pilot teachers, see setting up a school-wide documentation system.
Common questions
How long should a district pilot run?
Four to six weeks of active use is usually enough to judge adoption, data quality, and workflow fit, provided it overlaps at least one real reporting or meeting cycle. It is not long enough to judge student outcomes, so do not set outcome criteria for a pilot that short.
How many teachers should be in a pilot?
Enough to represent the workflow you care about: often 6 to 15 teachers across one to three schools. A small group that includes a skeptical teacher and a stretched-thin case manager tells you more than a large group of volunteers.
Should we pick our most enthusiastic teachers?
Include some, but not only them. Enthusiastic teachers succeed with almost any tool, so add at least one teacher whose experience predicts the typical classroom.
What should we decide before the pilot starts?
The one use case, who does each role, two or three success signals with numeric thresholds, the review date, and who makes the expand, adjust, or stop decision.
Should families be part of the pilot?
Only if family communication is part of the use case. If it is, write the family-sharing plan and consent steps before kickoff and include a family-access success signal.