A to-do list in Microsoft Teams combines a personal checklist with shared task boards, and the simplest path is to use the built-in Tasks by Planner and To Do app for shared work or a private browser checklist for personal steps. Teams itself is a chat and meetings hub, so task management lives in connected apps rather than a single screen. Planner creates boards of buckets and cards for group work that several people update together, while Microsoft To Do syncs personal lists across signed-in devices. For team members who need a temporary, no-account checklist that stays in one browser, a small web-based to-do list adds an extra layer for individual preparation, packing lists, or step-by-step verification without touching the shared workspace. Both approaches carry real trade-offs around sharing, storage, and offline behavior, and choosing between them depends on whether the work belongs to one person or a group. This article explains how Teams handles tasks natively, when a browser checklist is the right tool, and exactly how to add, complete, delete, and clear tasks in the lightweight option.
Built-In To-Do List Options in Microsoft Teams
Microsoft Teams does not host a checklist directly inside a chat or channel by default. Instead, the platform connects to dedicated task apps that open alongside it. The two that show up most often are Planner and To Do.
Planner is the shared option. It presents a board with columns called buckets and cards that represent individual items. Several team members can move cards between buckets, attach files, leave comments, and assign items to specific people. A card can be opened to add a description, checklist items inside the card, labels, attachments, a start date, a due date, and a priority. That level of structure suits work where more than one person needs to see the same list and update it during the week.
To Do is the personal option inside the same Microsoft account. It keeps individual task lists that follow a signed-in user across devices, so a checklist started on a laptop appears in the Teams sidebar and on a phone. To Do works well for personal steps that support shared Planner boards, such as reviewing a deck before a meeting or following up on action items afterwards.
Together these two apps answer most of what people mean by a to-do list in Teams. The trade-off is that they require a Microsoft account, depend on a sync connection, and store everything in the cloud. Anyone who needs a quick, throwaway checklist that never leaves the current browser sits outside that model.
When a Personal Browser Checklist Fits Better
Some tasks are too small, too temporary, or too personal for a shared Planner board. A packing pass before a customer visit, a list of files to copy before a migration, or a step-by-step verification before publishing a release are good examples. Putting these into a shared board clutters the team view and adds permission questions that do not matter for a one-person job.
This is exactly the case the browser-based To-Do List is built for. It opens as a single page, accepts text, and keeps the list in the current browser profile through local storage. There is no sign-up, no account creation, and no upload to any server. The interface is a focused list rather than a project tracker, which makes it suitable for a personal checklist that supports team work without becoming part of it.
A useful rule is to keep shared work in Planner, personal follow-up in To Do, and throwaway personal steps in the browser checklist. Each tool then stays focused on what it does best, and the team space stays uncluttered.
Adding and Managing Tasks in the Browser To-Do List
The browser checklist has four concrete actions and one boundary worth understanding. Here is the full sequence from a blank page to a tidy list.
- Open the page and wait for the list area to enable itself. The page holds its interactive controls until local storage has finished reading, so a fresh profile briefly shows the input as inactive before the list is ready. This boundary protects any saved tasks from being overwritten by the initial empty state.
- Type one concrete task into the New task field and select Add, or simply press Enter. The field strips leading and trailing whitespace, rejects an entry that is entirely whitespace, and caps each task at 160 characters. A browser-generated identifier is attached so later edits stay stable.
- Use the checkbox beside a task to switch it between active and completed. The summary above the list updates both the total count and the number completed as items move between the two states. Reloading the page confirms that the list survives a refresh, since the browser stores the current state in a versioned localStorage record.
- Select Delete beside any task when it is no longer needed, or select Clear completed to remove every finished item in one action. Clear completed is disabled when nothing is finished, which prevents a click that would have no useful result. Both actions are immediate, so copy anything important elsewhere before removing it.
- Stay within the 100-task limit. Lists above the supported limit are rejected as a whole during restoration, so the page refuses to render a stored list that exceeds the cap. A dedicated task manager is the better fit for anything larger.
Writing Team Tasks That Actually Get Done
A to-do list is only as useful as the wording on each line. Broad goals such as "Proposal" or "Photos" leave the next action unclear, so they tend to sit on the list unchecked. Writing each entry as an observable next action turns the list into a real workflow.
The same principle applies inside Teams. A Planner card titled "Update the deck" is easier to finish than one titled "Marketing," because the next action is visible. A To Do item that says "Email Maria the revised proposal" can be marked complete only when the email has actually been sent. The same wording rule keeps a personal browser checklist honest: an entry that says "Back up photos to the external drive" is finished when the backup exists, not when the thought occurs. A deeper look at phrasing and review habits sits in the guide on using a to-do list effectively every day.
For a shared team list, it also helps to include the owner and the deadline on the card itself rather than relying on memory. For a personal browser checklist, the owner is always the person at the keyboard, and the deadline belongs in a real calendar rather than in a 160-character line that the tool deliberately does not parse.
Storage, Limits, and Privacy of the Browser Checklist
The browser tool stores every task in localStorage under a versioned key tied to the current browser profile. Nothing is uploaded to a server, and no account is attached to the data. That has clear practical consequences:
- The list does not follow you to another browser, another profile, a private window, or another device. Each of those starts empty unless it has its own localStorage record.
- Clearing site data, resetting the browser profile, or running a cleanup utility removes the list. Treat localStorage as a convenience rather than a backup system.
- Anyone who can use the same unlocked browser profile may be able to read the list. Browser extensions and device administrators can also reach page storage.
- The list does not encrypt entries. Do not store passwords, recovery codes, medical records, financial account details, or other secrets in it.
For important deadlines and irreplaceable project records, keep those in a dedicated task manager or another backed-up service. The browser tool's scope is deliberately small: a temporary personal checklist, a short shopping list, a packing pass, or a group of steps you are completing at one workstation.
Choosing Between Teams Tasks and a Browser List
Both approaches serve different jobs, and the right choice depends on who needs to see the list. The table below compares the main options on a few practical axes.
| Need | Tasks by Planner and To Do | Browser To-Do List |
|---|---|---|
| Shared board for several people | Yes, with cards in buckets | No, single profile only |
| Personal list that syncs across signed-in devices | Yes, through To Do | No, current browser profile only |
| Checklist that works without an account | No, requires sign-in | Yes, opens straight from the page |
| Dates, reminders, priorities, recurring work | Yes | No, deliberately out of scope |
| Offline access in the current browser | Limited, depends on sync state | Yes, restored from localStorage on reload |
| Maximum number of tasks | Designed for large projects | 100, enforced during restoration |
| Recovery after delete or clear | Through Microsoft account history | None, actions are immediate |
Use the shared option when another person must see updates, when missing a deadline would cause real harm, or when the work spans more than a few days. Use the browser checklist for throwaway steps that one person completes at a single workstation.
Moving Work Between the Two
A practical workflow is to keep long-running shared items in Planner, personal follow-up in To Do, and short-lived personal steps in the browser checklist. Once a personal step is finished, the browser list can be cleared and the result carried back into To Do or Planner as a card update, a comment, or a status change. The browser list stays a private scratchpad, and the shared tools stay focused on work that the team actually owns.
This pattern also fits the limits of the lightweight tool. With a 100-task cap and 160 characters per entry, the browser checklist is not a long-term project record. It is a focused place to capture, work through, and discard the small steps that surround a team task without weighing down the shared workspace.