They said EOD and I don’t know whose day

"Can you get it over by EOD?"

You read that at 10am. Your end of day is about seven hours away. Theirs was two hours ago, or is tomorrow lunchtime, depending on which direction the gap runs.

Nobody is lying. The phrase simply does not contain the information it appears to contain.

Why "EOD" fails specifically

Ordinary times survive translation badly, but they at least point at something. "3pm" is wrong across zones but it is specifically wrong, and someone will eventually ask "3pm where?"

EOD sounds complete. It reads as a deadline, not as a time requiring conversion, so nobody thinks to ask. It also carries an implicit workday — and workdays differ by country, not just by offset. End of day in Dubai is Thursday's end of week; in most of Europe it is Friday's.

The result is a deadline both parties believe they understand and that differs by up to a full day.

What it actually costs

Small things, repeatedly. A file arriving after the reviewer has logged off, losing a day. An invoice dated on the wrong side of a month boundary. A release "cut EOD Friday" landing when nobody is around to watch it deploy.

And occasionally a large thing: a contractual deadline where "end of business day" was never defined, and the two parties' answers are eleven hours apart with money attached.

Write the instant, not the intent

The fix is dull and complete: give a time, a time zone, and a date.

"Due EOD Thursday." "Due 17:00 New York, Thursday 12 March."

For anything contractual, name the city rather than an abbreviation. "EST" in July is not a real time, and abbreviations like CST and IST mean different things in different countries. A city name resolves unambiguously on any date. See EST vs EDT.

For anything machine-read — logs, APIs, automated cutoffs — use a UTC timestamp. It has no seasonal behaviour at all.

A useful default for teams

If your team spans zones, pick one reference zone for deadlines and say so once, publicly:

"All deadlines are stated in UTC unless a city is named."

It costs one line in a handbook and removes the ambiguity permanently. The alternative — everyone quietly assuming their own zone is the default — is what you have now.

The sentence that unblocks it right now

If you are staring at an ambiguous EOD today, do not guess:

"Just to confirm — is that 5pm your time or mine? Mine is currently 11 hours ahead of yours."

Nobody has ever been annoyed by that question, and it is considerably cheaper than delivering a day late.

Related: My client keeps booking me during dinner · UTC to EST

Figures on this page are computed from the IANA time zone database. Last generated 2026-08-18.