Skip to content
Blog

The Paper Visitor Log and Québec's Law 25: What to Change

September 10, 2026 · 8 min read

There is a book on the counter. It is open, because it has to be open for the next person to write in it, and it is turned toward the visitor, because that is who writes in it. So the courier signing for a delivery reads the name of the candidate who came in for an interview that morning, the company she came from, and the manager she was there to see. Nobody decided this. It is just what an open logbook does, all day, to everyone who walks up to it.

The sign-in sheet is a disclosure, not just a record

The paper log is usually described as a record — proof of who was in the building, kept in case anyone asks. That is half of what it is. The other half is a small, continuous act of publishing.

Look at what a visitor can read while they are writing their own line. Names. Employers, if you ask for the company. The host, which tells them who works there and who that person meets with. Arrival times, which tell them how long people stay. A page of a visitor log is a list of business relationships, and it is sitting at eye level in the least controlled room in your building.

Some of that matters more than it sounds. A candidate does not necessarily want their current employer to learn they spent a Tuesday morning at your office. A supplier does not want to see their competitor's name three lines above their own. And a person who came in about something private — a clinic, a law office, an HR matter — did not agree to have their visit readable by whoever came next.

The rest of the paper log's problems follow from the same page being the only copy. You cannot search it. You cannot answer "was this person ever here" without turning pages. It lives on the desk you would evacuate first. And when someone asks you to remove their information, the honest answer is that you would have to find the line, and the line is in a bound book with everyone else's on the same page.

Ready to see it running?

A screen on the wall or a tablet at the desk — free to start, and you only move up a plan when the lobby grows.

Get started

What Law 25 is about, at the level a front desk needs

A note before this section: this is practical guidance for a reception desk, not legal advice. WeDisplay is not a law firm, and nothing here is a compliance ruling for your organization. What applies to you depends on what you collect, why you collect it and who you are — questions worth putting to counsel or to the Commission d'accès à l'information du Québec rather than to a blog post.

With that said, the shape of it is not mysterious. Law 25 is Québec's framework for how organizations handle personal information about people, and it is in force. A visitor's name is personal information. So is their employer, their phone number, the reason they came and the person they came to see. Collecting it at a front desk is normal and generally fine; the framework is about the care you take with it afterward.

At the altitude a receptionist can actually work with, the recurring themes are these. Collect what you need for a purpose you can state, rather than everything a form template happened to include. Tell people what you are collecting and why, at the moment you collect it, in terms they can understand. Protect it once you have it, which includes protecting it from being read casually by the next person at the counter. And be able to find it, show it and dispose of it — which means knowing where it is and having chosen how long you keep it, instead of accumulating by default.

None of that requires a compliance program. Most of it requires the sign-in step to stop being a shared page.

The practices worth changing

Six changes cover almost all of it, and none of them need a policy binder.

  • Collect three things. Name, purpose of visit, and host. That is enough to notify the right person, to know who is inside, and to answer a question later. Every extra field — home address, driver's licence, licence plate — is something you now have to protect, justify and eventually delete. The shortest form is also the easiest one to defend.
  • Make the list private by default. No visitor should be able to read another visitor's entry, and that includes on the way out. Checking out should not mean scrolling a roster of everyone in the building; showing a first name and an initial is enough for a person to find their own line and not enough to be a directory.
  • Tell them, in their language, at the counter. A short notice — what you collect, why, who sees it, how long you keep it — presented where the collection happens, not buried on a website nobody opens at reception. A notice in a language the visitor does not read is decoration.
  • Version the documents instead of photocopying them. If visitors sign an NDA or a safety briefing, the signed copy has to point at the exact wording they agreed to. Editing a master file in place silently rewrites the terms of every signature already collected. That deserves its own treatment, and we wrote about it in getting visitor documents signed at check-in.
  • Keep a log you can actually work with. Searchable, so a question takes a moment rather than an afternoon. Exportable, so you can hand a period to whoever is asking. And on a retention window you chose deliberately, so old visits go away because you decided they should, not because a book got full.
  • Notify hosts through what they already use. The point of the logbook was never the book — it was telling somebody their guest arrived. Do that directly, and the visitor no longer needs to be handed a page of other people's information to accomplish it.

