📸 Screenshot to insert [/en/cortex/actions]: Actions page in Week view, with actions spread across the days by area and the 'Analyze impact of actions' button at the top.
How it works, in one sentence
A human action is recorded (by you or coming from a meeting) → you click Analyze impact → the AI investigates the data around the action’s date, compares the KPI before/after and assigns a verdict with a justification → this feeds the Learnings.The calendar
Just like a calendar, with Week, Month, Quarter and Year views and navigation via arrows + Today. Actions appear colored by area, grouped by day. A per-area summary shows how many actions are positive, negative, neutral, and so on.Where actions come from
Created by you
Click New action: describe what was done, the date, the area and (optionally) the objective/KPI it’s meant to move.
Coming from meetings
Actions decided in a meeting (Meetings) land here automatically after your approval, on the meeting’s day.
Analyze impact — the part that makes the difference
This is the heart of the screen. There are two ways to trigger it:1
A specific action
Click an action to open the details panel and use Analyze impact of this action.
2
In bulk (the whole period)
The Analyze impact of actions button opens a confirmation and assesses all the actions in the selected period/areas at once.
Asynchronous and in real time
The analysis doesn’t freeze the screen. As soon as you trigger it, the action shows an “Analyzing…” state and the AI works in the background — investigating the data, comparing the KPI before and after the action’s date. The result appears on its own, in seconds, without you having to reload. When it’s ready, the card shows the verdict and, on opening it, the justification with numbers.Actions coming from meetings (or at company level, with no owning agent) are analyzed by the native Cortex — the company’s management agent. You don’t need to configure anything: clicking “Analyze impact” just works.
The verdicts
Positive / Negative / Neutral
Positive / Negative / Neutral
There’s evidence that the action improved (positive), worsened (negative) or didn’t change (neutral) the KPI. These three generate a Learning.
Too early
Too early
“too_early”: the KPI is measurable, but not enough time has passed yet (or there’s no post-action measurement) to assess it. E.g. a renegotiation made today doesn’t yet show in CAC.
Cannot assess
Cannot assess
“cannot_assess”: there’s no measurable KPI or available data to judge it. A sign that a data source still needs connecting or a KPI needs tying to the action.
