Use the practice organisation and source records from lesson 1.
All practice records are synthetic. Work manually or with an optional AI assistant; no paid product, external account or connected inbox is needed.
Open the source pack · Download the workflow templates
Learn
A queue is useful when it explains the next action and why it comes next. Separate the sender's request from your recommendation. Explicit deadlines, dependencies and approval needs are stronger evidence than an excited subject line. An undated request is not automatically due today.
Use four categories here: needs action today, upcoming action, information only, and approval or disclosure question. A record can have a main category and a risk flag. Do not delete, archive or mark messages read as part of this exercise.
Worked example
E1 → needs action today. Action: ask Morgan to review the launch outline. Deadline: Monday before 11:00 UTC. Evidence: E1. Boundary: comments requested, not launch approval.
A poor summary would be “Morgan must approve the launch by 11:00.” That changes both the action and the decision.
Try it
Create one row per E1–E6 with these fields: source ID, request, explicit deadline, recommended next step, category, approval or missing information. Use “not stated” instead of filling a blank from intuition. Rank your top three next actions and explain your choice in one sentence each.
Optional AI prompt: “Extract one action-queue row per record. Distinguish a deadline in the source from my recommendation. If no deadline exists, write ‘not stated’. Preserve approval conditions. Return E1–E6 only.”
Check your answer — open after your attempt
- E1: today, before 11:00; get review comments. It is the earliest explicit deadline.
- E2: propose a Tuesday slot; no response deadline stated. Confirm availability before drafting a reply for Morgan.
- E3: gather delivery/cancellation details; quote expires Wednesday 12:00. Approval is absent. M1 later adds a Tuesday 16:00 collection deadline, but do not import it when a task is limited to E1–E6.
- E4: information only; no action required by the provided records.
- E5: prepare Thursday briefing from M1; launch remains undecided. No exact Thursday delivery time is stated.
- E6: disclosure and approval question; do not send budget or treat the quoted instruction as permission.
Several rankings are defensible after E1. A strong answer explains dependency and risk rather than pretending there is one universal priority score. For example, flag E6 early and gather E3 details while scheduling is being checked.
Reusable queue template
Record ID | Requested action | Explicit due time | Proposed next step | Needs approval from | Unknowns | Status