What can go in the client-update draft?
A fictional supervisor asks for a short progress draft about five documents.
The question
The tracker appears to show four documents with sign-off. The exercise counts only approval for the exact version in the bundle. The supervisor reviews and sends the draft.
| Documents | |
|---|---|
| In the bundle | 5 |
| Showing sign-off | 4 |
Check each approval against the version in the bundle.
“Which facts can you include in the draft?”
Not saved by this site. Your browser may restore text when you navigate back.
A strong answer, step by step
Open each step in turn. This is one strong answer, not the only one.
Step 1: Check the bundle
What would you do here? Open the move you’d make.
Match each approval to the included version
The strong move. The exercise rule counts only the matching version.
Count each green status without checking its link
Tempting, but it misses something. The status alone does not identify the approved version.
Write that all five documents are ready
Tempting, but it misses something. The tracker already shows a document without sign-off.
See how a strong candidate says it
“The tracker shows four of five documents with sign-off. I’d confirm which version each approval covers.”
Why it works: The tracker gives a starting count. The version check determines the usable count.
Step 2: Draft the status
What would you do here? Open the move you’d make.
Separate the count, open checks and next update
The strong move. This gives the supervisor a factual progress draft.
Promise the bundle will be complete tomorrow
Tempting, but it misses something. The pending review gives no confirmed finish time.
Send the tracker as the full update
Tempting, but it misses something. The tracker leaves the version check and next action unclear.
See how a strong candidate says it
“I’d set out the current sign-offs, the pending checks and the next update. I’ll leave the timing commitment for the supervisor to review.”
Why it works: The reader can see what is complete and what needs action.
Step 3: Correct the count
One of the 4 approvals links to the previous version of its document. The current version has no sign-off. The other three approvals match their documents.
What would you do here? Open the move you’d make.
Report the three current approvals and two pending
The strong move. This removes the superseded approval from the count.
Keep four because the tracker still shows approval
Tempting, but it misses something. The linked approval applies to a previous version.
Treat the full bundle as approved when one new check passes
Tempting, but it misses something. Two documents now lack current sign-off.
See how a strong candidate says it
“One approval covers the previous version. That leaves 3 of 5 with current sign-off and 2 pending. I’ll flag the version mismatch to the supervisor.”
Why it works: Only the three matching approvals count under the exercise rule.
Step 4: Send for review
What would you do here? Open the move you’d make.
Give the factual draft to the supervisor
The strong move. The supervisor can review the facts and decide what to send.
Send the client a completion promise
Tempting, but it misses something. Two current versions remain pending.
Leave out the two pending documents
Tempting, but it misses something. The client update would then omit a material part of the bundle status.
See how a strong candidate says it
“My draft says, “Three documents have current sign-off. Two are pending. We will confirm the next update after the reviewer checks the current versions.” I’d send that draft to the supervisor for review.”
Why it works: The draft gives the verified count and keeps any external communication with the supervisor.
The answer, in short
- Decision
- Send a three-approved, two-pending draft for review.
- Because
- One approval refers to a previous version.
- What would change it
- Current sign-off for the two pending documents would change the count.
Common traps
- Use the approval for the exact version.
- Give the supervisor the pending count.
Check your answer
- I checked the tracker count.
- I matched approvals to versions.
- I corrected the pending count.
- I routed the draft for review.
Last reviewed Nov 11, 2026