How strategy changes flow through Cogliva

A plain-language impact summary

When you save an edit, a confirmation explains, in plain terms, which parts of the workspace the change affects — for example the Intelligence Map, the organisation's context, or the AI strategy context that grounds future recommendations.

Three ways to apply a change

• Proceed — save and trigger all back-processes now, so every connected view (Intelligence Map, Organisation Context, Diagnostics, Strategic Signals, and AI Strategy Context) reflects the change immediately.
• Save without back-processes — save the edit to the asset but skip downstream processing for now; a site-wide banner keeps the pending change visible until you decide to apply it.
• Cancel — discard the change and keep everything as it was.

The waiting-changes reminder

If you choose Save only, a notification bar appears across your Cogliva pages letting you know a change is waiting to be processed. It stays until you apply the pending updates — which refresh the connected views and the AI strategy context — so a deferred change is never quietly forgotten.

The change-impact map

After a save, Cogliva shows a graphical map of how the edit rippled outward — a box for each domain (Strategy Assets, Intelligence Map, organisation context, Diagnostics, Strategic Signals, and AI strategy context) with a short note on whether it was updated, queued, or unchanged. It makes the effect of a single edit easy to see at a glance.