Attendance that professors trust and registrars can defend.
A tag in each teaching room ties a tap to a specific session. Server rules decide Present or Late, the professor sees a live roster, and every correction sits on top of the original record.

What gets in the way today.
Roll calls eat lecture time
Paper sheets and name calls take minutes from every session, and proxy attendance is hard to spot.
Workarounds that do not hold
QR codes get screenshotted, apps add friction, and card readers are costly to install in every room.
Disputes without evidence
Late arrivals, room changes and failed devices create disputes the registrar cannot settle from the record.
Corrections nobody can trace
Manual corrections go untracked, and visibility across campuses is fragmented.
One estate, several layers.
The same kind of tag in every place, with the product each place needs behind it. The core product is where a deployment starts; which products join, and on which points, is settled in the tag plan.
From the first tap to the report.
Blue times are taps.
- 07:50RegistrarAdmin console
Sessions for the day already exist, generated from the timetable, rooms and enrolments.
- 09:02StudentRoom 2 door tag
Taps on the way in. Room, session, enrolment and timing check out: Present.
- 09:14StudentRoom 2 door tag
Taps inside the late window. The rule marks Late; nobody argues with a clock.
- 09:20ProfessorLive roster
A phone will not read the tag. The professor opens a time-boxed fallback mode; the activation is logged.
- 11:30StudentCorrection request
Files a correction for a session where the tag was down.
- 14:00Professor, then registrarReview
The professor approves, the registrar confirms. The change sits on top of the original event, with who decided and why.
- 17:00DeanReports
Attendance by section and course, with every adjustment explainable.
Decision-makers and the teams on the floor.
Decision-makers
- Every attendance change is explainable: the original event, the adjustment and who decided
- Policy applied uniformly across faculties
- Evidence for academic-standing and advising decisions
- Administration across several institutions
Operational teams
- No roll call, and a live roster for every session
- A supervised fallback when technology fails
- A fair, fast check-in for students, with nothing to install
- A formal route to correct a record
Scope, duration, and what is measured.
No promised numbers. The measures are agreed before the first tag goes up and reviewed at the end.
Scope and duration
Scope. One faculty: its teaching rooms, sections and enrolments.
Duration. One term, with the measures agreed before the first tag goes up.
What is measured
- Lecture minutes returned per session
- Correction requests filed, and how they were settled
- Attendance by section and course across the term
What is out of scope, and what is agreed per project.
Single sign-on and student-system integration are scoped per institution.
Students use the web app on their own phone; there is nothing to install.
Tags carry no student data. They identify the room, not the person.
tap2alert complements emergency numbers and fire-alarm systems. It does not replace them. Anyone in danger should also call the local emergency number.
Discuss your first deployment.
One faculty: its teaching rooms, sections and enrolments. One term, with the measures agreed before the first tag goes up.