Skip to content
allanninal.dev/build
Collaborate

Part 5 of 7 · Visitor check-in logger series ~5 min read

Contractors are a different problem

A visitor flow designed for somebody arriving once for a meeting is wrong for somebody who is here every day for two months, and the difference matters for the roll call as much as for the convenience.

Key takeaways

  • Contractors need a fast repeat check-in, not the full visitor flow.
  • Site induction is a record with an expiry, and it is worth holding.
  • Deliveries are usually not visits and should not clutter the roll call.
  • Out-of-hours work needs its own handling; the sweep would close it.
  • Where permits to work exist, the check-in is the natural place to check them.

The repeat visitor

How a returning contractor checks in with fewer stepsA vertical chain of five steps entered by a box labelled Somebody arrives at the screen. Step one asks whether they have been here before, identified by a code or a card; if not it exits to Full check-in with name and host. Step two asks whether their induction is current, if the site requires one; if not it exits to Redo it before entry. Step three takes one tap to confirm and go. Step four puts them on the roll call, the same as anybody. Step five notes the same check-out problem, and worse, with a side box explaining that there is no host expecting them. A note says the convenience is the point, because a slow repeat check-in is one that gets skipped.AWS ACCOUNTSomebody arrivesat the screenBeen here before?by a code or a cardFull check-inname and hostnoInduction current?if the site requires oneRedo itbefore entrynoOne tapconfirm and goOn the roll callsame as anybodySame check-out problemand worseWhy worseno host expecting themThe convenience is the point: a slow repeat check-in is one that gets skipped.
Fig 1. The contractor flow. Making the repeat case fast is what stops people walking past the screen entirely, which is the real risk.
  • Compute
  • App integration
  • Machine learning
  • Security & identity
  • Management
  • Front-end & mobile
  • People

Worse check-out

A contractor has no host waiting for a notification, which removes the most effective check-out mechanism from Part 4. They also frequently leave and return several times a day, which produces either a great deal of tapping or an inaccurate log.

The pragmatic answer is a daily rather than per-entry model for on-site contractors: they check in for the day, and the person managing the works confirms at the end of the day who has left. That is less precise and considerably more accurate in practice.

Site induction

What the induction record holds

  • Who was inducted, and by whom.
  • When, and what version of the site rules it covered.
  • An expiry, typically annual, after which it is not current.
  • Any site-specific competencies that were checked.
  • Not a copy of their qualifications unless there is a specific reason. Recording that they were seen is usually enough.
  • The check-in is where it is enforced, because that is the only moment everybody passes through.

The fifth point is a data minimisation one that gets missed. Holding scans of every contractor’s certificates creates a store of other people’s personal documents with no clear owner. Recording that they were checked, by whom and when, achieves the same assurance with much less exposure.

Deliveries

Why deliveries are recorded separately from visitorsA horizontal row of five boxes. A driver arrives: two minutes at the door. Not really a visit: they never enter properly. On the roll call? They would still be there. A separate log: deliveries, not visitors. Roll call stays clean, and short. A note says fifteen delivery entries a day would double the roll call and none of them are inside.DELIVERIES ARE NOT VISITSA driver arrivestwo minutes at the doorNot really a visitnever enters properlyOn the roll call?they would still be thereA separate logdeliveries, not visitorsRoll call stays cleanand shortFifteen delivery entries a day would double the roll call and none of them are inside.
Fig 2. Why deliveries are logged separately. Including them makes the roll call longer and less accurate at the same time.
  • Compute
  • App integration
  • Security & identity
  • Front-end & mobile

A driver who comes into a goods area for two minutes is not somebody the fire marshal needs to account for, and the check-out mechanisms will never catch them. Logging deliveries separately — if at all — keeps the list that matters short.

Where a driver genuinely enters the building for longer — an installation, a long unload — that is a visit and should be treated as one. The distinction is about time inside rather than about job title.

Out of hours

Somebody working on a Sunday, or overnight, would be closed by an end-of-day sweep designed for a nine-to-five building, which is exactly the situation where an accurate roll call matters most because there is nobody else around.

Out-of-hours entries need a different sweep time and, ideally, a check-in that records an expected finish. It is a small amount of configuration and it covers the case where the consequence of getting it wrong is highest.

Permits to work

Where a site operates permits to work — hot work, confined spaces, electrical isolation — the check-in is the natural place to confirm one exists and is current, because it is the one moment everybody passes through.

The system should check and record rather than issue. Permit issue is a safety process with a competent person at the centre of it, and this is a logger.

Next: what all of this costs to run.

All posts