A corporate reception desk performs two functions at once. It is the first point at which a visitor forms an impression of the organisation, and it is the first layer of physical access control between the public street and the working floors. A visitor management standard has to satisfy both functions, because a procedure that slows arrivals will be bypassed by staff, and a procedure that is welcoming but unrecorded provides no access control at all.
This document sets out a specification for visitor management in corporate offices in Mumbai, Pune and comparable cities: the objectives, the process from invitation to departure, the roles and records involved, the handling of personal data, and the measures by which a facility head can verify that the standard is being met. It is written so that it can be issued to a security vendor and a front-office team as a common reference. For the wider access-control context, see our guide to corporate office and IT park security in Mumbai and Pune.
Objectives of a visitor management standard
A visitor standard is easier to enforce when its objectives are stated plainly and are few in number. Four are sufficient for most offices.
- Identity: every visitor is identified against a government-issued photo identity document or an equivalent verified credential before reaching a working floor.
- Authorisation: every visit is attributable to a named internal host who has confirmed that the visitor is expected.
- Containment: a visitor can reach only the areas relevant to the purpose of the visit, and the record shows which those are.
- Accountability: the organisation can state, for any point in time, who is on the premises, who invited them and when they left.
The fourth objective is the one most often unmet. Many offices record arrivals diligently and record departures rarely, which leaves the register unable to answer the one question that matters during an evacuation or an incident: who is still in the building.
Visitor categories and handling rules
A single process for every person who enters reception produces either excessive friction for routine arrivals or insufficient control for sensitive ones. Defining categories at the outset allows the process to be proportionate.
| Category | Typical examples | Pre-registration | Identity check | Access scope |
|---|---|---|---|---|
| Scheduled business visitor | Client, partner, candidate, auditor | Host registers in advance | Photo identity matched to invitation | Meeting floor and common areas |
| Walk-in visitor | Unannounced caller, courier recipient | None; host confirms at desk | Photo identity recorded | Reception area until host collects |
| Recurring contractor | Facilities, IT support, housekeeping supervisors | Standing pass with validity dates | Pass checked at each entry | Named zones and hours only |
| Delivery personnel | Couriers, food and parcel delivery | None | Name and company logged | Reception or mail room; no floor access |
| Senior or high-sensitivity guest | Board members, regulators, executive guests | Host and front office, with advance briefing | Verified in advance where possible | As agreed with host; reception informed of route |
| Event or large-group arrival | Training batch, interview drive, town hall guests | Bulk list from organiser | List checked against identity | Event area only, with defined route |
The category determines the controls. The table above is a starting point; each organisation should adjust the access scope column to its own floor plan and data-handling requirements, and record the final version in the visitor policy.
The process, from invitation to departure
Stage 1: pre-registration
Pre-registration is the single measure that most reduces both queue length and risk. The host enters the visitor’s name, organisation, mobile number, expected arrival time and purpose before the visit. The visitor receives an invitation containing the address, the arrival instructions and a reference code or QR code. On arrival, the receptionist verifies the identity document against the pre-registered name rather than collecting details from the beginning, which shortens the transaction to the verification step alone.
The standard should specify the cut-off for pre-registration, for example before the visit starts, and the fallback for visits that were not registered in advance. A visit that arrives unregistered is not refused; it is processed as a walk-in, with the host confirming at the desk.
Stage 2: arrival and verification
At arrival the guard or receptionist performs four checks in a fixed order: the visitor’s identity against the invitation or the host’s confirmation; the photo identity document against the person; the declared items, such as laptops, storage media or tools, where the site requires declaration; and the host’s confirmation that the visitor is expected. The order is fixed so that the check does not depend on the individual operator’s judgement of whether the visitor appears credible.
The identity document is viewed and its details recorded; photocopying the document is not required and, for the reasons described in the data-protection section below, is generally better avoided.
Stage 3: badge issue and escort rules
A visitor badge should state the visitor’s name, the host, the date, the zones permitted and a visible expiry. A colour or format distinct from staff passes allows any employee to recognise a visitor at a glance. Badge stock is numbered and reconciled at the close of each day, so that an unreturned badge is identified the same evening rather than discovered later.
Stage 4: movement and monitoring
Between arrival and departure, control depends on three things: the badge, the turnstile or door control at floor entrances, and the awareness of staff. Where turnstiles or access-controlled doors are installed, visitor passes should be encoded for the permitted floors only. Where they are not, the guard at the floor entrance checks the badge against the zone printed on it. Guards raise a visitor found outside the permitted zone with the host or the front-office lead, and the standard should say so explicitly. The role of the security team is to observe, verify and report, and escalation proceeds through the organisation’s own management.
Stage 5: departure and reconciliation
Departure is recorded by the guard or receptionist, the badge is returned, and any declared items are checked against the declaration. The visitor’s time out is entered against the original record. At a defined hour each day, and at the end of the working day, the register is reconciled: every visitor with a time in and no time out is investigated with the host before the desk closes. This reconciliation is the control that makes the fourth objective, accountability, achievable.
Records to be captured
The minimum record is short. Longer forms reduce compliance without improving control, and they increase the quantity of personal data the organisation must then protect. The fields below are those commonly expected in access-control procedures aligned with ISO/IEC 27001 Annex A control 7.2, which addresses physical entry and the recording and supervision of visitors.
| Field | Purpose | Notes |
|---|---|---|
| Visitor name | Identification | Matched to the photo identity document |
| Organisation | Context and accountability | Drawn from the invitation where pre-registered |
| Purpose of visit | Authorisation | Selected from a short list, not free text |
| Internal host | Accountability | Named employee; confirms the visit |
| Time in and time out | Presence record | Both fields mandatory; time out reconciled daily |
| Badge number | Asset control | Links the person to the physical pass |
| Declared items | Asset control | Only where the site requires declaration |
| Zones permitted | Containment | Printed on the badge and held in the record |
The medium, whether a bound register with numbered pages or a digital system, is secondary to the discipline of the process. A paper register is workable at low volumes provided earlier entries are not visible to later visitors; a digital system adds pre-registration, host notification and searchable history. When specifying a system, the facility head should confirm where the data is stored, who can view it, how long it is kept and how it is deleted.
Roles of the front office and the security team
Visitor management sits across two functions, and ambiguity between them is the common reason a good policy fails in practice. The front office owns the visitor’s experience: greeting, invitation, host communication, waiting arrangements. The security team owns verification and access enforcement: identity checks, badge control, zone checks and escalation. A written division of responsibility avoids the situation in which each function assumes the other has completed a check.
| Activity | Front office | Security team |
|---|---|---|
| Pre-registration management | Owns | Receives the daily list |
| Greeting and host notification | Owns | Supports |
| Identity verification | Supports | Owns |
| Badge issue and reconciliation | Supports | Owns |
| Floor-entrance zone checks | Not applicable | Owns |
| Daily register reconciliation | Reviews exceptions | Prepares and escalates |
| Visitor complaints and waiting-time review | Owns | Provides data |
Where one provider supplies both functions, see front office and support services and corporate and commercial security; the same division applies, with the provider’s supervisor accountable for the combined desk.
Reducing friction without reducing control
The measure of a visitor process is the time between a visitor reaching the desk and being cleared to proceed. The following design measures reduce that time without removing any check.
- Pre-registration for scheduled visits. Verification replaces data entry, which is the largest single saving.
- Separate lanes or positions for expected and unexpected visitors. A queue of unexpected visitors then does not delay those with a reference code.
- Peak-hour staffing. Arrivals cluster before meeting start times, commonly in the early part of the morning and after lunch. The desk is staffed to the peak, not the average, with an additional guard or receptionist during those windows.
- Host response standard. A host who does not confirm within a set period, for example a few minutes, is called by the front-office lead. Waiting for a host is the commonest source of delay and is controllable.
Personal data in visitor records
A visitor register holds personal data: names, mobile numbers, photographs and identity document details. India’s Digital Personal Data Protection Act, 2023 applies to digital personal data, and the Digital Personal Data Protection Rules, 2025 were notified by the Ministry of Electronics and Information Technology on 14 November 2025. According to published summaries of the Rules, most of the substantive obligations, including those on notice, security safeguards and erasure, come into force eighteen months after publication. Organisations preparing their visitor processes now are therefore working ahead of the effective date, which is the sensible time to settle the design.
The practical implications for a visitor process are as follows. These are operational design points, and the organisation’s own legal adviser should confirm how the Act applies to its circumstances.
- Collect only what the purpose requires. The field list above is deliberately limited. Recording an identity document number is often unnecessary where viewing the document is sufficient.
- Give notice at the point of collection. A short notice at the desk, or in the invitation, states what is collected, why, and for how long it is kept.
- Avoid exposing earlier entries. A register in which each visitor can read the preceding lines discloses other visitors’ details and is addressed through a slip or digital format.
- Set a retention period and apply it. The period is chosen by the organisation against its security, audit and legal needs and is documented. Practitioner guidance for ISO/IEC 27001 audits commonly refers to retaining visitor records for the preceding twelve months so that samples can be shown to an auditor; this is a guidance figure, not a statutory one, and the organisation should set its own.
- Control access to the record. The front-office lead and the security supervisor view the register; others do so on a documented basis.
- Agree responsibilities with the vendor in writing. Where a security or front-office provider operates the desk, the contract states who holds the data, how it is protected and how it is returned or deleted at the end of the engagement.
Contingency procedures
The standard should cover the situations in which the normal process cannot run, because these are the occasions on which control is most likely to lapse.
Evacuation
In an evacuation, the visitor register is the document used to account for visitors. The guard on duty carries or has immediate access to the current list of visitors still on site and hands it to the nominated warden at the assembly point. This is the use for which time-out accuracy matters most.
Unregistered or refused visitors
A visitor who cannot produce an acceptable identity document, or whom the host declines to confirm, is not admitted beyond the reception area. The guard informs the host or the front-office lead and records the event. Their role is limited to controlling entry under the organisation’s access rules, and any further action rests with the organisation’s management.
Checklist for auditing the visitor process
The following checklist allows a facility head to verify the process in a single walk-through of the reception area and a sample of records.
| Item | Evidence to inspect |
|---|---|
| Visitor policy issued and current | Document with owner, version and review date |
| Categories and access scopes defined | Category table matching the floor plan |
| Pre-registration in use | Share of sampled visits with an advance record |
| Identity verified on every sampled visit | Register entries with identity type recorded |
| Host confirmation recorded | Host field complete on all sampled entries |
| Time out recorded | No open entries older than the previous working day |
| Badge stock reconciled | Daily count sheet signed by the supervisor |
| Floor-entrance checks operating | Observation of a guard checking badge zones |
| Data notice displayed | Signage or invitation text at the desk |
| Retention and access rules documented | Written procedure and access list |
| Contingency sheets available | Fallback forms stored at the desk |
| Staff briefed | Training record for guards and reception staff |
Specifying the requirement to a vendor
A tender or work order for a combined reception and security desk should state the visitor standard as a deliverable rather than leaving it to the vendor’s own procedure. At a minimum, the document should require the vendor to operate the process described above, to supply a named supervisor accountable for it, to provide the daily reconciliation, to train desk staff on the organisation’s categories and escalation rules, and to report on measures such as pre-registration share and arrival-to-badge time at an agreed interval. The vendor should also be required to hold a valid licence under the Private Security Agencies (Regulation) Act, 2005 for the guards it deploys, and to produce the verification and training records for those guards on request.
For budgeting the desk, the staffing implications of peak-hour coverage and relief arrangements can be estimated with the security cost calculator, which calculates on current statutory rates rather than a fixed figure.
Bryte Guard Force has deployed and supervised security teams across Maharashtra since 1996 and operates corporate and campus desks in Mumbai, Pune and other cities; see our work for business parks and corporate campuses. To have the standard above mapped to a specific reception, request a free site risk assessment, with a written proposal within 48 hours.
Frequently asked questions
What information should a corporate visitor register record?
The minimum is the visitor’s name, organisation, purpose of visit, internal host, time in, time out and badge number, with the permitted zones and any declared items added where the site requires them. Collecting additional fields increases the personal data held without improving control, so each addition should have a stated purpose.
Should security guards photocopy visitors’ identity documents?
In most offices this is unnecessary. Viewing the document and recording its type is sufficient to verify identity, and retaining copies adds a category of sensitive personal data that the organisation must then secure and delete. Where copies are required, for example by a regulated client or a particular contract, the requirement should be documented along with the retention period and access controls.
How long should visitor records be kept?
There is no single prescribed period for all offices. The organisation sets a period against its security, audit and legal needs and documents it. Practitioner guidance for ISO/IEC 27001 audits commonly refers to twelve months of records being available for sampling, which many organisations adopt as a reference point.
Can security guards stop or remove a visitor who breaches the rules?
Guards control entry to the premises under the organisation’s access rules and can decline admission to a person who cannot be verified. Their role is limited to observing, verifying and reporting. When a visitor is found outside a permitted zone, the guard informs the host or the front-office lead, and the organisation’s management decides any further step.
Do the Digital Personal Data Protection Rules apply to visitor registers?
Where a register holds digital personal data, the Digital Personal Data Protection Act, 2023 and the Rules notified in November 2025 are relevant, and published summaries indicate that most substantive obligations take effect eighteen months after notification. The organisation’s legal adviser should confirm the position for its own circumstances, and the visitor process should be designed now around limited collection, a clear notice, defined retention and controlled access.