What an Outlook follow-up flag can and cannot hold

A follow-up flag is the cheapest promise in Outlook. One tap on the flag column marks a message, and the day moves on. That mark is a small set of date fields, and Outlook fills them in for you the moment you set one. Ten minutes on which fields they are explains most of what happens next.

It explains the reminder that stayed quiet. It explains the flagged pile nobody works, and the client who went unchased because the flag sat there waiting to be noticed instead of coming to find you. Here is what a flag holds.

• A flag set in one motion means today. Microsoft’s documentation is plain about the default. An unmodified flag “uses today’s date for the Start date and Due date”. So every message you flag in passing becomes a task due today, and by Thursday the list is a wall of overdue.
• A flag holds four values, and what the message asked for lives in your head. In Microsoft’s own developer documentation there’s a start date, a due date, a completion date, and a status with three possible values. That’s the whole thing.
• Marking complete and clearing the flag are two different decisions. One keeps the record and one destroys it, and the destroying one is the one that looks tidier.
• A flag on a message you send fires on the date you picked. The date is the only thing it watches. The bell rings the same whether the reply came back a week ago or has yet to arrive.
• Where your flagged mail is listed depends on which Outlook you’re in, and the list Microsoft To Do gives you is a different object from the one classic Outlook shows you.

The dates Outlook fills in for you

Start here. This one accounts for more broken flag systems than every other cause combined.

There are two ways to flag a message you’ve received, and they give you different results. The single motion on the flag column in the message list is the one everybody uses. Microsoft states what it does: “unless you have changed the default flag, the flag uses today’s date for the Start date and Due date” (checked September 6, 2026). Today, then, on every one of them. The right-click menu on that same column holds the alternatives, and Microsoft publishes exactly what each of them sets.

Two rows in that table are worth reading twice. This Week means two days from now, capped at Friday. And No Date, which sounds like the safe neutral option, still schedules a reminder for the current date.

Microsoft’s own best-practices guidance for Outlook recommends leaving the default alone: “it’s considered best practice to set your Quick Click flag to Today (which is the default)” (checked September 6, 2026). That’s good advice for somebody who flags four messages a day and clears them by six. A professional practice is a different case, because a good half of what gets flagged there is due in March. The real choice is between one motion that dates everything today and two motions that put the true date on it. The second costs about a second more.

The cost compounds quietly. When every item claims to be due today, the list carries one fact, and it’s the same fact for all of them. Working it means reopening each message to find out what it was and when it was really for. That rereading is the actual price of a flag, and you pay it every time you look.

What a flag has no room for

The clearest description of a flag sits in the developer documentation, where Microsoft has to say precisely what the thing is made of.

Microsoft Graph carries a followupFlag on a message, described as something that “allows setting a flag in an item for the user to follow up on later”. Four properties make up the whole of it (checked September 6, 2026).

• startDateTime, “the date and time that the follow-up is to begin”
• dueDateTime, “the date and time that the follow-up is to be finished”
• completedDateTime, “the date and time that the follow-up was finished”
• flagStatus, “the status for follow-up for an item”, whose possible values are notFlagged, complete and flagged

So a flag carries three dates and a three-state switch. Everything else it seems to mean, you’re carrying yourself: what the message asked of you, who owes the next move, and the condition you’d actually like to set. When they reply. If the signed copy is still outstanding. Those are sentences a person understands, and a flag has no field for either of them.

One small detail in the same document sums up the whole design. Microsoft notes that to set the due date “you must also specify the startDateTime; otherwise, you get a 400 Bad Request response”. Outlook stores a due date only alongside a start date. The flag was built as a span of time with a bell on the end of it, and it behaves that way whatever you had in mind when you set it.

People usually complain that flags get ignored. The deeper fact is about what a flag can hold. The reason you set it lives elsewhere, so every review of the flagged pile is a rereading exercise rather than a working session. Where an obligation buried in somebody’s paragraph gets lifted out and written down with its own date is email task management, without writing it down, which is the same problem approached from the side where the answer is.

Where flagged mail becomes a list

A flag on its own is a mark on a message, sitting at whatever depth the day has pushed it to. It earns its keep when something gathers the marks into one view. Which view you get depends on which Outlook is in front of you.

