In this Article:
Try Kanbanchi now
Start your free trial

Outlook project tracking usually starts from a simple observation: most work does not begin on a board. It begins as an email.
A client asks for a revised proposal. A colleague forwards something with “can you take a look?” A supplier confirms a date that changes your schedule. By the time any of it reaches a project tool, somebody has already read it, decided it matters, and made a choice about what to do next.
Outlook is very good at the first part of that. It is not built for the rest, and most of the friction teams blame on Outlook comes from asking it to do a job it was never designed for.
This article covers what Outlook genuinely handles, where it stops, and how to get work out of the inbox and into something that can be tracked.
Three tools, and it is worth being precise about what each one does.
Flags mark an email for follow-up. A flagged message appears in your task list and, depending on your setup, in a follow-up view in Outlook. This is real and useful, but it is yours alone.
Categories color-code messages by whatever scheme you invent. Client, urgent, waiting, project name. Genuinely handy for personal triage.
Microsoft To Do is where Outlook’s task functionality now lives, and it syncs with flagged emails. You get a personal task list with due dates and reminders, connected to the messages that generated it.
All three work well. All three share the same limit: they are personal. Your flags are invisible to your colleagues. Categories exist only in your mailbox. Your task list is your own.
For an individual managing their own follow-ups, that is exactly right. For a team trying to see who owns what, it is the whole problem.
Outlook project tracking does not fail because flags are broken. It fails because a flagged inbox answers a different question from the one a team needs answered.
1. Nobody else can see it. If you flag a client request and then go on holiday, that request is not visible to anyone. It is not delayed; it is invisible.
2. There is no owner beyond you. An email you have flagged is work you have implicitly accepted. There is no mechanism to assign it, hand it off, or make it clear that someone else is now responsible.
3. There is no status. A flag has two states: flagged and not flagged. It cannot tell you whether the work has started, whether it is waiting on someone, or whether it is blocked.
4. The context stays in the thread. The decision that changed the deadline is in message seven of a twelve-message chain that only three people were copied on.
Each of those is survivable alone. Together they are why a team’s real project status ends up being reconstructed in a meeting rather than read off a screen.
No. Outlook has no native Kanban view, and there is no setting that turns your inbox or your task list into columns. This is the main gap in Outlook project tracking for teams who think in boards.
It surprises people, because Microsoft does have Kanban boards, just not in Outlook. Microsoft Planner provides them, and Planner boards can be surfaced inside Microsoft Teams. Neither of those is inside Outlook, which means switching applications to see the board.

A Kanban board in Microsoft Planner
There are three practical routes if you want a board and you work primarily in email:
1. Use Planner or Teams alongside Outlook. Works, but the board and the inbox stay separate. Somebody has to move work between them manually, and that somebody usually forgets.
2. Add-ins. Various third-party tools offer Outlook add-ins that create tasks or cards from a message without leaving the app. Quality and support vary considerably. Check whether the one you are considering supports the new Outlook as well as the classic client.
3. A board email address. Some project tools give each board its own email address. Forward a message there, and it becomes a card, with the subject as the title and the body as the description. This works with any email client, needs no add-in, and can be handed to people outside your organization without giving them access to the board.
If your team’s work genuinely arrives by email, the third option tends to be the most robust, because it does not depend on everyone having the same add-in installed.
For a wider look at Kanban options across Microsoft’s tools, see “Does Microsoft have a Kanban board?”
The mechanics matter less than the rule around them. Whatever route you choose, one decision does most of the work:
If an email creates work with an owner and a deadline, it stops being an email.
That sounds obvious and is routinely ignored. Leaving it flagged, meaning to deal with it, or replying “will do” is how requests disappear. Not because anyone is careless, but because an inbox is a stream and a stream has no memory of what you promised on Tuesday.
Three habits make the rule stick:
Convert at the point of reading. The moment you decide something is work, make it a task. Not later, not at the end of the day. The context is in your head now, and it will not be in an hour.
Carry the context across. A card that says “reply to client” is barely better than the flag. The card should carry what was asked, by when, and the thread it came from, so someone else could pick it up.
Reply from the task, not the inbox. Once the work is tracked, the conversation about it belongs with the work. Otherwise you have two records that disagree.
Our guide to team task management goes further into what a task needs to carry to be readable by someone who was not in the original thread.
Two questions that come up often enough to answer directly.
Time tracking. Outlook has no built-in time tracker. It has a calendar, which records what you scheduled rather than what you spent. If you need to compare estimates against actual effort, that lives in a project tool, ideally attached to the task rather than in a separate timesheet.
Gantt charts. Outlook has no timeline view. The calendar shows appointments, not project schedules with dependencies. If you need to see whether a delay in one task affects a later deadline, that is a project tool question. See Gantt vs Kanban if you are deciding which view your work actually needs.
Neither gap is a criticism of Outlook. It is an email client that grew a calendar, not a project platform.
Kanbanchi sits on the other side of that handoff: it is where the work goes once it stops being an email.

Kanbanchi interface example when using Microsoft environment
Boards hold cards with owners, dates, priorities, checklists, and attachments. The same cards appear on a Gantt chart when you need to see the schedule rather than the flow, and time can be tracked on the card itself. For teams on Microsoft 365, you can sign in with your Microsoft account and attach files from OneDrive.
Turning emails in Outlook to the task cards in Kanbanchi is super easy: save the board address as the email address and forward emails there. The point is not that Outlook should be replaced. It is that email should stop being the place where commitments are stored.
Only at a personal level. Flags, categories, and Microsoft To Do let one person manage their own follow-ups, and they do that well. What Outlook cannot do is show a team who owns what, what stage each piece of work is at, or whether a deadline is still realistic. Because flags and categories are visible only to the person who set them.
No. Outlook has no native Kanban view. Microsoft Planner provides Kanban boards and can be surfaced in Microsoft Teams, but not inside Outlook itself. To get a board connected to email, you need either a third-party add-in or a tool with a board email address that turns forwarded messages into cards.
Flagging a message adds it to your Microsoft To Do list, which is enough for personal follow-ups. For work that needs an owner, a status, and team visibility, you need to create a task in a project tool. For example, by forwarding the message to a board email address that converts it into a card.
No. Outlook has a calendar, which records scheduled time rather than time spent. Comparing estimated against actual effort requires a tool with a timer attached to the task.
No. Outlook’s calendar shows appointments, not a project timeline with dependencies. A Gantt view needs a project management tool.
Microsoft has progressively consolidated Outlook’s task functionality into Microsoft To Do, which now serves as the task list for flagged emails and personal to-dos across Microsoft 365. Both remain personal rather than shared. Neither gives a team visibility into who owns what.
Outlook is where work arrives. That is not a flaw; it is what an email client is for, and no amount of flagging turns a stream of messages into a system of record.
Outlook project tracking works best when you accept its scope. The change worth making is small and specific: when an email creates work that has an owner and a deadline, move it somewhere it can be seen, assigned, and finished. Everything else about tracking gets easier once that one habit holds.
Related article: How to Be More Effective with Task Management Software
In this Article:
Start using Kanbanchi now
Start your free trial