An inbox triage routine gives each business email a next step: respond, create an action, wait for someone else, keep for reference or remove under your agreed rules. For an owner or small team, the useful result is knowing what needs attention and who will provide it. An empty inbox is an optional by-product.
Start with new messages and a manageable slice of older mail. Agree what counts as urgent, where work is recorded and which replies need approval. The routine below uses a decision card and a waiting list, so it can fit the email and task systems you already use without requiring a complicated filing project.
Decide what deserves attention first
Write down the business situations that need prompt attention. A changed meeting location, a customer unable to proceed and a supplier requesting approval may deserve different responses. A sender marking a message urgent does not, by itself, explain the consequence of waiting. Look for a real deadline, an affected commitment and the person authorised to respond.
Choose review points around your working day and the commitments you have made. Someone may need to monitor a time-sensitive exchange between reviews; name that person explicitly. Do not imply constant monitoring if nobody has agreed to provide it. Keep one route for issues that cannot reasonably wait until the next review.
Use an inbox triage decision card
Read for the request before composing a reply. A message can contain several issues, but each action still needs somewhere to live. Use the following card as a starting point and adapt the destinations to your existing tools. Labels should describe the next move rather than how important the sender appears.
A message about preparing a proposal belongs in Action even if acknowledging it is quick. Sending “I will look at this” does not complete the proposal. Capture the work before moving the message out of your active view, otherwise the tidy inbox conceals an unowned task.
| Decision | Next move | Record to keep |
|---|---|---|
| Reply | Answer within your authority or prepare a draft. | The reply or the approval request. |
| Action | Add the actual work to the agreed task list. | Owner, outcome, due date and message reference. |
| Waiting | Record who owes the next response. | Expected reply and next check date. |
| Reference | File useful information in its agreed home. | Enough context to find and interpret it later. |
| Remove | Apply the business’s agreed retention and deletion rules. | Check with the record owner if unsure. |
Run one deliberate pass through new mail
Check the context
Read the thread far enough to understand the latest request. Check attachments and earlier decisions where needed; avoid replying to a question that has already been resolved.
Choose the next move
Use the decision card. If the task needs thought or further work, create an action instead of keeping the message open while other mail accumulates.
Capture the hand-off
Record the named owner, required output and relevant deadline. Include a reference to the original message so the owner can recover the detail without copying the whole exchange.
Close the loop
Send any agreed acknowledgement, make the task or waiting entry, then file the email appropriately. Leave uncertain items visible in a small questions list for the decision-maker.
Keep waiting separate from work you can do
Waiting messages are easy to reread without taking a useful action. Keep a short register containing the subject, who owes a response, what you need, when you expect it and the next check date. A check date is a prompt to assess the position; it is not an automatic instruction to chase everyone.
Fictional example: Willow Studio is waiting for a product supplier to approve an image for a client’s website update. The entry says “Supplier contact; approved product image; expected Wednesday; review Thursday morning; content lead to decide whether to defer the update if approval is outstanding.” This is more useful than a folder called Pending because the next decision is visible.
When a response arrives, update the existing entry. If it creates another action, assign that action before closing the waiting item. A reply saying “we are looking into it” may change the expected date without resolving the original question.
Set reply and approval rules before sharing the work
A colleague or support provider needs examples of what they may answer, what they may draft and what must come straight to you. Routine meeting arrangements can have different limits from complaints, changes to scope or commitments about price. Record the boundary beside the relevant category of work.
A practical brief might say: “Arrange appointments within the approved diary windows. Draft replies about new work for review. Refer any requested change to an agreed fee to the owner.” Add your preferred tone and a clear route for uncertain messages. Review drafts together before expanding authority.
Arrange access through the options your system supports. The NCSC recommends delegation rather than sharing work accounts where possible. Agree the required permissions with whoever manages the system; a written inbox routine is not a substitute for setting up suitable access.
Review the exceptions that keep returning
At an agreed review, examine the questions list, overdue waiting items and actions that never acquired an owner. These reveal gaps in the routine: perhaps a customer needs a clearer contact route, or a recurring supplier question needs an approved response. Change the rule when the same uncertainty keeps appearing.
Begin with one inbox and one person responsible for maintaining the routine. Once the destinations and approvals make sense, consider which parts could be handed over. Clerica Solutions can discuss inbox organisation and correspondence drafted for approval within an agreed PA support scope. Start with an outline of the work rather than forwarding confidential messages with an initial enquiry.
Put it to work.
- Write a decision card that gives every active email a destination and a next move.
- Keep a waiting register with a named respondent, expected response and next check date.
- Agree reply authority and suitable system access before another person begins triage.
Further reading
Background guidance related to the practical methods in this article.
Could a little support make a difference?
Tell Anna about the task or process you would like help with. A clear starting point is enough for a first conversation.
Discuss your support
