The first week of school is a stress test for every system you run. Rosters that looked fine in June reveal duplicates, missing guardians, and orphan course sections on the Tuesday teachers expect to take attendance. A back-to-school SIS readiness checklist gives operations leads a way to flush out these problems in the quiet weeks before students arrive — instead of triaging them while phones ring at the front desk. The schools that handle opening day quietly are almost always the schools that started checklist work in early summer, not in the last week of August.
Six weeks out: rosters and student records
Start by reconciling who is actually returning. Pull last year's active list, mark graduates and withdrawals, and import the new enrollment cohort. Resolve duplicate records before anything else — duplicates multiply downstream into duplicate transcripts, duplicate billing, and duplicate parent emails. In Borderset, the student directory in student tracking lets you spot near-matches by name plus date of birth in one screen, so the registrar can merge or escalate before any of those records touch a gradebook.
Verify guardians and contact data
Send a guardian-contact verification request through the family portal a month before opening day. Most parents update an email or phone number every summer; catching those changes pre-cycle saves your office from chasing dismissal authorizations on day one. Pay particular attention to custody and pickup authorization fields, which tend to drift over the summer and become urgent on the first afternoon dismissal.
Lock in attendance codes
Confirm the code set teachers will see — present, tardy, excused, unexcused, early dismissal — and disable last year's deprecated codes. If you run multiple sites, the playbook in attendance tracking for multi-campus schools is worth re-reading before the first bell. Borderset lets a district admin push the code set to every campus at once, which eliminates the most common cause of inconsistent reporting in week one.
Four weeks out: schedules, sections, and staff
Build out the master schedule in schedule management, assign room and teacher to every section, and run a conflict check before you publish to teachers. The most common day-one error is a section with no room or two sections sharing a teacher in the same block — both surface immediately when you validate against bell times. Print a single-page schedule for every classroom door; it is the cheapest way to catch a missed room assignment before parents notice.
Re-provision staff accounts
Deactivate departed staff, update role assignments for promotions, and confirm new hires have the right access scope. If you are migrating from an older platform this season, what to expect when integrating your school SIS walks through the sequence so August does not collide with go-live. Send a five-minute orientation email to every staff account with login link, password reset path, and the name of one human they can call.
Two weeks out: family logins and final dry run
Generate or refresh family portal invitations. Many parents will not log in until the first homework lands, so send the invite early with a one-page guide. Run a final dry run: a registrar takes a sample student through enrollment, schedule, attendance, and gradebook screens and notes anything that confuses. That checklist becomes day-one front-desk training. Schools using Borderset typically schedule a 30-minute readiness review with their implementation contact in this window — see how Enverson collapsed coordinator load for the pattern.
If you treat back-to-school as a checklist rather than a fire drill, the SIS becomes invisible by week two — which is exactly the goal. The signal that you got it right is a quiet front office and teachers who are talking about lesson plans instead of login problems. Borderset is built to fade into the background when the setup is honest, and the checklist above is the fastest way to get there.