Change Management in School Districts

Change management in school districts is the work of moving people, processes, and policies from one operating model to another without breaking the work happening in between. The hardest is often the behavior change required to actually use the technology, and the governance required to sustain it after launch.

This guide draws on Radnor Township School District's first-year experience moving finance workflows off paper, presented at PASBO in March 2026. Radnor processed over 2,600 forms in year one, expanded from 3 active workflows to 18, and reported 89% positive or neutral user feedback. Below is the 6-step playbook they used, developed by Informed K12 through working with 450+ districts, plus the questions every district should answer before they start.

The 6-step playbook

Step 1: Inventory

Before prioritizing, list every form. For each one, capture the department, the form name, annual volume, the format it lives in today (paper, PDF, spreadsheet), and the current owner.

The objective at this stage is not to decide what to digitize. It is to make the scope of the work visible. Districts consistently underestimate how many forms they actually run on. Radnor, for example, started with three workflows in scope: Mileage Reimbursement, Payment Order, and Conference Request. By month twelve, they had eighteen.

Three patterns to look for during inventory:

• Forms that exist in multiple versions across school sites.

• Forms with unclear ownership, where no one knows who maintains them.

• Forms that route through more hands than the volume justifies.

Step 2: Prioritize

Plot every form against two axes: volume and friction.

Radnor's starters were Payment Orders (75-100 per month, 6+ handoffs, ~2 weeks to process), Mileage Reimbursements (10-15 per month, 5 handoffs, ~2 weeks to process), and Conference Requests (5-10 per month, 8+ handoffs, up to 2 weeks). All three sat in the high-friction band. The Payment Order was the highest volume of the three, which made it the natural first launch.

Step 3: Map

Once a form is selected, map the current state and the future state through a working session with the people who actually run the form today. Three inputs feed the session: the current form, the contact list of every approver, and the current approval process. Three outputs come out: a form prototype, an approval chain, and a workflow map.

Two rules for the working session:

• Walk through every step, not just the happy path. Name every exception.

• Confirm routing rules before configuring anything. Routing assumptions made in design that turn out wrong in production cause adoption problems that no amount of training fixes.

Step 4: Design

Build controls into the form itself, not into a procedure document staff are supposed to follow.

• Required fields and attachments prevent incomplete submissions.

• Standard approvals reduce guessing about who needs to sign.

• Consistent routing makes exceptions rare instead of routine.

• Status visibility eliminates "where is it?" emails to the business office.

The point of this step is to remove decisions from the runtime of the workflow. Every decision left in the workflow is a place it can stall.

Step 5: Enable

Designate two owners for every workflow: an Approvals Owner and a Form Owner. The Approvals Owner maintains approver lists, handles role changes when staff turn over, and owns routing exceptions. The Form Owner owns field changes, maintains dropdowns, and monitors bottlenecks.

This is the step districts most commonly skip and most commonly regret. Without named owners, workflows drift. Approvers leave the district and their workflows route into a void. Forms accumulate fields no one needs and lose fields they do. Six months in, the workflow is technically live but functionally broken.

Step 6: Launch in waves

Big-bang launches fail in K-12 because the pace of district operations does not stop for adoption. Waves match the operational rhythm.

• Wave 1: Train by role. One access point. Intensive support during the first weeks.

• Wave 2: Add workflows. Reinforce norms from wave 1. Close gaps.

• Wave 3: Expand district-wide. Measure adoption. Plan the next batch.

Radnor launched three forms in June 2025. Training was 30 minutes, role-based, scheduled near go-live. Outreach ran on a four-week cadence after launch. The intranet served as the single access point, so staff did not have to remember which platform held which form.

Radnor Township: What the first year actually looked like

Radnor Township School District is in suburban Philadelphia. Like many districts, finance workflows ran on paper and PDFs. Outdated forms caused avoidable errors, and manual handoffs drained staff time. The initial scope was three workflows: Mileage Reimbursement, Payment Order, and Conference Request.

After one year on Informed K12, Radnor processed over 2,600 forms, expanded from 3 active workflows to 18, and reported 89% positive or neutral user feedback.

Four metrics that actually matter

Districts evaluating their change management should track four metrics.

• Cycle time: How long does it take forms to be completed from submission to final approval?

• Return rate: How many forms get returned with errors?

• Step-level efficiency: Where do forms get stuck?

• Adoption: Who is using the new process versus who is still working around it?

Qualitative signals matter too. Fewer "where is it?" emails to the business office. Less re-entry. Staff bringing forward new forms they want digitized. These are the early indicators that adoption is taking hold.

Pitfalls that derail change management

Five patterns consistently undermine district change management efforts.

• Digitizing the PDF without fixing routing. A digital form on a broken approval path is still a broken approval path.

• Letting exceptions become the norm. Every approved exception is a precedent. Document them deliberately or stop accepting them.

• Launching without anticipating employee needs. Training without context, support without escalation paths, and rollouts without site-specific adjustments.

• No owner for updates and approvals. Without named owners, the workflow degrades within a school year.

• Failing to monitor the process after launch. Going live is not finishing. The bottlenecks shift, and the work shifts with them.

Radnor's full PASBO presentation, including the form inventory worksheet, prioritization matrix, workflow mapping template, training and launch checklist, and adoption tracking checklist, is available to download.