The Decisions log
Decisions is the final stage of the decision pipeline — the permanent ledger of what your team has committed. When a decision is raised out of Pending, it lands here as a timestamped entry that cannot be edited, only added to.
Open Decisions from the left rail, below Pending.
What each entry records
Every entry captures both sides of the call:
- What you committed — the final quantity, value, or change you decided on.
- What was recommended — the engine’s original figure, kept alongside yours.
Holding both means anyone can see where a human call differed from the recommendation, and by how much — the honest record of commercial judgement, not just the outcome.
Finding a decision
Decisions are shown as a timeline, grouped by period with a running count on each heading, newest first. Search by title, product, SKU, or supplier to narrow the list, open any entry for its full detail, or export the record. When nothing matches you’ll see “No decisions match”; a brand-new workspace shows “No decisions recorded yet” until the first decision is committed.
Why it matters
The Decisions log is the audit trail for commercial policy:
- Accountability — who committed what, and when.
- Learning — where recommendations were consistently adjusted, so the guardrails and the engine can be tuned.
- Continuity — a new team member can read the recent record to understand how the team decides.