Glossary · Dispatch
Compliance gate
Updated
A compliance gate stops a trip being farmed out to an affiliate whose paperwork has lapsed, and in practice the paperwork that lapses is the certificate of insurance, which renews every 12 months. An affiliate who was fine in March can be uninsured in April without anyone at your office being told.
The gate exists because the liability does not transfer with the trip. If an affiliate's car is in an accident with your customer in the back, your name is on the booking and your insurer will ask what you checked. Operators who take affiliate work seriously keep a file per affiliate: insurance, operating authority, vehicle list, and a date for each.
The failure mode is manual. A spreadsheet of expiry dates is correct on the day it is built and wrong 30 days later. The dispatcher assigning a farm-out at 6:00 AM is not opening a spreadsheet, and the common mistake is finding out the certificate expired when the claim arrives.
How liverybook handles it
Each affiliate carries an approval status (pending, under_review, approved, suspended, blocked) and an insurance expiry date, and from those liverybook computes a compliance status: blocked, expired, expiring_soon, pending or compliant. Expiry alerts go out at 60, 30 and 7 days using the compliance expiry email template. The gate applies when a dispatcher picks a subcontractor on the run board, so it sits in the assignment step rather than in a file nobody opens.
Related terms
This term lives in Dispatch. liverybook is the operating system for ground transportation.