# Assign actions to observed risk triggers

Illustrative planning brief; no automatic product import.

Synthetic planning case: An external publishing plan has three observable conditions: missing artwork at day 4, unapproved copy at day 5, and a changed audience after approval. Its risk notes currently just say high, medium and low.

## Decision

Use an observable condition and an owned response for each scenario. A risk label alone does not tell the coordinator whether to act or which evidence closes the response.

## Owned work

- Define verifiable conditions
  - Owner role: Risk owner
  - Acceptance evidence: Dates and approval identities refer to the accepted external brief.
- Assign the response authority
  - Owner role: Coordinator
  - Acceptance evidence: The named owner can request or make the row’s bounded decision.
- Record the checkpoint outcome
  - Owner role: Receiving lead
  - Acceptance evidence: Observed condition, action and subsequent accepted evidence remain linked.

## Workflow

1. Define verifiable conditions. Check: Dates and approval identities refer to the accepted external brief.
2. Assign the response authority. Check: The named owner can request or make the row’s bounded decision.
3. Record the checkpoint outcome. Check: Observed condition, action and subsequent accepted evidence remain linked.

## Judgment

These are invented local checkpoints. The table is neither a risk probability model nor a native TeamBoostAI automation.


## Filled manual planning note

Use an observable condition and an owned response for each scenario. A risk label alone does not tell the coordinator whether to act or which evidence closes the response. Each row maps a distinct observation to a different response. Checkpoint timing and the governing approval state are explicit; the response is not selected from a severity adjective. These are invented local checkpoints. The table is neither a risk probability model nor a native TeamBoostAI automation.


## Working artifact

- Artwork delay / Missing accepted artwork at day 4 / Artwork owner supplies recovery choice
- Approval delay / Copy unapproved at day 5 / Receiving owner decides publishing hold
- Audience change / Current audience differs from brief / Brief owner reopens affected review


## Workflow questions

### Must every triggered scenario stop all work?

No. Each response has a scope; the artwork row asks for a recovery choice while the copy row holds publishing.

### Can a trigger be revised?

Yes through an explicit plan change with its reason and affected checks retained.

## Product connection

Use the owned checks and downloaded brief to discuss this planning decision alongside your TeamBoostAI tasks. Confirm available fields, roles and account features separately. The example is manual; it does not calculate live analytics, create work or run an experiment in the product.

Confirm account availability before adopting this manual outline.

## Original worked case

Synthetic records, manual planning only. No account import or live analytics.

### Inspect the invented case records

Scenario | Observable trigger | Bounded response
--- | --- | ---
Artwork absent | No accepted artwork at day 4 checkpoint | Ask artwork owner for recovery choice
Copy pending | No receiving approval at day 5 checkpoint | Hold publishing and request approval decision
Audience changed | Approved brief no longer names current audience | Reopen affected brief review

### Reasoning

Each row maps a distinct observation to a different response. Checkpoint timing and the governing approval state are explicit; the response is not selected from a severity adjective.

### Bounded result

Use an observable condition and an owned response for each scenario. A risk label alone does not tell the coordinator whether to act or which evidence closes the response.

### Distinct decision

The artifact converts three different risk observations into inspectable condition-specific responses.

### Limits

These are invented local checkpoints. The table is neither a risk probability model nor a native TeamBoostAI automation.

### Definitions and method context

- Original worked-case definitions — Definitions, policy choices, records and calculations are authored for this worksheet. No external standard, statistical validation or live product measurement is claimed.