# Internal announcement control worksheet

Use one copy per announcement type, audience snapshot, language set, and candidate version. This is an editable control record, not a policy, contract, legal notice, employment decision, incident record, emergency alarm, or release authorization.

## 1. Release control

- Announcement ID:
- Type (1–12):
- Candidate version/hash:
- Evidence cutoff (ISO 8601):
- Authorized sender:
- Draft owner:
- Source owner:
- Human release authority:
- Confidentiality:
- Final disposition: `DRAFT / BLOCKED / READY_FOR_RELEASE_REVIEW / NOT_RELEASED / RELEASED / SUPERSEDED`

## 2. Controlling record

| Field | Verified value | Source ID/version | Owner | Allowed wording / boundary |
|---|---|---|---|---|
| Decision or change | | | | |
| Approved facts | | | | |
| Known unknowns | | | | `Keep visible` |
| Prohibited detail | | | | |
| Publication time | | | | |
| Effective time | | | | |
| Deadline | | | | |
| Transition / expiry | | | | |
| Authoritative recipient link | | | | `Test least-privilege access` |

## 3. Audience reconciliation

| Segment | Directory query/source | Extracted | Excluded | Eligible | Direct-first? | Language | Accessible/backup channel | Owner |
|---|---|---:|---:|---:|---|---|---|---|
| | | | | | | | | |

- Total directory identities:
- Service/test/stale identities excluded:
- Protected/private-route exclusions:
- Final eligible total:
- Segment reconciliation formula:
- Sample-check result:
- Direct-first completion evidence:

Do not infer employment status, disability, leave, location, manager, clearance, language, or access from unapproved data.

## 4. Action and support

- Recipient state: `ACTION_REQUIRED / CONDITIONAL / OPTIONAL / NO_ACTION`
- Required action:
- Ordered steps and prerequisites:
- Completion system of record:
- Support owner and monitored route:
- Exception / accommodation route:
- What recipients must not do:
- Next update:

## 5. Channel and language plan

| Channel/language | Purpose | Exact audience | Preview owner | Accessibility checks | Failure route | Approved version |
|---|---|---|---|---|---|---|
| | | | | | | |

Emergency and life-safety messages must use the applicable approved emergency system; this worksheet cannot replace it.

## 6. Specialist review map

| Review domain | Reviewer/role | Required? | Exact scope | Candidate result | Time | Open condition |
|---|---|---|---|---|---|---|
| Source owner | | | | | | |
| People / employee relations | | | | | | |
| Legal / compliance | | | | | | |
| Privacy | | | | | | |
| Security / incident | | | | | | |
| Safety / facilities | | | | | | |
| Technical / change | | | | | | |
| Accessibility / localization | | | | | | |
| Communications | | | | | | |
| Release authority | | | | | | |

## 7. Choose one structure

- [ ] 1 — policy update
- [ ] 2 — process change
- [ ] 3 — system launch
- [ ] 4 — system maintenance
- [ ] 5 — organization change
- [ ] 6 — leadership update
- [ ] 7 — workplace or office update
- [ ] 8 — security notice
- [ ] 9 — required training
- [ ] 10 — project milestone
- [ ] 11 — incident resolution
- [ ] 12 — company meeting or event

Why this type is correct:

Why another type is not being used:

## 8. Candidate announcement

- Subject/title:
- Sender:
- Audience:
- Publication/effective/deadline times:
- Source IDs:

Body:

> [State what changed, who is affected, required or no action, exact time, authoritative source, support, limitation, and next update. Do not invent certainty or approval.]

## 9. Deterministic preflight

- [ ] One approved controlling record and version supports every material claim.
- [ ] Affected, excluded, direct-first, localized, accessible, and backup groups reconcile.
- [ ] Publication, effective, deadline, transition, next-update, and expiry times include timezone.
- [ ] Required, conditional, optional, or no action is explicit.
- [ ] Links and attachments load for a least-privileged test account.
- [ ] Personal, customer, security, legal, commercial, and privileged detail is minimized.
- [ ] Every language preserves terms, dates, duties, links, and support routes.
- [ ] Specialist approvals bind to this exact version/hash.
- [ ] Drafting, specialist approval, release approval, and distribution remain separate.
- [ ] Correction, rollback, channel failure, and support escalation are tested.
- [ ] No brackets, `.invalid`, IA086, fictional names, or teaching values remain in production.
- [ ] Opens, clicks, acknowledgements, comprehension, completion, and outcome are not conflated.

## 10. Release and outcome record

- Final candidate hash:
- Audience snapshot/hash:
- Human release decision and time:
- Actual release identity/time (if authorized):
- Attempts / accepted / failed:
- Acknowledgement definition and count:
- Completion definition and count:
- Correction ID/version:
- Superseded copies marked:
- Open failures and owner:
- Final outcome and evidence:

Material changes after approval invalidate the approval and require a new review.