The person closest to the change hears about it first.
Name an owner for what each signal is about. When an assumption goes off plan, Peaky tells them in Slack or by email with the impact in euros, and the plan only changes once the update is approved.

KEY FEATURES
Every change has an owner.
The right owner, notified
Owners stay responsible every time a signal returns, and hear about it in Slack or by email with the impact in euros.
Per signal or as a digest
Each owner chooses: a message per signal, or a daily or weekly digest, by email or in Slack.
Approve, snooze or archive
Approve the update to keep the plan current, snooze what can wait, and archive what’s handled.
Test it first
Not sure yet? Test the change in a scenario before it touches the plan.
Every change on record
Version history keeps every save with who made it and when, and any version can be restored.
The assistant asks first
The Peaky assistant only changes something after you approve its plan, and its changes show in version history.
HOW IT WORKS
From an off-plan assumption to an approved plan.
01 ASSIGN
Name the owners
Set owners on what a signal is about, once. They stay responsible every time it returns, and each driver shows who owns it.
02 NOTIFY
The owner hears first
When an assumption goes off plan, Peaky tells its owners per signal or in a digest, by email or in Slack, with the impact in euros.
03 APPROVE
Approve it, and it’s on record
Approve the update, or test it in a scenario first. Every change shows who made it and when, so nothing changes silently.