Why "In Due Course" can create friction
People use familiar workplace shorthand because it feels efficient in the moment. The problem is that a familiar phrase can still leave the real ask, the real stakes, or the expected next step unstated.
That gap gets more expensive in Slack and email, where the reader cannot rely on tone or a quick follow-up question to fill in the missing context.
Clarity Score: 2.5/10
Clear scores workplace language across directness, specificity, tone safety, and async clarity. "In Due Course" lands here because:
- Directness: 2/10. It suggests movement or politeness, but not the exact ask the reader should respond to.
- Specificity: 1/10. "In Due Course" usually omits the deadline, trigger, or decision that would make it actionable.
- Tone Safety: 5/10. It sounds gentle on the surface, though the ambiguity can still create stress.
- Async Clarity: 2/10. In text, the softened wording leaves too much room for interpretation.
A clearer version of the same message
If you want to keep the intent but remove the guesswork, a stronger version looks like this:
We will review this after the board meeting on Tuesday and send a decision by Wednesday afternoon.
What people hear when you say "In Due Course"
It postpones the answer without telling the reader whether later means today, next month, or never.
Formal phrasing can feel safer to the sender, but readers still need a date or trigger they can trust.
3 Clearer Alternatives
Different situations call for different rewrites. These examples keep the original intent while making the message easier to understand on first read.
Direct
Best when: when the response really is later
We will review this after the board meeting on Tuesday and send a decision by Wednesday afternoon.
It states the real ask instead of hinting around it.
Diplomatic
Best when: when you want to stay formal but clear
We are not deciding yet. The next review point is Tuesday's board meeting, and I will follow up by Wednesday afternoon.
It stays courteous without leaving the other person to decode the message.
Async-Friendly
Best when: when you want a thread-ready deferral
Not deciding this today. Next step is the board meeting on Tuesday, and I will post the decision here by Wednesday afternoon.
It gives the reader a clean next step they can answer in-thread.
Before and After in Slack
The stronger version works better because the reader can see the request, the timing, and the expected response in one pass, even if the message is slightly longer.
Before:
We will revert in due course.
After:
We will review this after the board meeting on Tuesday and send a decision by Wednesday afternoon.
What changed
The rewrite keeps the polite intent but removes the uncertainty that makes the original phrase expensive to receive.
Common questions about "In Due Course"
What does "In Due Course" mean at work?
At work, "In Due Course" means at some later time, after other steps happen first. In workplace writing, it often sounds formal while hiding the actual timeline, owner, or condition for follow-up.
Why can "In Due Course" feel unclear at work?
It postpones the answer without telling the reader whether later means today, next month, or never.