Why your society needs visitor gate management
Every afternoon the gate phone rings: a delivery person, a cab, a relative nobody pre-informed. Security calls flat owners; owners miss the call; the queue grows. Paper registers fill up but nobody can search them when a dispute arises.
Pain point 1: Gate calls that residents miss
Walk-ins stall at the gate while security hunts for a phone number. Residents in meetings or abroad cannot answer in time.
Fix: Guards log walk-ins on Gate desk — request_walkin_approval sends a push
notification to flat owners. Residents approve or deny from Visitors without a phone call.
Pain point 2: No proof of who entered when
A vendor claims they visited; a resident denies it. The paper register has illegible handwriting or no entry at all.
Fix: Every verification, approval, entry, and exit writes to gate_events and the append-only audit log. Pre-approved passes carry OTP and QR tied to a specific visitor name and flat.
Pain point 3: Delivery and cab chaos at peak hours
Multiple couriers arrive at once. Guards wave them through to avoid backlog — security weakens.
Fix: Residents pre-create passes with kind delivery or cab. Guards verify OTP or QR
in seconds; log_gate_event records entry and exit so the committee sees throughput.
Pain point 4: Separate gate app disconnected from society records
Standalone gate apps do not share the verified flat roster used for voting and billing.
Fix: Plinth visitor passes use the same claimed-flat roster. Governance, billing, and gate operations stay on one member truth.