Contractor compliance

Contractor insurance verification at the gate.

Insurance checks at contract signing are table stakes. Nine months later the policy has lapsed, the contractor keeps working, an incident occurs, and the coverage the facility thought was in place turns out not to be. The fix is to check every time entry happens, not just once at onboarding.

The onboarding-only problem

Contract signing is a moment. Compliance is a state that changes over time. Say a contractor firm signs a services agreement in January with general liability cover of $5 million. In September the policy renews at $2 million because premiums rose. Nobody at the facility knows. In November a scaffold collapse causes property damage that exceeds the actual cover. The facility now has an uninsured exposure of $3 million that everyone assumed did not exist.

This pattern happens across insurance categories:

  • General liability (public liability in the UK) renewal reduces cover.
  • Workers' compensation or employer's liability lapses because a contractor firm downsizes to a sole trader.
  • Professional indemnity not renewed after a claim.
  • Trade certifications expire without renewal (licenses, aerial lift or scaffold training, and in the UK cards such as CSCS or ECS).

The three obligations to check

What a facility should check at every contractor entry:

  1. Insurance in force. Policy number, coverage limits, expiry date, insurer.
  2. Site induction current. Contractor has completed the site's induction within the required window (typically 6 or 12 months).
  3. Trade certifications current. Any trade-specific certificates required for the work being done (e.g. aerial lift, forklift, welding). A permit for the job itself is a separate control, covered in permits for outside contractors.

Any one of the three being expired or missing should stop entry until resolved.

How to enforce without slowing the queue

The concern with gate-level enforcement is queue length. Two design choices avoid that:

  • Advance notice. Remind the contractor firm well before a policy or certificate expires (30 days is a common lead time), and escalate to the individual and to your own site manager as the date gets close. Expiry should never come as a surprise to anyone.
  • Self-service renewal. Let the contractor send the renewal document themselves, from their phone, before they travel to site, so the record is current before they reach the gate rather than fixed at the window while a queue builds.

What the insurer wants to see when a claim happens

If an incident does occur and the insurer challenges cover, the audit-trail evidence that matters:

  • Timestamped log of every entry by the contractor, with the specific insurance policy referenced at each check-in.
  • Copy of the policy document that was on file at the time of each entry.
  • Any overrides recorded (facility manager approved entry despite expired document, with a written reason).
  • The site's contractor policy document showing what the facility requires as minimum cover.

A facility that can produce all of the above is in a far stronger position than one whose answer is "we sign contractors in on paper".

What BeckonDesk does at the gate

  • Company insurance. Each contractor company can carry an insurance expiry date. Once it has passed, every contractor registered under that company is refused at the kiosk and sent to reception. The company's contact is emailed 30 days before the date.
  • Certificates. Contractors upload certificates (PDF or image, with an expiry date) through their contractor portal on their phone. A renewal replaces the older copy of the same certificate. An expired certificate stops entry, and the contractor is emailed 30 days before it expires.
  • Inductions. An induction the contractor has failed, not finished or let lapse also stops entry. Contractors complete inductions in the portal, not at the kiosk.
  • The record. Each contractor sign-in and sign-out is timestamped, the uploaded certificate files stay on the contractor's record, and the contractor compliance report exports as CSV.

Some of the practices above are yours to run rather than BeckonDesk's. It sends one reminder 30 days out, not a 7-day or 1-day sequence. It does not read expiry dates from documents. It has no rules for which certificate types a job needs, so a contractor with no certificate on file is not stopped for that. It does not record which policy was checked at each entry, and there is no override that lets a non-compliant contractor through with a reason: the record has to be fixed.

Related reading

Set up a real contractor firm in your trial.

Add a company with an insurance expiry date, register a contractor and give them their pass, then see the kiosk refuse them once the date has passed.

Start free trial Book a walkthrough