Compliance dispatch gating
No ticket, no truck. Switch on the gate and the job is blocked before the crew rolls, not written up after.
This is the piece most invoicing-first trade apps leave out. Switch on the compliance gate and, before a worker is dispatched, their tickets are checked against what the site demands - a lapsed licence or an unmet requirement blocks the dispatch. Compliance is enforced, not hoped for.
The check that stops the job
- Before dispatch, a worker's tickets are checked against what the site requires.
- A lapsed licence or an unmet requirement blocks the dispatch - it's not a sticky note on the fridge.
- With the gate on, the check runs on every dispatch - not a reminder you can click past on a busy day.
Built from your own data
- Site requirements come from your qualification list; worker tickets come from their records.
- A trade-specific hazard library with default controls keeps the safety side consistent.
Common questions
- What does "no ticket, no truck" actually mean?
- If a worker doesn't hold a qualification a site requires, or their ticket has lapsed, the system won't let them be dispatched to that job until it's resolved.
- Can the check be turned off for one job?
- When the compliance gate is switched on, it runs on every dispatch - it isn't a per-job reminder you tick past. You choose whether to turn the hard block on; with it off, you still get the warnings.
- Is the compliance gate on by default?
- No. You choose whether to switch the hard block on. With it on, the check runs on every dispatch; with it off, you still get the warnings but can proceed. It's your call how strict to be.
- Where do the requirements come from?
- From your own data - the qualifications you've marked a site as requiring, checked against the tickets held on each worker's record. Nothing is hard-coded; the gate enforces the rules you set.