Tickets and hours checked for the day the work runs, and border eligibility answered for the whole trip — at the dispatch desk, not at the roadside. The rules are yours, written in your words. The answers are named, and the ones that cannot be answered say why.
Nothing here is built in. A credential is whatever you call it; a rule is a sentence you write. The product compares the two.
Licence classes, endorsements, site tickets, medicals — by the name your safety file uses, with expiry and who verified the paper. A renewal is a new entry; the old one stays, because “what were they holding that day” is a question only history answers.
“Wellsite runs need an H2S ticket.” “Every haul needs a Class 1.” A rule is a row that says this kind of work, or work carrying this tag, needs that ticket. Change your policy by changing the row.
A ticket lapsing Thursday clears Wednesday’s run and blocks Friday’s. Eligibility is checked at the start of the work, not today, which is the only version that is right on both days.
Already lapsed first, because that is not a reminder any more. Then what falls due within sixty days, and whether anybody has verified it.
You can knowingly assign somebody whose paperwork is in flight. What was missing is frozen against that decision — not recomputed later, when the renewed ticket would make a real override look clean.
A qualification history outlives the employment by years, and the moment it matters most — an audit, an incident, a claim — is usually after the person has gone. The file stays; the roster does not offer them.
A driver who starts the day in one country and crosses into another comes under the local rules on arrival — and the hours already behind them do not disappear. A break long enough to restart one country’s cycle may be too short for the next one’s, so a driver who reset legally before crossing can arrive with the cycle still running. Rig judges each part of the journey under its own rules and says which part failed.
The rules themselves are not built into the product. They arrive as a cited, versioned package that a named qualified reviewer activates for your operation — Canadian, US, or a permitted exemption that applies only while the permit is on file. Until one is in force, every hours answer is unknown, and unknown never clears a driver.
Crossing binds the carrier, the driver, the unit, the cargo, the route and the hours as a single check — because they interact. A driver qualified today whose medical expires mid-trip is not qualified for this trip.
Operating authority, registration and program membership per jurisdiction, with dates. Not recorded is not the same as not held — it is an open question, not a refusal.
By jurisdiction, combination and cargo — deliberately, by somebody. Years of running one configuration say nothing about whether the next one may run there.
Whether a medical or a licence issued at home is accepted across the line is a reviewed finding, not a default. Neither assumption is made for you: not that a local one is required, and not that the foreign one is accepted.
Valid at departure is not valid for the trip. An authority or a ticket that lapses during the movement fails that movement, with the date, so somebody can renew it.
Where you run a certified hours system, it stays the authority and Rig checks against it. When the two disagree the stricter answer stands and the difference is surfaced — a disagreement about hours is usually a data problem, and finding it at the desk beats finding it at an inspection. There is no compliance score: a border check returns the conditions by name, because a single number cannot say which one failed.