TransitIQ

Controlled real-life pilot

Field-test one complete school journey.

Follow one coordinated scenario from platform setup through pickup, live tracking, attendance, parent updates, and drop-off. Complete the steps in order and record evidence at every checkpoint.

01 · Team and equipment

Use four phones for a convincing demonstration.

4

Recommended: 4 Android phones

Phone 1 is the Supervisor. Phones 2–4 are three different Parents. Use one laptop for the Platform Super Admin and a second laptop or browser profile for the School Admin.

Minimum viable setup: 3 phones — one Supervisor and two Parents. A fifth phone is useful as a backup device or second guardian.

Platform

Platform Super Admin

Reviews the school application, activates the school, assigns ownership, and supervises the pilot environment.

School

School Admin

Creates staff, buses, students, addresses, routes, and trips; monitors the live operation.

Mobile

Supervisor

Uses the unified Android app, checks the manifest, reorders assigned stops, and records attendance.

Mobile

Parent

Uses the same app, completes Email OTP activation, manages the child address, and follows the journey.

02 · Preparation

Prepare a small, realistic test school.

1 schoolOne campus and verified administrator
1 busRegistration number and capacity
1 supervisorReal test email and Android phone
4 studentsNamed Student A through Student D
3 parentsSeparate email inboxes and phones
2 routesMorning Pickup and afternoon Drop-off
  • Install the APK only from the official TransitIQ download page.
  • Enable location and notification permissions on each test phone.
  • Confirm all devices have mobile data or stable Wi-Fi and correct date/time.
  • Keep credentials private; the coordinator shares each account directly with its tester.
  • Use safe test addresses and obtain consent before testing with real children.

03 · End-to-end scenario

Run these steps in order.

  1. 1

    Register and activate the school

    The School Admin submits a campus application. The Platform Super Admin signs in at the platform dashboard, reviews it, assigns the responsible sales owner if required, activates the school, and privately sends the initial school credential.

    Pass evidence: school status is Active and the School Admin can sign in.
  2. 2

    Build the school team and fleet

    The School Admin creates one Supervisor and one bus, then confirms both appear in Fleet. The Supervisor receives the correct mobile activation instruction.

    Pass evidence: Supervisor and bus appear once with correct status.
  3. 3

    Add four students and invite parents

    Create Students A–D with unique IDs. Attach the correct guardian to each student and send invitations to three Parent email addresses.

    Pass evidence: no duplicate student is created after a second save click; each invitation belongs to the intended child.
  4. 4

    Activate mobile accounts with Email OTP

    The Supervisor and Parents open the unified app, enter their own email addresses, receive the six-digit Email OTP, and confirm it. Each role must open its own journey automatically.

    Pass evidence: Supervisor sees operations; Parents see only their linked children.
  5. 5

    Select and approve addresses on Google Maps

    Each Parent searches for or pins a pickup/drop-off address, adjusts the marker, and submits it. The School Admin reviews the map and accepts the requested location.

    Pass evidence: map, address label, marker, and coordinates agree on dashboard and phone.
  6. 6

    Create the Pickup and Drop-off routes

    The School Admin creates both directions, assigns the bus and Supervisor, adds Students A–D, and saves the planned order.

    Pass evidence: route line and numbered stops render on Google Maps in the saved order.
  7. 7

    Let the Supervisor reorder assigned stops

    On the Supervisor app, use the drag handle beside each student to move the assigned Pickup order to B → A → D → C. The Supervisor may reorder assigned students but must not add a new student.

    Pass evidence: the new order persists after refresh and the School dashboard shows the same revision.
  8. 8

    Create and start the morning trip

    The School Admin creates a Pickup trip from the saved route. The Supervisor reviews the manifest, starts the trip, and permits location sharing.

    Pass evidence: trip changes to In progress; school and permitted Parents see the live bus position.
  9. 9

    Record boarding and exceptions

    At each stop, mark the correct student Boarded, Absent, or No show. Try one duplicate tap to confirm the action is not recorded twice.

    Pass evidence: attendance totals, timestamps, and Parent status agree without duplicate events.
  10. 10

    Complete school arrival

    Finish the Pickup trip at school. Confirm the Supervisor cannot accidentally complete the trip twice and that final attendance remains visible in reports.

    Pass evidence: trip reaches Completed once and all expected notifications are visible.
  11. 11

    Run the afternoon Drop-off

    Create or start the Drop-off trip, confirm the reversed direction, use an intentional Supervisor order override, and record each child as Dropped off.

    Pass evidence: each Parent sees only their child and receives the correct drop-off status.
  12. 12

    Review audit and operational reports

    The School Admin reviews attendance, route revisions, map status, trip history, and notifications. The Platform Super Admin confirms school and account actions are auditable.

    Pass evidence: the report matches the scenario and every privileged change has an actor and timestamp.

04 · Safety and resilience

Try the failures a real journey will encounter.

Network loss

Disable connectivity on the Supervisor phone for two minutes. The app must explain the state, preserve safe actions, and recover without duplicating events.

Permission denial

Deny location once, then restore it. The app must guide the tester and resume tracking without a reinstall.

Role isolation

A Parent must not see other children, staff tools, route editing, or Platform/School dashboard data.

Language and layout

Switch between Arabic and English. Verify readable labels, correct RTL/LTR alignment, complete placeholders, and no horizontal overflow.

Duplicate actions

Double-tap Save, Start, Boarded, and Complete. Each intended action must occur only once.

Session recovery

Close and reopen the app. Biometric/device-lock access may restore the valid session; expired sessions must return to secure verification.

05 · Evidence and Issue report

Record facts that the team can reproduce.

For every test

  • Date, time, and tester
  • Role and device model
  • App version and Android version
  • Wi-Fi or mobile network
  • Expected result and actual result

For every problem

  • Exact numbered step
  • Screenshot or short video
  • Student, route, and trip test labels
  • Whether retry fixed it
  • Severity: Blocker, Major, Minor, or Polish

Pilot verdict

Download or reinstall the Android beta