A school trip register records which pupils are accounted for at a particular time and place. It should identify the register, the staff member taking it and any exceptions, rather than relying on the planned pupil list alone. Offline registers also need a clear distinction between marks saved on a device and marks received by the school system.
How is a trip register different from a pupil list?
The pupil list says who is attached to the visit. A register records what staff observed at a specific check. The same visit can have separate departure, arrival, boarding and return registers, each with its own context.
Give each register a recognisable name so another member of staff can distinguish a morning check from the latest one. Keep the roster current when pupils are added or withdrawn, and reconcile the actual departure group before using a copied or downloaded list.
How should attendance exceptions be recorded?
Use explicit statuses to distinguish pupils who are present from those accounted for elsewhere or still unresolved. An overall count is useful, but staff also need to identify the individual exception and its recorded context.
Trip Manager's register offers states including present, absent, expected elsewhere, collected by parent, with first aider, missing and not marked yet. Staff must select a state from their actual check; neither a previous register nor completed consent proves a pupil is currently present.
- Agree which member of staff owns each check.
- Use notes to clarify an exception where appropriate.
- Make unresolved states visible and follow the school's response procedure.
- Avoid treating a bulk marking control as a substitute for checking the group.
What should staff prepare before going offline?
Prepare the assigned trip on each device while a connection is available, then check that the information needed for the visit opens correctly. Downloading yesterday's plan is not enough if the roster or arrangements have changed today.
Trip Manager's iPhone and iPad app lets staff prepare assigned trips for offline use and queue register marks until a connection returns. This applies to supported trip information and registers; it does not mean every platform feature or parent message works without connectivity.
| Before departure | When a connection returns |
|---|---|
| Sign in and open the assigned trip | Check queued marks are received |
| Prepare current trip information | Review waiting or unsuccessful sync states |
| Check the roster and device access | Resolve discrepancies with the trip team |
| Agree a fallback if the device fails | Reconcile any separately recorded changes |
Why does sync status matter?
A mark waiting on a device is not yet a shared update. Staff need to know whether another colleague or the school office is looking at the same register information.
The companion app distinguishes sent and waiting states. After reconnecting, review those states and any discrepancy rather than assuming signal restoration completed every action. During a software demo, ask to see the offline-to-online handover as well as the attendance screen.
What should a school check in a register demonstration?
Ask to see a realistic attendance check with an exception, a second register later in the day and the history staff can revisit. Then prepare a trip for offline use and inspect what the app reports when queued marks are sent.
Trip Manager combines web registers with a companion staff app, keeping the trip roster and register history within the visit workspace. Access to sensitive pupil information is a separate permission, so include staff role checks in your rollout plan.
Read next: School setup and MIS checks