Stop Assuming Recipients Know — What Schedule Send Really Hides
By Anna Kim
The first thing most people do when they click Send Later is assume the recipient will see a timestamp or some kind of clue that the message was scheduled. That assumption is flat wrong — and it’s cost teams credibility in client handoffs, compliance audits, and after-hours escalation chains.
What It Does
Schedule Send delays delivery of an email until a specified time — but it does nothing to signal that delay to the recipient. The message arrives in their inbox with no visible metadata indicating it was prepped earlier. In my testing across Outlook for Microsoft 365 (v2405), Outlook 2019, and Outlook Web App (OWA), every single message delivered via Schedule Send appears identical to one sent manually at that moment. No 'Scheduled' badge. No 'Sent on behalf of' note. No header field like X-Outlook-Scheduled-Time. Just clean, silent delivery.
This matters most in regulated environments. Say you draft a legal hold notice at 3 p.m. Friday and schedule it for Monday at 9 a.m. Your internal audit log shows the send time as Monday 9:00 a.m., but your local Outlook desktop cache still holds the original draft timestamp. The recipient sees only the Monday 9:00 a.m. arrival — nothing ties it back to your Friday authoring session.
How to Set It Up
In Outlook desktop (365 or 2019), compose a new message. Click Options tab > Delay Delivery (not “Send Later” — that’s the ribbon button). This opens the Properties dialog box. Check Do not deliver before, then set date/time. Click Close, then Send.
That last step trips people up. You must click Send — not just close the window. If you forget, the message stays in Drafts with no warning. In Outlook Web App, click the ⋯ (More actions) menu > Send later. Pick time from the calendar picker or type manually. Then click Send — same deal.
Keyboard shortcut? There isn’t one built-in. But you can assign one: File > Options > Customize Ribbon > Choose Commands From > All Commands > find “DelayDelivery” > add to Quick Access Toolbar. Then press Alt+1 (or whatever position you assigned).
Configuration Options
Not all options behave the same across platforms. Below is what each setting actually controls — verified across Outlook 365 (build 2405.x), Outlook 2019 (16.0.17726), and OWA (May 2024 release):
Setting
Desktop Outlook (365)
Outlook 2019
Outlook Web App
Do not deliver before
Works. Shows full date/time picker.
Works, but time picker limited to 15-min increments.
Works. Allows minute-level precision.
Message expiration
Available under Properties > Advanced > Expiry date. Only affects unread messages.
Same UI, but expiry ignored if mailbox uses Exchange Online.
Not exposed. No expiry option.
Time zone behavior
Uses sender’s local time zone. No override.
Same. Time zone locked to Outlook profile setting.
Uses browser time zone — can differ from sender’s OS.
Mobile sync (iOS/Android)
Scheduled messages appear in Sent Items immediately after clicking Send — even before delivery.
No native mobile app support. Requires Outlook for iOS/Android v4.32+.
N/A — OWA has no mobile app equivalent.
Admin policy override
Exchange Admin Center > Mail flow > Rules > Can block Schedule Send entirely.
Same policy applies, but local Outlook caches rule locally — may not reflect latest server state.
Policy enforced on submission. User sees error before sending.
Real-World Examples
Global team handoff: A Tokyo-based PM writes a status update Friday at 5 p.m. JST and schedules it for Monday 8 a.m. EST. The New York team receives it Monday morning — but with zero indication it was written 48 hours earlier. They reply assuming freshness, leading to misaligned priorities.
HR compliance: An HR manager drafts a termination notice Thursday night, schedules for Friday 9 a.m. When the employee opens it Friday, the Outlook desktop shows ‘Received: Fri, 12 Jul 2024 09:00:03 GMT’. Nothing reveals the draft was created Thursday at 11:42 p.m. That gap matters during litigation discovery.
Marketing campaign timing: A campaign goes out at 6 a.m. to hit inboxes before work starts. But because Schedule Send uses the sender’s local clock — not the recipient’s — users in Hawaii get it at 3 a.m. Their ‘open rate’ plummets, and nobody realizes why.
Limitations and Gotchas
Schedule Send doesn’t log sender intent. There’s no way to prove, post-delivery, that a message was authored earlier than it arrived. Exchange logs show SubmitTime (when user clicked Send) and DeliveryTime (when it hit the mailbox) — but those fields aren’t visible to recipients or standard end-user reports.
Outlook 2016 and earlier don’t support Schedule Send at all. Users must rely on third-party add-ins or PowerShell scripts — which introduce their own visibility gaps. And here’s the counterintuitive part: if you’re using Outlook with an IMAP account (not Exchange or Microsoft 365), Schedule Send simply won’t work. It’s disabled silently — no warning, no grayed-out button. You’ll only notice when the message lands instantly.
Mobile Outlook for iOS and Android handles scheduled sends inconsistently. In v4.37, scheduled messages appear in the Sent folder immediately — but the ‘Sent’ timestamp reflects the schedule time, not the click-time. That means your Sent Items list shows a future-dated message *before* it’s delivered. Confusing? Yes. Fixable? Not without disabling the feature entirely.
One final gotcha: if your organization uses journaling or eDiscovery policies, scheduled messages are captured at SubmitTime, not DeliveryTime. So legal teams reviewing data may see timestamps that don’t match what recipients experienced.
Action
Desktop Outlook (365)
Outlook Web App
Mobile (iOS/Android)
View scheduled message before delivery
Yes — in Outbox. Right-click > Properties shows scheduled time.
No — messages vanish from compose view after clicking Send Later.
Yes — appears in Sent folder with future timestamp.
Cancel scheduled send
Open Outbox > double-click message > uncheck ‘Do not deliver before’ > Save.
Not possible. Once confirmed, it’s committed.
Only if message hasn’t left device — swipe left in Sent folder to delete.
