End of Day (EOD): Meaning at Work, EOD vs COB and What Time

EOD vs COB vs EOB

The three acronyms are often used interchangeably, and in most offices they point to the same moment. The nuances matter when a deadline is tight.

• EOD (end of day): the end of the recipient's working day. Usually 5 PM, sometimes read as "before I log off".
• COB (close of business): the official end of business hours, usually 5 PM local time. The most formal of the three, common in finance, legal and government.
• EOB (end of business): same meaning as COB, mostly used in US offices.
• EOW (end of week): the end of the last working day of the week, usually Friday at 5 PM.
• EOM (end of month): the last business day of the month. In finance, it can mean the month-end close.

Short version: COB and EOB point to a fixed time, the close of business hours. EOD points to the end of someone's working day, which can run later. Ask for something "by COB" and expect it by 5 PM. Ask "by EOD" and some people will send it at 9 PM.

What time is EOD?

In most offices EOD means 5 PM, the usual end of a 9-to-5 business day, in the time zone of the person who has to deliver. Some companies use 6 PM. In a business context, EOD rarely means midnight, even though the calendar day ends then. When the hour matters, write it: "by 5 PM London time on Friday."

Outside offices, EOD can mean something else entirely. In military and bomb disposal contexts, EOD stands for explosive ordnance disposal. This page covers the business meaning only.

How EOD works in sales

EOD has no formal definition. In practice it follows three conventions:

• Recipient's local time zone, not the sender's. If a New York seller emails a London buyer "I'll send the proposal by EOD", that's 5 PM in London, not 5 PM in New York. Most accidents happen here.
• 5 PM or 6 PM local. Some companies set close of business at 5 PM, others at 6 PM. When it matters, spell it out: "by 6 PM London time on Friday."
• Business days only. EOD Friday means Friday 5 PM, not Sunday 11:59 PM. Saturday and Sunday don't count.

Where EOD shows up in sales operations:

• Sales rep deadlines: "Get your forecast in by EOD" usually means the rep's local time. In distributed teams, managers should name the time zone.
• Customer-facing emails: "Send the signed order form by EOD" means the recipient's time zone, ideally with an explicit hour ("by 5 PM your time today").
• Internal handoffs (SDR to AE): usually the rep's time zone, with a chat message as backup so nothing waits in an inbox overnight.

EOD and COB in a sentence

• "Can you send me the updated forecast by EOD?" By the end of your working day today.
• "Please approve the invoice by COB Thursday." By 5 PM on Thursday, within business hours.
• "I'll get back to you EOD tomorrow." Before the end of tomorrow's working day.
• "The report is due EOW." By close of business on Friday.
• "We close the books at EOM." On the last business day of the month.

Three illustrative EOD interactions in sales

The people and deals below are fictional. They show how the same three letters can help or hurt.

1. Cleanly used: "Hi Sarah, if you can return the signed agreement by EOD Friday (5 PM London time), we can lock in the Q1 start date." Specific hour, time zone, date and consequence. Sarah signs at 4:42 PM on Friday. Deal closed.
2. Ambiguous, and it hurt the deal: "Need your signature by EOD." The buyer is in Singapore, the seller in San Francisco. The buyer assumes the seller's time zone and replies at midnight Singapore time, 9 AM in San Francisco. The seller has already flagged the deal as slipping to their VP. Trust dented for no reason.
3. Used as a soft deadline: "I'll have the proposal to you by EOD", then sent 24 hours late. That's not an EOD failure, it's a commitment failure. EOD is only as strong as the seller's reliability.

EOD is a small word with an outsized effect on sales operations. Used precisely, it shortens cycle time and creates urgency without sounding pushy. Used loosely, it creates time zone confusion, missed handoffs and repeated "your time or mine?" exchanges.

For distributed sales teams, the cost of a vague EOD adds up. Picture a three-person SDR team across three time zones with one EOD mix-up per week each: that's around 150 confusion moments a year. Each one takes a few minutes to sort out, and once in a while it costs a deal.

The fix is operational, not linguistic. Make "always state the time zone for cross-region deadlines" a team norm, default to the recipient's time zone, and use calendar and reminder tools that show the time zone by default.

• Defaulting to your own time zone. The recipient's time zone is the norm for customer-facing EOD. The sender's time zone is the norm only for internal team deadlines.
• Using EOD on a Friday for a Monday meeting. The buyer reads "EOD" as their Friday 5 PM, you needed it by your Friday 5 PM, and the document misses the prep call. Say what the deadline is for.
• EOD without a consequence. "Reply by EOD" with no hint of what happens otherwise is no deadline at all. Pair it with a real consequence ("or we move the demo to next week") or drop the EOD framing.
• Using EOD for global teams. Cross-region deadlines should always include an hour and a time zone. A bare EOD is unsafe as soon as more than one time zone is involved.