Classic Outlook. Microsoft states that “flagged messages appear in the To-Do Bar, in Tasks, and in the Calendar Daily Task List” (checked September 6, 2026). That’s three surfaces onto the same underlying items. There’s also a Search Folder made for the purpose: “messages that you flag appear automatically in the For Follow Up Search Folder.” That folder is the most useful thing in this whole feature and the least known, because it’s where a flag turns from a decoration on a message into a queue. What a Search Folder is, what it can and cannot ask, and which handful are worth having are in how to organize Outlook folders, and rules that fill them.

New Outlook and the web. The flag here is a lighter object. Microsoft’s description is that “a flag gives you a visual cue that you want to return to that message later”. The flagged mail is reachable through a filter on the message list, and a reminder is available on a flagged item for a Microsoft 365 account (checked September 6, 2026). A visual cue and a filter is what you’re handling here.

Microsoft To Do. This is where flagged mail becomes an actual task list, through a Flagged email list you switch on before it exists. Three of its documented properties matter to a firm. It arrives holding a slice of your history: Microsoft states that “the flagged email list will initially populate with the 100 most recently flagged emails within the last 30 days”, with newly flagged mail joining it afterward. It takes your primary mailbox only: “only emails flagged from your primary mailbox will sync with Flagged email folder in To Do. Flagged emails from shared folders and shared mailboxes are not supported.” And it’s a simpler object than classic Outlook’s Tasks. Microsoft says To Do “doesn’t currently support the start and end dates, task status, task completion percentage, multiple priority levels, task work hours, task colors, or categories that are available in Outlook Tasks” (all checked September 6, 2026).

Put those together and the honest position is this. If your firm runs classic Outlook, flags feed a genuine task surface with dates on it. If your firm has moved to new Outlook, flags feed a simpler list that drops most of the date fields the flag itself still stores. Either way, the list in front of you holds the last month of your own mailbox. Older flags, and anything flagged at the firm’s shared address, sit outside it.

Marking complete is not clearing the flag

This one is small, easy to get right, and costs firms real money once a year.

When you’ve finished with a flagged message, two commands sit next to each other, and they do opposite things to your record. Microsoft spells out the difference. Mark Complete: “the item remains marked with a follow-up flag, however, it appears with a strikethrough.” Clear Flag: “the flag is removed from the message and there is no record of the message ever appearing in views such as the To-Do Bar and Tasks” (checked September 6, 2026).

No record. The message survives, and the fact that you once owed somebody an answer on it goes with the flag.

For most personal mail that’s fine, and tidier. For a practice, Mark Complete is the one you want. The question that arrives six months later is usually did we deal with this, and when, rather than is this outstanding. A struck-through completed flag answers that in one glance. A cleared flag leaves you reconstructing it from the thread.

Microsoft’s own page adds the caveat that goes with it. Even a completed item “completely disappears from all Outlook views” the moment you delete the message. The record lives on the message and dies with it. Whether a completed thread should then be archived rather than deleted, and what the deletion clock behind that actually is, is covered in organizing a busy Outlook inbox.

Flagging a message you are sending

Half of what people mean by following up is a message they sent, to somebody who has yet to answer. Outlook has two features here, and they get confused with each other, so they’re worth separating cleanly.

A flag for yourself on send. The same six options from the table above, applied to the outgoing message so it shows up in your own task surface. Microsoft’s best-practices guidance suggests renaming the resulting item so it reads as a follow-up rather than as the subject line. This one is real and it works, with exactly the limits already established. It fires on the date you picked, and the date is all it knows.

A flag for the recipient. A different feature, and the one to think about before you use it. Microsoft describes what the other person gets. On their side, “a flag appears in the message list and text appears above the From line in the message”. And crucially, “if the recipient is also using Outlook, an item will be added to his or her to-do list” (checked September 6, 2026). Two conditions hide in that sentence. The recipient has to be in Outlook, and in a version that renders the flag. A client reading your mail in Gmail on a phone gets a line of text at the top of the message, and that’s the whole of it.

Microsoft attaches its own warning, unusually direct for a help page: “use this feature with discretion. Some recipients might not appreciate having reminders added to their Outlook” (checked September 6, 2026). That’s a fair reading of how it lands. Writing into somebody else’s task list is a strong move, and between professionals it’s closer to a favor asked than a note made. Removing the flag later changes your side only: “recipients of the message still see the flag. When you remove a flag, it only affects what you see.”

Finding out whether anybody replied. Outlook has something here, and it’s manual. On a flagged sent message there’s a command called Find related messages. Microsoft says that using it means “the Advanced Find dialog box appears and a search starts for messages that are a response to your flagged message” (checked September 6, 2026). That’s a search you run, on a message you first had to remember to go and look at. It has a documented hole too: the feature “isn’t available” for an Exchange account whose sent items have been moved into an Outlook Data File, “either manually or with AutoArchive”.

