"Blocked by [the cause]" names the actual obstacle. "Blocked on [what you're waiting for]" names the pending item. Both sound natural in everyday project communication. They simply place the emphasis on different facts, and both forms are correct.
Quick check
Pending item or root cause?
You know "Blocker" well.
Keep going with the full learning path — more workplace contexts, related expressions, and practice using it yourself with feedback.
Continue with "Blocker" →There's more to "Blocker" than it seems.
You've got part of it, but the full learning path goes deeper into its nuances, workplace contexts, and when it sounds natural — then gives you practice using it yourself.
Learn "Blocker" in depth →Not a grammar error -- a focus shift
The main risk is not incorrect grammar. It is treating both expressions as the same, although each one points to a different detail.
"I'm blocked by a permissions issue -- IT needs to grant me admin access first."
"Blocked by" names the issue that caused the delay. Here, the permissions issue is the specific obstacle.
"I'm blocked on the API team's response before I can finish the integration."
"Blocked on" names what the speaker is waiting to receive. Here, the API team's response is pending, but it is not necessarily "the cause."
Try it yourself
Put the underlying cause first
Both forms can appear in the same situation
You can often describe the same situation accurately with either expression. Your choice depends on which information needs the most attention.
"She's blocked on the vendor's quote, but the actual cause is their slow procurement process."
This sentence uses both forms on purpose. "Blocked on the vendor's quote" names the pending item. "The actual cause is their slow procurement process" names the deeper reason. This is not needless repetition; it gives two useful facts together.
Picking the one that matches your emphasis
Here is a practical rule. Use "blocked by" to name the root cause. Use "blocked on" to name what you are waiting to receive. Both may be true at the same time, so choose the fact your listener needs first.
The mistake to avoid
A common mistake is assuming that one form must be wrong. The forms differ, but both belong in natural project language and stress different facts. Do not correct a colleague based on the preposition alone. Revise the sentence only when it does not match their intended meaning. The issue is "accuracy," not a forbidden form.
Why this pair is worth learning on purpose
Many similar English pairs have one right answer in each context. This pair works differently, which is why it deserves attention. Learners may waste time searching for "the correct form" and asking whether "blocked on" or "blocked by" is right. Here, both forms are correct. Choose based on the fact you want to present first.
Once you understand this difference, the pair feels less confusing. There is no single answer for every situation. One form may express your meaning more clearly, which gives you useful freedom when writing a status update.
Practice scenarios
Practice using blocker in these realistic work situations.
- choosing "blocked on" to name what you're waiting for
- choosing "blocked by" to name the actual cause
- using both in the same sentence when the pending item and the root cause are worth naming separately
Useful practice phrases to try.
- "I'm blocked by [cause] -- [next step]."
- "I'm blocked on [pending item] before I can [next step]."
- "[Person/team] is blocked on [item], but the actual cause is [root cause]."
Want to actually use "Blocker" naturally at work?
Understanding it is one thing. Practice its nuances, see how it works in real workplace situations, and use it yourself with feedback.
Start the "Blocker" learning path →It is wrong to call one form "correct" and the "alternative" a mistake.
Choose the form that puts your listener's most important fact first.