Requirement Templates

Compliance → Requirement Templates is the engine behind every compliance check in FleetOps. A template says: when a trip looks like this, these documents and conditions are required. At dispatch, every template that matches the trip contributes its items to one merged checklist — blocking items must be satisfied before the trip may go.

Creating a template

  1. In New template, give it a Name (e.g. Beitbridge cross-border pack) and an optional description.
  2. Under Applies when…, set the matchers. Blank means any:
    • Hazardous / Abnormal / Cross-border — Any, Yes, or No.
    • DG class — restrict to a dangerous-goods class (e.g. 3).
    • Corridor — restrict to a corridor (e.g. beitbridge).
  3. Add Requirement items with + Add item. Each item has:
    • Subject — Vehicle, Driver, Trip, or Load: what the requirement attaches to.
    • Kind — Document (something that must be on file) or Condition (something that must be true).
    • Code and Description — the identifier and the human wording.
    • Severity — Blocking stops dispatch; Warning is advisory.
  4. Press Create template.

Rows without a code are ignored on save; every kept item needs a description.

Templates are append-and-browse. There is no edit or delete — author a corrected template instead. The Active only toggle on the catalogue hides retired templates.

Previewing with Resolve a context

Resolve a context answers "what would the dispatch gate demand for a trip like this?" — tick the flags, optionally set a DG class and corridor, and press Resolve. You get the merged checklist with blocking/warning counts and, per item, which template contributed it. Use it to test a new template before relying on it.

Dangerous-goods capture happens on Dangerous Goods; abnormal loads on Abnormal Loads; cross-border permits on Cross-Border Permits.