# Keep severity and frequency distinct in review

Illustrative planning brief; no automatic product import.

Synthetic planning case: A five-case rehearsal records four minor copy issues and one loss of a required output. A report says most issues were minor and therefore the consequence picture is minor.

## Decision

Report occurrence counts and consequence categories separately: four minor issues and one required-output loss. The majority category cannot describe the consequence of the fifth case.

## Owned work

- Keep the case-level consequences
  - Owner role: Recorder
  - Acceptance evidence: Case E stays visible alongside the four minor corrections.
- Use meaningful units
  - Owner role: Risk reviewer
  - Acceptance evidence: No arithmetic is performed on arbitrary minor/major category codes.
- Choose the consequence-specific response
  - Owner role: Receiving owner
  - Acceptance evidence: The required-output case gets its own recovery decision under the actual brief.

## Workflow

1. Keep the case-level consequences. Check: Case E stays visible alongside the four minor corrections.
2. Use meaningful units. Check: No arithmetic is performed on arbitrary minor/major category codes.
3. Choose the consequence-specific response. Check: The required-output case gets its own recovery decision under the actual brief.

## Judgment

Consequence categories are supplied local descriptions, not a universal severity scale or assurance standard.


## Filled manual planning note

Report occurrence counts and consequence categories separately: four minor issues and one required-output loss. The majority category cannot describe the consequence of the fifth case. Minor issues occur in 4/5 of this log; required-output loss occurs in 1/5. These are descriptive case counts. A category name is not a numerical loss unit, so averaging category codes would not supply an expected loss. Consequence categories are supplied local descriptions, not a universal severity scale or assurance standard.


## Working artifact

- Minor correction count / Four logged cases / Descriptive frequency only
- Required-output loss / One separate case / Retain its different consequence
- Category coding / Names, not common loss units / Do not average invented numerical codes


## Workflow questions

### Does one serious case predict future frequency?

No. These five invented observations do not estimate a population rate.

### Can consequences ever be quantified?

Yes with justified comparable units and assumptions; arbitrary category numbers are insufficient.

## 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

Rehearsal case | Observed issue | Consequence category
--- | --- | ---
A | Copy typo | Minor correction
B | Copy typo | Minor correction
C | Copy typo | Minor correction
D | Copy typo | Minor correction
E | Required output absent | Required outcome lost

### Reasoning

Minor issues occur in 4/5 of this log; required-output loss occurs in 1/5. These are descriptive case counts. A category name is not a numerical loss unit, so averaging category codes would not supply an expected loss.

### Bounded result

Report occurrence counts and consequence categories separately: four minor issues and one required-output loss. The majority category cannot describe the consequence of the fifth case.

### Distinct decision

This separates empirical occurrence counts from nonnumeric consequence labels rather than calculating an acceptance preference average.

### Limits

Consequence categories are supplied local descriptions, not a universal severity scale or assurance standard.

### 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.