Platform
Integrations
All use cases
IndustriesPricingProductField Notes
Sign inGet started
Otiox Command · Decisions & Interventions

In Otiox, a decision is part of the model — not lost in a conversation.

Get startedView platform
Most systems record what happened, never what was decided or why. In the Otiox ontology a decision is a thing in its own right: bound to the risk that prompted it, the evidence behind it, and the outcome that followed. Judgement becomes something an organisation can keep, examine and learn from.
app.otiox.comFig. 00
Interventions
What was done about a risk, and what happened next, compared with the same kind of finding when nothing was done.
+ Log intervention
By actionModerate
Release the reservation
2 times · 2 likely helped
Likely helped in 100 % of decided cases
Post the completion
2 times · 2 likely helped
Likely helped in 100 % of decided cases
Reconcile lots with stock
1 time · 1 likely helped
Likely helped in 100 % of decided cases
Move PO arrival date
1 time · 1 likely helped
Likely helped in 100 % of decided cases
Swap the lot
1 time · 1 likely helped
Likely helped in 100 % of decided cases
Escalate PO approval
1 time · 1 likely helped
Likely helped in 100 % of decided cases
"Likely helped" means the risk did not happen after the action; it does not prove the action caused it.
01

Judgement, kept and examined.

Decisions, actions and their outcomes, bound to the risks and records they concerned — whether made by a person or by an automation.
Decision Log
Who decided, on what evidence, and what happened next. People and automations alike.
WhenDecisionOutcome
24 Oct
Expedite PO-PRED-0001 by air
M. Novak
Averted
22 Oct
Build 40 × KIT-220 from stock
Auto-assembly
Done
19 Oct
Hold LOT-2026-097 for re-test
J. Ilić
Open
15 Oct
Accept late date on SO-PRED-0002
M. Novak
Came true
01

Decision Log

When, who, what was decided and on what basis — the risk, the scenario, the investigation. Every entry links back to the records it touched.

'Why did we do that?' — answered in seconds

Interventions
What was done about a risk, and what happened next, compared with the same kind of finding when nothing was done.
+ Log intervention
By actionModerate
Release the reservation
2 times · 2 likely helped
Likely helped in 100 % of decided cases
Post the completion
2 times · 2 likely helped
Likely helped in 100 % of decided cases
Reconcile lots with stock
1 time · 1 likely helped
Likely helped in 100 % of decided cases
Move PO arrival date
1 time · 1 likely helped
Likely helped in 100 % of decided cases
Swap the lot
1 time · 1 likely helped
Likely helped in 100 % of decided cases
Escalate PO approval
1 time · 1 likely helped
Likely helped in 100 % of decided cases
"Likely helped" means the risk did not happen after the action; it does not prove the action caused it.
02

Interventions by action

Release the reservation, post the completion, move a delivery date, swap the lot, escalate the approval. Each action shows how often it was taken and how often the risk then did not occur.

Remedies judged by their results

Interventions
What was done about a risk, and what happened next, compared with the same kind of finding when nothing was done.
+ Log intervention
By actionModerate
Release the reservation
2 times · 2 likely helped
Likely helped in 100 % of decided cases
Post the completion
2 times · 2 likely helped
Likely helped in 100 % of decided cases
Reconcile lots with stock
1 time · 1 likely helped
Likely helped in 100 % of decided cases
Move PO arrival date
1 time · 1 likely helped
Likely helped in 100 % of decided cases
Swap the lot
1 time · 1 likely helped
Likely helped in 100 % of decided cases
Escalate PO approval
1 time · 1 likely helped
Likely helped in 100 % of decided cases
"Likely helped" means the risk did not happen after the action; it does not prove the action caused it.
03

Measured against inaction

Outcomes after an intervention are compared with the same kind of finding when nothing was done, so that 'likely helped' carries meaning.

Real effect, separated from coincidence

Decision Log
Who decided, on what evidence, and what happened next. People and automations alike.
WhenDecisionOutcome
24 Oct
Expedite PO-PRED-0001 by air
M. Novak
Averted
22 Oct
Build 40 × KIT-220 from stock
Auto-assembly
Done
19 Oct
Hold LOT-2026-097 for re-test
J. Ilić
Open
15 Oct
Accept late date on SO-PRED-0002
M. Novak
Came true
04

Auto-assembly decisions

When Otiox builds kits or sub-assemblies automatically, each build is recorded with the rule and the stock that triggered it — open to review like any human judgement.

Automation that can be audited

