Compliance overrides

Compliance → Overrides (/operations/compliance/policy) lets you relax a check without waiting for a software change, for example during a trial or for a fleet the check does not fit. It is the one screen that can turn a safety block into a warning, so it keeps a full paper trail.

What an override can do

An override can only weaken a check, never strengthen it:

• Lower what skipping or failing costs: block → warn → record.
• Make one question not required, for example a fire-extinguisher question on rigids that do not carry one.

To make a check stricter, edit it on Checks and publish a new version.

Rules Onyx enforces

• Every override states a reason.
• Every override expires (expires_on, as YYYY-MM-DD). There is no “forever”. An expired override simply stops applying.
• The whole document is accepted or refused. Nothing is applied in part.

Put a document in force

1. In Why is this being put in force?, say why you are doing this, for example Night shift trial agreed with the depot manager.

2. Paste the JSON document into Document. Insert an example fills in a working sample:

   {
     "policy_version": 1,
     "overrides": [{
       "template": "DRIVER-FFD",
       "enforcement": "warn",
       "reason": "Night shift trial agreed with the depot manager",
       "expires_on": "2027-03-01"
     }]
   }

   template is the check’s code. Add "question": "<code>" with "required": false to relax a single question.

3. Click Put in force. If the document is refused, the message says why and At: names the part that is wrong.

If you name a check code that does not exist, the document still goes in force, with a warning listing the unknown codes. Check your spelling.

In force, history and withdrawing

In force shows the active version, its overrides and when each expires. Withdraw takes the document out of force, and every check runs as its own version defines it again.

History lists every document uploaded, with who uploaded it and when. A document that has been in force is replaced by a new upload, never edited.

Each submission an override affected records the policy version that allowed it, so you can always see why a run started after a failed check.