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 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. 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.
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.
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 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.
When someone arrives without a pass
Most entries at a busy gate are unannounced. The guard app treats each kind differently, and none of them asks the guard to decide who someone is.
Guard app with photo and ID capture
For an unannounced visitor the guard raises the request. 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 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. Leave-at-gate holds the parcel against the flat until someone collects it, which ends the weekly argument about whether a delivery ever arrived.
Cabs work the same way, with the vehicle number captured so that a complaint about a driver has something attached to it.
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, the guard is told 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 of who added the entry, when and on what grounds — because a list that can be edited silently will eventually be used to settle a personal dispute.
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 |
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. Residents see only their own flat’s entries, which is what makes the system acceptable to live with.
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.
Passes hang off the unit record rather than a name typed at the gate. When a flat changes hands, the previous owner’s domestic staff passes stop working because the handover updated the unit — while a resident with unpaid dues keeps gate access, because collections and security are separate concerns.