SCHOOL OPERATIONS · TRANSPORT ADMINISTRATION
School Transport Record Management: Vehicles, Drivers, Stops and Student Assignments
A school-side guide to maintaining transport records, verifying student pickup context and distinguishing administration from live vehicle tracking.
Conceptual product view · no customer records or performance figures
THE SHORT ANSWER
Organise school transport records by maintaining current vehicle and driver information, clear pickup/drop details and verified student assignments. Keep transport fees and attendance in their relevant school processes, communicate carefully with families and review exceptions under school policy. Administrative records should not be mistaken for route optimisation or live GPS tracking.
01 / VEHICLE & DRIVER RECORDS
Keep the basic operating information current and accountable.
A school’s transport office needs to know which vehicles and drivers are associated with its service and who is responsible for maintaining those records. Establish a review cadence for changes, define which supporting documents are required under school policy and identify who verifies that information before an assignment is made.
Avoid treating a record as evidence that a vehicle is roadworthy or that a driver meets every legal requirement. The school must follow applicable obligations and professional advice, maintain its source documents and ensure that only authorised staff update transport information. Software recordkeeping is not a substitute for inspection or compliance.
02 / STOPS & PICKUP DETAILS
Make pickup and drop information specific enough to use safely.
Agree how the school names stops or pickup points and how staff verify that a student is associated with the correct location. Families may move or request a change during the year, so define who can approve an update and how the revised information reaches the relevant transport staff.
Protect location information and share only with people who need it for the transport task. If a record is incomplete or conflicting, establish a confirmation step rather than assuming the most recent message is accurate. A clear assignment can reduce ambiguity, but the school still needs operational procedures for handover and student safety.
03 / STUDENT ASSIGNMENTS
Verify the learner, transport context and any change together.
When a student is assigned to transport, confirm identity, the approved pickup/drop context and the effective date. If the school allocates seats or has other capacity rules, those decisions should be made by the responsible transport team under its policy. Keep a way to review previous assignments when a family asks about a change.
Do not infer that assignment to transport also sets a route, stop sequence or vehicle allocation unless the school has established that relationship and the product supports it. The registry does not support claiming every route or vehicle-to-route workflow. Confirm the exact scope before planning around a specific dispatch process.
04 / FEES & ATTENDANCE
Keep related administrative records distinct but reconcilable.
Transport charges may be part of a school’s fee process or handled according to its policy. Define the category, period and adjustment authority, and ensure accounts staff can distinguish a transport charge from the underlying student transport assignment. Review any outstanding amount against the relevant fee records before contacting a family.
Transport attendance or boarding information can be sensitive and operationally important. Clarify who records it, what the status means and how exceptions are handled. Do not imply that a record provides real-time vehicle position or confirms physical handover unless a separately verified system and process support that use.
05 / FAMILY COMMUNICATION
Share confirmed information through a controlled channel.
Parents need accurate information about assigned pickup/drop context and school-approved changes. Check student identity and recipient details, communicate the effective date and explain whom to contact with an urgent question. Avoid sending broad lists that reveal other students’ locations or transport arrangements.
A notification or parent-facing information field should not be treated as a live location service. Confirm whether communication is outbound only, how replies are handled and which staff monitor the channel. Keep a separate emergency protocol for situations requiring immediate action.
06 / REPORTS & REAL-TIME LIMITS
Use records to review assignments, not to imply a live fleet view.
A periodic transport review can check student assignments, vehicle and driver records, pickup details and unresolved change requests. Use the reports the system actually provides and retain the school’s supporting evidence. Route or vehicle assignment and vehicle/route reports need explicit confirmation before claiming them as product functions.
CodePex School ERP declares vehicle and driver records, stops/pickup points, student transport assignments, driver/vehicle relationships, transport fee handling, transport attendance and parent-facing transport information. GPS/live vehicle tracking, route maintenance/assignment and vehicle/route reports are not declared for public claims. These School ERP statements do not apply to Campus Transport, which is not supported.
A FIELD GUIDE FOR YOUR TEAM
A school transport-record review
Use this to check the administrative record while keeping the school’s safety and dispatch procedures separate.
| Lens | Question to ask | What to record |
|---|---|---|
| People & vehicle | Are driver and vehicle records current and reviewed? | Named owner and supporting source documents. |
| Student assignment | Is the correct learner linked to approved pickup/drop information? | Verified assignment and effective date. |
| Change | Who approves an update and how is it communicated? | Authorised change and recipient check. |
| Related records | Are fees and transport attendance handled in their proper context? | Separate records and clear responsibility. |
| Limits | Are users clear that this is not live GPS tracking? | Confirmed product scope and separate safety process. |
CODEPEX IN CONTEXT
Useful guidance begins with clear scope.
School ERP declares selected transport administration records, including vehicles, drivers, stops/pickup points, student assignment, some driver/vehicle relationships, transport fees, attendance and parent-facing information. GPS tracking and several route workflows are not declared. Campus Transport is not supported. Confirm every required operational detail with CodePex.
Product-specific statements are based on the current owner-controlled capability declaration. Ask CodePex to confirm any institution-specific configuration or unlisted requirement.