Office Visitor Management: Reception Desk, Passes and Records

Visitor management at an office gate

Most Indian offices run their front desk on a paper register and a phone call. A visitor writes their name in a book, the guard rings an extension, somebody walks down, and the register goes back in a drawer that nobody opens again unless there is an incident.

That works until it does not. The failure modes are predictable: the host is in a meeting and does not pick up, the visitor has no idea who they actually need to see, a courier leaves a parcel with whoever is standing there, and when the security audit asks who was in the building on a particular afternoon the honest answer is that nobody knows.

This is what a visitor management system is for. Not surveillance, and not a turnstile. A record of who was expected, who actually arrived, who let them in, and when they left.

The four arrivals an office actually gets

Almost every visitor is one of four kinds, and a system that only handles the first one is not much use.

The expected visitor. A meeting was scheduled. Somebody inside knows they are coming. This is the easy case, and the only one most paper processes handle well. The visitor should be pre-registered by the person they are meeting, arrive to a pass already waiting, and be admitted without anyone making a phone call.

The walk-in with a named host. No appointment, but they know who they want. The desk needs to reach that person, get a yes or no, and admit or turn away on the answer. The important part is what happens when the host does not respond, which is most of the time in a busy office.

The walk-in with no named host. A sales call, an interview candidate who only has an HR email address, a vendor who says "accounts, I think". There is nobody to ring. Somebody at reception has to make a judgement. A system that requires a host to be named cannot represent this arrival at all, so in practice it gets recorded as a fake host or not recorded.

The delivery. A courier with a parcel for a person, or for the company generally. This is the most frequent arrival in most offices and the one most likely to be handled by nobody in particular.

Pre-approval is the only thing that removes work

Every other feature adds steps at the gate. Pre-approval removes them.

When the employee who scheduled the meeting registers the visitor in advance, the visitor arrives to a pass with a code, the guard verifies it, and nobody is interrupted. No phone call, no waiting in the lobby, no judgement call by a guard who has never met the visitor.

The practical test of a visitor system is how few taps it takes an ordinary employee, not an admin, to pre-register somebody for tomorrow morning. If it takes more than about thirty seconds, employees will not do it, and the office falls back to phone calls.

Host timeouts are where most systems quietly fail

The design question nobody asks in a demo: what happens when the host does not answer?

A visitor is standing at the desk. A notification went to somebody's phone. That person is in a meeting, on a call, or has notifications off. In a paper process the guard keeps ringing. In a badly designed digital process the request simply sits there and the visitor waits.

The answer is a timeout with a named fallback. After a configurable window, the request should escalate to reception, who can make the call. That single rule is the difference between a system that works in a real office and one that works in a demo where the host is sitting beside the salesperson.

Deliveries and parcel custody

A parcel addressed to a person can be held for that person. A parcel addressed to the company has to be held by somebody, and "held by somebody" needs a name and a pickup code, or it becomes a pile on the reception counter.

The rule worth adopting: deliveries default to reception unless a specific employee is named. Reception gets a pickup code, the employee is notified, and the parcel is marked collected when it is handed over. It is a small workflow that eliminates a recurring daily annoyance.

Visitor data is personal data

An office that photographs visitors and stores their phone numbers is processing personal data, and under India's Digital Personal Data Protection Act the office is the data fiduciary. Housing societies often get treated leniently here. A company will not be.

Three things follow from that:

• Collect only what the purpose needs. A name, a phone number, who they are visiting, and a timestamp cover almost every legitimate security purpose. An ID card scan usually does not.
• Tell the visitor. A visitor handing over a phone number at a desk should be able to see why it is being collected and how long it is kept.
• Delete on a schedule. Visitor records should have a retention window and actually be purged at the end of it. An indefinitely growing visitor database with photographs is a liability, not an asset.

If the answer to "how long do we keep visitor photos" is "forever, I think", that is the first thing to fix, before buying any software.

Reception is a role, not a person

The front desk is frequently staffed by whoever is available, including temporary cover. That has a permissions consequence that most systems ignore: if the only way to let somebody approve visitors is to make them a full administrator, then temporary front-desk cover can also edit the employee roster and change company settings.

Ask specifically whether reception can be a narrow role. If not, understand that you are handing administrative access to the front desk.

What to check before buying

• Can an ordinary employee pre-register a visitor themselves, in under a minute, without an admin?
• What happens when the host does not respond? Is the timeout configurable, and where does it escalate?
• Can the system represent a visitor with no named host, or does it force a fake one?
• Do deliveries have a custody path with a pickup code?
• Is there a real record of who approved each entry, that cannot be edited afterwards?
• Can you export the visitor log for a date range for an audit?
• What is the retention period for visitor photos and phone numbers, and is the purge automatic?
• Can the guard desk keep working when the internet drops?
• Does reception need full admin rights to do its job?
• If you have more than one entrance or site, is that one tenant with several gates, or several accounts to keep in sync?

How this works on Plinth

Plinth runs office visitor management on the same gate engine it runs for residential campuses, which means the parts that are hard to get right, the guard booth app, offline entry queues, QR and OTP verification, blacklists and multi-gate logging, were already in production before the office product existed.

An office is set up as a company tenant. The employee roster carries employee ID, department, designation and an optional photo, and employees claim their own record with a one-time code so the directory stays current without an admin maintaining it by hand.

Employees pre-approve their own visitors. Walk-ins name a host from a searchable directory, or go straight to reception when there is no host to name. If a named host does not respond inside the configured window, the request escalates to reception automatically rather than leaving the visitor waiting. Deliveries default to reception with a pickup code, and the parcel is marked collected on handover.

The guard uses the Plinth Gate app on a tablet at the desk, with PIN login, camera QR scanning and an offline queue, so entries keep being recorded through a network drop and sync when it returns.

Every approval, denial, escalation and parcel handover writes to an append-only audit log, which is what turns "who let that person in on Tuesday" into a lookup instead of an argument.

Frequently asked questions

Can employees register their own visitors, or does it have to go through reception? Employees register their own. Requiring reception to enter every visitor is the reason most offices abandon their visitor system within a month.

What happens if the person being visited does not answer? The request escalates to reception after a configurable timeout, so somebody can always make a decision rather than the visitor waiting indefinitely.

How do we handle a visitor who does not know who they need to meet? Reception-routed walk-ins exist for exactly this. The guard sends the request to reception rather than being forced to name an employee.

Do we need a separate app for the security guard? Yes, and that is the right design. The guard desk runs a dedicated booth app with PIN login rather than a personal account, so a shift change does not mean sharing a password.

Is visitor data covered by DPDP? Yes. A company collecting visitor names, phone numbers and photographs is processing personal data and is the data fiduciary for it. Collect the minimum, tell the visitor, and purge on a schedule.

Can one company account cover several offices? Yes. Multiple entrances or sites are gate locations inside one tenant, not separate accounts.

Does this track employee attendance too? No, and deliberately. Gate visitor logging and employee attendance are different problems with different consent implications, and mixing them is how a visitor system turns into a surveillance complaint.

Step-by-step guides

• Admin: Set Up Office Visitor Management
• Reception: Approve Walk-in Visitors
• Employee: Pre-approve a Visitor

Related: visitor register vs software · visitor data privacy rules · how societies do the same thing