Who's Supposed to Remember Every Child's Day-to-Day Change?

At Kindezi West Charter School in Atlanta, dismissal ran on two people and a spreadsheet, and Director of Operations DeShaun Blake knew exactly how fragile that made things.

"We live off these Excel and these Google Sheets that just do not work for real-time movement of our students. A parent is calling the front desk on a regular basis saying, 'My child on Thursday is going here.' Who is supposed to remember every single child's day to day change?"

What Thursday Actually Looks Like

Dismissal isn't one process. It's several, running at the same time, in different directions.

At Kindezi West, that meant carpool, cafeteria vans, sports pickups, and walkers all leaving campus simultaneously, tracked across spreadsheets that could show what a student's schedule was supposed to be, not what it actually was that day. A spreadsheet doesn't know a parent called at 1:45 to say their child is going to a friend's house instead. A person has to know that, remember it, and pass it along to whoever's actually at the point of dismissal.

Multiply that by 417 students, and the math stops working long before the last bus pulls away. Every schedule change is one more thing a specific person has to catch, hold onto, and relay correctly, on top of everything else dismissal already requires.

Which raises the obvious question DeShaun asked: who is that person, and what happens when they're not the one at the front desk that day?

When Two People Are the Whole System

At Kindezi West, the honest answer was that only two staff members understood the full dismissal process. Everyone else was working from whatever those two people had time to communicate.

That's not a criticism of the school. It's what happens by default when dismissal runs on institutional memory instead of a shared record. New hires had no clear handoff. Updates didn't reliably reach everyone who needed them. Those two people had built real expertise, the kind that usually only comes from doing something well for a long time. The opportunity was turning that expertise into something the whole school could rely on, not just the two people who held it.

That's worth sitting with regardless of what platform a school ends up using. A dismissal process that depends on specific people being present isn't really a process. It's a workaround that's held up so far.

What Changed

Kindezi West was already using Ruvna Accountability, running emergency drills through the platform, so when Ruvna Dismissal launched, DeShaun's team evaluated it against three questions: does it integrate with their SIS, is it safe, and can everyone on staff actually access it.

The answer that mattered most was the third one. With Ruvna Dismissal, any authorized staff member can see real-time student movement, not just the two people who used to hold that knowledge. Changes in their SIS, InfiniteCampus, sync automatically, so a schedule update doesn't require anyone to re-upload a spreadsheet or manually track down who needs to know.

As DeShaun put it, "Anybody that we give access to can see all the things that are happening and movements. That just blew our mind."

When Ruvna Dismissal launched, our CEO Joey Nutinsky put it this way: "Behind most dismissal processes, there's one person holding it all together in ways that are more fragile than anyone realizes." Kindezi West is what that looks like in practice.

The shift wasn't really about the software. It was about what the software let the process stop depending on.

DeShaun's Advice to Other Schools

Asked what he'd tell other schools considering the same step, DeShaun didn't lead with a product pitch. He said to be willing to peel back the layers, know your top three real problems before evaluating any solution, and start with a small group of the right stakeholders before rolling anything out more broadly.

That's advice worth taking regardless of what a school ends up choosing. The goal was never another tool. It was making the afternoon safer and easier for every person responsible for getting a student home, and making sure that responsibility didn't rest on whoever happened to be at the desk that day.

What's Holding Your Dismissal Together?

If your dismissal process is running smoothly right now, it's worth asking who's actually holding it up. If the honest answer is one or two specific people, that's not a failure. It's just useful information about where the risk sits.

You can read the full Kindezi West story here, and if you want to talk through what a dismissal process that doesn't depend on any one person could look like at your school, we're happy to walk you through it.