Doing it on a tablet you already own

This is what the visitor kiosk is for, and it runs on a tablet at the desk rather than new hardware.

  • A check-in that asks for three things. The visitor taps who they are, why they are here and who they are seeing, and they are checked in with a visit code and a digital pass. The tablet speaks seven languages — English, French, Spanish, Romanian, Punjabi, Hindi and Mandarin — and each visitor can switch to theirs for the length of their visit, so the questions and the notice they read are in a language they actually use.
  • A screen that gives nothing away. The check-out list shows a first name and an initial, never a full one. Host emails, phone numbers and department inboxes are never sent to the tablet at all. Kiosk pages are kept out of search engines entirely. And each kiosk is bound to exactly one paired tablet, so a link that leaks is useless anywhere else — another device sees a neutral notice, with no company names, no host list and no visitor data.
  • Documents signed on the glass, versioned. Attach a document to a visitor type and nobody of that type checks in without signing it, on the tablet, in the language they picked. Your privacy notice can ride the same path as your NDA. Editing the text publishes a new version rather than rewriting the old one, because every signature points at the exact version it agreed to. The signed PDF holds the text, the signature, the name and the timestamp, and if the visitor left an email address their own copy is sent to them.
  • A log you can search and hand over. Every visit is searchable and exportable to CSV, with trends by day, by visitor type, by company and by hour of arrival. Visits purge themselves on a retention window you choose, so the disposal question has an answer you can point at.
  • The host told where they already are. Every check-in emails the host. Connect Slack, Microsoft Teams or Zoom Team Chat and the same notice lands in the channel your team already watches. A department can have its own inbox — Shipping, Reception — so whoever is on duty receives the guest.
  • A reception team working in French. The dashboard and the public site are fully available in French, English, Spanish and Romanian, chosen per user, so the person running the desk configures visitor types, notices and retention in the language they work in. If your lobby screens raise the same language question, bilingual digital signage in Québec covers the display side. There is also a short overview of the whole setup on the front desk page.

What to do this week

  1. Stand at your own counter and read the open page. Not as the person who owns the log — as the next visitor. Whatever you can read there, every visitor this week can read too.
  2. Cut the form to name, purpose and host. Take a marker to the columns you cannot justify out loud. If nobody has used the phone-number column in a year, it is not a record, it is an exposure.
  3. Write the notice, in one short paragraph. What you collect, why, who sees it, how long you keep it. Have it translated into French and whatever else your visitors actually speak, and put it where the collection happens.
  4. Pick a retention window and say it out loud. Any deliberate period beats an indefinite one. Write it down, tell the desk, and make sure something enforces it other than someone's memory.
  5. Take the documents off the photocopier. Find the current wording of every form a visitor signs, confirm it is the one in the folder, and move it somewhere that publishes a new version when it changes instead of overwriting the old one.

None of this is a project. It is an afternoon at the desk, and it replaces the single most public piece of paper in your building.

Related articles

NDAs at Reception: Getting Visitor Documents Signed at Check-In

Get an NDA or safety briefing signed before a visitor is through the door — versioned documents, e-signature on the tablet, and the Québec Law 25 angle.

Published on August 21, 2026 · 7 min read

The Fire Drill List: Evacuation Roll Call for Staff and Visitors

Who is really in the building when the alarm goes off? How a who's-in board and a tap-through roll call replace the clipboard at the assembly point.

Published on August 20, 2026 · 7 min read

Visitor Kiosk Software: How to Compare the Category

A buyer's framework for comparing visitor management platforms — how the category is priced, what a second entrance costs, and what to test in a week.

Published on August 18, 2026 · 8 min read