What's Really Holding Your Dismissal Process Together?

Kyra Sandness
4/23/2026
What's Really Holding Your Dismissal Process Together?

Every school has one. The person who knows every exception, every parent's face, every last-minute change. They've been at the front desk for a decade, they remember which student goes home with grandma on Thursdays, and they've kept afternoon dismissal running smoothly for years. The process works because of them, and most schools don't fully realize that until something forces the issue.

That's the honest conversation we had at April's Connected Schools Webinar. Three school operations leaders sat down to talk about dismissal, not a highlight reel, but an honest look at where things actually stand.

The System That Isn't Really a System

When Jeffrey, Director of Operations at The Philadelphia School in Center City Philadelphia, sat down with his team before the webinar to map out their dismissal process, they tried to build a flowchart. It didn't go well. Attendance data gets exported into a dismissal sheet, where it immediately becomes static. Teachers work from that frozen snapshot for the rest of the day. Aftercare, sports, and enrichment programs all live on a separate sheet that connects to nothing.

"We were all feeling nauseous," Jeffrey said, "because the amount of dependencies was just endless. This person has to tell that person, who exports to this spreadsheet, and that data is dead."

The disconnect between systems compounds the problem. At The Langley School in McLean, Virginia, parents send dismissal changes to whoever they can reach first: the division assistant, the teacher, the front desk, sometimes all three. Each of those people works from a different document, and none of those documents talk to each other. On most days, a dedicated staff manages to stitch it all together. But the fragility of that arrangement becomes most visible when something disrupts the routine. 

When a key division assistant who carried much of that institutional knowledge was out for an extended period, the gaps became impossible to ignore. Students missed buses. Staff scrambled to track down early pickups.

"It always worked eventually," said Dwayne Green, Chief Operations Officer, "but instead of being one step, it took like five steps."

Across three campuses and 1,200 students, DeShaun Blake, Director of Operations at Kindezi West Charter School in Atlanta, was living the same reality. Carpool, vans, walkers, and sports all move simultaneously. For a long time, two staff members had quietly made themselves responsible for tracking all of it, without that responsibility ever being formally documented or shared with anyone else. The process appeared to work. It just wasn't built to last.

When the Process Lives in One Person

What each of these leaders described is a version of the same structural vulnerability: a process that functions because of who is carrying it, not because of how it's built. And often, the people carrying it most aren't even the ones you'd expect. DeShaun noted that when he arrived at Kindezi, the two staff members who understood student movement at the end of the day weren't senior administrators. When leadership had questions, they didn't have answers, because the knowledge wasn't institutionalized. It belonged to individuals.

It's also something that even well-intentioned leaders contribute to without realizing it. Collecting a dismissal change from a parent in the carpool line and handling it personally rather than routing it through a formal channel feels efficient in the moment. But that information doesn't exist anywhere else in the system. If that person isn't there the next day, those students have no documented plan for where they're going.

Jeffrey connected this to a longer-term question about institutional continuity. When two long-tenured front office staff members left his school within the same period, entire procedures disappeared with them. Basic things, like calling parents when a student had no attendance note, had never been written down.

"I hope the school outlasts me," he said, "and when it does, that someone else will know what I was doing because I wrote it down."

What Getting Honest About It Actually Looks Like

One of the most useful parts of the conversation was what each panelist said about the process of actually looking at dismissal clearly. When the webinar's live poll asked attendees what their biggest obstacle to improving dismissal was, the top answer was a lack of time to step back and rethink it.

All three panelists gently pushed back on that framing. DeShaun's advice was to peel back the onion before trying to solve anything. Understanding who controls which pieces of the day, where the handoffs are, and what breaks when a specific person isn't there is the necessary first step. "You have to be ready to look at what the rest of your day actually looks like," he said, "because when you start, you'll see other processes you didn't even realize were connected."

Jeffrey offered a practical starting point for schools feeling overwhelmed by the scale of the problem: start with one or two people, not the full stakeholder list. Build a shared understanding of the problem first. Momentum comes from that small group seeing clearly what the issues are, then expanding from there.

"You don't learn to juggle five things at once," he said. "You juggle one really well, then two, then three."

Dwayne's advice was simpler still. Any step toward efficiency is a good step. You don't have to fix everything at once to move in the right direction.

The Shift Worth Making

What came through most clearly in this conversation was that these leaders aren't waiting for something to go wrong before taking a closer look. They're asking harder questions now, while things are mostly working, because they've recognized that "mostly working" and "built to last" are not the same thing.

Dismissal sits at the intersection of safety, communication, and operational reliability. It's also, as DeShaun put it, one of the most important moments of the school day.

"We always want to return students to their families the way they were found when they got to us," he said. "Dismissal is a part of that."

The schools that are ahead of this challenge aren't necessarily the ones with the most sophisticated tools. They're the ones that took the time to look honestly at what they had and ask whether it would hold up without the right person in the right place at the right time.

Watch the full recording of "The 3:00 Problem: What's Really Holding Your Dismissal Process Together" to hear the complete conversation, including how each panelist is thinking about next steps for their schools.

Latest articles

Ruvna at ATLIS 2026: Four Sessions, One Booth, and a Rooftop Happy Hour

Ruvna is heading to ATLIS 2026 in Columbus with a team of seven, four sessions, and a rooftop happy hour co-hosted with Blackbaud and August Schools. Here's everything happening at booth #65 and beyond.

The Person Who Holds Dismissal Together — And What Happens When They're Not There

Most independent schools don't have a dismissal system. They have one person holding it together. Ruvna Dismissal is built to change that.

How Independent Schools Are Thinking About Safety During High-Traffic Events

From graduation ceremonies to athletic events, high-traffic events open your campus to an entirely different population. Here's how schools are approaching safety planning when it matters most.