From an edited forecast assumption to an approved agent action, inspect the record of what happened without piecing together old files and messages.
Trust comes from the record: who changed what, when, and why it was approved.
A complete record of who changed what, connected to the decision it belonged to.
The record should help you reconstruct a decision, not just tell you that a field was edited.
See which person or agent changed a forecast assumption, which model it belonged to and when the edit took effect.
Oculon proposed churn splitRevenue model · sandboxApr 3 · 10:05Open an edit to see the previous value, the new value and the exact dimension and period it affected.
Review what an agent read, suggested or changed alongside actions taken by the finance team.
Oculon proposed churn 1.1% → 1.3%Read 3 models · sandbox10:05AgentFollow a scenario merge back to its proposal and approval, so the shared forecast has an understandable history.
Filter by model, actor or period to narrow a long change history to the handful of edits that matter.
Export the relevant activity when finance, leadership or auditors need a record of how a planning decision evolved.
Move from an audit event to the corresponding version or model state, rather than trying to recreate that view by hand.
Agents never change the plan on their own: every material change shows its approver.
Who acted, what changed, when, and where.
Yes. Version comparison can show changed values, formulas, assumptions, and the person who made the change.
AI actions are designed to move through the same governed workflow and audit history as other changes.
Yes. Search and filter the history by actor, object, change or date, and export it when a review needs to happen outside Oculon.
Yes. Oculon supports returning to a prior model state.
