Guided CSV import
Load a defined timetable export from SIMS or Arbor, map the required columns and identify problems before the data enters the working view.
Planned feature set
PASSport is planned for pastoral staff who need a quick timetable view of selected pupils. A school-generated CSV from SIMS or Arbor becomes a visual, filterable day map, replacing repeated timetable cross-checking with one clear period-by-period reference.
Load a defined timetable export from SIMS or Arbor, map the required columns and identify problems before the data enters the working view.
See the expected lesson, room and teaching period for selected pupils without opening individual timetables one by one.
Create and switch between authorised pastoral cohorts, year groups or working lists while keeping the whole day in view.
Move directly to now, next period or a chosen point in the day so the display matches the pace of pastoral work.
Why it earns a place
A product should do more than put a polished skin over the same institutional friction.
PASSport does not reproduce the MIS. It reshapes one defined dataset around the rapid operational question pastoral staff need answered.
A controlled CSV route can deliver value without requiring a school to begin with a complex live-system integration.
The product shows where a pupil is timetabled to be. It is not live location tracking and it does not replace attendance or safeguarding systems.
Expected impact
The intended impact is faster period checks and fewer timetable look-ups when pastoral teams are coordinating support for a defined group of pupils.
No invented stopwatch claims. Numeric time savings will be published only after pilot schools have established a baseline and measured the same task using the product.
Security · UK GDPR
These are requirements for the planned service, not a claim that an unfinished product is certified or that software makes a school automatically compliant.
Define the minimum fields needed for each job, validate imports and avoid copying wider MIS records into the product without a clear purpose.
Use role-based permissions, least-privilege defaults and auditable administrative actions for data that should not be visible to every member of staff.
Treat encryption in transit and at rest, tested backups, retention controls and reliable deletion as baseline technical requirements.
Prepare a clear data map, processing agreement, subprocessor list, retention schedule, technical-measures summary and practical DPIA support before contracting.