One more restriction is worth knowing before a firm builds on any of this. Microsoft states that “you can’t change the flag text or set the Start date and Due date if you are using an IMAP email account” (checked September 6, 2026). On an IMAP account a flag is a plain mark, and the machinery this page describes sits outside it.

Why the reminder did not appear

“My Outlook reminder didn’t go off” is one of the most common complaints about flags, and it has several ordinary causes before it has an interesting one.

The most likely one is that the flag carried today’s dates and a reminder you never chose, because that’s what the single motion from the message list sets. The reminder behavior people remember comes from a customized flag. The second cause is a setting that covers the whole profile. Microsoft’s troubleshooting article on the subject, KB 2787708, gives one cause for reminders “for meetings, tasks, and follow-up items” not displaying: “you have the option to display reminders is turned off either in the Outlook user interface or through a Group Policy setting.” It adds the part that tells you whether this is yours to fix: “when a feature is configured by group policy, the option is disabled (grayed out) in the user interface. Therefore, it cannot be modified” (checked September 6, 2026). A grayed-out setting means the answer is your administrator rather than your Outlook.

The third cause is structural, and it’s the one to plan around. A reminder is delivered by whatever client is running at the moment it comes due. Microsoft states the browser case outright: “notifications only appear when Outlook for the web is open in your browser. If you close Outlook for the web, you won’t get notifications for calendar events until you open Outlook again” (checked September 6, 2026). Desktop Outlook behaves the way any desktop application does. A bell it raises while the application is closed is a bell you meet later. Windows notification settings, focus modes and do-not-disturb sit on top of all of it.

All of that is ordinary. A reminder is a local alarm, and it depends on a piece of software being awake and being allowed to interrupt you. It serves the things you’d like a nudge on. A follow-up you have to make deserves something sturdier, because a firm that learns this in October has usually learned it the expensive way.

Nothing notices that nobody replied

Here’s the gap under everything above. It’s worth stating on its own, because it’s the reason careful people still lose threads.

The follow-up you actually need is conditional. Remind me about this if the client has not sent the signed letter. Tell me on Friday if this is still unanswered. The flag’s four properties are a start date, a due date, a completion date and a three-state switch, so a condition is the one thing it has no field for. Outlook has nothing to evaluate, so the bell rings on the day you named. Whether the matter settled a week ago or has gone completely silent, you find out by opening the thread.

That has two costs, and they pull in opposite directions. The false alarms train you to dismiss the reminder, which is how a flag system dies. And a silence produces nothing at all, which is how the thing you were waiting on slips away. An unanswered message is the hardest kind of work to hold, because an absence lands nowhere. What that costs, and how long a silence has to run before it means something, is unanswered emails, and the threads that come back.

Flagging more carefully is the natural next thought, and it’s worth testing against the evidence. The research on how people actually get back to messages they meant to return to is unkind about markers in general, and it’s set out in snoozed email, and where later actually goes. If your instinct after reading this page is to tighten up the marking, that page is the one to read next. Tools that watch the outbound side for you and fire when the answer is missing are a real category with real trade-offs, and the closest comparison is Point versus Boomerang.

The flag in a mailbox several people read

If the mail arrives at the firm’s own address rather than yours, flags behave in a way that’s worth knowing in advance.

The flag lives on the message rather than on you. It’s a property of the mail item itself, which is how Microsoft’s own developer documentation models it. So everyone with access to that mailbox is looking at the same flag. One person sets it, all of them see it, and any of them can clear it. That works as a convention, and some practices do run a shared queue on flags this way. The one thing it leaves open is who is handling something, because the flag has no field for that. A flagged message in a shared mailbox tells your team that somebody thought this mattered.

The second thing is documented, and it catches people out. Microsoft states that “only emails flagged from your primary mailbox will sync with Flagged email folder in To Do. Flagged emails from shared folders and shared mailboxes are not supported” (checked September 6, 2026). So the flags your team sets on the firm address stay in the mailbox, and the mailbox is where your review habit has to happen.

It’s the same shape as the shared read-state problem, where an unread message tells you only that nobody has opened it yet. Both are covered, along with Microsoft’s own limits on shared mailboxes, in organizing a busy Outlook inbox. Where several people work one queue all day, the honest comparison is alternatives to a shared inbox tool.

