One tagged estate for access, services, early warnings and emergencies.
Access, movement, prevention and response, planned as one estate: resident information points, a private channel to management, visitor passes at the gate, help points that route to security first, and verified patrols.

What gets in the way today.
Information everywhere and nowhere
Rules, notices and numbers are scattered across chat groups, PDFs and notice boards.
Small issues that escalate
Residents stay silent about noise, lighting and leaks until they become disputes.
A congested gate
Visitors get lost, GPS is poor inside the compound, and manual approvals queue at the barrier.
Verbal emergencies, unverified patrols
Alarms evacuate but do not communicate, and patrols are unverified.
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.
- 08:10VisitorMain gate
Shows the pass the resident shared. The guard validates it at the gate tag; entry is logged.
- 09:30ResidentLift lobby tag
Taps and raises a maintenance request for the lobby light.
- 10:00ManagementTriage
The request is triaged and assigned.
- 14:00TechnicianLift lobby tag
Taps on arrival; the visit is recorded against the request, which is then closed.
- 22:15GuardPatrol checkpoint
Checkpoint taps along the route; coverage is visible to the security contractor and to management.
- 23:40ResidentHelp point
Taps for help. Security is first; escalation to civil defence follows the written policy.
Decision-makers and the teams on the floor.
Decision-makers
- Service differentiation for the estate
- Resident retention through visible responsiveness
- Accountable security contractors
Operational teams
- Fewer calls and a structured gate flow
- Verified patrols
- Alerts that arrive with their location
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 gate, one building’s common areas and one patrol route.
Duration. Two months, then a review with the facility and security teams.
What is measured
- Issues reported at a tag and time to acknowledge
- Patrol checkpoints covered per route
- Gate waiting time at peak
What is out of scope, and what is agreed per project.
The escalation policy from compound security to civil defence is agreed in writing before any help point goes live.
A visitor pass does not open gates or barriers; links to barriers and intercoms are scoped per project.
Maintenance requests, triage and technician visits at resident points are delivered as a scoped project.
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 gate, one building’s common areas and one patrol route. Two months, then a review with the facility and security teams.