Why "COB" 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: 4.1/10
Clear scores workplace language across directness, specificity, tone safety, and async clarity. "COB" lands here because:
- Directness: 5/10. It clearly marks the request as a deadline.
- Specificity: 2/10. It still leaves open which office hours and timezone count as the business day.
- Tone Safety: 4/10. It can sound more formal and harder-edged than EOD, especially outside finance or legal contexts.
- Async Clarity: 5/10. People know it is deadline language, but not always the exact cutoff they are being held to.
A clearer version of the same message
If you want to keep the intent but remove the guesswork, a stronger version looks like this:
Please send the signed draft by 5 PM ET today. Legal needs it before their office closes.
What people hear when you say "COB"
COB sounds precise because it uses business language. In practice, it still hides assumptions about office hours and timezone.
That is why it works best in environments with a shared clock and worst in distributed teams.
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 office cutoff matters
Please send the signed draft by 5 PM ET today.
It translates business shorthand into a shared timestamp.
Diplomatic
Best when: when you want to explain the deadline
Can you get this over by 5 PM ET? Legal needs it before their office closes.
It makes the business constraint visible instead of assumed.
Async-Friendly
Best when: when teams are distributed
Due today by 5 PM ET. If you are not going to hit that, post an update here by 3 PM ET.
It adds both timezone and escalation behavior.
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:
Need this by COB.
After:
Need this by 5 PM ET today so legal can review it before their office closes.
What changed
The clearer version keeps the business context but removes the hidden local assumptions baked into COB.
Common questions about "COB"
What does COB mean at work?
COB means "close of business." In workplace messages, it usually means the end of the business day, but the exact business hours and timezone are often assumed rather than stated.
Is COB better than EOD?
Only a little. COB implies business hours rather than literal midnight, but it still needs a timezone and actual time to be fully clear.