A flag habit that survives a busy week

Plenty of people run a working follow-up system on flags alone, and if yours is working, keep it. What separates the systems that survive from the ones that quietly stop being read comes down to three decisions.

The date has to be true. A due date of today, set because that’s what one motion produces, tells you one thing about the message, and it’s the same thing it tells you about all the others. A list like that is a list you’ll stop opening within a month. The right-click menu costs a second and puts a real date on it. Where the real date is still unknown, No Date is more honest than a false today, with the caveat from the table above that Outlook still schedules a reminder for the current date.

The completion has to leave a mark. Between the two finishing commands, a professional practice wants the one that keeps a struck-through record. The one that erases every trace sits where your hand naturally goes. That’s worth deciding once rather than message by message.

There has to be exactly one place you read the list. Flags scattered across the To-Do Bar, a To Do app and a Search Folder give you three half-read lists rather than one working one. Pick the surface your version of Outlook actually gives you, and write down what it leaves out: anything older than a month if you’re relying on To Do, and anything at the firm’s shared address either way.

And one thing to watch. A status folder named Follow Up or Waiting is the common alternative to a flag, and it’s worse in a specific way. A message lives in exactly one folder, so filing a thread under Waiting takes it out of where it belonged, and the hole that leaves in a client’s history is invisible. Why status folders in particular fail in Outlook is worked through in how to organize Outlook folders, and rules that fill them.

What carries the when and the what

The flag stores a date you supplied and a status. What the message asked, and whether anybody has answered, stay with you, which is why the flagged pile has to be reread to be worked.

Point works on the Microsoft 365 mailbox and calendar you already have. Your address stays, your history stays, your mail keeps living where it lives today, and the people you write to see what they’ve always seen. What changes is where the judgment comes from. Every message is read for the request inside it and the date attached to that request, and weighed on both. So the top of your feed holds the work today actually owes, rather than the most recent arrival. Each thread carries a plain-language summary, which is enough to tell whether a long chain concerns you before you open it. An ask sitting in somebody’s fourth paragraph becomes a task with its own date and a way back to the sentence that produced it, so the thing a flag was standing in for gets written down properly. A request for a meeting becomes work Point takes on: Point runs the scheduling exchange and writes the settled time to your real calendar.

The part that answers this page directly is the conditional follow-up, the thing the flag has no field for. An open loop comes back to you before it goes cold, rather than on a date you guessed at. Work you’ve handed off is tracked, so you’re prompted to chase it at the point chasing is worth doing. And a standing request can watch for a particular message or condition and tell you when it happens, so you can stop checking. That’s the difference between a bell you set and something keeping an eye out.

Where the result is kept matters if you’ve just spent an afternoon on flags. What Point decides goes onto the real Outlook items, as three ordinary categories named Now, Later and Other. The ordering holds up on your phone, in the browser and in whatever client you happen to open, and filing a thread in Point archives it in Outlook for real. Your own side stays as it is. The flags you’ve set stay exactly where you set them, and your folders, rules and signatures keep working as they do today. What the connection touches is set out in the Microsoft 365 path.

How far Point goes alone is a dial with three positions: suggest-only, review, and fully handled. You choose the position per action type, rather than once for everything. Out of the box each type sits on review, so the work is prepared and then waits for you. An ordered activity log sits behind that, and undo reaches back across what Point did. The honest limit is that an email already delivered to a recipient’s server is past recall by anybody. Pricing is per seat and unpublished during the private beta. The flat list of everything is the benefits page.

The case for staying as you are is real. If you flag a handful of messages a week and clear them, the machinery on this page is more than the problem deserves. If the whole fault was a reminder that stayed quiet, that’s answered further up, and the fix is free. The assistant Microsoft sells alongside Outlook works on a different principle and has its own boundaries, described in what Copilot in Outlook cannot do. A fair account of what Outlook is genuinely excellent at is Point versus Outlook alone.

Common questions

How do I flag an email for follow up in Outlook?

There are two ways, and they give different results. The flag column beside a message in the list flags it in one motion, and Microsoft states that unless the default has been changed this “uses today’s date for the Start date and Due date”. The right-click menu on that same column offers the dated options instead, which are Today, Tomorrow, This Week, Next Week, No Date and Custom, each with a published start date, due date and reminder time. If the date matters at all, the second way is worth the extra second, because a flag set the quick way is always a task due today.

What does a follow-up flag actually do?

