Daily operations

Trips

A trip is one run of a route — the morning pickup, the evening drop-off, or a one-off journey for a games fixture or a trip.

Go to Transport → Trips to see the day’s trips, their status and who is on each.

A trip records the route, the vehicle, the driver, the scheduled and actual times, and the students who boarded. Completed trips build the history that reports draw on.

Operations

Transport → Operations is where the transport office maintains drivers and conductors, assigns vehicles to routes, and schedules the journeys that repeat each school day.

Route allocations and service runs

A route allocation says that a vehicle may serve a route in the morning, evening, or both. One vehicle may have more than one allocation, so the same bus can serve different routes at different times. When adding the later allocation, select This vehicle or crew also serves another route in this direction; then create service runs whose times show that the journeys do not overlap.

A service run is one recurring journey within an allocation. Create every journey separately under Transport → Operations → Service runs, with its:

• Direction and run number — for example Morning Run 1 and Morning Run 2.
• Planned start and end time.
• Driver and conductor or assistant for that journey.

For a bus that makes four journeys each day, create two morning service runs and two evening service runs. The same conductor does not have to cover all four: select the right conductor on each run. ShuleOne checks the planned times and stops the same bus, driver or conductor being placed on overlapping runs. Journeys that meet end-to-start, such as 7:00–7:40 and 7:40–8:20, are allowed.

The allocation’s driver and conductor remain the defaults for simple routes and new runs. A service run’s crew is the recurring schedule. If a substitute is needed for one day only, open Transport → Trips and use Change trip crew while that trip is still Planned; the recurring schedule is not changed.

Assign students to the correct journey

When assigning a student under Transport → Assignments, select their route and pickup point, then choose their Morning service run and Evening service run. These choices are independent: a learner may use Morning Run 2 and Evening Run 1.

Leaving a direction on Run 1 (default) keeps existing one-run routes working. A student is added only to the manifest for the selected journey, and vehicle capacity is checked for that run rather than across unrelated journeys.

The driver console

Transport → Driver Console is the simplified view a driver uses on a phone or tablet in the vehicle. It shows:

• The route and its pickup points in order.
• The students expected at each point.
• A way to mark each student boarded or absent.
• A way to start and end the trip.

Marking students as they board is what makes the rest of the module true. It produces the manifest of who is actually on the vehicle, lets the office answer “is my child on the bus” with a fact, and gives parents an accurate notification.

Keep it simple for the driver. If the console takes more than a tap per child, it will not be used at a busy stop.

The daily routine

Before the morning run

• Check the day’s trips are scheduled and vehicles assigned.
• Check for students with a change of arrangement recorded for the day.

During

• The driver starts the trip and marks boarding at each point.
• The office watches live tracking for anything stuck.

After the evening run

• Confirm every trip is closed.
• Follow up any student marked absent at drop-off who was expected.

Changes for a day

A child going home with a friend, or being collected by a parent, is a change for that day rather than a change of assignment. Record it on the trip so:

• The driver’s list does not show them as missing.
• No “your child did not board” alert goes to the parent.
• The record shows who left with whom.

This is the detail that matters after the fact, when someone asks how a child got home.