The Paper Visitor Register: What It Costs and When to Replace It

What the paper register actually fails at

A visitor book costs about forty rupees and needs no training. Before replacing one, it is worth being precise about what it does badly, because two of its failures matter a great deal and several do not matter at all.

The failures that do not matter much

Handwriting. Illegible entries are annoying but rarely consequential. Nobody has lost a contract because a courier's name was unreadable.

Data entry speed. A guard writes four fields in fifteen seconds. Most digital systems are slower at the desk, not faster, unless the visitor was pre-registered.

Looking unprofessional. Sometimes cited by vendors. A tablet in the lobby does not make an office more credible than a well-run desk with a person who knows what they are doing.

If these are the reasons for replacing the register, the project will not repay the effort.

The failures that matter

You cannot answer a question about the past. This is the real one. "Who was in the building between two and four on the fourteenth?" requires somebody to page through a book, and the book only contains what people chose to write. There is no way to search, filter or export. For an incident, an insurance claim, a client security questionnaire or a contact-tracing request, the register is effectively write only.

The approval is not recorded. The register records that a visitor arrived. It does not record who decided to let them in. When the question is "who authorised this person's entry", a paper register almost never answers it, because the authorisation happened over a phone call that left no trace.

Nobody is accountable for the gap between arrival and admission. A visitor stands at the desk while the guard rings extensions. There is no record that anybody was asked, no timeout, and no escalation. The visitor's experience depends entirely on whether their host happened to pick up.

Deliveries have no custody chain. A parcel is handed over, put on a counter, and either reaches its recipient or does not. When it does not, there is no record of who took it.

Repeat and unwanted visitors are invisible. A person asked not to return can walk in the next week and the guard on that shift has no way to know. A paper register cannot flag anybody.

It is a data protection problem in its own right. An open book on a counter shows every previous visitor's name and phone number to every new visitor. Under DPDP that is a disclosure of personal data to unrelated parties, and it happens continuously by design.

That last point is worth sitting with. Offices often move to software believing paper is the privacy safe option. It is the opposite: paper is legible to everyone in the lobby and impossible to purge on a schedule.

When paper is still the right answer

Honestly: a single-entrance office of under about fifteen people, with a receptionist who knows everybody by sight and gets a handful of visitors a week, does not need software. The register plus a person who pays attention outperforms a badly adopted system.

The tipping point is usually one of these:

• More than one entrance, or more than one site.
• Enough visitors per day that reception cannot remember them.
• A client, an auditor or a certification process that asks for visitor records.
• Any incident where you could not answer a question about who was inside.
• Frequent deliveries that go missing.
• Employees who complain that they were not told their visitor had arrived.

Notice that four of those six are about retrieval and accountability, not speed.

What a spreadsheet gets you, and where it stops

A shared spreadsheet is a real improvement on paper. It is searchable, exportable and not visible to the next visitor in the queue. Small offices run on this successfully for years.

Where it stops:

• The guard has to be logged in to a shared account, so entries are not attributable to a shift.
• Rows can be edited or deleted afterwards, so it is not evidence of anything.
• There is no way to notify a host, so approvals still happen by phone.
• No pre-registration, so every visitor is a walk-in.
• No blacklist, no pass codes, no offline behaviour.
• Visitor phone numbers accumulate in a file nobody purges.

A spreadsheet fixes retrieval and leaves accountability untouched. If the reason you are moving off paper is the audit question, a spreadsheet answers it. If the reason is "we do not know who let that person in", it does not.

What actually changes with a proper system

The genuine differences, stated without inflation:

The last row is the one to check in any demo. A cloud visitor system with no offline path is worse than paper during an outage, because the guard has nothing to fall back on.

The adoption problem, which is the actual risk

Most failed visitor-system rollouts fail the same way. Reception is made responsible for entering every visitor, employees never learn to pre-register anybody, and within a few weeks the tablet is a decoration and the register is back on the counter.

Two rules prevent it:

1. Employees pre-register their own visitors. If pre-registration requires going through an admin, it will not happen. It has to be something an ordinary employee does from their phone in under a minute.
2. The desk process must be faster than the book for the common case. Scanning a code on a pre-registered visitor is faster than writing four fields. Typing a walk-in's details into a form is slower. So the system only wins if pre-registration is genuinely used, which loops back to rule one.

Ask a vendor to show you an ordinary employee, not an administrator, pre-registering a visitor for tomorrow. Time it. That number predicts whether the rollout survives.

How this works on Plinth

Employees pre-approve their own visitors from the app, without going through reception or an administrator, which is the behaviour the whole thing depends on.

Walk-ins are handled properly rather than being forced into the pre-approval shape: the guard can name a host from a searchable employee directory, or send the request straight to reception when the visitor has no host to name. If a named host does not respond within the configured window, the request escalates to reception automatically.

The guard desk runs the Plinth Gate app with PIN login rather than a shared personal account, so entries are attributable to a shift, and an offline queue keeps recording through a network drop.

Approvals, denials, escalations and parcel handovers write to an append-only audit log, and the visitor log exports to CSV for a date range, which is what a client security questionnaire or an incident review actually needs.

Frequently asked questions

Is a paper visitor register legal in India? There is no general law requiring or prohibiting one. The issue is not legality but data protection: an open register on a counter discloses previous visitors' personal data to every new visitor, and cannot be purged on a schedule.

Do we have to stop keeping a paper register? Many offices keep one as an outage fallback. That is reasonable. What is not reasonable is keeping it as the primary record while also collecting the same data digitally, because then you have two retention problems.

How long should visitor records be kept? Long enough to serve the security purpose you are keeping them for, and no longer. Decide the period deliberately, write it down, and make the deletion automatic.

Will our security guards manage a tablet app? Generally yes, provided login is a PIN rather than an email and password, and the app keeps working offline. Both are things to verify rather than assume.

Is a spreadsheet enough for a small office? For a small single-entrance office with light visitor traffic, often yes. It fixes retrieval. It does not record who approved an entry, and its rows can be edited afterwards, so it is not evidence.

Step-by-step guides

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

Related: office visitor management · visitor data privacy rules