For schools, transport teams & families

Recorded handoffs.
Clear family updates.

Kinnovar gives a school one clear record of the transport day — who was expected, what was recorded and when, what families were told, and how an exception was resolved.

In controlled pilots with a small number of schools. Workspaces are set up with the founders — there's nothing to sign up for yet.

Route 12 · Morning
Illustrative
  1. 7:40ExpectedRoute 12 · Morning pickupScheduled
  2. 7:42RecordedBoarding recorded · Stop 3Recorded
  3. 7:43CommunicatedFamily notice deliveredNotice sent
  4. 7:51ExceptionStop change flagged by driverNeeds review
  5. 7:53ActionAssigned · transport coordinatorIn progress
  6. 8:05AuditedException resolved · loggedResolved
3 of 9 recorded

What Kinnovar does

  • Recorded events

    Boarding, notices, and updates are timestamped as they happen — not reconstructed later from memory.

  • Clear exceptions

    When something doesn't go to plan, it's flagged and owned — not lost in a group chat.

  • Role-based access

    Schools, transport staff, and families each see what's relevant to them, and nothing more.

  • Auditable history

    Every record stays reviewable after the fact, for the school and for the family.

How it works

One route, recorded end to end

A pilot runs a single route or pickup line through six steps — from what was expected, to what was recorded, to how an exception was resolved and logged.

  1. School confirms a routeStops, riders, assigned staff
  2. Transport staff see the runOnly the route they're on
  3. Handoff recordedBoarding recorded at 7:42 AM
  4. Family notifiedSame timestamp, plain language
  5. Exception ownedFlagged, assigned, followed up
  6. History reviewableThe day, readable end to end

See how Kinnovar works, step by step

Illustrative example — not live school or student data.

Built for three audiences

Who it's for, and what each role gets

One morning touches three people who rarely see the same information. Kinnovar gives them one record — and each of them only the part that's theirs.

  1. Home — a family gets the note
  2. The stop — the handoff is recorded
  3. School — the day stays reviewable
  • School administrator

    Sees the whole transport day in one place, and can answer a parent's question without phoning the driver.

    • Routes and stop assignments for the pilot route
    • Which handoffs were recorded, and when
    • Open exceptions, who owns each one, and what changed
    • The full event history, still reviewable after the day ends
  • Driver or transport attendant

    Gets one short list for the run they are actually on, and a fast way to record a handoff or flag a problem.

    • Today's assignment — route, stops, and expected riders
    • Record a boarding or handoff in a few taps
    • Flag an exception at the moment it happens, not afterwards
    • No access to any student outside the assigned route
  • Parent or guardian

    Gets a timestamped update instead of an unanswered message, and can see what has been recorded for their own child.

    • A notice when a handoff is recorded — with the time it happened
    • A notice when something changes, and what is being done
    • Their own child's records only
    • No app store download required, and no parent paywall

Now, pilot, and later

What exists today — and what doesn't

Kinnovar is early. The clearest thing we can give a school evaluating us is an honest line between what is running, what a pilot covers, and what is still only intent.

  1. Now

    Discovery conversations and controlled pilot requests

    What a school can do with Kinnovar today: talk to the founders about how its transport day actually runs, and ask to be considered for a controlled pilot. There is no self-service signup, and no product to log into yet.

    • A 20-minute conversation about your current workflow
    • A written pilot outline, scoped to one route or one pickup line
    • Answers on data handling before anything is shared
  2. Pilot scope

    The workflow a pilot school actually runs

    This is the validated first scope — deliberately narrow, so it can be proven in real mornings and afternoons rather than demonstrated in a meeting.

    • Transport routes and assignments
    • Recorded student handoffs
    • Timely family notifications
    • Exception handling with a named owner
    • Auditable event history
    • Role-based access for school, transport, and family users
  3. Later

    Broader school operations — subject to evidence and review

    The longer-term intent is a school workspace that covers more of the school day. None of it is built, none of it is scheduled, and none of it is included in a pilot. Each item needs pilot evidence plus a documented privacy, security, and control review before it becomes work.

    • A minimum student record, only where an approved workflow requires it
    • Self-service school registration and workspace creation
    • Wider school operations beyond transport

    Explicitly deferred, and not part of any current offer: exams, marks, full academic records, payments, and student-information-system integrations.

Trust & data handling

Read the data rules before the meeting

Kinnovar is early, and a school evaluating an early vendor deserves the limits stated plainly rather than discovered later. The Trust page labels every control as already true today, a pilot-launch commitment, or a design principle — and names the certifications we do not hold.

Read Trust & Security
  • A recorded handoff is evidence that an event was entered at a time — never a claim that a child is safe, present, or delivered.
  • Each school's data is isolated from every other school's. Role-based access means people see what their job needs and nothing more.
  • We collect the minimum a transport handoff and a parent notice require — no academic records, no health data, no behavioural data.
  • No advertising. No selling of student or guardian data. No AI profiling of children, and no eligibility, behaviour, or risk scoring.

The controlled pilot

Start narrow. Prove it works. Then decide.

One school, one workflow, a defined pilot period agreed before it starts — with stop conditions either side can use.

Request a pilot

For a school ready to talk about running one route through Kinnovar, with a named operational owner.

Request a Pilot

Request school access

For a school that wants to understand the onboarding path first. Early workspaces are set up with the founders — this is not a self-service signup, and no account is created.

See what schools get

Twenty minutes about your transport day.

No demo script, no pricing, no obligation — we're speaking with a small number of schools before deciding what to build next.