Most estate gates still run on a paper logbook and a phone. A visitor arrives, the guard writes down their name, rings the resident, waits, and lets them in, or doesn’t. It works, mostly. But it’s slow, it depends on residents answering their phones, and the record it leaves is hard to read and easy to lose.
One-time visitor codes are a different way of doing the same job. Here’s how they work, how they compare, and what to look for.
How one-time codes work
The idea is simple. The resident tells the gate a visitor is coming before they arrive.
- The resident creates a short code for their visitor, usually on their phone, and sets how long it’s valid.
- The resident sends the code to the visitor, by message.
- At the gate, the visitor gives the guard the code.
- The guard checks the code. If it’s valid for that house and that time, the visitor goes in.
- The entry is recorded, with the time and the house.
The guard no longer has to reach the resident. The resident has already said yes.
Codes and logbooks, side by side
At the gate. A logbook means writing, phoning and waiting. A code means checking and opening. Queues at busy times get shorter.
For residents. With a logbook, you have to answer the guard’s call, wherever you are. With a code, you decide in advance, once.
For security. A logbook records who the guard wrote down. A code records who a resident actually expected. It’s much harder to talk your way past a code than past a busy guard.
For the record. A logbook is pages of handwriting. Codes leave a list you can search by house, date or time when something needs checking.
When things go wrong. A logbook never runs out of battery. Any code system must have a plan for power cuts and network outages, or the gate stops.
What a good code system needs
- It must be easy for guards. Big, clear screens, a simple yes or no, and nothing to type twice. If it’s slower than the logbook, guards will go back to the logbook.
- It must be easy for residents. Creating a code should take seconds, on any phone.
- Visitors shouldn’t need an app. A plain message is enough.
- Codes should expire. A code that works forever is a key anyone can copy.
- It must keep working offline. Decide what happens when the network drops, before it drops.
- It must respect privacy. A record of who visits whom is personal data. Decide who can see it, and for how long it’s kept. Our note on NDPA basics explains why that matters.
Questions for your estate committee
- Who creates codes: only residents, or also staff, tenants and domestic workers?
- How long should a code last by default?
- What happens for deliveries and taxis?
- Who can see the entry records, and who can’t?
- What’s the backup when the system is down?
What we’re building
We’re designing the Estate Entrance Security System, code-based visitor access for residential estates, with estates now. If your estate would like a say in how it works, join the waitlist or tell us how your gate runs today.