Playbooks/ Zuletzt aktualisiert: 2026-10-29

Playbook: who accepted that risk, and on what evidence?

The situation

Three weeks ago someone looked at a warning *projected cash-flow shortfall* and decided to do nothing. Now the shortfall has happened and the question is: was that a mistake, or a reasonable call on what was known then? Without a record, nobody can answer, and the same discussion repeats next month.

Otiox records every decision on every finding: what was decided, by whom, on what evidence, and later, what actually happened.

Before you start

  • A decision can be made on any finding from the Risk Inbox, the Prediction engine or the Integrity engine.
  • *Risk accepted* and *Deferred* are decisions too. They are recorded like actions.

Step 1 — Record the decision where it is made

Open a finding and choose what to do.

Record a decision: risk accepted, with what you know that the system does not
Record a decision: risk accepted, with what you know that the system does not

Your options:

  • Action taken: run the suggested fix (a draft PO, a transfer, a recorded VAT decision). The action, its preview and its result are attached to the decision.
  • Risk accepted: you know the risk and choose to carry it. Write *why*: the information the system does not have (a customer who always pays late but always pays, a shipment you know is on the way).
  • Deferred: decide later, with a date.
  • Declined: the finding is wrong or does not apply; say why, so the detector can learn.
What happens when you save: the finding takes the status that follows from the decision, and the decision goes to the log with your name and the time.

Step 2 — Read the decision log

Open Command → Decision Log.

Decision Log: when, which finding, the decision, who, and the outcome
Decision Log: when, which finding, the decision, who, and the outcome

What you see in the demo:

| When | Finding | Decision | Outcome |

|---|---|---|---|

| 30 Oct 07:20 | CBM overflow (Overflow Bay B-12) | Action taken: move stock out to locations with room | not known yet |

| 29 Oct 12:25 | Order #7b3eae92: no VAT and no reason | Action taken: record the VAT decision | not known yet |

| 17 Oct 17:13 | Projected cash-flow shortfall (critical) | Risk accepted | not known yet |

Filter by Action taken, Risk accepted, Deferred or Declined, or switch to Approvals & automation to see what the system decided under its own rules.

Step 3 — Close the loop with the outcome

When the predicted event happens, or does not, the Outcome column fills in. A risk accepted that then happened is not automatically a bad decision: the evidence recorded at the time tells you whether it was a reasonable call.

Why it matters

Decisions are where judgment lives. Recording them with their evidence turns *we always did it this way* into *this is what we decided, why, and how it turned out*.

What you have at the end

  • Every decision on every finding, with who, when and why.
  • The action and its result attached to the decision.
  • Outcomes that show which calls held up.
Screenshots come from the Otiox demo workspace. Choose Switch to demo in the sidebar to follow along; changes there never touch live data. Command reads your records and never changes them.