That’s Not a Demotion! Part Deux.

The hard work is just beginning

When last we left our heroes, Karega Rausch had just traded a national perch running the National Association of Charter School Authorizers for a job managing buildings and buses in Indianapolis, and Nevada’s SPCSA was in the middle of turning a $14 million charter failure into a fresh start under a proven provider.

That was the trailer, the argument for why the Indianapolis Public Education Corporation matters and why it’s a bigger deal than it might first look.

This is the part where we go into the machine room. IPEC is a genuinely new kind of institution, built to manage facilities and transportation for both Indianapolis Public Schools and the city’s charter schools together, sitting between authorizing and pure logistics, solving a scale problem no single school board or authorizer could solve alone.

I’ve lived through a version of this before, in DC, and the lessons are less about strategy than about the seams that don’t show up until you’re a few years into execution.

The timeline problem

DC relinquished school facilities management to what was then the Office of Public Education Facilities Modernization, later folded into the Department of General Services, and separately relinquished technology operations and capital planning to a centralized IT function. The logic was the same logic behind IPEC: pool the expertise, plan at scale, stop asking every individual school to reinvent facilities and IT procurement from scratch. It was, on the whole, a good idea.

But especially in the early years, the seams showed. A school in turnaround trying something like a credit recovery model needs a technology refresh now, this year, because the model depends on it. A centralized, genuinely well-designed, cost-effective capital plan says the refresh is two years out, because two years out is when it makes sense for the system as a whole. Both parties are right.

That’s the tension: the school’s timeline and the system’s timeline are not the same timeline, and nobody built the model to reconcile them when they conflict.

Whose norms govern the bus

Transportation raises a version of this that’s easy to miss on a spreadsheet. Pooling buses across operators is a genuinely good use of a scarce, increasingly hard-to-staff resource. But a school bus is also, whether anyone designs it this way or not, an extension of a school’s culture and discipline system.

Put students from multiple schools, multiple discipline codes, multiple cultures on the same bus, and a real question emerges that transportation optimization software will never answer on its own: whose norms govern the bus, and who’s accountable when they conflict?

Shared common space raises the same question in a more everyday form. Cafeterias, gyms, and other spaces two co-located schools have to split between them are exactly where two different school cultures rub up against each other most directly, different schedules, different rules about noise and movement, different disciplinary expectations, all coexisting in spaces that were designed and built for one school, not two competing for the same square footage on the same clock.

Wait, what school is this?

Physical security compounds this in a way that gets almost no attention. Public schools have spent the last two decades converging on a single, tightly controlled point of public entry, one door, one check-in desk, often a metal detector, specifically so a school knows exactly who is walking in and can keep its students safe. Co-location scrambles that by design.

If two schools with two different operators and two different discipline codes share one entrance, whose staff is actually screening who walks through it, and whose rules govern the lobby? A parent standing in that entryway with a five-year-old, watching an unfamiliar uniform walk past toward a different set of classrooms, might reasonably think: wait, what school is this?

That confusion isn’t trivial. Families trust schools partly because a school has a legible identity, one culture, one set of adults responsible, one front door that means one thing. A shared entrance is a small detail on a floor plan and a first, possibly defining, impression for a family trying to figure out where they actually belong.

The property law nobody wants to touch

There’s an even more basic wrinkle Indianapolis is discovering in real time: buildings don’t agree to be shared just because a law says they should. IPEC lets schools opt in or opt out of putting their buildings under the corporation’s control, building by building, and the state is using real money to make opting in attractive. Charter facilities funding, currently $1,400 per student, moves to IPEC and only flows to buildings that actually join the portfolio.

That’s a real incentive, but it runs straight into a mess IPEC didn’t create and can’t simply legislate away. Indianapolis has more than sixty charter schools, and their buildings all got there differently: some in old district buildings, some in converted churches, some newly built, many financed with debt held by lenders who have their own approval rights over anything that happens to the property.

Multiply that by sixty-plus schools, each with its own financing history, and you get a property law puzzle that has nothing to do with pedagogy and everything to do with whether IPEC’s theory of shared infrastructure can actually attach itself to buildings that were never built with sharing in mind.

Indianapolis’s head start

There’s real reason for optimism here, and it’s specific to Indianapolis. The city’s Innovation Network Schools, many of them charter-run, have operated inside IPS buildings for close to a decade now, and they already contract with the district for shared services, including transportation and maintenance.

That’s not a solved problem. Mixed academic results across the network suggest the model still has real room to grow, but it means Indianapolis isn’t starting from zero on the governance and behavioral norms this kind of sharing requires. IPEC inherits a city that has already been practicing a smaller version of exactly what it now has to do at scale.

None of this is an argument against IPEC. If anything, it’s the opposite: the fact that these seams are predictable, the timeline mismatch, the bus, the shared cafeteria, the front door, the tangled property titles, means they’re not an excuse to avoid this kind of institution. They’re a checklist for building it well.

The mistake isn’t attempting cross-sector facilities and transportation management. The mistake is discovering these seams the way DC discovered them, a few years in, one frustrated turnaround principal at a time, instead of designing for them from day one.

Indianapolis has a head start most cities attempting something like this wouldn’t have. Whether that’s enough is the actual open question, more interesting, honestly, than whether the idea itself is sound.