Before you use it
- Use when
- A status update blends verified facts, guesses and missing information.
Keep this limit in mind
- Do not use 'unknown' as an excuse to omit available evidence; name the next way to reduce uncertainty where it matters.
Current editorial reading
Show what you know and what you suspect
For a technical update, you could write: “Known: the import was accepted; see job 42. Unknown: the downstream result and customer impact. Working explanation: a queue delay may explain the wait. Next check: Mira will inspect the job outcome and impact signals at the agreed checkpoint.” The queue explanation is a hypothesis. It does not establish success or absence of harm.
Give each important unknown a next check
Name the evidence to seek, who will check it and when the next update is due. Revise the statement as results arrive. If the observed situation meets the team’s escalation rules, act without waiting for a complete explanation. CDC guidance supports acknowledging uncertainty; this technical example is an editorial application, not a CDC-tested incident procedure.
Take it with you
Use “impact not yet established” while that is the actual state. Keep assumptions open to revision and follow required verification and escalation rules.
Sources and evidence (2)
What we checked
CDC guidance asks communicators to acknowledge uncertainty in data, findings, recommendations, guidance and action steps.
Selected guidance inspected on 2026-10-05. Used for uncertainty labeling; public-health guidance does not independently validate this workplace workflow.
CDC Clear Communication Index, item 11: State of the Science · State of the Science, opening paragraphs
Information currently treated as known may still be incomplete or insufficient to answer the audience’s questions.
Limits what a Known label establishes: neither a label nor a completed intermediate step proves the downstream outcome.
CDC Clear Communication Index, item 11: State of the Science · State of the Science, opening paragraph
Google’s incident guidance recommends predefined declaration conditions and early use of incident management rather than waiting for a worsening situation.
Selected passage inspected on 2026-10-05. Its example thresholds are local practice, not universal timing rules; no incident was operated.
Managing Incidents · When to Declare an Incident
Editorial sources (2)
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Try it in a task guide
These guides use this edition of the method alongside other ideas for the same task.
Separate known, unknown and assumed states.Clarify an Unclear Work Task
Connected ideas
You are readingKeep unknown impact unknown
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaGive technical terms one local definition
Original edition evidence and sources
These records belong to the original released edition. The current editorial reading has its own evidence above; neither set silently replaces the other.
CDC guidance explicitly recommends distinguishing what authoritative sources know and do not know rather than presenting uncertainty as settled.
The exact evidence standard depends on domain; this supports uncertainty labeling, not scientific review of ordinary work messages.
How to Use the CDC Clear Communication Index · State of the science item
All sources (1)
Original edition, downloads and provenance
The reading above is editorial version 1.0.1, bound to this exact source edition. The original data and saved downloads retain that edition and the separate editorial layer. They may contain earlier wording; use the current reading above when interpreting it.
Version 0.1.0
No review details are supplied for this edition.
Read the original edition and overlay as JSON · Release details
