Skip to main contentSchylvaRequest a demo

School transport administration

Keep transport routes, capacity and student assignments organised.

Authorised administrators maintain routes, opted-in Student assignments, fees and billing frequency.

Capacity is review context, not an enforced limit. No Parent or Student delivery, live tracking or fleet operations.

Inside the assignment

One student.
One active route.

Route
An active route for an opted-in Student
Fee
A positive amount
Frequency
Monthly, quarterly or annual

Static product screenshot.
These are not interactive form fields.

Focused Schylva transport Student assignment form using fictional data and showing route, fee and billing frequency controls
Student route assignment · static product screenshotEnlarge screenshot: Student route assignment

Student route assignment

Reviewed sample school data. Static image—product controls are not interactive.

Current Schylva web workflow · fictional school data

Shows route, fee and frequency—not automation, invoices or family delivery.

Administrator record management

Three questions.
A clearer record.

Confirm eligibility, an active route and assignment details.

  1. Before assignment

    Who is eligible?

    The Student record must show transport opt-in.

  2. During setup

    Which route is available?

    Use an active route with required contact and optional context.

  3. After selection

    What will be recorded?

    Keep Student, route, positive fee and frequency together.

The administrator assignment process

Ready the records.
Then connect them.

Five stages define record ownership. Student eligibility and route setup come before the assignment. This is a record workflow, not a trip planner.

First, prepare the two prerequisites.

Student record context

Record the Student transport opt-in.

An authorised administrator maintains eligibility.

Opt-in does not assign a route.

Authorised administrator

Prepare an active or inactive route.

Record its name, required contact and optional capacity or teacher reference.

Teacher reference creates no Teacher workflow.

Then, make and review the assignment.

Administrator transport workspace

Find eligible Students without a route.

Review the unassigned list.

No automated allocation or optimisation.

Assignment record

Connect the Student to an active route.

Enter a positive fee; choose monthly, quarterly or annual frequency.

Route, fee and frequency stay together.

Route detail

Review route details and assignments.

Review the route and assigned Students.

Supported fields are editable; capacity is not enforced.

Ownership, not passenger delivery

Administered by school.
Grounded in context.

The current product supports administrator record management, not Parent, Student or Teacher transport workspaces.

Fee and frequency context

Relate the setting.

The assignment stores fee and frequency; evaluate Fee Management separately.

Review Fee Management

The interface, up close

From route controls
to a recorded assignment.

Three focused administrator states use fictional school data. The assignment fields are shown above; inspect the overview and assigned-Student result here. These are not evidence of family delivery, invoices, capacity enforcement or fleet operations.

01 · Overview and route controls

A place to prepare the records.

Focused Schylva transport administrator overview using fictional school data and showing transport counts and route creation controls
Administrator transport overview · static product screenshotEnlarge screenshot: Administrator transport overview

Administrator transport overview

Reviewed sample school data. Static image—product controls are not interactive.

Current Schylva web workflow · fictional school data

Shows counts and route controls—not submission or live operations.

03 · Assigned-Student result

The assignment, fee
and frequency together.

Focused Schylva Assigned Students card using fictional data and showing one Student's transport fee and quarterly frequency
Assigned-Student result · static product screenshotEnlarge screenshot: Assigned-Student result

Assigned-Student result

Reviewed sample school data. Static image—product controls are not interactive.

Current Schylva web workflow · fictional school data

Shows one assignment with fee and quarterly frequency—not route metadata, GPS, trips, dispatch or capacity enforcement.

Return to the assignment fields

A clear product boundary

Transport records.
Not fleet operations.

Compare records, configuration choices and boundaries.

Supported today

  • Transport-opted, unassigned and active-route counts
  • Routes require a name and emergency contact
  • Optional capacity and teacher-reference context
  • Review opted-in Students without an assignment
  • One active route per opted-in Student
  • Positive fee; monthly, quarterly or annual frequency

Current boundaries

  • No current Parent or Student route-assignment delivery
  • No live GPS, maps, vehicle location, drivers, stops, trips, ETA, route history or geofencing
  • No capacity enforcement, automatic allocation, route optimisation or dispatch
  • No transport attendance, bulk import, transport notifications or fleet-management workflow
  • No fee-invoice claim without exact-candidate verification
  • No delete, remove or reassignment claim; the teacher field is only a reference

Prepare a useful walkthrough

Bring one example.
Test the right questions.

Trace the record without production school or Student data.

  1. How does the school confirm transport opt-in?

    Review eligibility before assignment.

  2. Which route record should be represented?

    Prepare its name, contact, status and optional capacity.

  3. Who owns the assignment and fee settings?

    Confirm ownership, fee and frequency.

  4. Does the requirement include tracking or fleet operations?

    Separate those needs from current scope.

Confirm for your school
  • Administrator ownership and settings permission
  • Review Student transport opt-in
  • Route name, contact and status
  • Capacity as review context only
  • Representative fee and frequency
  • Wider fee relationships require demonstration

School transport questions

The details
worth settling.

Confirm ownership, eligibility, records, fees and boundaries.

What can authorised administrators manage?

With settings permission, they maintain routes, review unassigned eligible Students and record one active-route assignment with fee and frequency.

Does seating capacity block extra assignments?

No. Capacity is optional context, not enforcement or automatic allocation.

Which Students can be assigned to a route?

Students whose available school record indicates transport opt-in.

Which transport fee settings are supported?

A positive fee and monthly, quarterly or annual frequency. Invoice or payment behaviour requires exact-candidate proof.

Can Parents or Students see the assigned route?

No. Parent and Student transport delivery is not supported in the current release.

Does Schylva provide GPS tracking or fleet operations?

No. Live GPS, maps, vehicles, drivers, stops, trips, ETA, history, geofencing, dispatch and optimisation are outside scope.

A focused transport demonstration

Trace one
fictional assignment.

Bring an opted-in Student, route, fee and frequency.

  • One fictional transport-opted Student
  • One fictional route and emergency contact
  • The optional capacity context
  • One representative fee and frequency

Use fictional or redacted information—no real names, contacts, IDs or screenshots. Response within two working days.