Why it is a separate MicroERP
A school bus operator can coordinate safe journey obligations using an external school roster instead of installing the whole student administration app.
Student AdministrationReviewed functional scope
Student Transport Management MicroERP
Accountable pupil transport/handover completion
Who it helpsSchool transport / authorized pupil handover coordinator
FROM A REAL REQUEST TO A USEFUL RESULT
The working flow.
An agreed pupil journey or pickup obligation
- 01
Assign route/stops/capacity and authorized pickup
- 02
communicate route changes
- 03
record boarding/alighting and identity handover
- 04
resolve missing/unapproved exceptions
- 05
reconcile completed journey
The useful outcome
Accountable pupil transport/handover completion
ALL FEATURES IN THEIR OWNING PRODUCT3 feature modules.
3 feature modules.
One product scope.
Open each module to review its purpose and actions. These features belong inside Student Transport Management MicroERP.
02School Transport Routing3 scoped actions
Plan safe operational routes and pupil pickup commitments.
- Stop and route assignments
- Capacity limits
- Route-change notices
03Student Bus Attendance3 scoped actions
Track who boarded and left each operated school journey.
- Boarding register
- Missing-pupil exception
- Trip completion reconciliation
CLEAR OWNERSHIP. CONNECTED FUNCTIONS.
How the scope fits together.
Dependencies to plan
- student-guardian-reference-core
- route-scheduling-core
- custody-evidence-core
Outside this scope
- Class attendance and bus boarding are different records.
- No automatic safety decision or release to an unauthorized person.
REUSE THE SAME PRODUCT
Mapped to your industry.
Industry compositions select relevant products and modules. Some options apply only under particular operating conditions; review the industry page before choosing.
Start with this scope.
Confirm your workflows, required integrations, team access, migration and acceptance checks in one implementation brief.