Lockers are one of those workflows nobody talks about until they break. Two students share a number, a combination gets lost in a back-of-house spreadsheet, a transfer student arrives and the front office cannot tell which bank has open units. Locker assignment is not glamorous, but the same operational discipline that keeps attendance and schedules clean applies to physical assets. With the right structure, locker management runs itself for the year.
Assign by grade, cohort, and proximity
The fastest way to lose control of locker assignments is to hand them out in alphabetical order from a paper list. Group lockers into banks, then assign by grade and cohort so students travel the shortest distance between homeroom and their locker. Borderset stores locker banks as a structured list tied to the student record — pull a roster, draw from a bank, and the assignments are recorded once.
Combination and key tracking
Combinations and key numbers should never live in a shared spreadsheet that any front-office user can open. Treat them like attendance overrides — visible to the assistant principal and the custodial lead, not to substitute teachers. With student tracking in Borderset, locker combinations sit on the student record behind a role-based permission so they appear only for staff who need them. The audit log shows who viewed each combination and when, which matters the day a student claims someone else opened their locker.
Mid-year changes without spreadsheet sprawl
Mid-year is where locker workflows usually decay. A student transfers, a locker jams, a pair swap so one student can be closer to the elevator. When each change lives in a separate email, the master roster drifts within weeks. Borderset records the swap, retires the previous assignment with a timestamp, and updates the directory the next time the front office prints a hall map.
Tie lockers to schedules, not just rosters
A locker is useful when it sits between two classes a student actually attends. If your schedule management data lives in the same system as locker assignments, you can flag students whose locker is on the wrong floor relative to their morning block. That kind of insight is invisible on paper but cheap to surface when the data is unified. It also helps when planning physical-education locker rotations alongside academic ones.
Locker workflows also intersect with attendance. A student who has not been in the building for two weeks is occupying a unit that could be reassigned to a new arrival. Pair locker reports with the attendance tracking patterns your school already uses and you have a simple rule: prolonged absence triggers a locker-status review.
End-of-year audit trail
The last week of school is when an unmanaged locker system reveals itself — abandoned belongings, broken latches, lost combinations. An auditable history of who held which locker, when it was reassigned, and what condition it was returned in turns the end-of-year sweep from a scavenger hunt into a checklist. Borderset exports the locker register as a CSV the facilities team can mark up, then re-imports it for the new year. That is how a small workflow stays small.
There is also a security dimension worth naming. When facilities staff need to access a locker for a maintenance issue, the request should be logged against the student's record with a reason and a timestamp. Borderset captures that record next to teacher and counselor entries through teacher tracking, so the same audit trail covers both academic and physical-asset interactions. The principal can answer a parent question about who opened a locker without piecing together emails from three departments.
A note for groups running several buildings
Districts and multi-campus operators feel locker management most acutely because each building has its own quirks — different bank numbering, different bell schedules, different facility leads. Pulling all of that into one record set is a quiet operational win. Our case study on scaling from two to nine campuses shows the same pattern in practice: small workflows, run consistently, scale better than big workflows run heroically.