I07:42
Boarded
At the stop, the driver taps the name on a roster of the children who board there. The parent knows before the bus pulls away.
Know your child
is on the bus
RouteBoard tracks every school bus live and texts every parent the moment their child boards, reaches school and is dropped home — within seconds, in one SMS.
Aarav boarded bus KA-01-AB-5521 at 07:42. Track: …/t/9mKd2
Delivered 07:42 · one SMS
07:42
On board
2 stops away
Bus moving
- Nothing to installParents get a plain SMS — no app, no smartphone needed
- Nothing to fitNo cards, no readers, no trackers bolted to a bus
- Works without signalTaps queue on the driver's phone and send themselves
Every bus, every child, on one sheet
While parents get their own child, the transport desk gets the whole day: who is on which bus, which bus is still out, and the one child the office needs to call about.
Today · all routes
Tue 4 Nov · demonstration data1 exception
Route / bus
I · Boarded
II · At school
III · Left school
IV · Dropped
Jayanagar 4th Block
KA-01-AB-5521
32 / 32
07:42
32
08:15
32 / 32
15:05
32
15:48
Banashankari II Stage
KA-01-AB-5522
27 / 28
07:51
27
08:22
27 / 27
15:05
19 / 27
on route
Wilson Garden
KA-01-AB-5530
1 absent
Aarav S.
40
08:09
40 / 40
15:04
—
15:40
Koramangala 8th Block
KA-01-AB-5544
35 / 35
07:38
35
08:11
35 / 35
15:06
—
15:52
Wilson Garden · I · Boarded
1 absent
Aarav Sharma · VII-B · 07:50
Aarav did not board the bus at Jayanagar 4th Block today.
Sent 07:50 · delivered 07:50
One cell on this chart
is worth the whole system
A parent will forgive a late arrival notice. They will not forgive silence when their child was not on the bus. So the one message that cannot fail is the one nobody else sends: the driver closes a stop, a name is still untapped, and the message goes out before the bus has left the kerb.
It is queued in the database, not fired off and forgotten — so a dead zone, a provider outage or a dropped connection delays it by a minute instead of losing it. Every attempt is logged with its result, which is what you point at when a parent says they heard nothing.
Four moments, and nothing in between
The whole product is four taps a day. Each one writes a cell on the chart and sends one SMS — and the numbering is the day's own order, not a feature list.
II08:15
At school
One tap ends the morning trip and clears every parent on it at once. Nobody taps forty names twice.
III15:05
Left school
The same roster, reversed. The SMS carries a link to a live map of the bus that expires with the trip.
IV15:48
Dropped
The day closes. Anyone the driver never tapped is recorded as unaccounted and messaged — never quietly dropped.
What it changes at the transport desk
For the person who signs
The phone stops ringing
Every call to the office is a parent asking a question the chart already answered. They get the answer on their own phone, at the moment it becomes true, without asking anyone.
There is a record, not a recollection
Attendance per trip, per stop, per day, written by the taps themselves. The log is append-only: a correction is a new entry, never an edit — because the day you need to read it is the day somebody disputes it.
Nothing to buy and nothing to install
No cards, no readers, no fitting out buses. The driver opens a link and adds it to their home screen; taps queue on the phone and send themselves when signal returns. Parents install nothing at all.
Your data is not reachable from another school's login
Every row carries its school, and the database itself refuses to return rows from another one — the check sits below the application, where a bug in our code cannot step around it.
The other half of the product
It also plans the routes
Not just messages. Hand over the student list you already keep and RouteBoard turns six hundred addresses into stops, stops into routes no bus is overloaded on, and a time against every one of them.
Addresses in, route sheet out
drawn liveIllustration · II & III in build
Model
Reads an address for its locality and landmark, then names the stop its children fall into.
Algorithm
Splits stops across your buses against real capacities and orders each run. It can prove the limits hold; a model cannot.
You
A draft is a draft. Drag the order, move a child, in the planner you already use.
What you collect,
and what is left
Schools charge a transport fee already. The sheet puts the whole arithmetic in one place: what comes in from the children on buses, what the service costs to run every month, and what stays with the school.
No per-bus fee and no hardware line. The running cost is the messages, the hosting behind them and the upkeep — nothing that scales with how many buses you own. Planning the routes is a separate charge, paid once at setup, so it is kept out of the monthly margin.
Move the figures to your own school. We have not set a published price yet, which is exactly why the arithmetic is on the page instead of a quote form.
Cost sheet · per month1,32,000 messages
Children on buses1,500
You charge, per child₹50
Delivered cost per message₹0.1800
Messages per child, per day
Upkeep · backend and website, per month₹8,000
₹75,000
You collect
₹34,010
Running cost
₹40,990
Stays with the school
55%
Gross margin
Messaging ₹23,760Hosting ₹2,250Upkeep ₹8,000= ₹22.67 per child, per month
Planning the routes · charged once415k tokens · 1,500 addresses
Model rate · per million tokens₹250
Geocoding · per address₹0.42
₹734
One-time, at setup
₹0.49
Per child, once
₹217
Re-planning, per year
Messaging at ₹0.1800 delivered over 22 school days. ₹0.1357 is Meta's published utility rate to an Indian number including 18% GST; the SMS default of ₹0.18 is an assumption, not a quote — set your own aggregator's rate. Hosting is a ₹1.50 per-child share of database and servers, and volume discounts on messaging do not begin until roughly 25 million a month, so this stays linear at any school size. Planning is 250 model tokens per child plus one geocoding lookup each, run once over the roll, with a tenth of the roll re-planned 3 times a year; both of its rates are assumptions you should replace with your provider's. It is charged once and sits outside the margin above, because it is not what the service costs to run.
Run it on one route first
Fifteen minutes, no commitment. Bring a rough count of children on buses and we will show you the driver's screen, the message a parent receives, and the live map behind the link.
RouteBoard is pre-pilot. There are no customer logos on this page because there are no customers yet — only a working system and the arithmetic above.