When a group runs two or more campuses, holiday and break calendars almost never line up exactly. One site observes a regional holiday the other does not. One closes early for parent-teacher conferences while the other holds a full day. Families with siblings at different campuses notice immediately, and so do attendance reports that suddenly show one site with a no-school day coded as absences. Borderset treats per-campus calendar divergence as the default, not the exception, which is the only honest way to model how multi-campus groups actually operate.
Build a base calendar, then overlay per campus
The clean model is a group-wide base calendar — federal holidays, full-system closures — with per-campus overlays for everything else. In schedule management, define the base, then attach campus-specific exceptions: early dismissals, regional observances, professional-development days. Each campus's published calendar then resolves to base plus its own overlay, automatically. The overlay model also means a single edit at the base level (a snow day declared by the district) propagates to every campus instantly.
Code break days correctly in attendance
A no-school day is not an absence. Make sure every break day is flagged as a non-instructional day so teachers cannot record attendance and reports do not count it. Most multi-campus attendance noise comes from one campus's break appearing as a sea of absences in a group-level report. The discipline behind clean attendance under these conditions is covered in attendance tracking for multi-campus schools. In Borderset, the non-instructional flag also suppresses parent-facing absence notifications so families do not get a "your child was absent" email on a holiday.
Sync to payroll and contracted days
Faculty contracts often promise a number of working days. When one campus adds a break, that campus's faculty calendar must reflect the change or you end the year with miscounted contracted days. Tie the campus overlay directly to staff calendars so payroll and HR pull from the same source as instruction. The cost of getting this wrong is a year-end true-up conversation no operations lead wants.
Communicate clearly to families
Families with multiple children across campuses need one place to see both calendars. Publish the merged view in the parent portal and send a single monthly summary that calls out where campuses diverge. Schools that get this right reduce the December and March surge in "is school open Monday?" tickets to almost nothing. The team behind the Level Up case study documented the comms cadence that worked for them, and it is worth borrowing. The pattern that consistently helps: a Sunday-evening reminder the night before any partial day, sent to every household with a child affected.
Internal documentation matters too
Operations staff need a single source of truth about why a particular campus has a different day off. Drop the rationale and approval into your internal blogs feature so anyone joining the operations team next year understands the precedent without re-litigating the decision. A two-paragraph note saved in the right place will save a thirty-minute meeting eighteen months later.
Audit before publishing the year
Before the calendar goes out, run a comparison view across campuses: instructional days per campus, early dismissals per campus, conferences per campus. Discrepancies become discussion points before they become surprises. Borderset's calendar overlay makes that comparison a single screen, so leadership can sign off knowing the year is internally consistent and that every break, holiday, and half-day will flow correctly into attendance, payroll, and family communications. The goal is a calendar that nobody has to apologize for once the year begins.