Samipyo

How it works

How Samipyo turns evidence into a state

Three steps, in the same order every time: record the evidence, derive the state, show it with its confidence.

  1. Evidence is recorded

    Staff confirm boarding or exit by hand. The bus reports its GPS position during an active trip. Each event is stored as recorded, with its source: manual or GPS.

  2. A deterministic engine derives the state

    The same evidence in the same order always gives the same state, so a disputed event can be reconstructed later.

  3. People see the state and how confident it is

    According to their role, people see the state with its confidence and the source-tagged timeline. A state confirmed by a responsible adult is distinguishable from one derived from a weaker signal.

The shape of it

Sources in, one state out

From evidence to state Three evidence sources feed one evidence record. Manual confirmation by a named staff member and bus GPS during an active trip are built so far. Bluetooth detection is planned and not built yet. The evidence is kept as recorded, with its source, and is never overwritten. A deterministic, auditable state engine turns it into a state. There are three outputs. Confirmed: confirmed by staff, with its source. Derived: from a weaker signal such as bus GPS, shown as less certain. Unknown: no evidence is never read as absent. Manual confirmation A named staff member confirms boarding or exit Bus GPS Bus position during an active trip BLE detection Planned Planned, not built yet Evidence Kept as recorded, with its source, never overwritten State engine Same evidence in, same state out. Deterministic, auditable Confirmed Confirmed by staff, with its source Derived From a weaker signal such as bus GPS, shown as less certain Unknown No evidence is never read as absent From evidence to state Three evidence sources feed one evidence record. Manual confirmation by a named staff member and bus GPS during an active trip are built so far. Bluetooth detection is planned and not built yet. The evidence is kept as recorded, with its source, and is never overwritten. A deterministic, auditable state engine turns it into a state. There are three outputs. Confirmed: confirmed by staff, with its source. Derived: from a weaker signal such as bus GPS, shown as less certain. Unknown: no evidence is never read as absent. Manual confirmation A named staff member confirms boarding or exit Bus GPS Bus position during an active trip BLE detection Planned Planned, not built yet Evidence Kept as recorded, with its source, never overwritten State engine Same evidence in, same state out. Deterministic, auditable Confirmed Confirmed by staff, with its source Derived From a weaker signal such as bus GPS, shown as less certain Unknown No evidence is never read as absent
Evidence from staff and the bus is kept as recorded and turned into a state by fixed rules. A state confirmed by staff is distinguished from one derived from a weaker signal, and where there is no evidence the state stays unknown.
No evidence is not absence.

A student with no evidence is shown as unknown or as an exception, never as "not on the bus".

Evidence is not state

A tick or a GPS point is a record of something that happened. The state is derived from records by fixed rules, and the records are kept as they came in.

A person can correct it

Authorised staff can correct a state. Each correction is audited with who, when and why.

Privacy by design

Sessions, not surveillance

Location is processed only during an active school or transport session. There is no behavioural profiling, no advertising, and no analytics on individual children.

Planned, not built
Automatic detection with Bluetooth tags read by ordinary staff phones is planned. Today the platform runs on manual confirmation and bus GPS.

See it in your own school

Talk to us, or read how it looks from the school's side.

Contact For schools