All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

School Bus Tracking · Available now

Keep each school bus run, boarding and decision connected.

School Bus Tracking keeps a district or operator's bus runs connected to their stops, promised delivery time, driver and vehicle assignments, student boarding records, and transport partner. A Dispatcher prepares each run and its supporting records.

  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewRun status list
School Bus Tracking · Loads

Run status list

Loads in one list

New load
Loads in view
6
Draft
2
Planned
1
Dispatched
1
Draft2
Maple Ridge morning routeHilltop Learning District
04 Nov
Riverbend middle school runRiverbend Public Schools
26 Oct
Add
Planned1
Pine Hollow afternoon routeEast Creek Education Trust
27 Oct
Add
Dispatched1
East Creek morning routeHilltop Learning District
24 Oct
Add
In transit1
Cedar Grove afternoon routeMaple Ridge School District
23 Oct
Add
Exception1
Hilltop accessible routeOak Meadow Academy Group
03 Nov
Add
Maple Ridge morning routeLoads · LDS-13904
Draft
Promised delivery at04 Nov
OrganizationHilltop Learning District
OwnerAmina Yusuf
CounterpartySilverbrook Transit Co.
Review the revisionLDS-13904 · Maple Ridge morning route

Transport Supervisor examines the current run revision and supporting evidence.

Waiting for Transport Supervisor
ApproveReturn
Example screen with sample data
Tables, ready to use
14
Saved views
14
Roles with set permissions
5
Reports and dashboards
8
Features

See the run behind every decision

Every feature works on the same records. Pick one to see the screen your team works in.

Bus runs

Plan a school bus run and follow its recorded progress through delivery.

  • Preparation
  • Execution
  • Outcome
  • Loads
  • Load stops
  • Load assignments
  • Operation receipts
  • Review decisions
Explore bus runs
OverviewMy bus runs
School Bus Tracking · Bus runs

My bus runs

Loads

New
Record numberSubjectStatusPromised delivery atOwner
LDS-76997Maple Ridge morning routeDraft18 OctSofia Costa
LDS-44230Pine Hollow afternoon routePlanned11 OctSofia Costa
LDS-98165East Creek morning routeDispatched22 OctHyejin Park
LDS-17648Cedar Grove afternoon routeIn transit29 OctFatima Idris
LDS-43721Hilltop accessible routeDelivered28 OctCarlos Mendez
6 of 6 records
Maple Ridge morning routeLoads · LDS-76997
Draft
Promised delivery at18 Oct
OwnerSofia Costa
Example screen with sample data
Process

From planned route to recorded arrival

Plan and account for a school bus run ships ready to use. One step needs a named approval before the work moves on: Review the revision (Transport Supervisor).

Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.

  1. Prepare a run

    Record the operator, owner, partner and delivery promise.

    Maple Ridge morning routeLDS-13904 · Dispatcher
    Prepare a runBy Dispatcher
  2. Plan the run

    Inspect ordered stops and their windows.

    Maple Ridge morning routeLDS-13904 · Dispatcher
    Plan the runBy Dispatcher
  3. Assign the bus and driver

    Inspect the driver and bus recorded for the run interval.

    Maple Ridge morning routeLDS-13904 · Transport Supervisor
    Assign the bus and driverBy Transport Supervisor
  4. Review the revision

    A Transport Supervisor inspects the decision against the current revision.

    Maple Ridge morning routeLDS-13904 · Transport Supervisor
    Review the revisionBy Transport Supervisor
    ApprovalTransport Supervisor examines the current run revision and supporting evidence.
  5. Record pickup and boarding

    Keep actual pickup, stop and boarding observations together.

    Maple Ridge morning routeLDS-13904 · Dispatcher
    Record pickup and boardingBy Dispatcher
  6. Reconcile completion

    Compare actual delivery with the promise and inspect unresolved receipts.

    Maple Ridge morning routeLDS-13904 · Transport Supervisor
    Reconcile completionBy Transport Supervisor
Inside a record

Agree where observations come from

Open any load to see its load assignments, the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Promised delivery at, Organization, Owner and Counterparty.

  2. 2
    Load assignments

    Each line is linked to this load.

  3. 3
    Who works on it

    Dispatcher, Transport Supervisor and Auditor, each with their own permissions.

  4. 4
    Process stages

    Prepare a run and Plan the run, with the role that acts.

  5. 5
    Approvals

    Review the revision, with who decides.

Run status listMaple Ridge morning route
School Bus Tracking · Loads

Maple Ridge morning route

Hilltop Learning District · Draft

Log activity
1
Record details
Promised delivery at04 Nov
OrganizationHilltop Learning District
OwnerAmina Yusuf
CounterpartySilverbrook Transit Co.
2
Load assignments

