A roll that suggests itself. A teacher who confirms it.
Today a teacher marks every name, every lesson. With Schanion the room's Wi-Fi and a room code do the first pass, the teacher looks up, counts, and confirms in one tap. Then catch-up and the note home follow on their own.
Try taking a roll.
Ring the bell, then be the teacher. The signals say 14 are here. Look around and count. You will see 15.
12 Business Management · Room B12 · Period 3
Take the roll by looking, not by typing.
Press play and watch them arrive.
- Wi-Fi in this room
- Room code
- Late
- On site elsewhere
- Flagged
- No signal
Tap a desk to cycle: here, away, then back to what the signal says.
What the roll knows right now
- 7 in the room by signal
- 9 with no signal
Start the lesson first. Students' school devices join the room's Wi-Fi as they arrive.
Signals are simulated here, on scripted pupils. In a school they come from its Wi-Fi controller and the room code. A device on the Wi-Fi is never proof someone is in the room, so the teacher always confirms. Nothing is saved.
How it works.
- 1
Signals arrive
The school's Wi-Fi controller reports which access point a registered school device joined, and each access point is mapped to a room. A student whose device is not on the Wi-Fi types the six-digit code on the room's screen. The code changes every two minutes and belongs to one lesson.
- 2
The roll suggests itself
A signal in the lesson's room suggests present, or late after the school's cut-off. A signal elsewhere on site is shown as information and suggests nothing. No signal leaves a name unsuggested.
- 3
The teacher glances and counts
The room shows the strength at a glance. The teacher counts heads. If the count matches the signals, one tap confirms the roll. If not, nothing is filed and the names to check are listed.
- 4
Everything after it follows
Anyone without a signal is marked absent for follow-up, a catch-up plan starts from what the teacher has shared, the roll is filed to the school record, and a family note is drafted for approval and goes only as far as the student allows.
The rules it keeps.
- A signal only suggests.
- Nothing here confirms a roll. A teacher confirms every one, because the school is responsible for attendance and a device being on the Wi-Fi is never proof someone is in the room.
- School hours only.
- Events outside school hours, on weekends, from the future or from long ago are ignored. Nothing tracks a student outside school.
- No raw device ids.
- A device identifier becomes a keyed hash the moment it is registered. The original is never stored.
- Kept briefly.
- Signals are removed after 30 days by a daily clean-up job, so the record never becomes a location history.
- Worth a look, not a verdict.
- If one device shows up for two students, or a code is entered while the student's device was in another room, the teacher is shown a flag and decides.
- Parents see attendance, not location.
- A family sees attendance as the student has chosen to share it. Nobody sees where a student has been on site.
Setting it up in a school.
- Turn presence on and map each access point to a room in Integrations.
- Register school devices by student email and device id. The ids are hashed straight away.
- Set SCHANION_PRESENCE_KEY and have the Wi-Fi controller, or a small script beside it, post events to /api/presence.
- Set CRON_SECRET so the daily clean-up can run. Vercel Cron sends it automatically.
- Run a week with teachers confirming as usual, and compare the signals with the roll before relying on them.
What is real and what is not. The feed, the checks, the room code, the glance and the one-tap confirm are built and tested. In the demonstration the signals are invented. No real Wi-Fi controller has been connected, and each controller brand will need a small connector to post in this format. The roll is not yet written back to a school's own student information system, so teachers still enter the official roll there, and no email or SMS is sent.