eduKate Yishun · Learning and the next step forward
Find a useful starting point
Choose the question closest to your situation, or read the full guide in order.
Browse all chapters · Explore recovery and transformation · Explore the learning library
A useful work status update tells the reader what is true now, what remains unfinished and whether a decision is needed. It connects that decision to a particular task, with enough evidence for the reader to respond. “Working on it” describes activity. “Eight entries are checked; two need a room choice from the coordinator” describes a position someone can use.
To write a clear status update, identify the current task and version, separate verified progress from remaining work, explain any specific blocker, and ask the appropriate person for one concrete decision. Keep responsibility for your task visible. Requesting information or a choice does not mean that someone else has taken over the work.
This guide concerns ordinary work such as preparing activity lists, club booklets and presentation materials. It gives you a short update structure, two complete worked examples and a different case to practise independently. All organisations, people, records, messages and outcomes below are fictional teaching examples created for this article.
Find your next step in about 50 seconds
- You need a usable update now: begin with the short structure.
- Your message contains plenty of activity but little evidence: check the current record and meaningful completion.
- You need another person’s decision: clarify the remaining work and the request.
- You want complete examples: follow the activity index and the booklet.
- You want to practise: try the independent slide task, then inspect the reasoned answer.
Contents
Chapters 1–5 · Give the reader a useful position before the detail
Chapters 6–10 · Ask for a decision that has a clear consequence
Chapters 11–15 · Worked case: repair a misleading readiness claim
Start with the task and its present state. The reader should not need to reconstruct those from a list of yesterday’s actions. A useful opening might be: “The ten-entry activity index is still in preparation. Six entries have passed the agreed checks; four remain unfinished.” That sentence supplies a task, a boundary and a current position.
Follow with the evidence that matters to the next decision. Name the working file or record and the time checked. Then explain the unfinished portion. Four unfinished entries might include two drafts you can complete yourself and two entries waiting for a coordinator’s room choice. The distinction tells the reader what their response can actually unblock.
Use this adaptable structure:
Task and snapshot: What result am I preparing, in which version, checked when?
Verified position: What has met the agreed requirement, and what evidence establishes that?
Remaining work: What can I do next, and what is waiting for something specific?
Decision requested: Who can decide what, using which information, and when is the answer needed for the current plan?
My next action: What responsibility do I retain, and when will I report again?
You do not need five headings in every message. A short task may fit into four sentences. Keep the distinctions even when you remove the labels. “Please advise” cannot replace a decision request if the reader has to guess what advice would help.
Put the central issue early. If an unresolved choice prevents completion, do not bury it beneath a cheerful account of formatting improvements. Equally, do not describe the entire task as stopped when useful work can continue. A truthful update can say both that two entries are waiting and that you are completing two others.
The result should help someone understand the task without reading your entire working history. Keep supporting records available for inspection, but select the details that explain the current position. For a wider view of how this fits everyday operational repair, use Business Turnaround and Rebuilding.
Before writing, name the recipient’s role in this particular task. A coordinator may choose the activity location. A colleague may know where the current file is stored. A meeting organiser may only collect updates. Those roles do not carry the same authority, even when all three people appear in the same conversation.
Purdue OWL’s audience guidance asks writers to consider readers’ differing needs and expectations.
For a status update, make that consideration practical. What does this reader already know? What choice belongs to them? What evidence do they need to make it? If they are only recording progress, provide the current state and identify the person from whom a decision has been requested. Do not ask them to approve something outside their role.
A recipient may need no decision at all. “The cover is checked, the contents page remains in draft, and I will review it this afternoon” can be a complete informational update. Adding an artificial request for approval creates unnecessary ambiguity about whether ordinary work may continue.
When a decision is needed, separate it from a general request for help. “Can you help with the booklet?” could mean checking wording, choosing a timetable, completing a page or taking over the assignment. “Please confirm whether the contact panel should use option A or option B; I will insert the selected wording” identifies a choice while keeping the work with its current owner.
Do not invent authority from silence or seniority. If you do not know who owns the choice, ask who can confirm it. You can still report the verified state and continue unaffected work. Unknown authority is a missing part of the arrangement, not permission to choose whichever answer makes the status look better.
Keep the request small enough to answer. A message asking someone to approve a title, choose a room, change the date and resolve a missing file may involve several different roles. Separate the decisions where necessary, while maintaining one accurate account of the task. Each recipient should understand what you need from them and what remains your responsibility.
If the task itself has changed and the expected result is unclear, first use How to Clarify New Expectations Before Changing Your Approach. An update cannot make an undefined requirement reliably complete.
A status is a statement about a particular moment. “The timetable is checked” may have been true before a revised timetable arrived. Include a snapshot time when the work can change between messages, and identify the task record against which you checked it. The reader can then distinguish your observation from something that may have happened later.
Use the version identifier people actually use. “Activity index I3, checked Tuesday at 11:00 against schedule S7” is more useful than “latest file”. If you cannot establish which schedule is current, say so. Opening the most recently downloaded attachment does not by itself establish that it is the approved reference.
Keep three kinds of statement separate. A fact is supported by the record you inspected: “Entries A01–A06 match schedule S7.” An inference interprets facts: “The two missing room choices may prevent the full index being finished by the target.” An unknown remains unanswered: “The room for A09 is not yet confirmed in S7.” These statements have different strengths.
You may reasonably include an inference if you label its conditions. “If the room choices remain unresolved, I cannot finish those two entries” follows directly from a requirement to include a confirmed room. “The coordinator is delaying the project” adds a claim about a person and the wider cause that the record may not establish.
Preserve the difference between checking a source and receiving a message. A colleague might write that a location has changed. Until you know whether that message is the agreed authority for the location, report the message as information needing confirmation. Do not quietly promote it into the current schedule because it sounds plausible.
Your record need not be elaborate. A file identifier, a timestamp, the agreed requirement and a short list of item states can be enough. Keep the evidence retrievable so a reader can inspect a disputed detail. Avoid pasting a long conversation when a precise reference and a short explanation identify the relevant point.
Finally, check that the record and the message describe the same moment. If you revise two entries after drafting the update, either refresh the counts and snapshot or send the earlier statement clearly dated as such. Mixing fresh commentary with stale totals gives the appearance of a current account without its reliability.
Work counts as complete when it satisfies the requirement that matters for the task. Typing an entry is different from checking it. Inserting four components into a booklet is different from confirming that all four contain current information. A useful update names the relevant state rather than using “done” for every action.
Suppose an index entry requires a title, an activity code and a confirmed room code, all checked against schedule S7. An entry containing all three fields but an unconfirmed room code remains unfinished. It may be nearly ready in an everyday sense, but the missing confirmation is still part of the required result.
Use counts when the items and states are clear. “Six checked, two drafts and two waiting for room choices, out of ten entries” is understandable because the categories do not overlap. If you say “eight drafted and six checked”, explain whether the six are included in the eight. Otherwise a reader might wrongly add the numbers.
Avoid turning a count into an unsupported estimate of total effort. Six checked entries out of ten means six of those entries have passed the stated check. It does not establish that sixty per cent of all work is complete. The remaining entries may be harder, and final assembly may still be required.
Elapsed time is another separate measure. Two hours used from a four-hour working period means half the planned period has passed. It says nothing by itself about how much of the result is complete. Report time when it matters to a decision, but do not use the clock as a substitute for inspecting the work.
A completion check can also become outdated. If a revised brief changes the required information on one page, the previous check does not automatically remain valid. Keep any still-valid checks, and identify exactly which parts need examination again. Starting everything from zero can conceal useful progress; preserving every old tick can conceal a real gap.
For repeated tasks, a stable checking aid may help you establish consistent evidence. How to Build a Checklist That Prevents Repeated Mistakes covers that separate job. In the update itself, explain what the check establishes and name any exception that changes the current decision.
Remaining work includes everything still needed for the agreed result. A blocker is a particular unmet condition preventing a particular action. Confusing the two can make ordinary unfinished work sound like an external problem, or make a real dependency disappear inside a general to-do list.
Atlassian’s status report guide recommends making current obstacles and upcoming actions clear.
For each unfinished part, ask what can happen next. A draft that needs proofreading is work you may be able to continue. A room field requiring the coordinator’s choice cannot be completed accurately until that choice is available. Both parts are unfinished, but only the second depends on the requested decision.
Describe a blocker with a dependency sentence: “I cannot finalise entries A09 and A10 because their required room codes are undecided.” This is more useful than “Waiting on people.” It identifies the affected items, the missing input and the action that cannot yet be completed. It does not speculate about another person’s effort or intentions.
Then state the unaffected action: “I am checking A07 and A08 while that decision is pending.” This shows how the task will continue without pretending the missing choice has been solved. If genuinely nothing useful can proceed, say what condition must change before work resumes.
Do not list a final verification step as blocked merely because you have not reached it. The final PDF preview may follow entry completion as part of the ordinary sequence. You can report that it remains to be done. The specific external dependency is still the unresolved room choice, rather than every later step in the workflow.
A useful update also identifies what a response will not solve. Receiving the room choices allows two entries to be completed; it does not instantly check those entries, assemble the index and verify the resulting file. Name those remaining actions so the reader does not mistake their answer for immediate task completion.
If your difficulty concerns choosing among several unfinished tasks, review the unfinished work before drafting the message. That review helps determine what deserves attention next. Here, the purpose is to communicate the position of the selected task accurately enough for another person to decide or stay informed.
A decision request should tell the reader what to decide, what information supports the choice and what their answer changes. “Please advise urgently” supplies none of those reliably. A better request names the open field and the recipient’s authority: “As the coordinator responsible for room allocation, please confirm the room codes for A09 and A10.”
Supply genuine options only when the record establishes them. If the coordinator can choose either R2 or R3, and both are authorised options for this fictional task, you can list them. If you do not know the available rooms, ask for the confirmed codes. Inventing two convenient options may make the question easier to read but harder to answer correctly.
Explain why a response time matters. “Please confirm by 13:00 so I can complete the entries and perform the remaining checks before the 16:00 target” makes the relationship visible. It is a requested response time, not a newly imposed deadline or a guarantee that the target will be met.
Where the time is an estimate, label it. If you have not assessed how long the remaining work will take, do not invent a confident completion time. You can say that you will review the target after the missing decision arrives. The reader then knows both what you need and what is still uncertain.
Keep ownership explicit: “I will update the two entries, check them and assemble the PDF once the codes are confirmed.” You are asking the coordinator to supply a decision within their role. You are retaining preparation and verification of the task. A decision request does not transfer responsibility merely because another person must respond.
If responsibility really needs to move, that is a different conversation with its own conditions. How to Repair a Broken Handoff at Work covers that boundary. Do not rely on a status message such as “over to you” to perform both jobs ambiguously.
Before sending, read only the request sentence. Could the recipient answer it without guessing the missing question? Then read only your next-action sentence. Is it clear what you will still do? Those two checks catch many updates that report a problem but leave the practical arrangement unresolved.
Mira is preparing a ten-entry activity index for a fictional reading-room event. She remains responsible for drafting, checking and assembling the index. Nolan is the event coordinator and is authorised to choose the room codes. He is not being asked to write entries or take over the index.
The agreed result is one PDF containing entries A01–A10. Each entry must contain its activity title, activity code and confirmed room code, checked against the coordinator’s current schedule. The completed PDF must then be previewed to ensure all ten entries appear legibly and in the agreed order. The target is Tuesday at 16:00.
The working record below is complete for this example. Its snapshot is Tuesday at 11:00. Index I3 is the current working file. Schedule S7, issued Tuesday at 09:30, is the current reference. No later schedule or decision has arrived by the snapshot time.
| Entries or step | Position at Tuesday 11:00 | Evidence and remaining action |
|---|---|---|
| A01–A06 | Six entries checked | Titles, activity codes and room codes match S7 |
| A07–A08 | Two entries drafted, not checked | All required information is available in S7; Mira must check the drafts |
| A09–A10 | Two incomplete entries | Titles and activity codes are present; S7 marks both room choices undecided |
| PDF assembly and preview | Not yet completed | Required after all ten entries are complete |
At 10:40, Mira asked Nolan to confirm the two undecided room codes by 13:00 if possible. She explained that this would allow her to continue the remaining entry checks and final preparation towards the 16:00 target. Nolan has not yet responded. There is no record that he has agreed to the requested response time.
Mira can work on A07 and A08 now. She cannot accurately fill the room fields for A09 and A10. She has not yet estimated a reliable completion time after those codes arrive. Her next planned status update is 13:15, or earlier if the room decision materially changes the position.
Notice what the record does not say. It does not say that Nolan is late against an agreed response commitment. It does not say that the full index is eight-tenths complete. It does not establish that missing room choices are the only work left. Six entries are checked, four are unfinished, and PDF assembly and preview remain.
The update must preserve those distinctions while staying readable. Nolan needs enough detail to understand and answer the room question. Mira’s other readers need to know that preparation continues and that the target remains conditional on unresolved work. Neither audience needs a minute-by-minute account of how I3 was created.
Mira’s first draft reads:
“The index is basically done. I have spent most of the morning on it and only need Nolan to finish the rooms. We should be fine for 16:00. Please sort it out when you can.”
The draft sounds brief, but it changes the evidence. “Basically done” hides four unfinished entries and the final PDF work. Time spent replaces a checked result. “Nolan to finish the rooms” blurs a room decision with responsibility for preparing the index. “We should be fine” suggests confidence that the available record does not establish.
The last sentence is also difficult to act on. Nolan has to infer which activities need room codes. “When you can” hides the requested 13:00 response time and its purpose. A reader cannot tell whether this message is a reminder, a changed deadline or an attempt to pass the assignment elsewhere.
A repaired update reads:
Activity index I3 — Tuesday 11:00, checked against schedule S7 issued at 09:30. The ten-entry index is still in preparation. Six entries, A01–A06, have passed the title, activity-code and room-code checks. A07–A08 are drafted and ready for me to check. A09–A10 are incomplete because S7 leaves their room choices undecided.
Nolan: please confirm the room codes for A09 and A10, as requested at 10:40. A response by 13:00 would support the remaining preparation towards the 16:00 target; that response time has not yet been confirmed. I cannot finish those two entries without the room decisions.
I am checking A07–A08 now. I remain responsible for completing and checking A09–A10, assembling the PDF and previewing all ten entries. I have not yet confirmed a reliable finishing time. I will update the position at 13:15, or earlier if the room decision changes the plan.
This version is longer because the task contains several relevant states. It could be shortened for readers who already know the agreed checks, while preserving the count, blocked items, request and retained ownership. Concision means removing unnecessary explanation, not removing the distinctions needed for a decision.
The counts reconcile: six checked, two drafted and two incomplete make ten entries. PDF assembly is a further step, not an eleventh entry. The update does not present the six checked entries as a percentage of total effort, and it does not treat the requested response time as an accepted commitment.
The uncertainty is useful information. Nolan can see why his decision matters without being told that his answer guarantees completion. Mira’s responsibility remains clear. Once the room codes arrive, she must still put them into the index and carry out the remaining checks.
An update should change when the underlying record changes, rather than preserving an earlier summary for consistency. In the activity-index example, suppose the following events occur after the 11:00 snapshot. At 12:05, Mira completes the checks on A07 and A08. At 12:20, Nolan issues schedule S8, confirming A09 in R2 while leaving A10 undecided.
Mira inserts R2 into A09, checks that entry against S8 and saves index I4 at 12:35. She also verifies that S8 has not changed the information in A01–A08. At the new snapshot, nine entries are checked and A10 remains incomplete. The final PDF assembly and preview have still not been completed.
A short follow-up can now say:
“At 12:35, index I4 has nine checked entries against schedule S8. A10 is still incomplete because its room remains undecided. Nolan, the remaining decision is the room code for A10. I will finish that entry and complete PDF assembly and preview after the code is confirmed. Finishing by the 16:00 target remains unconfirmed; I will report again at 13:15.”
This message does not repeat the old request for two room choices. It recognises the decision already supplied and narrows the remaining question. It also retains the final work that was present in the earlier account. Receiving one answer has improved the position without making the entire task complete.
Version identifiers help readers follow the change. I3 was the index at 11:00; I4 is the index at 12:35. S7 and S8 are schedule versions. The number eight does not make a schedule a later version of an index; the two documents have separate histories.
If an earlier message was wrong, correct it directly. Consider a separate hypothetical version of the case in which A06 was wrongly counted as checked at 11:00. A correction could say: “My 11:00 message incorrectly counted A06 as checked; it was still a draft. The corrected position at that time was five checked, three drafted and two incomplete.” This hypothetical error did not occur in the supplied case. Explain any real correction without replacing the historical record with today’s better result.
A changed status and a corrected status are different. New work changes the position after a snapshot. A correction repairs an inaccurate account of that snapshot. Label the difference so readers can understand whether the task moved forward or the earlier information was unreliable.
The second example concerns one booklet with four components, rather than ten similar entries. Rowan is preparing a welcome booklet for a fictional maker club. Rowan retains responsibility for editing the booklet, checking its contents and previewing the PDF. Coordinator Eve is authorised to choose the contact-panel wording and issues the current timetable.
The agreed result contains a cover, a weekly timetable, a room key and a contact panel. The timetable must match Eve’s current timetable. The contact panel must use one of two wording options chosen by Eve. Before the booklet can be described as ready for use, Rowan must check all four components and preview the resulting PDF.
The target is Wednesday at 16:00. The current snapshot is Wednesday at 14:00. Working booklet B3 was saved at 13:00. Its timetable component still uses timetable T5. Eve issued T6 at 13:20, changing Thursday’s session start from 14:00 to 14:30. No other timetable details changed in this example.
| Component or step | Verified position at Wednesday 14:00 | What remains |
|---|---|---|
| Cover | Checked and still meets the current brief | No known correction |
| Room key | Checked and still meets the current brief | No known correction |
| Weekly timetable | Contains the superseded Thursday start from T5 | Update to T6 and check the component |
| Contact panel | Draft contains a clearly marked choice between wording A and wording B | Eve must choose; Rowan must insert and check the selected wording |
| Final PDF preview | Not performed | Preview after the components are complete |
The two contact options differ only in presentation. Option A says, “For club questions, use the enquiries address listed below.” Option B says, “Questions about the club? Use the enquiries address below.” Both use the same already agreed address in the underlying fictional record. The choice does not concern changing the address, collecting information or authorising a new service.
Rowan can correct the timetable without waiting for the wording choice, because T6 is the authoritative current reference. At 14:00, Rowan has not started that correction. Eve has not selected contact wording, and Rowan has not asked her for a specific response time. There is no reliable finishing estimate recorded yet.
All four components are present in B3. Only two have passed the current requirements. The task therefore illustrates why counting visible sections can mislead. Presence is evidence of assembly, while readiness requires current content and completed checks. A status update must communicate the state relevant to use, not the easiest count to report.
Rowan drafts this message at 14:00:
“All four parts of the booklet are complete, so we are at 100%. It just needs a quick look. Eve, can everyone approve it? I will send it at 16:00.”
The message treats four inserted components as four completed components. It overlooks the timetable change and reduces an unresolved wording decision to “a quick look”. It also asks Eve whether “everyone” can approve something, although the record gives Eve a specific wording choice and leaves editing and checking with Rowan.
The final sentence turns a target into a promise without evidence that the remaining work will fit. Even if Rowan expects to finish, the message should distinguish that expectation from a verified condition. The current booklet still contains superseded information and an unresolved choice.
A repaired message reads:
Welcome booklet B3 — Wednesday 14:00. The booklet is still in preparation. The cover and room key are checked. The timetable component needs correction: B3 still shows Thursday at 14:00 from T5, while Eve’s current timetable T6, issued at 13:20, gives 14:30. The contact panel remains a draft awaiting the wording choice.
Eve: please choose contact wording A or B. Both retain the agreed enquiries address. Could you confirm the choice by 15:00 to support preparation towards the 16:00 target? I have not yet confirmed that finishing time.
I will update the timetable to T6 now. I remain responsible for inserting the chosen contact wording, checking both unfinished components and previewing the completed PDF. I will report again at 15:10, or sooner if the decision or remaining work changes my expectation of finishing by the target.
The update distinguishes two different reasons for unfinished work. The timetable needs an action Rowan can perform now. The contact panel needs a choice from Eve before Rowan can complete it. Combining both under “waiting for approval” would incorrectly suggest that Rowan cannot continue.
The timestamp also matters. T6 was issued after B3 was saved, but it was available before the 14:00 update. Rowan should therefore compare B3 with T6 when reporting the current position. Saying that B3 was accurate at 13:00 would not answer whether it is ready now.
The proposed 15:00 response time is transparent. It is a request linked to the existing target, not a statement that Eve has agreed to answer then. The 15:10 update is Rowan’s planned communication. Neither time turns the remaining checks into a guaranteed duration.
If Eve responds with option B, the next status should record that decision and the resulting action. It should not immediately say the booklet is ready merely because the choice has arrived. Readiness is established after Rowan inserts the wording, corrects the timetable, checks both components and previews the PDF.
You can be precise about uncertainty. “I do not know when this will finish” may be true, but the reader also needs to know what is known. “Two components remain unchecked; one needs a wording decision, and I have not yet estimated the final preview time” locates the uncertainty inside a useful account of the work.
Avoid replacing missing evidence with reassuring adjectives. “Small”, “quick” and “nearly” can be reasonable descriptions when their meaning is shared, but they should not carry the entire completion claim. A small textual change may still require checking the resulting file. A short remaining list may contain an unresolved choice that cannot be timed by the person writing the update.
Where you offer an estimate, state the basis and the condition that could change it. For example, you might know from today’s direct inspection that one correction remains and the necessary source is available. That can support a more definite plan than a task with several unknown inputs. It still does not justify describing unchecked work as complete.
Do not convert a missed requested response time into evidence of refusal. If the coordinator has not answered by your requested time, report that the decision is still pending and explain the effect on your current plan. Check the ordinary communication arrangement already agreed for the task. Silence alone does not establish motive or permission to proceed with an invented answer.
The next update should have a useful trigger. A scheduled checkpoint is suitable when readers need a regular view. A material event can also justify an earlier message: a required decision arrives, a current reference changes, or a previously expected result proves unavailable. Avoid sending repeated messages that contain no changed evidence or question.
Choose enough detail for the reader to act, while keeping procedural detail in the working material. A status message may say that two entries require checking; it does not need to teach every checking step. How to Write Work Instructions Someone Else Can Follow addresses that separate need.
Finish with a statement that remains true under uncertainty: who owns the task, what they will do next, what answer is needed and when the position will be reviewed. Those commitments make an update useful even when a confident completion prediction is not yet available.
Now apply the method to a different record. Do not start by editing the poor message. First work out the current position from the evidence. Your output is a short update that the named decision-maker can answer without assuming that responsibility for the deck has moved.
Sam is preparing a six-slide orientation deck for a fictional community drawing session. Sam owns editing, checking and previewing the deck. Leah is authorised to choose the activity shown on slide 6 and to issue the session brief. Amir collects progress messages for the planning record; he is not authorised to choose activities or change the target time.
The agreed result is six slides matching the current session brief, followed by a preview of the whole deck in presentation view. The target is Friday at 14:00. Sam’s working period began at 09:00. The current snapshot is Friday at 11:00, and the working file is deck D2.
At 10:00, slides 1–3 had passed checks against brief R3. At 10:40, Leah issued R4. It changed slide 2’s required statement from “Bring paper” to “Paper is provided”. It left the other requirements unchanged. At 11:00, Sam rechecked slides 1 and 3 against R4 and confirmed that they still meet the brief. Slide 2 has not yet been corrected or rechecked.
Slides 4 and 5 are drafted and can be checked now using R4. Slide 6 contains the heading and a marked empty space for the selected activity. R4 says Leah will choose either shape sketching or pattern drawing; no choice has arrived by 11:00. The final presentation preview has not been performed. Sam has not established a reliable finishing estimate for the remaining work.
Sam’s draft message to Amir reads:
“Half my planned time has gone, so the deck is 50% complete. Three slides are approved and the rest are nearly there. Amir, please choose the activity and confirm we can move the target to 15:00. I’ll leave the final slide with you.”
Write a replacement update addressed to Leah, with a copy for Amir’s progress record. State the current counts without overlapping categories. Identify which earlier check is no longer sufficient. Request only the decision Leah is authorised to make in the supplied record. Propose a response time and next update time as requests or plans, rather than established agreements.
Before reading the answer, explain why elapsed time does not establish the deck’s completion percentage. Also explain why the message must not promise a changed target or leave slide 6 with Amir. The supplied information contains no authority for either action.
At 11:00, two slides are checked against the current brief: slides 1 and 3. Slide 2 needs correction and a fresh check. Slides 4 and 5 remain drafts awaiting checks. Slide 6 is incomplete because Leah’s activity choice is missing. These mutually exclusive categories account for all six slides: two checked, one requiring correction, two drafts and one awaiting a decision.
The old count of three checked slides was valid against R3 at 10:00. It is not the current count under R4. The change specifically affects slide 2, while slides 1 and 3 have been rechecked and remain valid. There is no reason to discard those two valid checks or to preserve slide 2’s outdated one.
A suitable replacement is:
Orientation deck D2 — Friday 11:00, checked against brief R4 issued at 10:40. Slides 1 and 3 meet the current brief. Slide 2 needs correction from “Bring paper” to “Paper is provided” and a fresh check. Slides 4 and 5 are drafted and still need checking. Slide 6 remains incomplete while the activity choice is pending. The whole-deck presentation preview is also outstanding.
Leah: please choose shape sketching or pattern drawing for slide 6. Could you confirm by 11:30 to support preparation towards the existing 14:00 target? That response time is a request, and I have not yet established a reliable finishing estimate.
I will correct slide 2 and check slides 4 and 5 while awaiting the choice. I remain responsible for completing and checking slide 6 and previewing the whole deck. I plan to update the position at 12:00, or earlier if the decision changes the plan. Amir is copied for the progress record.
The proposed 11:30 response time and 12:00 checkpoint are reasonable choices for this exercise because they are explicitly requests and plans. Other times could be defensible if their relationship to the work is explained. The record supplies no basis for asserting that Leah has already agreed to a response time.
The replacement keeps the 14:00 target visible without guaranteeing it. It does not request a target change from Amir or imply that Leah has authority to change it; the supplied record establishes her activity-choice authority only. If a changed target becomes necessary, Sam must identify the appropriate arrangement separately.
Two hours have passed between 09:00 and 11:00. The interval from 09:00 to the 14:00 target is five hours, so the poor draft’s “half my planned time” claim is unsupported even as a clock calculation. More fundamentally, no elapsed-time fraction establishes how much of the deck meets its requirements. The useful evidence is the current slide states and the unperformed final preview.
Finally, the answer preserves ownership. Leah chooses the activity; Sam completes the slide. Amir records progress. None of those roles becomes another merely because they receive the same message. The update asks for one supported decision and makes the remaining work visible without assigning it to an unauthorised reader.
Read your update once as the person who must respond. Can you identify the task, current version and snapshot? Can you distinguish checked work from drafts, corrections and unresolved decisions? If a count appears, can you reconcile it with the total without guessing whether categories overlap?
Then inspect the request. Is the decision concrete? Does it belong to the named recipient? Are the options supplied by the record, rather than invented for convenience? Does the message explain what the answer will allow you to do? If no decision is needed, remove any unnecessary approval language and let the message serve as an accurate progress account.
Check time statements separately. A target is the intended finishing point. A requested response time is when you would like an input. An estimate is a prediction based on stated information. A snapshot is when the evidence was checked. A next-update time is your communication plan. Using one as though it were another creates avoidable confusion.
Remove claims that the evidence cannot carry. Time spent does not prove progress. A filled page does not prove current accuracy. A decision received does not prove the resulting edit was completed. An unanswered request does not prove refusal. Replace each unsupported shortcut with the smallest truthful statement that explains the present position.
Keep the next action connected to its purpose. “I will check the two draft entries while the room decision is pending” shows useful continuation. “I will keep working” gives the reader less information. “Over to you” may leave responsibility unclear when all you need is one choice and you still own the task.
Save enough of the underlying record to make the update checkable, and refresh the message when meaningful evidence changes. You do not need to preserve a flattering story about progress. You need an account that lets people coordinate around what is currently true, what remains uncertain and what happens next.
This guide sits within Recovery and Transformation. A useful next step can be modest: write one accurate status, request one appropriate decision and continue the part of the work you can responsibly complete. That gives the next conversation a clear starting point and preserves the value of work already done.
Contents · Previous chapter · Return to recovery and transformation
Continue through this learning web: Branch hub · Review Unfinished Work · Review Unfinished Work · Recovery & Transformation · Library