Some messages look simple in the inbox but contain work that cannot be finished in one sitting: compare several proposals, assemble a careful response, or coordinate details with other people. Leaving such a message unread or starring it may keep it in view, but it does not decide what to do, when to do it, or how to tell whether it is moving forward. A useful plan gives the work a clear next action, a realistic time estimate, and a review date. You can then return to the message with a specific purpose instead of repeatedly wondering where to begin.
The useful bits
- Write down the smallest useful next action, not just “handle this email.”
- Estimate focused work time and schedule it separately from the review date.
- At review, update the plan or close the task; do not rely on visibility alone.
Separate the message from the work
An email is a container for information and requests; it is not automatically a workable task. A message asking for a detailed proposal may require checking figures, confirming availability, and drafting a response. Keeping it visible helps you find it again, but visibility does not reserve time or identify which of those actions comes first.
Start by stating the outcome the sender needs and what is stopping you from delivering it now. If you cannot complete the whole request, identify the next action that would make progress possible. This turns a broad obligation into a task you can begin, even if the final reply must wait.
Choose a next action you can actually start
Use a verb and name the object of the work: “compare the two draft schedules” is more actionable than “work on the schedule.” Keep the step small enough that you can tell when it is done. If it depends on someone else, make the next action something within your control, such as preparing the questions you need to send.
Avoid putting the entire request into the next-action field. “Finish the proposal” may conceal several separate steps. If the first step reveals more work, record that follow-up then. The plan can evolve; its immediate purpose is to make starting straightforward.
Message: Please send a proposal covering [scope], [timing], and [budget]. Next action: Gather the current [scope] notes and list missing details. After that: Check [budget] with [contact], then draft the reply.
Estimate effort, not elapsed waiting time
Estimate how much focused work the next action will take, rather than how long the whole request might remain open. A short review of notes and a draft may fit one work block; waiting for a colleague’s answer does not count as focused effort. If the task contains distinct pieces, estimate them separately so you can schedule a realistic first session.
An estimate is a planning aid, not a promise. If you are unsure, choose a modest first block and define what you expect to finish in it. After working, compare the estimate with what happened and revise the remaining plan. This is more useful than repeatedly postponing a large, vague task.
Set two dates with different jobs
Choose a work time for the next action and a review date for checking the task’s state. They may be the same day, but they answer different questions: when will you do the work, and when will you verify what should happen next? Put the work block where you manage your schedule, and record the review date somewhere you will revisit alongside the message.
Set the review date based on the next dependency or commitment, not simply because the message is still visible. If you are waiting for information, review when you need to check for it or decide on a follow-up. If a reply is due by a particular date, plan enough time before then to finish and send it.
Keep a compact plan with the message
Use a task list, calendar note, or another system you already check. Include a short reference to the email, the next action, the effort estimate, and the review date. The message can remain available in your mail folders or through search, but do not assume that an unread state, flag, or visible position records the full plan.
Keep the note brief enough to scan. If the work changes, update the action and date rather than leaving an outdated reminder beside the message. Where a task involves sensitive details, avoid copying more email content into another system than you need to identify the work.
Email: [sender] — [proposal request] Next action: Compare [option A] and [option B] Effort: [one focused work block] Work time: [scheduled time] Review: [date to check progress or next dependency]
Use the review to make a decision
When the review date arrives, open the message and compare the plan with the current situation. If the action is complete, record the next step, send the response if it is ready, or close the task. If someone else needs to reply, decide whether to wait, follow up, or revise the deadline. If the estimate was too small, break the remaining work into another clear action and schedule it.
A quick confirmation is that you can answer three questions without rereading the whole thread: What happens next? When will I work on it? When will I check it again? If one answer is missing, the message may be visible, but the plan still needs work. The goal is not to keep every email in sight; it is to make important work return at a useful moment.
- Next action is specific and under your control.
- Effort estimate describes focused work, not waiting.
- Review date has a reason and an intended decision.
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