An app the guard will still use in week three
Software at a gate fails on usability, not features. Four buttons beat a beautiful dashboard.
The constraints at a real gate
- One hand is often holding a parcel or a pen.
- The guard may be new, and may change every few months.
- Peak hours are crowded and loud.
- The tablet may be old, the wifi weak, the sun bright.
- The guard is not going to read a help article.
What that means for the design
Very large touch targets, a fixed set of choices, no free text where a list will do, and a visible confirmation after every entry. The screen should be readable outdoors and the flow should survive a mis-tap. Anything that requires training beyond five minutes will not be used.
Shift handover
The outgoing guard should be able to see open visits — people still inside — and hand them to the next shift. Unexplained open entries at shift change are the most common source of a broken log.
What to measure
Entries per day, entries with no exit, average entry time and the share of visits approved by a resident. If entry time rises or exits go missing, the system is failing regardless of what the dashboard says.
Questions people ask
Does the guard need a smartphone?
A shared tablet at the gate works and is usually better, because it stays at the post and does not walk away in a pocket.
Can we restrict what the guard sees?
Yes — the gate role sees the entry screen and open visits, not resident contact lists or historical reports.