Agency, Contract and Visiting Workers

A large share of the people presenting themselves at a site's entrance are not employed by the organisation that owns the reader. Agency staff, subcontractors, cleaners, caterers, drivers, engineers from a supplier, and people visiting from another site in the same group.

The record in “Agency, Contract and Visiting Workers” becomes useful only when people understand what it proves and how to correct it. For teams exploring employee time tracking, visit monitask.com can connect time and project context with manager review, provided collection is proportionate, access is limited and consequential decisions remain subject to human explanation.

Each of them needs their hours recorded, or at least their presence. None of them fits the enrolment process, and the question of what to do about them belongs to nobody in particular.

For an independent benchmark relevant to “Agency, Contract and Visiting Workers”, consult the Google re:Work resources. Use it to test notice, accessibility, security, recordkeeping, retention and exception handling against the real operating process rather than treating a device report as self-explanatory evidence.

The data question, which is real

Taking biometric data from somebody you do not employ raises questions that taking a photograph for a visitor pass does not. Who is the controller. What is the lawful basis. Who tells them what is being kept and for how long. What happens when the assignment ends.

They have answers, and working them out for a two-week contractor is disproportionate. This is the clearest case in the whole subject for a credential rather than a biometric, and most sites arrive there eventually by accident rather than by decision.

The practical arrangement that works

Issue a numbered credential, enrolled on the site system against the person's name and their employer, with an expiry matched to the assignment. Same terminal, same record quality, same audit trail.

The cost is a card and five minutes. What it replaces is either a biometric enrolment that should not be happening, or — far more commonly — a paper sheet and a parallel record that nobody reconciles.

Why it does not happen

Because there is no owner. The agency coordinator is managing supply, security is managing access, the site manager is managing the work, and payroll only sees people it pays. The contractor's hours are the contractor's problem until there is a dispute about an invoice.

The result is that the one group whose presence is most often queried — because it is billed by the hour by a third party — has the weakest records on the site.

The invoice reconciliation nobody can do

This is where it bites. An agency invoices for hours. The site wants to check them. The site's own record for those people is a drawer of sheets or a set of temporary card numbers with no names against them.

So the invoice is approved on trust, every month, for a substantial sum. A site that issues named credentials to agency staff can reconcile the invoice against its own reads in twenty minutes, and the first time it does so is usually instructive.

Visitors and short assignments

A day visitor does not need a time record; they need a presence record, which the visitor book or a day pass already provides. The distinction is worth keeping, because trying to put everybody into the time system creates work for no purpose.

The line is whether anybody will be paid or invoiced for the person's hours. If yes, they need a credential on the time system. If no, the visitor process is sufficient and should not be elaborated.

Who should own it

The person who signs the contractor invoices, because they are the only one with an interest in the records being right.

That is a slightly unusual answer and it is the durable one. Giving the question to security produces an access arrangement with no hours in it; giving it to HR produces nothing, because these are not their people. Giving it to whoever is paying makes the control self-maintaining, which is the only kind that survives a reorganisation.

The record the agency keeps

The agency has its own record and it is usually a timesheet signed by a supervisor at the end of the week, from memory, on a Friday afternoon.

That is the document the invoice is built from, and it is weaker than anything the site's own system produces. Where a site issues credentials and can produce reads, the sensible next step is to agree with the agency that the site's record is the basis for invoicing. Most will accept, because it removes a dispute they also do not want, and the conversation has never been had.

The site that is somebody else's

The mirror image is worth a line: the organisation's own staff working on a client's or a partner's site, clocking on somebody else's reader under arrangements nobody here has seen.

Those hours come back as a report from another organisation and are accepted as given. If the hours matter — for pay, for working time limits, for billing — somebody should have asked what produces them. It is the same question this whole collection asks, pointed in the other direction, and it is almost never asked at all.