Monday Morning Inbox Triage with a 10:00 Deadline
It is 09:15 on Monday. You are covering the mail and inbox for a licensing team, and you have your own fixed task: the weekly register must reach the finance officer by 10:00 and takes about 30 minutes of uninterrupted work. Six items are open:
- A voicemail from a licensee: her certificate has not arrived and her premises open at 17:00 today.
- An email from finance asking for a one-line confirmation that the register will arrive by 10:00.
- A freedom-of-information request logged on Friday, with the statutory reply due in 18 working days.
- A colleague's request for you to approve 3 days' leave starting Wednesday.
- A courier at reception with a signed-for package for the team, unopened.
- A second voicemail: a member of the public asking whether a named local business holds a licence. Team policy is not to confirm licence details by phone to unverified callers.
1. Sequence all six items across the next 45 minutes, showing how the timing works.
Read the worked answer
Sequence: 2 → 1 → 5 → register (own deadline) → 4 → 3 → 6.
Timing:
- 09:15, item 2 (2 minutes): a one-line reply unblocks someone else and costs almost nothing; withholding it while you work invites a chase call at 09:55.
- 09:17, item 1 (8 minutes): check the system, establish whether the certificate was issued, and tell the licensee what happens next before 17:00. This is the only item with a same-day external consequence.
- 09:25, item 5 (3 minutes): sign for and log the package; that releases the courier and takes a minute, whereas leaving it makes it someone else's problem later.
- 09:28, register (30 minutes): protected block; aim to send by 09:58 so there is slack before 10:00.
- After 10:00: item 4 (needs manager judgement anyway), item 3 (18 working days - log and diarise today, do not draft today), item 6 (see below).
Criteria: fixed external deadline first among equals, then someone else's blocker, then tiny unblocking actions, then protect your own hard deadline, then items that are safe to defer.
2. What do you do with item 6, and what wording would you use?
Read the worked answer
Do not confirm the licence details, and do not simply hang up.
The policy exists because a phone caller's identity cannot be verified, and confirming who holds a licence releases personal and commercial information to an unknown person. Two calls to two different numbers can be used to map a business's details.
Wording: "I can't confirm licence details over the phone because I can't verify who I'm speaking to. I can tell you how to check publicly: the licence register is available on request, and if you put your question in writing or by email I can send you the correct route." Then take the caller's details for a written reply if they want one.
Two traps: giving a "soft" confirmation ("I couldn't possibly comment, but you're right") leaks the answer; and refusing with no alternative makes a compliant refusal look like poor service. Note the request itself should be logged.
3. Which single item can safely wait until after 10:00, and which needs a decision today even though it has a long deadline? Explain the difference.
Read the worked answer
Safe to wait: item 4 (leave request). It starts Wednesday, no action is possible without the manager, and a few hours' delay changes nothing. Item 3 is also not due today, but see below.
Needs action today despite its long deadline: item 3 (the freedom-of-information request).
The difference is not the deadline date but what the deadline depends on:
- The 18 working days run from receipt, and the work needed - locating records, deciding what can be released, possibly consulting a third party - takes far longer than the reply itself. Diarising it today costs two minutes and starts the clock properly; discovering it in week three is the classic failure mode.
- By contrast, item 4 has no preparatory work that an early start would protect.
So: item 4 can wait; item 3 must at least be logged, acknowledged and diarised today. Treating "long deadline" as "no action needed" is the reasoning error this tests.