How Multi-Branch Schools Coordinate PTM Scheduling Across Campuses

A school group running two, three, or a dozen campuses faces the same PTM coordination problem as a single school, just repeated at scale — and a few decisions are worth making deliberately at the group level rather than leaving every branch to figure out separately.

Should every branch run PTM on the same day?

Running every campus's PTM on the same date has an obvious appeal — one shared calendar announcement, one round of group-wide preparation. The tradeoff is that any group-level support (IT help, a shared admin fielding questions) gets stretched across every campus at once. Staggering PTM dates by a week or two per branch spreads that load without meaningfully complicating the parent experience, since each family only interacts with their own campus's calendar anyway.

Keeping each branch's records genuinely separate

Even under one management, each campus typically runs as its own school record — its own roster, its own bookings, its own branding — rather than one combined pool where a parent from one campus could ever see another campus's data. See what to check about data isolation for why that separation matters, group-wide or not.

Staggering rounds instead of running everything at once

Since PTM access opens per 30-day round, a group doesn't need every campus to open its round on the same calendar day — offsetting them by even a week gives group leadership a staggered view of how each campus's PTM cycle is progressing, rather than a single chaotic week where every campus's questions land at once.

None of this changes the underlying cadence question each campus still has to answer for itself — see how often schools should hold PTMs for that decision at the individual-campus level.