How to stop dispatching non-compliant workers to site
Nobody decides to send an uncertified worker to site. It happens because a ticket expired three weeks ago and nobody noticed, a new hire was dispatched before orientation, and the dispatcher was filling a 6am hole with whoever was free. By the time anyone checks, the worker is already on the deck.
If that risk lives on your shoulders — in construction, trades, or labour staffing — this guide is about making it structurally impossible, not just better-managed. The short version: stop treating compliance as something you record, and start treating it as something that blocks dispatch.
How workers slip onto site non-compliant
Every firm that's been burned by this had a tracking system. The problem is where the tracking sits relative to the decision:
- The certifications live in a spreadsheet. It's accurate the day someone updates it and wrong every day after. Expiry dates don't raise their hand.
- The ticket check is a human step. Dispatch happens fast, under pressure, early. A step that depends on someone remembering to look is a step that gets skipped on the busy mornings — exactly when mistakes are most likely.
- Orientation status isn't tied to scheduling. A worker can be in the system, assignable, and on a job before they've been oriented, because the two facts live in different places.
- Nothing physically stops it. The scheduler will happily put anyone on any job. It has no opinion about whether they should be there.
What it actually costs you
The cost isn't only the moment of exposure — though in jurisdictions with an active safety regulator (WorkSafeBC in BC, and provincial or state equivalents elsewhere), sending a worker to site without the required certification is a liability you carry directly. It compounds:
- Work stops. A worker pulled off site mid-shift is a hole in the crew and a call to the client you didn't want to make.
- The relationship takes the hit. General contractors remember which labour supplier sent someone who shouldn't have been there. It's the kind of thing that quietly costs you the next contract.
- You can't prove you were careful. When you're asked to show that a worker was compliant at the moment they were dispatched, "we usually check" is not an answer.
Why a warning isn't enough
The common half-fix is a warning: the system flags that a ticket is expired but still lets you proceed. On a calm day that works. On the day you're short three framers and the phone won't stop, a yellow banner is something you click past, not something that changes the outcome.
There's a real difference between software that records non-compliance and software that prevents it. Recording gives you something to explain after the fact. Preventing means the wrong outcome never happens — the worker simply isn't dispatchable until the problem is fixed. For a risk this consequential, prevention is the only version that actually protects you.
The fix: a dispatch board that can refuse
The structural fix is to put the compliance check inside the dispatch action, so it can say no. This is what a compliance-gated dispatch board does:
- Every assignment is checked against the worker's live compliance state. Certifications and orientation aren't a separate file — they're a condition of being dispatchable.
- An expired ticket or missing orientation blocks the assignment. Not a warning you can scroll past — the dispatch doesn't go through.
- Overrides exist, but they're recorded. When a supervisor genuinely needs to override, it's logged with who, when, and why — so the exception is a deliberate, accountable decision, not a silent gap.
- The gate is fed by one source. The same certification and orientation records your safety side maintains are what clear a worker for site. Update once; the gate reflects it everywhere.
How to set up a compliance gate
Whatever tool you use, the pattern is the same. Aim for this:
- Catalogue the certifications each role and site actually requires. Be specific — "working at height," "fall protection," site-specific orientations — not a generic "safety ticket."
- Record issue and expiry dates, and verify them. A signed verification on each ticket means "we thought it was current" stops being a defence.
- Turn on expiry alerts. You want to renew a ticket before it lapses, not discover it lapsed when a dispatch gets blocked.
- Tie orientation to dispatchability. Until a worker has completed (and signed off on) orientation, they can't be assigned.
- Make the gate hard, the override accountable. Block by default; allow a recorded override for the rare legitimate exception.
Frequently asked questions
Isn't a warning banner good enough?
What about legitimate exceptions?
Does a compliance gate replace our safety software?
How does the gate stay current?
Make the wrong dispatch impossible.
See a dispatch board that checks tickets and orientation before it lets anyone onto a job — on your own roster.