Regular suppliers and drivers
They show up every week, sometimes every day. Registering suppliers must be quick but recorded on every access: “we know him” is not a procedure.
Employees, visitors, suppliers, consultants and maintenance engineers don’t enter your building in the same role — and they shouldn’t be registered with the same tool. A practical guide to who gets registered where, so reception, administration and HR stop tripping over each other’s data.
In short
A visitor log tracks the people who enter your company as guests or externals: clients, suppliers, consultants, engineers. Employee attendance is a different process altogether: working hours, clock-ins, shifts and absences — an HR matter, with different data and different owners.
The practical rule: externals check in at reception and go into the visitor log; employees clock in on a dedicated attendance system. Mixing the two produces unreliable data and organisational confusion.
The mix-up is common, especially in small and mid-sized companies: one entrance, one front desk and often one tool — a paper sheet, a spreadsheet, sometimes an app — that swallows everyone: the visiting client, the maintenance engineer, the new hire and the courier. As long as nothing happens, nobody notices. The day you need to know who was on site, or payroll asks for a contractor’s hours, the numbers don’t add up.
This guide puts things in order: what a visitor log does, what an employee time tracking system does, how to handle the in-between cases — regular suppliers, consultants, external contractors — and how to set up a clear procedure without adding red tape.
A visitor log — or visitor register — keeps track of the people outside your organisation who enter the premises: who they are, where they come from, who they are meeting, when they arrive and when they leave. It belongs to reception, not to the HR department: it describes a visit, not an employment relationship.
A small, purposeful set of data: knowing who is on site and why. For guidance on which data to collect and which to avoid, see our guide to the GDPR visitor log.
Registering employees serves a completely different purpose: it doesn’t describe a visit, it describes the employment relationship. The question is no longer “who are you meeting and why are you here”, but “when did you start, when did you finish and how do those hours get processed”. In practice, an attendance system handles:
For employees, then, the right tool is not the reception register but an employee attendance system built for clock-ins, working hours, shifts and HR data, feeding directly into payroll and personnel administration.
The table below sums up the comparison point by point — the quickest way to see which process fits which situation:
| Aspect | Visitor log | Employee attendance |
|---|---|---|
| Purpose | Knowing who enters, why, and who they meet | Recording attendance and working hours |
| People involved | Guests, clients, suppliers, consultants, engineers | Internal staff |
| Frequency | Occasional or non-continuous access | Daily, continuous access |
| Data collected | Name, company, host, reason, visit times | Clock-ins, shifts, absences, overtime |
| Who owns it | Reception, security, facility management | HR and personnel administration |
| Right tool | Visitor management software | Attendance / HR software |
| Expected output | Entry history, list of people on site | Monthly timesheets, payroll data |
| Example | The engineer arriving for maintenance | The operator clocking in for a shift |
Two columns, two worlds: purpose, data, owners and tools all change. The point is not which process is “better” — they do different jobs.
This is where most of the confusion starts. Some people are not employees, but they are not occasional visitors either: they come in often, sometimes every day, and they know the site better than some insiders. The typical cases:
They show up every week, sometimes every day. Registering suppliers must be quick but recorded on every access: “we know him” is not a procedure.
A project can keep them on site for weeks. They remain external staff: it makes sense to register them as such, ideally with a fast-track check-in for repeat entries.
Crews working in production areas or on internal projects. Here access tracking overlaps with safety coordination: it calls for rigour, not improvisation.
Planned or emergency interventions, often in operational areas. Knowing who intervened, when and on what stays useful months later.
Occasional by definition: a standard visitor check-in, handled with discretion — the reason for the visit should not be readable by anyone walking past.
The classic case: a polished welcome, the host notified, a badge if your process includes one. It is the first impression your company makes.
The practical rule: if a person is not an employee but enters your premises for a visit, an intervention or external work, the tidiest route is a visitor or external staff registration process, following the rules your company has set. On industrial sites the distinction is often required by audits and certifications too — we cover it in our page on visitor management for industrial sites.
It is rarely bad faith: these are habits formed when the company was smaller and never revisited. The ones we see most often:
One last source of confusion is the tool itself: solutions born for different jobs get used as if they were interchangeable. They are not:
| Tool | What it is good at | Where it falls short |
|---|---|---|
| Paper register | Simple, immediate, zero setup | Messy, visible to anyone, nearly impossible to search afterwards |
| Excel sheet | Tidier than paper, zero cost | Poorly controlled, copies floating around, awkward at a reception desk |
| Access control (badges, turnstiles) | Authorising or blocking physical entry | Says nothing about hospitality or the context of a visit |
| Attendance / HR software | Employee clock-ins, hours and shifts | Not designed for guests and occasional entries |
| Visitor management software | Guests, suppliers, consultants and external staff | No substitute for clock-ins, payroll and HR processes |
Access control tells you whether a door opens; the attendance system tells you how many hours an employee worked; the visitor log tells you who came in, why, and who was expecting them. For a deeper comparison of the first approaches, see our guide paper, Excel or software.
IRIGuest covers the first of the two processes: managing visitors and external staff. It replaces the paper register and improvised spreadsheets with a tidy tablet check-in: the visitor registers, signs on screen, the host can be notified, and the history stays searchable — restricted to authorised people, not lying open on the desk.
Registration questions are fully customisable: a company can distinguish visitors, suppliers, consultants and external firms right at check-in, each with its own flow and notices. And if your process includes an identification pass, IRIGuest works hand in hand with QR-coded visitor badges.
In more structured organisations the Cloud version adds automatic host notifications, multi-gate and multi-site management and centralised reporting: reception registers, the company sees everything in one place.
In structured companies the two tools live side by side, each in its place: an attendance/HR system for employees, IRIGuest at reception for visitors and external staff, possibly flanked by physical access control on the gates. None of the three replaces the others; together they cover every entry with no grey areas.
It is the same philosophy behind the IRIDay suite by Iride Progetti, which includes the attendance system mentioned above: specialised tools that complement each other, rather than one catch-all container that does everything halfway. IRIGuest is designed to be complementary to HR and MES systems, not an alternative to them.
The deciding principle is the one this guide opened with: first distinguish the people coming in — employees, guests, externals — and only then choose the tools. Doing it the other way round is the fastest route back to that single Excel file.
Generally no: it is not the right tool. Employees need attendance management tied to working hours, shifts, clock-ins and HR and payroll processes — purposes a visitor log does not cover. The log can, however, handle edge cases such as an employee from another site making an occasional visit.
The visitor log records who enters the company as a guest or external: who they are, who they meet, when they arrive and leave. The attendance register concerns internal staff: it records working hours, shifts and absences and feeds HR administration and payroll. Purpose, data and internal owners all differ.
It depends on company procedures. Occasional suppliers, engineers and drivers are usually treated as entries to be registered, especially when they access reception, offices or production areas. For regular suppliers a leaner process — for example with QR codes — makes sense, as long as every access is still recorded.
No. IRIGuest is designed for managing visitors, guests, suppliers and external staff. For employees the correct choice is a dedicated attendance or HR system, such as the one in the IRIDay suite: the two tools are complementary and can coexist in the same company.
Yes. If your company chooses to manage consultants, engineers and maintenance staff as external entries to be registered, IRIGuest lets you distinguish them from standard visitors with custom questions and registration flows, even when their presence repeats over several days.
Because the two processes have different purposes, data and owners: mixing them in one file creates confusion, makes it harder to control who accesses the information, and complicates reconstructing entries when it matters. Two dedicated tools, each with its own scope, work far better.
The attendance system looks after your employees. IRIGuest looks after visitors, suppliers and external staff: tablet check-in, on-screen signature and a history that is always in order.