Skip to main content
GullySystem
Automotive

Roles and Permissions for School transport operators

Control which records and actions each user can access.

Platform

Does this function belong in your operation?

Use when different staff should see or change different business information.

A user joins, changes responsibility or leaves.

A replacement attendant needs the assigned run’s authorised instructions. That does not justify access to every pupil, family payment or sensitive concern in the operator’s records. The school controls the approved recipient relationships, while the operator controls staff assignment. Check both before exposing information, and test how access ends when cover or the school relationship changes.

Bring the records the workflow depends on.

  • School-approved users and pupil relationship references
  • Assigned school, run and crew responsibilities
  • Required pupil, collection and financial fields by task
  • Temporary cover, export authority and access-removal decisions

Outputs to check

  • School-and-run-scoped access matrix
  • Verified permission and revocation test record
  • External-copy and exceptional-access review list

Follow the roles and permissions workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Map responsibilities

    Identify the records and actions each role needs.

  2. 2. Review sensitive rights

    Separate high-impact actions and define approval authority.

  3. 3. Assign named users

    Grant the approved roles without sharing credentials.

  4. 4. Test access

    Check permitted actions, denied actions and combined-role effects.

  5. 5. Review changes

    Remove obsolete access after transfers, temporary cover or departures.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

School data authority

Defines who may receive pupil and collection information and authorises changes to those relationships.

Operator access administrator

Applies named crew and office access within the agreed school scope.

Records reviewer

Tests restrictions, temporary cover and exported lists without treating a role label as proof of protection.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Attendant covers another route

Give the authorised current run scope and remove obsolete access after cover.

Family relationship changes

Use the school’s recorded decision to update access; do not infer authority from a message or shared phone.

Roster exported for a run

Record the recipient and handling requirements, including how obsolete copies are withdrawn.

Sensitive concern linked to a trip

Expose only the operational instruction needed by the crew while keeping case evidence restricted.

Can this work independently?

The application and any connected portal must enforce the tested permissions. A stored relationship is not proof of collection authority, and a role matrix cannot revoke an exported copy by itself. Parent access and school-system links require separately confirmed support; no portal is assumed in this scope.

Systems and records it connects with

  • School relationship records: authoritative recipients and changes.
  • Run assignments: current crew and operational scope.
  • Controlled documents and audit history: access changes and external-copy handling.

Configure, test and introduce the workflow.

  • Map who needs each pupil, handover and billing field with the school’s data owner.
  • Test another family’s record, a substitute attendant and a sensitive linked case.
  • Verify revocation and obsolete-list handling before expanding the user group.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • A family user can access only pupil records covered by the school’s authorised relationship, including siblings where that authority applies.
  • Temporary crew access is limited to authorised work and its removal is tested.
  • Sensitive cases and financial records remain outside unrelated run views.
School transport operators

How the business operates.

A school transport operator carries an assigned pupil list between agreed stops and school under the school’s operating arrangements. The morning list and afternoon list can differ after an absence, early collection or approved change. Link each run to its vehicle, driver and attendant responsibilities, keeping the actual handover record separate from the timetable. The proposed software scope supports these records and their reconciliation. It does not decide who may collect a child, establish vehicle readiness or replace the school’s safeguarding and incident procedures.

School transport coordination

Receive the school’s authorised enrolment, stop and calendar information. Record the source of changes affecting the return journey. An absence message and a request for a different collection arrangement need separate decisions; the operator should not infer one from the other.

Run and crew planning

Prepare the stop sequence and run list for the actual school day. Link vehicle, driver and assigned attendant responsibilities, including substitute crew handoffs. School closure, exam dispersal and authorised additional runs change the plan only through the responsible school contact.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • School-approved pupil identifier, route enrolment and service dates
  • Morning and afternoon stop lists with the source of each accepted change
  • Run sheet identifying vehicle, driver, attendant responsibilities and substitute briefing
  • Reported boarding, absence, school arrival and return handover records

Operational bottlenecks to check

Morning list reused after early collection

A pupil collected from school separately remains on the return list. Retain the school’s acknowledged change and the direction affected so the crew can identify the correct afternoon expectation.

Substitute crew receives an old route sheet

A late staffing change can leave the replacement with outdated stops or handover instructions. Record which list was supplied and acknowledged; a driver name change alone does not complete the handoff.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Confirm the school’s operating source

    Identify the school contact, pupil-list owner and accepted communication channel. Record the transport arrangement and the authority for stop and collection changes.

  2. 2. Build each direction’s run list

    Use the current school calendar and assigned stop list. Apply accepted absence or alternative-collection instructions to the relevant journey without deleting the original allocation history.

  3. 3. Assign and brief the crew

    Link the vehicle and actual crew to the run version. A substitute receives the authorised route and handover instructions; the record does not itself certify readiness or competence.

  4. 4. Retain actual passenger evidence

    Record boarding and the relevant school or return handover evidence with its source. Keep a mismatch between the expected list and the actual record visible for the responsible school team.

  5. 5. Reconcile the return journey

    Check school-reported early collection and changed arrangements before relying on the afternoon list. An unresolved handover follows the school’s established response process and remains open in the record.

  6. 6. Close operating and financial records separately

    Reconcile completed runs and outstanding pupil-related exceptions. Bill the correct contractual payer, then match actual receipts; an unpaid fee does not automatically create a transport release or suspension decision.

Industry reports to connect with

  • Run lists with pending school-authorised changes
  • Expected riders versus recorded boarding and handovers
  • Substitute assignments without a completed instruction handoff
  • Unresolved absence or return-journey discrepancies

Questions before implementation.

When should school transport operators consider roles and permissions?

Use when different staff should see or change different business information. A user joins, changes responsibility or leaves.

What should we bring to the requirements discussion?

Bring anonymised examples of School-approved users and pupil relationship references; Assigned school, run and crew responsibilities; Required pupil, collection and financial fields by task; Temporary cover, export authority and access-removal decisions. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Control which records and actions each user can access. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Permissions require ongoing ownership and do not replace broader security controls.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. A family user can access only pupil records covered by the school’s authorised relationship, including siblings where that authority applies. Use this check when reviewing the first working version.

Related functions for school transport operators.

    Talk to us

    Discuss roles and permissions for your business.

    Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

    What happens after you share your requirements

    1. We review your brief and the systems you already use.
    2. We clarify the workflow, missing information and the work to consider first.
    3. The proposed scope sets out the deliverables, responsibilities and dependencies.
    4. Review the scope and commercial terms before deciding whether to proceed.

    Start with your requirements

    Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

    Share your requirements