One visit at Meridian One.
The film on our home page, as text. Rahul Mehta visits Priya Sharma at Meridian One. Sample data.
Arriving and checking in
- 10:58, Meridian One
A busy Tuesday lobby.
Guests, contractors and interview candidates, all arriving at once.
-
The old way holds everyone up.
A queue, a pen on a string, and a register the next visitor can read.
-
A smarter way starts here.
Rahul walks past the queue to the check-in poster. No app to install, no shared tablet.
For your team: nothing to buy. Setup ends with a poster you print in the office.
-
On his own phone.
The one device every visitor already carries and already knows how to use.
-
Scan to begin.
The camera opens check-in in the browser. Android or iPhone, nothing to download.
-
Meridian One greets him first.
Before a single question, he sees what he will be asked, why, and how long each part is kept.
For your team: your name, logo and colour on every visitor screen.
-
Name, mobile, company.
Typed on his own phone, where nobody else in the lobby can read it. Nothing is saved until he agrees.
For your team: no open register for the next visitor to read.
-
He finds Priya, not her number.
Two or three letters bring up her name and team. No numbers, no emails, no staff list to scroll.
For your team: your directory stays private, even to someone standing in the lobby.
-
Consent, in his language.
What is collected, why, for how long, and how to withdraw. One clear button, never pre-ticked. Prefer not to? The desk signs him in instead.
For your team: each consent is stored with the exact notice and language he saw. That is the proof the DPDP Act asks you to keep.
-
Waiting, with a backup.
Rahul can put his phone away. If Priya does not answer in three minutes, her backup is asked. At six, the front desk.
For your team: you set who backs up whom, and when. Nobody at reception rings extensions.
Approval and the gate
- 11:00, Floor 3
Priya approves in WhatsApp.
His photo, company and purpose arrive in a chat she already uses. One tap. No app, no extension to ring.
- 11:00, back in the lobby
His phone lights up.
The waiting screen becomes his pass: where to go, and a code that changes every minute, so a screenshot is no use to anyone else.
For your team: every approval is logged with who said yes and when, the "authorised by" entry PCI DSS 9.3.4 asks for.
-
Straight to the gate.
No stop at the desk. The pass already shows his gate, building and floor.
-
The guard scans. Rahul walks in.
The guard app shows his photo, name, host and approval. The guard checks his face and lets him through. Priya’s number stays hidden.
For your team: in a fire drill, the roll call is already on the guard’s phone.
Five minutes. No queue. Every step on record.
- 10:58
Checked in on his own phone
No app, no shared tablet, no register on the desk.
- 10:58
Consent recorded
Saved with the exact notice and language he saw.
- 10:59
Mobile confirmed
One WhatsApp message from his own number.
- 10:59
ID checked, then discarded
Named in his notice, not shown in this film. Only the result is kept.
- 11:00
Approved by Priya on WhatsApp
Who said yes, and when, is logged.
- 11:03
Admitted at Gate 2
The guard matched his photo. The scan is logged to the guard’s PIN.
- 11:03
Added to the live register
The front desk sees him on site, and the roll call counts him.
Leaving
- 12:10, checked out
One tap to check out.
His receipt shows the date each part of his data is erased. A copy lands on WhatsApp.
For your team: visits left open close at the end of the day, so the evening register is accurate.
- 20 Oct 2026
Photo and mobile erased
- 13 Oct 2027
Visit record erased
What stays: a count. One visit to Finance on a Tuesday, with no name attached.
Every nightly clean-up writes a signed erasure report your DPO can hand to an auditor. Assurance plan
Sample settings. Each site chooses its own periods, within the legal minimum.
See it in your own lobby.
A short call with your building in mind. You leave knowing exactly how day one would run.