Maple Ridge morning route

LoadDriverVehicle
Riverbend middle school runCarlos MendezBus 46, wheelchair lift
East Creek morning routeCarlos MendezBus 46, wheelchair lift
Oak Meadow morning routeRavi MehtaBus 46, wheelchair lift
Load assignments
6
3

Who works on it

  • DispatcherManage Loads, record attachments, student boardings
  • Transport SupervisorView Drivers, load assignments, load stops, Loads, operation…
  • AuditorView Drivers, load assignments, load stops, Loads, operation…
4

Process stages

  • Prepare a runDispatcher
  • Plan the runDispatcher
5

Approvals

  • Review the revisionTransport Supervisor
    Approved
Example screen with sample data
Approvals

Review the current revision

OverviewApprovals
School Bus Tracking · Overview

Approvals

Signed in as Transport Supervisor

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • SB-75405Maple Ridge AM
    Hilltop accessible routeRequested by Dispatcher
    Submitted0dActions
  • SB-98241Pine Hollow PM
    Pine Hollow afternoon routeRequested by Dispatcher
    Submitted2dActions
  • SB-72655East Creek AM
    Hilltop accessible routeRequested by Dispatcher
    Submitted2dActions
  • SB-85025Cedar Grove PM
    Pine Hollow afternoon routeRequested by Dispatcher
    Submitted6dActions

Who approves what

DecisionApprover
Review the revisionA Transport Supervisor inspects the decision against the current revision.Transport Supervisor
1 approval rule · set per role in Proto
Example screen with sample data
Roles

A workspace for each role

Everyone opens School Bus Tracking to the work that is theirs. Pick a role to see what it starts with.

Dispatcher

Prepare assigned operational records and execute eligible reviewed actions.

This is the first screen this role sees.

OverviewStop window schedule

Stop window schedule

Load stops · Dispatcher

ParentStop sequenceAddressWindow startWindow endActual arrival at
Oak Meadow morning route40Maple Ridge Elementary entrance19 Oct21 Oct26 Oct
Pine Hollow afternoon route20Pine Hollow Library curb14 Oct17 Oct26 Oct
Cedar Grove afternoon route80East Creek Community Center11 Oct20 Oct22 Oct
Hilltop accessible route50Cedar Grove School north gate13 Oct16 Oct21 Oct
Oak Meadow morning route70Hilltop Transit Plaza20 Oct28 Oct02 Nov
6 of 6 records
Example screen with sample data
Reports

Read delivery and review patterns

Read run timing, assignment coverage, boarding reviews and unresolved receipts.

Overview
School Bus Tracking · Overview

School Bus Tracking dashboard

This quarter

Load stops in view
6

Loads by status

How far records got this quarter

StageReachedStep
Draft28
Planned621%
Dispatched350%
In transit133%

Number of loads by status

Sample counts per stage

0
-40Draft
-10Planned
0Dispatched
-40In transit
-10Delivered
Example screen with sample data
  1. 01Run status by organization

    Group bus runs by organization, recorded status and promised delivery date.

  2. 02Delivery timing

    Compare actual delivery time with the promised delivery time for runs with both dates.

  3. 03Stop arrival record

    Show each run's ordered stops, windows and actual arrival and departure times.

  4. 04Assignment coverage

    List assignment intervals with their driver, vehicle and status.

  5. 05Boarding review queue

    Group boarding records by status, organization and route.

  6. 06Vehicle readiness and defects

    Show readiness alongside linked defect severity and release dates.

  7. 07Review decision history

    Show each decision's source revision, reviewer, decision time and reason.

  8. 08Operation receipt exceptions

    Show failed and needs-review receipts by action, occurrence time and parent run.

Controls

Keep evidence with the run

Each stage of plan and account for a school bus run names the role that acts and the status it records, so a change is never anonymous.

OverviewPlan and account for a school bus run
School Bus Tracking · Process

Plan and account for a school bus run

Each stage, the role that acts and the status it records

Process stages
10
Approval steps
1
Roles involved
3
Tables touched
11
Assign the bus and driver
Transport Supervisor, Dispatcher
StatusHeld → Confirmed
RecordsLoad assignments, Vehicles, Drivers
Record pickup and boarding
Dispatcher
StatusDraft → Submitted
RecordsStudent boardings, Loads
Follow the run
Dispatcher
StatusPlanned → Dispatched
RecordsLoads
Plan and account for a school bus run
  1. Start
    Assign the bus and driverHeld → Confirmed
    Load assignments
  2. Approval
    Review the revisionTransport Supervisor
    Review decisions
  3. Step
    Record pickup and boardingDraft → Submitted
    Student boardings
  4. Step
    Follow the runPlanned → Dispatched
    Loads
  5. Step
    Reconcile completionIn transit → Delivered
    Operation receipts