Risk Inbox
What is likely to go wrong next, why the engine thinks so, and what you can do about it.
Run engine
Open · 14Acted on · 6Came true · 3Averted · 5
RecordRiskLikely
MO-PRED-0001Late production82 %
SO-PRED-0004Promise at risk71 %
LOT-2026-118Lot expiring64 %
INV-2026-0213Payment late58 %
RM-STEEL-04Stockout47 %
05

Recorded without effort

Actions taken from the Risk Inbox are logged automatically. Steps taken outside Otiox can be recorded by hand, with the same detail.

A complete record, without administration

Command · decision log
Risk accepted, with the reason
Projected cash-flow shortfall
WhenDecisionWho
TodayRisk acceptedFinance
Last weekDeferredPurchasing
Last monthAction takenPlanning
Evidence frozen as it was
Record

Decide on the finding — reason required.

Reviewed later against what was known then.

06

Candid about causality

'Likely helped' means the risk did not occur after the action — not that the action caused it. Otiox shows the comparison and leaves the judgement to you.

Evidence, presented honestly

02

What was done — and what followed.

Interventions gather every action taken against a risk, whether run from a finding or recorded by hand, and show what happened next. Over time, the page becomes your organisation's own account of what works.
  1. 01
    Grouped by action, with times taken and likely-helped counts
  2. 02
    Share of decided cases in which the risk did not occur
  3. 03
    'Too early to tell' until the outcome is known
  4. 04
    180 days of history, one click away
app.otiox.com
Command · decision log
Risk accepted, with the reason
Projected cash-flow shortfall
WhenDecisionWho
TodayRisk acceptedFinance
Last weekDeferredPurchasing
Last monthAction takenPlanning
Evidence frozen as it was
Record

Decide on the finding — reason required.

Reviewed later against what was known then.

03

The decision loop

Closed automatically, every time.
  1. 01

    Risk raised

    A prediction or finding calls for judgement

  2. 02

    Decide

    Take a suggested action, rehearse a scenario, or decide by hand

  3. 03

    Record

    Decision, author and evidence written to the log

  4. 04

    Observe

    The risk is followed to its outcome

  5. 05

    Learn

    The action's record of results updates

04

A ledger of judgement.

The Decision Log reads as a clear account of how the business was steered: when, by whom, on what basis, and with what result. People and automations appear side by side.
  1. 01
    Filtered by person, automation, area or outcome
  2. 02
    Each entry linked to its risk, scenario or investigation
  3. 03
    Outcomes: averted, realised, done or still open
  4. 04
    Exportable for reviews, audits and board reporting
app.otiox.com
Decision Log
Who decided, on what evidence, and what happened next. People and automations alike.
WhenDecisionOutcome
24 Oct
Expedite PO-PRED-0001 by air
M. Novak
Averted
22 Oct
Build 40 × KIT-220 from stock
Auto-assembly
Done
19 Oct
Hold LOT-2026-097 for re-test
J. Ilić
Open
15 Oct
Accept late date on SO-PRED-0002
M. Novak
Came true
05

The idea, applied.

Scenarios from the demo workspace, walked through step by step — on the same data you receive when you sign up.
01

Decisions with evidence

Who decided, on what evidence, and what followed.
02

Approval bottleneck

The PO waits for a signature. The supplier's clock has not started.
03

Expiring reserved lot

The lot reserved for a build expires before it begins.
06

One ontology, seven ways of seeing it.

Every Command view reads the same things, the same relationships and the same history. An answer found in one becomes evidence in all the others.
01

Predictive Engine

Risks, forecasts and what-if scenarios, explained
02

Accuracy & Calibration

Every prediction frozen and judged against what happened
03

Investigations & Causal Map

Why things happened, with evidence for and against
04

Explorer & Dependency Map

Everything a record is related to, and what is at risk
05

Time Machine

Any record or stock exactly as it was on a date
06

Rules & Controls

Company rules monitored, with attested control runs
07

Questions

01Must every decision be logged by hand?
No. Actions taken from the Risk Inbox or a finding are recorded automatically. Manual entries exist for steps taken outside Otiox, such as a call to a supplier.
02What does 'likely helped' mean?
The risk did not occur after the action. Otiox compares this with how often the same kind of finding occurred when nothing was done, and is explicit that it is not proof of cause.
03What are auto-assembly decisions?
When Otiox builds kits or sub-assemblies from stock automatically, each build is recorded as a decision, with the rule and stock levels that triggered it, so it can be reviewed like any other.
04Can a decision be changed later?
An entry is kept as written. Subsequent decisions are added as new entries, so the history remains intact.
Otiox

Let every decision teach the next.

Open the demo workspace and read the Decision Log — each judgement, its evidence, and what came of it.

Get startedLearn more