Visitor management system for housing societies
Replace the gate register with pre-approved passes, photo-verified entry and a log you can actually search. Guards keep working when the network drops; residents approve from the app, a phone call or an SMS.
A visitor management system replaces the gate register with digital pre-approval and verified entry. Residents approve visitors by app, SMS or automated call; guards capture a photo and log the entry in seconds; every movement is searchable by date, flat or name. KeyMatrix works offline and syncs when the network returns.
The paper register is your weakest security layer
The register at your gate is doing more work than it can carry. It is the only record of who entered the property, the only evidence if something goes missing, and the only thing a committee can point to when a resident asks how a stranger reached the eighth floor. It is also a paper notebook filled in at speed by a guard who is simultaneously opening a barrier, taking a phone call and signing for a parcel.
The failures are predictable because they are structural, not personal. Handwriting is unreadable within a week. Names are written as the visitor pronounces them and nobody checks. Phone numbers are transposed. Exit times go unrecorded because nobody is standing at the gate when the visitor leaves, which means the register cannot tell you who is inside the property right now — the one question it exists to answer.
The moment the register matters is the moment it fails. After a theft, a committee turns to the book and finds three illegible entries and no exit times across the relevant afternoon. There is no photograph, no way to confirm the phone number was real, and no way to search four months of entries for the same person visiting different flats. The register was never a security control. It was a record of the intention to keep one.
- Unreadable at the point of use. A name written at a gate in the rain is not evidence, and it cannot be searched.
- No exit capture. Without exit times, the register cannot answer who is on the property at any given moment.
- Unverified identity. A number written by hand is never dialled, so nothing about the visitor was ever confirmed.
- No pattern visibility. Repeated visits by the same person to different flats are invisible when each day is a separate page.
Key capabilities
Six capabilities cover the full life of a visit — from the resident expecting someone to the log a committee reads six months later.
Pre-approved entry with OTP and QR passes
A resident expecting a guest creates a pass before the visitor arrives. The visitor receives a QR code and a one-time code by SMS or WhatsApp; at the gate they show either one and the guard scans or types it. Entry takes a few seconds and requires no call to the flat, which is what makes it stick — the fastest path through the gate is also the recorded one.
Passes carry their own rules. A one-time pass for a dinner guest expires the same evening. A recurring pass for a tutor covers Tuesday and Thursday afternoons and nothing else. A pass issued for a party covers thirty named guests under one code. When a pass expires it stops working at the gate rather than quietly continuing to be honoured.
Guard app with photo and ID capture
For unannounced visitors the guard raises the request instead. The app captures a photograph, the visitor name, the flat being visited and the purpose, then notifies the resident and waits. The photograph is the part that changes behaviour: it takes one second, it cannot be faked at the point of capture, and it converts an entry from a claim into evidence.
Where a society requires it, the guard can also capture an ID document. That is a policy decision rather than a default — collecting identity documents creates an obligation to protect them, so the setting is off unless a committee turns it on, and captured documents follow the same retention schedule as everything else.
Delivery and cab approvals in one tap
Deliveries are the highest-volume event at any gate and the one most likely to be waved through unlogged. The app handles them as their own type: the guard selects the courier, the resident gets a single notification with approve and leave-at-gate as the two options, and the parcel is logged either way. Cabs work the same way, with the vehicle number captured so that a complaint about a driver has something attached to it.
Leave-at-gate creates a holding record rather than closing the entry. The parcel sits against the flat until someone collects it, which is what stops the weekly argument about whether a delivery ever arrived.
Blacklist and watchlist alerts at the gate
A committee can add a person or a vehicle to a watchlist with a reason and an expiry. When that number or plate appears at the gate the app tells the guard before entry is granted, rather than after somebody reviews the log. A blacklist blocks; a watchlist warns and notifies a named committee member.
Both carry an audit trail. Who added the entry, when, and on what grounds is recorded, because a list that can be edited silently is a list that will eventually be used to settle a personal dispute.
Passes for domestic help and frequent visitors
Domestic staff, drivers, tutors and physiotherapists are not visitors in any meaningful sense — they arrive daily, often to several flats. They get a durable pass tied to the people they work for, so entry is a scan rather than a fresh approval each morning, and their attendance across the property is visible to the committee without anyone keeping a parallel notebook.
When a household stops employing someone, the resident revokes their own share of the pass. If that was their only employer the pass stops working; if they still work for three other flats, it continues for those three. This is the case a spreadsheet always gets wrong.
Real-time, searchable entry and exit logs
Every event lands in one log that can be filtered by date range, flat, gate, visitor name, phone number or vehicle. The questions a committee actually asks — who visited flat B-704 in March, has this number been here before, which vehicles were inside between 2am and 5am — are queries rather than an afternoon spent with a notebook.
Exit capture is what makes the log complete. Scanning out closes the entry, and anything still open after a threshold is flagged, so the count of people currently on the property is a number the system can state rather than an estimate.
How it works
Three steps at the gate, none of which asks the guard to make a judgement call about who someone is.
Who it helps
A gate system is only adopted if it makes each group’s day easier than the register did. These are the four groups whose behaviour has to change, and what each one gets in return.
What gets recorded, by entry type
Different arrivals need different amounts of friction. The system varies the check rather than applying the slowest one to everybody.
| Entry type | Verification | Resident action | Logged as |
|---|---|---|---|
| Pre-approved guest | QR or OTP shown at the gate | Creates the pass in advance | Entry with pass reference and expiry |
| Unannounced visitor | Photo captured by the guard | Approves or declines the request | Entry with photo, purpose and approver |
| Delivery | Courier selected by the guard | Approve, or leave at gate | Delivery record held against the flat |
| Cab or taxi | Vehicle number captured | Approves the pickup or drop | Entry with vehicle number |
| Domestic staff | Durable pass, scanned daily | None after the first setup | Attendance against every employing flat |
| Watchlisted person | Alert raised before entry | Committee member notified | Blocked or held, with the reason recorded |
Works with the rest of KeyMatrix
Gate data stops being a silo the moment it shares a record with everything else. A visitor entry is attached to the same unit record that carries the maintenance bill, the complaint history and the owner and tenant of record — so the gate knows that B-704 is tenanted, who the current tenant is, and that their agreement expires in March.
That shared record is what makes the small things work. A resident with dues does not lose gate access, because collections and security are separate concerns and conflating them is how a committee ends up in a dispute. But a flat that has changed hands stops honouring the previous owner’s domestic staff passes automatically, because the handover updated the unit record and the passes hang off it.
The same applies outward. A delivery left at the gate can raise a helpdesk ticket if it is not collected within a day. A watchlist alert can notify the committee members on duty this week rather than a fixed list that went stale two AGMs ago. None of this requires an integration, because none of it crosses a system boundary.
- Unit management. Owner, tenant and occupancy come from the unit record, so passes follow the flat rather than a name typed at the gate.
- Helpdesk. An uncollected parcel or a gate incident becomes a ticket with the entry already attached.
- Staff attendance. Domestic staff and society staff share one attendance history instead of two registers.
- Parking and ANPR. Vehicle numbers captured at the gate reconcile against allotted parking, so an unfamiliar plate is visible.