Example screen with sample data
AI agent

Ask Proto about the next case

Ask Proto to inspect school bus runs, review queues and operation evidence.

It can

  • Dispatcher: Find planned runs whose assignments are held or whose stop windows need review.
  • Transport Supervisor: List submitted boarding records with their parent run, route, stop and boarding time for review.
  • Auditor: Show failed and needs-review operation receipts with their parent run and recorded reason.

Stays with a person

  • The Transport Supervisor can inspect the current revision and its evidence.
  • Proto can organize the relevant run, stop, assignment and evidence records for that person.
  • A recommendation does not create a review decision or prove that an operation completed.
  • Keep the current user's organization and permissions in force for every request.
Integrations

Connects to the tools you use

Set up connections through ERP.AI and Proto workflows, with every change logged.

  • School Bus Tracking
  • Identity provider
  • Fleet system
  • Location or routing service
  • Student information system
Data model

Your data, in tables you can change

Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.

Browse all 14 tables
14tables
  • Bus runs5
  • Stops and windows3
  • Assignments and readiness5
  • Student boardings5
  • Review and evidence5
  • Organizations and partners5
Implementation

Roll out one team at a time

Start with one team and one process, then add the rest once the basics are running.

  1. Agree the operating boundary

    Select the organization, transport partner, Dispatcher and Transport Supervisor for the pilot. Define how promises, stop windows and boarding evidence are recorded.

  2. Map the source records

    Preserve stable run, driver, vehicle and partner codes. Link team members to their organization and user account, and link each stop, assignment, boarding and receipt to its parent run.

  3. Configure a bounded pilot

    Use a representative morning route with ordered stops, a ready vehicle and eligible driver. Record a boarding submission and an actual delivery time on the run.

  4. Rehearse exceptions

    Try a held bus, an expired driver eligibility date, a changed revision after approval, a rejected boarding and a failed operation receipt. Preserve the original evidence through each correction.

  5. Reconcile and release

    Compare imported run counts and linked child records with their source, inspect cross-organization access, and obtain the responsible team’s acceptance before expanding the program.

Pricing

$0per user

The base account and everyday work in the ERP.AI app are free, for every user.

  • No per-user or per-seat fees
  • Viewing, editing, approving and exporting records in the app is free
  • Pay only for machine work: API calls, imports, workflows and AI agents
  • Prepaid credits from $5. Purchased credits never expire

Pricing details

Machine work rate card Included per $1 of credit

Machine work rate card
UsagePer $1
Record reads (list, filter, get)20,000
Search or aggregate queries4,000
Record writes4,000
Imported or synced records200,000
Workflow runs2,000
AI agent runs2,000
Scheduled jobs or webhooks20,000
File uploads (MB)2,000
CSV or PDF exports100
FAQ

Questions, answered

Scope, rollout and pricing for School Bus Tracking.

All questions
How do I get started?

Click Get started, then use Proto to configure School Bus Tracking for your business. Pilot one organization and a representative morning route with ordered stops, an eligible driver, a Ready vehicle and a supervisor review.

What does a bus run include?

A run has a number, subject, status, promised delivery time, organization, owner and transport partner. Stops, assignments, boarding observations, attachments, decisions and operation receipts link to it.

Can we see where a bus is right now?

The run has recorded status and actual stop times. If your team needs a live location feed, agree a connection to the fleet or location service during implementation.

How are student boardings reviewed?

The Dispatcher records the route, authorized stop, boarding time and passenger count against the run. The Transport Supervisor can inspect a submitted record against the run and its supporting observations. The boarding record carries its status and decision time.

Who decides whether a changed run can proceed?

The Transport Supervisor examines the current revision and supporting evidence. A review decision, when recorded, carries an approve, reject or return value, reason and source revision.

How do we check driver and bus readiness?

Inspect driver activity and eligibility date, vehicle readiness and linked defects alongside the assignment interval before dispatch.

What happens when a run is late?

Record actual delivery time and compare it with the promised delivery time. Keep the relevant stop observations and evidence with the run.

How are failed operations handled?

Inspect the original operation receipt, operation key, expected revision and failure reason. Reconcile any recorded effect before treating the attempt as complete.

Can several operators share the workspace?

Each run links to its organization, owner and transport partner. Configure team membership and permissions for the operating scope and rehearse cross-organization access before release.

Can we migrate existing route records?

Bring stable organization, partner, run, driver and vehicle identifiers. Import parent runs before their stops, assignments and boarding observations, then reconcile the linked history.

Set up School Bus Tracking your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appSchool Bus Tracking

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.