Visitor management software: from the paper logbook to a “who is inside” list

When the evacuation alarm sounds, the hardest question is: who is in the building right now? For employees the answer is clear, but visitors sit in the paper logbook at reception, in rows with no exit time written. Visitor management software is software that records a visitor’s details, the person they are visiting, KVKK (Turkey’s personal data protection law) consent, entry and exit times and whether they are inside at that moment.

In this article we explain what the paper logbook cannot do, how a digital flow closes those gaps and what to watch for in the transition, using the Visitor Management module inside YazSis KurumsalPortal.

What the paper logbook cannot do

• It does not tell you who is inside now; you have to scan the rows with no exit written one by one, and this is where the most time is lost in an emergency.
• The person being visited learns that their guest has arrived only by phone.
• The page with personal details passes in front of everyone who arrives, and whether KVKK consent was obtained is not recorded.
• When a report such as the number of visits or time on site is needed, the pages are scanned by hand; this takes time and is prone to error.

The digital flow: five steps from the door to the exit

1. Register the visitor. Reception registers the visitor and the person they will visit digitally.
2. Obtain consent. KVKK consent is a step in the registration flow; the consent is stored together with the visit record and can be checked later.
3. Notify the host. An automatic notification goes to the employee being visited, the host, so they find out in time that their guest has arrived.
4. Start the entry. The visitor is now inside and appears in the real-time list.
5. Complete the exit. When the exit is recorded, the visitor drops off the list and the time on site is entered in the record.

The order of the steps matters: consent is obtained before the host is notified and before entry. This way the consent step is not forgotten in the flow; every visit sits in the same record as its consent. The person at reception is also never unsure what to do, because the flow guides them to the next step.

The “who is inside” list in an emergency

The module shows visitors who have checked in and whose exit has not yet been completed in a real-time list of people inside. In an evacuation or emergency, the reception and security team can see from this list who is on the premises and whom they are visiting, on one screen. For example, the team counting at the assembly point after an evacuation can compare visitors against this list to check whether anyone is missing. With a logbook, this takes manual scanning of pages and a count that is often based on guesswork. Fast reception and emergency visibility are the most concrete gains of this flow.

KVKK consent and record keeping

Visitor records and KVKK consent records are kept in the portal running on the customer’s own server. Who can see the records is determined by role-based permissions. These controls help you build a KVKK-focused process; however, the content of the privacy notice must be prepared according to the organization’s own KVKK assessment. The software does not replace the text; it places the consent step in the registration flow. Because the consent is stored with the visit, the answer to “was consent obtained from this visitor?” can later be read from the record without leafing through a logbook.

Three questions when going live

• Who will do the registration? If reception shifts change, make sure the person registering on each shift knows the system. A queue of visitors waiting during registration is where the digital flow wears out fastest, so it matters that registration is quick.
• Who will remind about the exit? If a visitor does not stop by reception on the way out, the list does not reflect reality. Telling the visitor and the host about exit registration in advance keeps the list reliable.
• Who will prepare the privacy notice? The content of the text used for KVKK consent is prepared according to the organization’s own assessment. Settling the text beforehand prevents the registration flow from stalling on setup day.

Reporting and roles

Visit records are reported together with time on site and can be exported as XLSX. When you need to look back at visit history, you have an orderly record with the date, the person visited and time on site; you do not need to leaf through logbook pages. Three roles use the module:

• Reception: registers the visitor, obtains consent, starts the entry and completes the exit.
• Security: monitors the list of people inside, sees who is on the premises in an emergency, and notices visitors whose exit has not been recorded.
• Administrative affairs: reviews visit records and reports.

A small implementation tip

In the first week of the transition, instead of leaving the paper logbook at reception as a backup, declare the digital record the single source. In a reception that keeps two logbooks, the question of which one is current comes back and the “who is inside” list loses its reliability. Announcing the switch date in advance and informing reception and security together also reduces confusion on the first day of the process.

You can see how the record works and how it relates to the other modules on the Visitor Management and KurumsalPortal pages.