If a family moves to a different school in your charter network in February, how simple is the records exchange? On paper, it should be simple—you’re a single network, after all.
But their experience depends entirely on the campus they’re leaving.
That campus registrar may pull the files from a shared drive and send them that afternoon. Or they may pull them from a filing cabinet, but the person who understands the filing convention is out this week. Maybe the records request goes to an inbox that three people see, but none of them feel ownership over.
This system isn’t by design, but as different campuses in a network open, each builds its own processes. The network focuses on standardizing curriculum, hiring, finances, facilities, and the SIS, but no one has ownership of records management.
Autonomy is why these networks work
Charter networks often thrive because of campus autonomy. Principals who can adjust a schedule, change a staffing model, or respond to what's happening in their building make the model work.
If you lead operations at a network, maybe you've seen a poorly executed centralization effort. A well-reasoned leadership decision arrives at a campus, but isn’t well-received. The network can show the savings in a spreadsheet, but the local principals voice different concerns and frustrations.
So while some skepticism is earned, it's also why centralizing the entire back office can be a hard sell. But when you consider which functions qualify as advantageous to centralize, records land on the shortlist.
Which kind of autonomy matters most?
It helps to separate the autonomy a network chooses from the autonomy it inherits.
Someone argued for instructional autonomy. They wrote it into the charter and defended it at renewals. The same goes for school culture, staffing models, and how a campus handles its calendar. These are the things that make one campus different from another, and those differences help create local culture.
Records autonomy tends to look different. No one advocated for a separate filing system at every campus, but as each campus opened, they needed a way to move student records, and someone built something that worked well enough at the time. No campus differentiates itself by how it files transcripts, and no family chooses a school because of its record-keeping process. So why not bring records management under a single system?
What does variation cost?
When every campus runs its own process, the network back office can't answer a basic question about any of them without making a call. You can't report on a turnaround time you don't collect, and you can't fix a problem you never see.
At most campuses, one person understands how the records system works, and the processes may not be documented. When they take a week off, requests stall. When they leave, the campus often has to rebuild the entire process. Our Spring 2025 implementation research found that registrars were more likely than non-registrars to work in paper-heavy environments, which makes that dependency a tough handoff.
Families feel the inconsistency, too, because two families in the same network can ask for the same thing and get two different answers and wait times.
Some states have tighter turnarounds than others. Florida gives schools three school days to produce a student record. Georgia, California, and Texas give ten working days.
What happens when a campus closes?
A charter is a contract with an end date, and how far out that date sits depends on the state and its performance metrics. Five years is common, though some extend to ten or fifteen years—but no state issues a permanent charter.
Student records don't work on that schedule. Alumni request transcripts for decades after they graduate, and those requests don't stop when a school closes.
More than 25% of charter schools close within five years, and 55% close within 20. In the first half of 2025, 50 charters announced closures, with 27 of them citing low enrollment. Campuses merging and authorizers reassigning schools also create problems for records requests.
A charter high school in Oklahoma City closed on July 1, 2026, but paper transcripts for 100 students still sat in the empty building weeks later. The state board and the school's board disagreed over who held the key. And while the state had electronic copies the whole time, the paper records were stuck as a security risk.
Under a network-level process, those records live and leave with the network, not a building.
What makes a function worth centralizing?
Ask three questions about any function before you standardize it.
- Does it differentiate one campus from another?
- Does it impact instruction or school culture?
- Does it create risk for the network when it varies?
Most functions give mixed results with these three questions. Food service differentiates a campus in ways families notice, and professional development directly influences instruction. Records answer no, no, and yes.
You don’t need to centralize the whole back office to make a change that the staff and families will notice. And it gives you somewhere to start, because a network with standardized records has a working example to point to the next time the question comes up.
Drop what no one will miss
Under a network-wide platform, campus staff lose the parts no one enjoys in the first place: chasing paper files, fielding status calls, waiting for callbacks from other schools, and explaining delays to families.
- Families and alumni submit requests themselves through a secure portal
- Staff approve requests instead of processing them by hand.
- The back office gets a single view of every request across the network, plus an audit trail to produce at renewal.
- A new campus never has to build its own process again.
With Parchment by Instructure, charter network campuses keep their individual cultures, network leadership gets consistency, records are digitally available and secure, and families get the same experience no matter which school they call.
Where to start
The family that moved in February doesn't know how many campuses your network runs, and they shouldn't have to. They just need a record to arrive at the new school so their student can be placed correctly.
Standardizing records brings consistency to the back office, simplifies processes for staff and alumni, and makes records available online.
