Why the Gate Never Stops a Truck
A RED result at the gate doesn't hold anything back — the truck proceeds either way. What actually changes is who gets told, and whether that unit shows up on the list dispatch is supposed to check before the next trip.
The scan can't say no. There is no deny action to press.
This isn't a setting that gets turned off for a lenient fleet — it's how the code is written. The gate endpoint hardcodes that a truck proceeds, and its own docstring says so outright: log-only, trucks never stopped, the truck proceeds regardless of what the documents show.
The verdict computes on the spot
A scan rolls the tractor, every trailer involved, and the driver's licence into one result, collapsed into four outcomes — valid, expired, missing, invalid — simpler than the finer-grained status a dashboard shows, built for a guard to read in a glance.
Nothing reads a "deny" back
A scan event can carry a decision note, but it's stored as a record of what happened, not read back or enforced anywhere. The only server-side behavior a bad result actually triggers is what's below — never a block.
A bad result still does two things
The web gate screen fires a background WhatsApp to the supervisor group — plate, unit code, result, the specific issues, and an explicit "truck proceeded, log-only" line — and the unit's status feeds the next do-not-schedule export.
A list dispatch is meant to check, not a lock DocVigia enforces.
Every night, alongside the alert ladder's own run, DocVigia writes every RED unit — expired or missing a document entirely — to a plain JSON file: plate, unit code, distribution center and the specific issues, timestamped and counted.
What this export doesn't guarantee
DocVigia writes the file. Whether a fleet's dispatch process or TMS actually opens it before assigning the next trip is a step that happens on that fleet's own side — the export is meant to be consumed, but DocVigia doesn't reach into a dispatch system to block an assignment itself, the same way the gate itself doesn't block a truck. Both are information, placed where the person who needs it can act on it, not an automatic lock.
"Log-only" means exactly that, in both directions.
- A RED result never holds a driver at the gate. The response the guard's screen shows always lets the truck proceed — there's no code path where the API itself refuses a scan.
- The gate's four outcomes are coarser than the dashboard's. Valid, expired, missing, invalid — a status a manager sees as "expiring soon" on the dashboard doesn't have its own tier at the gate; it reads as valid until it's actually expired.
- The do-not-schedule file has to actually get read. It's an export dispatch is meant to check each run — nothing forces that check to happen, and DocVigia has no visibility into whether it does.
- A scan is designed to survive no signal, at the API level. Event timestamps use the device's own clock rather than the server's arrival time — specifically so a scan made in a yard with no signal still records the moment it actually happened once it syncs.
Questions about the gate.
If a unit is RED, can a guard refuse to let it through anyway?
Nothing in the product stops a person from making that call themselves — the system's own design is to log and proceed, then escalate to a supervisor by WhatsApp instead of building a barrier into the screen. Whether a fleet layers its own stricter policy on top is a decision outside DocVigia.
Does the guard's app need a signal to scan?
The backend contract is built for offline replay — a scan's timestamp is set by the device, not the server, specifically so a late-syncing event from a dead zone still records accurately. That's what the API guarantees; it describes what the server expects, not a claim about every possible client built against it.
Who actually acts on the do-not-schedule export?
DocVigia writes it every night with every RED unit's plate, code and specific issues. A fleet's own dispatch process or TMS is meant to check it before assigning a trip — that's the intended use, but it's a step that happens on the fleet's side, not something DocVigia verifies happened.