Managing contractors on site without losing oversight

Getting contractor vetting right — current insurance, accreditation, a proper register — solves one half of the oversight problem. The other half is what actually happens once a fully vetted, genuinely competent contractor is on site doing the work. That gap is easy to overlook precisely because the contractor is trustworthy; oversight tends to get treated as unnecessary for exactly the contractors it's easiest to relax around.

Sign-in and access, not just a name on a list

Knowing a contractor is booked and knowing a contractor is actually on site, at a specific time, in a specific area, are different things. A sign-in process that's genuinely followed — not just a book by the door nobody checks — gives a facilities team a real answer to "who was in the building, and where" if that question ever needs answering after the fact.

Linking the work done to the job it was meant to close

A contractor attending site to fix something should leave a record that ties directly back to the original work order — what they found, what they did, and confirmation the issue is actually resolved. A contractor visit that isn't linked back to a specific tracked job is, from a records point of view, indistinguishable from a visit that never happened, regardless of how well the work was actually done.

• –A genuine sign-in and sign-out process, tied to a specific job or reason for the visit
• –Site-specific induction covering access, hazards and any building-specific rules before independent access
• –Work carried out recorded against the originating job, not as a standalone note
• –A clear escalation route if a contractor identifies something beyond the original job's scope

The scope creep problem

A contractor on site for one job will sometimes, reasonably, notice something else that needs attention — and without a clear route for raising that as a separate job, it either gets fixed informally with no record, or gets ignored because raising it properly feels like more hassle than it's worth. Neither outcome is good: the first creates untracked work with no paper trail, the second leaves a genuine issue unaddressed.

Good contractor oversight is ultimately a continuity problem as much as a control one — the same discipline that keeps oversight intact while contractors come and go is closely related to what keeps a facilities role's institutional knowledge intact when staff themselves change.

Scope creep, one favour at a time

A contractor attends for a booked job, finishes early, and someone asks whether they would mind looking at something else while they are here. Helpful, efficient, and entirely undocumented — the second piece of work has no job number, no risk assessment covering it, no record that it happened, and no evidence if it later turns out to matter.

The problem is not the favour but the absence of a trace. An estate where this happens routinely has an unknown quantity of work done on its buildings that appears in no record, which surfaces later as an asset in an unexplained condition or a job everyone assumes somebody else must have booked.

Common mistakes

• –Allowing work outside the booked job with no job raised for it
• –Sign-in recorded without tying the visit to the specific work order
• –No check that a contractor's documents are current on the day they attend
• –Permit requirements applied inconsistently depending on who is supervising
• –No record of what was actually done, only that somebody attended
• –Letting site staff authorise additional work with no route back to the register