How it works
This is the workflow a Kinnovar pilot actually runs — six steps, three audiences, one shared record. Every example below is illustrative, so you can see the shape of it before any real school data exists anywhere.
Illustrative pilot workflow — not live school or student data. Every route number, name, and timestamp on this page is invented for explanation. Kinnovar holds no production school, guardian, or student data today.
Expectation, recorded event, communication, exception, action, auditable history — the loop Kinnovar is built around.
School
An administrator sets up (or confirms) one route for the pilot — its stops, the riders expected at each stop, and who on the transport team is assigned to it. A pilot starts with a single route or a single pickup line, not the whole school.
What the record saysRoute 12 · 9 stops · morning run · assigned to 1 attendant
Transport
The driver or attendant assigned to that route opens their own assignment for the day. They see the stops and the riders expected on this route — and nothing about students on any other route.
What the record saysAssignment opened · Route 12 · morning
Transport
At the stop, the attendant records the handoff. The record is a timestamped fact about what was entered, at the moment it was entered — it is evidence that a boarding was recorded, not proof of a child's status.
What the record saysBoarding recorded at 7:42 AM · Stop 3 of 9
Family
The guardians linked to that rider get a short notice carrying the same timestamp the record carries. No app store download, no parent subscription, and no safety claim attached to it.
What the record saysNotice delivered at 7:43 AM · “Boarding recorded at 7:42 AM”
Transport → School
When something does not go to plan — a missed stop, a late run, a change requested at the door — it is flagged at the time and assigned to a named person, instead of surfacing later in a group chat nobody owns.
What the record saysException opened 7:51 AM · assigned to transport coordinator 7:53 AM
School
Afterwards, the school can read the day back in order: what was expected, what was recorded, what families were told, what went wrong, who owned it, and when it closed. The history stays reviewable — that is the point of recording it.
What the record saysException resolved 8:05 AM · full event history retained
Three perspectives
Role-based access means each person sees what their job needs and nothing more. These are illustrative sketches of that difference, not screenshots of a live product.
Sees the route, and every event on it.
Route 12 · Morning Illustrative
Can answer “what happened at stop 3?” without phoning anyone.
Sees one run — the one they are on.
Today · Route 12 Illustrative
No access to students on any other route.
Sees their own child's records, in plain language.
Your updates Illustrative
Boarding recorded at 7:42 AM
Route 12, Stop 3. Recorded by the attendant on this route.
Stop change reported at 7:51 AM
The school is reviewing this and will follow up.
A timestamped record of what was entered — not a claim about a child's safety.
This distinction is a hard product rule, not a wording preference. It is why Kinnovar says “boarding recorded at 7:42 AM” and will not say “student confirmed safe.”
The next step is a 20-minute conversation about how your transport day runs today — not a demo script.