Verified presence and accountable field operations, without pooling every agency’s data.
Fixed checkpoints confirm that inspectors, doctors and auditors were where they reported, against scheduled sessions or patrol routes. Overrides need a reason and are added on top. Each entity keeps its own data.

What gets in the way today.
Field staff cannot be verified
Ministries cannot confirm that distributed inspectors, doctors and auditors were where they reported.
Estates with many owners
Ports and public facilities hold several authorities and contractors, each with its own records. No single owner can run one system.
Paper sign-in and verbal overrides
Sign-in sheets and verbal confirmations leave no audit trail, and overrides are informal.
Counters without structured feedback
Public service counters hear complaints late, and visitor flow is managed by hand.
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:30InspectorFacility checkpoint
Taps the checkpoint on arrival. Tag, project, enrolment and the active session are validated.
- 09:00DirectorateLive roster
Presence across sites on one roster, with absences flagged automatically.
- 10:15SystemFlag
A missed departure is flagged for the supervisor.
- 12:00SupervisorOverride
Records an override with a reason. The original event stays; the override sits on top.
- 15:20CitizenCounter 3
Taps the counter tag after being served and sends private feedback to the team responsible.
- 17:00DirectorateReports
Exports for the week.
Decision-makers and the teams on the floor.
Decision-makers
- An evidence trail for field operations
- Governance without pooling data: each entity keeps its own records
- A staged roll-out gated on results
Operational teams
- A tap instead of paperwork
- Clear role coverage per site and shift
- Documented exceptions with reasons
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 directorate: its field checkpoints and the staff who use them.
Duration. One month of field operation, then a review.
What is measured
- Arrivals recorded at checkpoints against the schedule
- Overrides per week, with reasons
- Reports produced without manual collation
What is out of scope, and what is agreed per project.
Data is not pooled across agencies. On shared estates, disclosure to a zone owner or regulator follows a written policy.
Where data is hosted is stated in writing before any agreement.
Checking that each tap came from the physical tag needs secure (NTAG 424 DNA) tags, which tap2 is designed to support where a deployment requires them.
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 directorate: its field checkpoints and the staff who use them. One month of field operation, then a review.