It stores three dates and a status on the message, and it lists that message somewhere you can find it again. Microsoft’s developer documentation defines the flag as exactly four properties, which are a start date, a due date, a completed date, and a status whose possible values are notFlagged, complete and flagged. What the message asked of you, and the condition you’d like to attach, stay in your head. So a flag records that you meant to come back, and working a flagged list means reopening each message to find out why.

Why didn’t my Outlook flag reminder go off?

Usually because the flag was set the quick way, which puts today’s dates on it and leaves out the customized reminder. Beyond that, Microsoft’s troubleshooting article gives one cause for reminders not displaying at all: the option to display reminders being turned off in the Outlook interface or by a Group Policy setting. It notes that a policy-managed setting is grayed out and cannot be changed by the user. A reminder is also delivered only by a client that’s running, and Microsoft states that notifications in Outlook on the web appear only while it is open in the browser.

What is the difference between Mark Complete and Clear Flag?

Marking complete keeps the record, and clearing the flag destroys it. In Microsoft’s words, on Mark Complete “the item remains marked with a follow-up flag, however, it appears with a strikethrough”. On Clear Flag, “the flag is removed from the message and there is no record of the message ever appearing in views such as the To-Do Bar and Tasks”. For a professional practice the completed version is nearly always the right one, because the question that comes back later is whether something was dealt with rather than whether it’s still open.

Where can I see all my flagged emails in Outlook?

It depends which Outlook you have. Microsoft states that in classic Outlook flagged messages appear in the To-Do Bar, in Tasks and in the Calendar Daily Task List. Flagged messages also appear automatically in the For Follow Up Search Folder. In new Outlook and on the web, the flagged mail is reachable through a filter on the message list. Microsoft To Do can also hold them in a Flagged email list, with two documented limits: it initially populates with the 100 most recently flagged emails from the last 30 days, and flagged mail from shared folders and shared mailboxes is not supported.

Can Outlook remind me if someone hasn’t replied?

No. The reminder fires on the date you chose, whatever the other person did, because a flag has no conditional field for Outlook to evaluate. The nearest built-in feature is manual: on a flagged sent message, Find related messages opens the Advanced Find dialog and searches for messages that are a response to it. Running it is on you to remember. Microsoft also notes that this is unavailable for an Exchange account whose sent items were moved to an Outlook Data File, either manually or with AutoArchive.

Should I flag emails for other people?

Sparingly, and knowing what they’ll actually see. Microsoft states that a flag for recipients puts a flag in their message list with text above the From line, and that an item is added to their to-do list only if the recipient is also using Outlook. Somebody reading in another client gets a line of text, and that’s all. Microsoft’s own guidance is to “use this feature with discretion” because some recipients might not appreciate having reminders added to their Outlook. Removing your flag later changes your own view only, and recipients still see the flag after you remove yours.

Do flags work on a shared mailbox?

The flag itself does, because it’s stored on the message rather than on a person. Everyone with access sees the same flag, and any of them can clear it. Who is handling the item stays outside the flag, since there’s no field for that. The documented limit is on the list. Microsoft states that only emails flagged from your primary mailbox sync with the Flagged email folder in To Do, and that flagged emails from shared folders and shared mailboxes are not supported, so a team’s flags on the firm address stay inside the mailbox.

The short version

• Flagging in one motion sets today as both the start date and the due date. A list where everything is due today carries one fact, repeated, and it stops being read.
• The right-click options are Today, Tomorrow, This Week, Next Week, No Date and Custom, and Microsoft publishes exactly what each sets. This Week means two days from now. No Date still schedules a reminder for today.
• A flag is four properties: start, due, completed, and a status with three values. What the message asked for, and the condition you’d like to attach, stay with you.
• Mark Complete keeps a struck-through record. Clear Flag leaves no record that the message was ever a to-do item. For a firm, that difference matters six months later.
• Reminders are local alarms. They depend on a client running and being allowed to interrupt, and they can be switched off for the whole profile by Group Policy.
• Flagging a message for a recipient writes into their to-do list only if they’re also in Outlook. It stays on their side after you remove yours, and it comes with Microsoft’s own advice to use it with discretion.
• Outlook watches the date you chose, and a silence on the thread passes it by. The bell rings the same either way.
• What a flag was standing in for is an obligation with a date and a condition attached. Point reads the message itself for that, puts the result onto the real Outlook items, and brings an open loop back before it goes cold, rather than when you happened to schedule it.