Skip to article
BITTUMailPOWERED BY BITTU ICLOUD
The Mail BlogProductivity

A Method for Sorting Email by Action, Not by Sender

A practical method for sorting email into act, waiting, read, and reference groups, with a simple review routine to keep the system useful.

Paper folders, message cards and a clock arranged on a sage background.
Original BITTU Mail editorial artwork. Illustrative image.

A sender-based inbox can be hard to work through: a colleague’s note may need action, while a message from the same person may only need saving. Sorting by what you must do next gives each message a clearer place, regardless of who sent it. You can use labels or folders if your mail service provides them, or simply apply the categories during a manual inbox review. The method is not automatic sorting; you decide what each message means and update its category as the situation changes.

The useful bits

  • Choose one action category per message based on its next required step.
  • Move messages from waiting when a reply arrives or a follow-up becomes due.
  • Keep reference mail searchable without treating it as unfinished work.

Define the four outcomes before sorting

Use four plain-language categories: Act, Waiting, Read, and Reference. Act means you need to do something. Waiting means someone else has the next move, or you are expecting information before proceeding. Read means you have seen the message and do not need to act, but have not decided that it belongs in long-term reference. Reference means you may need to find it later, but it is not an open task.

Write a short definition for each category and keep it nearby while you begin. The point is consistency, not finding a perfect label for every unusual message. If a message does not fit neatly, choose the category that best describes its current status and make a note of any action you need to remember.

Choose one label by asking what happens next

Process each message with the same question: what is the next step, and who owns it? If you must reply, decide, send a file, or complete another task, classify it as Act. If you have already replied and now need someone else’s answer, use Waiting. If there is nothing to do and no reason to keep the message as a record, use Read. If it contains details you expect to consult again, use Reference.

Avoid assigning several categories just because a message could be useful in different ways. One primary status makes a review quicker. If you use folders rather than labels, move the message to its current category; if you use labels, apply the one that reflects its current state. The available controls depend on your mail service and account.

Keep action mail separate from your task list

Act is a useful inbox-processing category, but it is not a complete task manager. A message saying “Please review the draft” may need a real deadline and a specific next step. Record those details in the task system you actually use, then leave the message in Act if you want it as a prompt or move it to Reference if the task is tracked elsewhere.

Make the action specific enough to start: “reply to [person] about [topic]” is more useful than “handle email.” If the work will take time, do not rely on an unread marker or a vague folder name to remind you. Confirm that the task has been recorded somewhere you routinely check.

Treat Waiting as a state that changes

Waiting messages are easy to overlook because they do not demand an immediate reply. When you send a request or hand off work, place the related conversation in Waiting and note what response you expect. If the matter is time-sensitive, record when you plan to follow up in your calendar or task system rather than assuming the folder itself will alert you.

When a reply arrives, reassess the conversation. It may become Act if you now need to respond, Read if the exchange is finished, or Reference if the answer is worth keeping. This small state change prevents Waiting from turning into a permanent pile of old conversations.

Use a short, consistent review routine

Sort a manageable batch rather than trying to reorganize every old message at once. For each message, decide whether it needs an action, depends on someone else, is simply read, or should be retained for reference. Then apply the label or move it to the appropriate folder if those controls are available. If the next step is unclear, open the message and verify the request, dates, recipients, and any commitment before categorizing it.

At the end of the review, scan Act for items that need to become concrete tasks, then check Waiting for responses that may have arrived. You can use search to locate a sender, subject, or conversation when you need context; sender identity alone does not determine the category. In BITTU Mail, folders and search are available, though the exact controls may depend on account state.

EXAMPLE / ADAPT TO YOUR SITUATION
Message from [alex@example.com]: asks you to approve [draft]. → Act; record the approval task.
You reply to [alex@example.com] asking for [missing detail]. → Waiting; follow up if needed.
[alex@example.com] sends the detail and you approve it. → Read, unless the final decision should be kept.
Message from [billing@example.com]: contains [receipt number] for your records. → Reference.

Check whether the system is helping

After a few review sessions, check whether Act mostly contains genuine next steps and whether Waiting contains conversations where someone else has the next move. Look for messages that have stayed in a category after their status changed. Move them rather than creating extra categories to explain the mismatch.

The method is working if you can scan the groups and answer two questions quickly: what do I need to do, and what am I waiting for? If those answers are unclear, simplify the category definitions or make task details more explicit. The categories organize your decisions; they do not sort messages automatically or guarantee that you will not miss a deadline.

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