Blocker and risk both sound like reasons to worry, but they describe different points in time -- and that difference changes how urgently each one should be treated.
A blocker has already stopped work; a risk is a potential future problem that hasn't happened yet.
Time is the deciding factor
If the thing you're describing hasn't happened yet, and might not, it's a risk. If it has already happened and is currently preventing progress, it's a blocker.
"The vendor's contract not being signed is a blocker -- testing cannot start without it."
This has already happened. The contract is unsigned right now, and testing is actively stopped because of it.
"The vendor might miss their delivery date next month -- that's a risk, not yet a blocker."
This hasn't happened yet. It might happen, and it's worth tracking, but nothing is currently stopped by it.
Treating a future possibility as an already-active stoppage
Treating a future possibility as if it were an already-active stoppage is a common precision mistake in status reporting. It's tempting to reach for the more urgent-sounding word when something feels worrying, even before it has actually materialized into a real, current problem.
Want to learn "Blocker" in depth?
Lyra Practice teaches advanced non-native professionals the nuance of high-value expressions like this one, then has you practice using them in realistic work scenarios.
Start learning for free →"Flagging every risk as a blocker in a status report makes the real, already-active stoppage harder to spot."
This is the practical cost: if risks and blockers get the same label, a reader can't tell, from the label alone, whether something needs attention right now or just needs to be monitored going forward.
Why the distinction changes what happens next
A risk calls for monitoring, contingency planning, or an early heads-up -- work continues while someone keeps an eye on it. A blocker calls for immediate attention, because work has already stopped and won't resume until it's resolved. Mislabeling a risk as a blocker can trigger an unnecessary scramble; mislabeling a blocker as a risk can leave a genuinely stopped task without the urgency it needs.
The mistake to avoid
Mistake: treating a potential future problem as already a blocker, before it has actually happened. If nothing is stopped yet, "risk" -- not "blocker" -- is the accurate word, even when the possible outcome feels serious.
Both words deserve a place in the same report
Good status reporting usually includes both words, applied to different things -- the active blocker that needs resolving today, and the risks worth watching so they don't become tomorrow's blockers. Neither word is more important than the other; they simply describe different moments in time, and a report that only uses one of them is probably missing something the reader needs to know.
A report that lists only blockers can miss the early warning a stakeholder would have wanted; a report that lists only risks, with no mention of what's actually stopped today, can leave urgent work under-resourced. The two words work best side by side, not as substitutes for each other.
Practice scenarios
Practice using blocker in situations like:
- distinguishing an already-active blocker from a future risk that hasn't materialized yet
- avoiding the habit of calling a risk a blocker because it feels urgent
- flagging a genuine risk without inflating it into a current stoppage
Useful practice phrases:
- "[Condition] is a blocker -- [task] cannot proceed without it, right now."
- "[Possible future event] is a risk, not yet a blocker."
- "That hasn't happened yet, so I'd call it a risk rather than a blocker for now."
One word describes what's already true; the other describes what might become true.
Keep them separate and your status reports stay easy to trust.
Lyra Practice helps advanced non-native English professionals learn the nuance of high-value workplace expressions and practice using them in realistic scenarios, so their English sounds natural, precise, and senior at work. Try Lyra Practice.