Lesson 11 of 12 · 6-minute lesson

Manage decisions and follow-up

Manage conditions until evidence is reviewed and respond when circumstances change.

For: Accountable executives, action owners and reviewers

The situation

A limited test is proposed, but the decision is not yet approved and several conditions remain open.

The problem

A decision report creates false confidence if its conditions disappear into meeting notes or email.

The choice

Maya assigns each action, states the required evidence and sets the next review trigger.

What you will learn

By the end of this lesson

  • Keep the decision clearly limited.
  • Submit and review evidence needed to close actions.
  • Respond to time, concerns and significant changes.

The pivotal moments

What changes—and why it matters

Moment 1

Keep the proposal clearly limited

What the person does

Maya records the proposed limited test separately from live use.

What the workspace records

The proposal keeps the reasons, uncertainty and conditions.

Notice

An unapproved proposal cannot be treated as permission to test.

Why it matters

Everyone can see what is proposed and what remains unapproved.

Decision detail preserving the limited-test boundary
Reasons, conditions and approval state keep the proposal clearly limited.

Moment 2

State the evidence needed

What the person does

Each owner sees the action and what a reviewer must see.

What the workspace records

The action links to its condition and required evidence.

Notice

Marking a task done does not prove that a control works.

Why it matters

Owners know what is needed before an action can close.

Owned action with evidence required before it can close
Every condition has an owner and evidence requirement.

Moment 3

Respond to significant change

What the person does

Maya schedules a review and records other triggers.

What the workspace records

An incident, new purpose, different supplier or new type of data can reopen the review.

Notice

A file alone cannot close a condition.

Why it matters

Governance stays active as the proposal moves through approval and testing.

Scheduled review with significant change triggers
Time, concerns and significant changes can trigger review.

Official guidance used in this lesson

Check the published guidance

The complication

The difficult part stays visible

Completing an action and demonstrating that its control works are different claims.

The outcome

The proposed decision, conditions, actions, evidence and review stay connected to the use case while approval remains outstanding.

Check your understanding

When can a condition close?

Show the answer

After the required evidence is submitted and an authorised reviewer accepts it—not when a task is merely marked complete.

Key points

Remember these three things

  • Keep the decision clearly limited.
  • Require reviewed evidence before an action closes.
  • Revisit the AI use case when circumstances change.

What happens next

See how roles and access preserve accountability across shared work.