A LOOK INSIDE OCULON

Review the impact before you approve the change.

A forecast revision, scenario merge or agent action shouldn’t arrive for sign-off without an explanation. Review what moved, who requested it and what happens if you approve.

A good approval is informed judgment, captured where the work happens.

AApprovals/Waiting for youEdited just nowShare
SearchFilterView
ChangeFromImpactDueStatus
Win rate 22% → 19%MayaQ4 −$180KFriReview
EMEA recovery planOculon agentEMEA +$0.7M ARRMonReview
Promote Upside · 2 of 3CFOARR +$1.4MTueDiscussing
Hosting mapping CC 410 → 420DevMargin view onlyWedApproved
Q1 hiring sequenceSamRunway +3 moThuApproved

Every proposed change arrives with its impact, and nothing reaches the plan until it is approved.

HOW IT WORKS

Reviewing and approving
changes.

A review should begin with the proposed change and end with a decision everyone can trace.

01 / See the change

See the impact
Before you approve

When a hiring assumption moves from April to June, compare the old and proposed values alongside the effect on payroll, operating expenses and runway.

  • Old and proposed values side by side
  • Impact on payroll, opex and runway
  • Approve, reject or ask for changes
02 / Keep judgment human

Agents propose
People approve

Let an agent prepare a scenario or recommend a model edit. Review the proposed changes before they become part of the shared plan.

  • Agent edits arrive as proposals
  • Material changes wait for a reviewer
  • Discussion beside the proposal
03 / Keep the process connected

The decision stays
Attached to the plan

Record the reviewer, decision and reason next to the change itself, so the next forecast cycle doesn’t depend on someone remembering an approval thread.

  • Reviewer, decision and reason recorded
  • Approval linked to the change it covers
  • History kept in the audit trail
IN PRACTICE

Built for the work
that matters.

SStrategic Finance/FY26 Forecast · ProposalMEdited just nowShare
SearchCompareView
VariableTrendFormulaCurrentProposedImpact
Proposed change
%Enterprise win rate% Win rate22%19%−3 pts
Impact
$Q4 revenue$ Model$5.80M$5.62M−$180K
$FY26 ARR$ Model$28.9M$28.3M−$0.6M
#Runway (months)$ Cash÷$ Burn2625−1
Review trail
#Requested by—MayaRevenue
#Evidence—60-day trendSalesforce
#Due—FriBefore forecast v14
A forecast assumption · Review the change and its impact before the plan moves forward.Illustrative example · sample data

FAQs

What are Approvals for?

Approvals keep review and sign-off within the planning workflow so the team can make decisions with the relevant assumptions and context in view.

How do Approvals work with AI Governance?

AI Governance defines the boundaries for agent work. Approvals provide human review around proposed material decisions.

How are Approvals different from Audit Trail?

Approvals help the team review and decide on proposed work. Audit Trail records activity and changes so their history can be investigated.

Your next chapter.
In full context.

Oculon in dark mode: a financial overview board and an Agent reviewing revenue performance in the same workspace.
Request Demo

Page preview · This destination is not built in the local prototype yet.