simler
Docs · Actions

Running exercises

Actions

Findings shouldn't die in a report. The Actions page is your organization's improvement backlog: missed steps from debriefs and knowledge gaps from Ask land there automatically, get owned and fixed, and — where possible — are verified closed against your own data.

Where actions come from

  • Debrief findings — every missed step from an exercise debrief becomes an action, with its severity and the role that owned it.
  • Knowledge gaps— every question your connected sources couldn't answer in Ask becomes an action describing what was missing.

Actions belong to the whole organization: any member can pick one up, assign an owner, and work it. Nothing is ever deleted — archiving is the way out, so your remediation history stays intact.

Working the backlog

  1. 1

    Start

    Move an action to in progress and assign an owner so it's clear who's on it.
  2. 2

    Fix at the source

    Update the plan, inventory, or process the finding points at. 'Generate fix' drafts a paste-ready paragraph for your document — you review and apply it; simler never changes your documents or systems for you.
  3. 3

    Close — verified where possible

    For a knowledge gap, 'Verify & close' re-asks the original question against your connected sources. If they now answer it, the action closes as verified, citing the source. Anything can also be closed manually — the two are recorded differently.

Verified beats self-reported

A verified closure means the platform confirmed the fix against your own data — not that someone said it was done. That distinction is visible on every action and in your counts.

Prove it in the next exercise

Pin any open action with Test in next exercise and the next simulation you generate weaves it in as a retest focus — the exercise itself proves whether the fix holds. Run a quarterly rhythm and the loop compounds: exercise → findings → fixes → verified → retested.