A shared mailbox can accumulate folders faster than a team can agree what they mean. One person files a customer request under “Urgent,” another uses “Support,” and the next teammate cannot tell whether a message needs a reply or is simply being stored. The solution is not a complicated filing system. It is a short set of folder purposes, clear responsibility for moving messages, and a decision rule for items that seem to belong in more than one place. Agree on those rules before reorganizing, then try them on real messages together.
The useful bits
- Create folders for distinct work states or subjects, not vague labels.
- Name who files messages and when; do not assume everyone will do it.
- Choose one primary folder for overlap and use a consistent exception rule.
Start with the questions the folders should answer
Before creating or renaming folders, ask what teammates need to find quickly. A folder may help answer “Who still owes us a reply?”, “Which requests are waiting on us?” or “Where are completed records kept?” If two proposed folders answer the same question, combine them or distinguish their purposes explicitly.
Keep the first version small enough that a teammate can choose a folder without asking. Avoid labels such as “Miscellaneous” or “Important” unless the team defines exactly what qualifies and why the folder is useful. A folder should have a job, not merely capture a feeling about a message.
Write a one-sentence purpose for each folder
Describe each folder in plain language: what belongs there, and what does not. For example, “Waiting on customer” could hold messages where the team has asked a question and cannot proceed until the customer responds. It would not hold messages awaiting an internal decision.
Choose names that make those distinctions visible. If “Open” could mean either “we need to reply” or “someone else needs to reply,” rename it or split the work states. The goal is not to record every detail of a conversation in the folder name. It is to help the next person understand the message’s current status.
Waiting on us — A response or action from our team is still needed. Waiting on customer — We have asked for information and cannot proceed until it arrives. Reference — No action is pending; keep the message for lookup.
Assign filing responsibility and a moment to do it
Decide who is expected to move a message and when. For example, the teammate who handles a request could file it after taking ownership, then update its folder if responsibility changes. Alternatively, the person who sends a reply could file the message after sending. Choose one approach the team can follow consistently rather than relying on an unspoken assumption.
Set a practical trigger: when someone takes the message, after a reply, or during a defined handoff. State who handles unassigned messages and what to do when that person is unavailable. Filing should reflect a real work state; it should not replace telling a teammate that a message needs their attention.
Resolve overlap with a primary-purpose rule
Some messages concern several subjects or have both a topic and an action status. Agree that one folder represents the primary reason someone will look for the message. A status folder may take priority while work is active; after the work is complete, the team may move the message to a reference folder if that is how the group retrieves records.
If the team has a clear, permitted way to make a message findable without filing it twice, it can use that method consistently. Otherwise, choose one home and make the rule explicit. Do not assume that a folder system supports duplicate placement or that every teammate can change its organization; available actions can depend on account role and setup.
A customer asks about an invoice and the team needs to confirm a detail. While the team is waiting for that confirmation, file it under “Waiting on us” if the next action belongs to the team. If the team asks the customer for a missing document, use “Waiting on customer.” The invoice topic can remain in the subject or be found with search rather than creating a second competing home.
Make exceptions easy to handle
Agree what to do when a message does not fit, or when its status is unclear. A short-lived holding folder can help only if someone owns reviewing it and moving each item. Otherwise, it becomes a permanent pile with a reassuring name. If no holding folder is needed, ask the responsible teammate to choose the closest primary purpose and flag unclear cases for the team’s next check-in.
Also decide how to treat a conversation that changes state. When a reply arrives, the previous folder may no longer describe the current work. The person handling the new message should move it according to the same rules, or leave it where it is only if the team has agreed that the folder represents the whole conversation’s history rather than its current status.
Try the rules on a small set of messages
Before applying the system across the mailbox, review a small set of recent messages together. For each one, ask: what is its primary purpose, who owns the next action, and which folder should hold it now? If teammates make different choices, revise the definitions rather than treating the disagreement as a filing mistake.
Confirm the rules are working by checking whether another teammate can locate a message and explain why it is in that folder. Look for items left in a temporary location, folders that collect unrelated work, and messages whose status no longer matches their location. Adjust names or responsibilities when those patterns appear, and tell the team what changed.
- Can a teammate explain each folder’s purpose in one sentence?
- Is there a named owner and a clear filing moment for active messages?
- Does every overlap have a consistent primary-folder decision?
- Can someone else find a sample message and understand its current status?
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction