How to Run a Dismissal Pilot Without Disrupting Your School

The most common reason districts delay improving dismissal is fear of disruption. Changing a process that runs every school day, involves hundreds of parents and dozens of staff, and has safety implications — the instinct is to wait for summer, wait for a new year, wait for the right moment. The right moment rarely arrives.

A well-structured pilot can change dismissal for the better without disrupting the school. Here's how to run one.

Start with One Grade Level

The most effective dismissal pilots start with one grade — kindergarten or 1st grade at elementary level — rather than the whole school. Car riders in the lowest grades have the highest parent engagement and the most consistent pickup patterns. They're the easiest to onboard to a parent app and the most likely to use it reliably.

Running the pilot on a single grade level means the rest of dismissal continues as normal. Staff have a clear boundary between the pilot group and the existing process. Failure modes are contained. And success is visible and measurable.

The Pre-Launch Checklist (2 Weeks Before)

• SIS sync: Confirm student roster, guardian contacts, and dismissal categories are accurate in your SIS. The quality of your dismissal data depends on the quality of your SIS data.
• Staff briefing: The teachers and front office staff involved in the pilot need to understand the new workflow before it goes live. Run a 20-minute walkthrough — not a training session, a walkthrough. Show them exactly what they'll see and what they'll do.
• Parent outreach: Send a single clear message to parents in the pilot grade: "Starting [date], we're using a new app for dismissal. Download it here. Here's what will change. Here's what won't." Keep it simple. Parents don't need to understand the system — they need to know how to use it.
• Backup plan: Document what staff should do if a parent doesn't have the app on day one. The answer should be: handle it exactly as you do today, manually, and follow up with the parent afterward.

Week One: Measure Everything

The first week of a pilot is primarily a measurement exercise. What matters:

• Parent app adoption rate (what percentage of the pilot group has set up the app by end of week one?)
• Average dismissal time for the pilot grade vs. baseline
• Number of manual interventions (pickups that had to be handled outside the app)
• Staff error rate (missed notifications, late calls)
• Parent complaints or confusion reports

You can't improve what you don't measure. Week one baseline data becomes the comparison point for weeks two through four.

Common Week-One Problems and Fixes

Low app adoption: Some parents won't download the app by day one. Don't force it — handle them manually and follow up with a second outreach message mid-week. By week two, most holdouts have adopted if the first-week experience was smooth.

Notification latency: If the time between a parent arriving and a teacher receiving the notification feels long, check network connectivity in the classrooms involved. This is almost always a WiFi coverage issue, not a software issue.

Custody check friction: If the system is flagging pickups that staff know are fine, review the custody data in your SIS. Inaccurate SIS data surfaces immediately in a real-time system in a way it never does in a paper process.

The 30-Day Review

After 30 days, run a structured review with three groups: staff involved in the pilot, parents in the pilot grade, and school administration.

The questions that matter most: Did dismissal time change? Did the number of parent complaints to the front office change? Did staff feel that the process was easier or harder? Would they want to expand it to the rest of the school?

If the answers are positive, you have the evidence to propose a full rollout. If there are specific problems, you have 30 days of data to understand what caused them and how to fix them before expanding.

Expanding to Full School

A successful grade-level pilot makes the full-school rollout much easier. Staff have firsthand experience. Parent word-of-mouth has started ("the app works great, my neighbor in kindergarten said"). The implementation team has debugged the configuration against real-world usage.

Plan the full rollout over a two-week transition, grade by grade. Don't try to switch the entire school at once. By the time you reach the last grade, you'll have worked out every edge case.