Turn Work Records into a Progress Update Your Manager Can Use

To write a useful progress update, compare the current records with the last update, name exactly what changed, and separate finished work from saved drafts or unresolved approval. End with the decision or help the reader can provide. A short report can keep a conflict visible instead of choosing the most confident label.

This walkthrough turns a previous update and eight dated records into a complete update for a manager named Alex. The finished report is short; the supporting notes stay separate so Alex can see the change and the requested help without reading a work diary.

Start with the reader and the previous update

Before collecting more detail, ask what the update is for. Here Alex needs changed work status and one concrete help request. That is enough to decide what belongs in the report. If an existing shared report already gives your manager that view, update it rather than adding another weekly message.

A product-management discussion about status updates describes turning records scattered across tools into different reporting formats. A separate managers' discussion includes both useful leadership updates and objections to repetitive reports that nobody uses. These are individual accounts, with exact posting dates unverified, rather than evidence that every team needs a new report or an AI tool.

Use a reporting period and a cutoff so “current” has a clear meaning. Keep the previous update: without it, a list of this week's activity may not show what actually changed.

Read the complete example records

The records and reports below are original fiction, not a captured AI conversation or a real workplace result. All 2030 dates belong to the example.

This is the entire source packet. The standalone source packet contains the same text.

Original fictional teaching case PROGRESS-01. No real company records, tool output, model trial or customer data.
Reader: Alex, the writer's manager. Alex needs changed work status and a concrete help request.
Period: 2030-05-06 through 2030-05-10. Cutoff: 2030-05-10 16:00 UTC.
These dates belong only to the fictional case.
P0 — Previous update, 2030-05-03
Quick-start handout: version 1 drafted; review still pending.
Resource index: export and link check planned, not yet done.
Workshop: no date agreed.
Next: revise the handout after review and prepare the index.

Current records:
R1 | 2030-05-06T10:00:00Z | writer work log
Quick-start handout v2 saved. This is a revised draft, not a review or approval record.

R2 | 2030-05-07T11:00:00Z | named reviewer message
Dee checked pages 1 and 2 of handout v2. Page 3 needs clearer wording. Dee has not approved the whole handout.

R3 | 2030-05-08T12:00:00Z | writer work log
Handout v3 saved with page 3 revised. No review of v3 is recorded in this entry.

R4 | 2030-05-09T09:00:00Z | index check log
Resource index exported with 24 entries. 23 links opened in the local check; one link was broken. The check is incomplete.

R5 | 2030-05-10T13:00:00Z | index check log
Broken link replaced. All 24 links opened in this local check. The index has not been shared. This record says nothing about access from other users' accounts.

R6 | 2030-05-10T14:00:00Z | tracker snapshot
Handout status field says Ready. It provides no approver, revision identifier or approval receipt.

R7 | 2030-05-10T15:00:00Z | named reviewer message
Dee says: I have not reviewed the changed page 3 in v3. I have not given final approval. This message does not identify any other final approver.

R8 | 2030-05-10T15:40:00Z | writer planning note
Ask Alex to confirm who can give final review and resolve the Ready label. Then request the review; do not call the handout approved until supported. No handout distribution record is supplied. Workshop date is still undecided; keep it unscheduled. No completion date or outcome metric is agreed.

The cutoff includes every record above. R8 is a plan; it does not describe a review already requested or a tracker already changed.

Describe changes without widening what was completed

Compare each subject with P0 before compressing it into a sentence:

The index has a real change within the fictional record: R4 says its check was incomplete; R5 describes replacing the broken link and opening all 24 links. You can report that local check as complete. Calling everything “still in progress” would lose supported progress.

Keep the object of the completion claim attached to the verb. “The local link check is complete” says something different from “the index is complete and everyone can use it.” R5 supports the former. It explicitly says the index has not been shared and does not establish access from someone else's account.

Likewise, “v3 saved with page 3 revised” describes a new draft. Dee's earlier review covered pages 1–2 of v2, not a final review of v3. The fact that the requested wording was changed does not establish that the changed page was subsequently reviewed.

Preserve a status conflict until someone can resolve it

R6 and R7 describe different parts of the handout's status. The tracker has a Ready label without an approver, revision identifier or approval receipt. Dee says they have not reviewed changed page 3 in v3 and have not given final approval. The packet identifies no other final approver.

Do not report the handout as approved because the tracker says Ready. Also do not rewrite the situation as “Dee rejected v3” or “only Dee can approve it.” Neither appears in the records. The useful status is final review unconfirmed, with the tracker label and Dee's message both retained.

Dates help you follow a sequence; they do not give every entry authority over every claim. R5 can update the local-check result because it explicitly records the replacement and the completed check. R7 tells you what Dee has not reviewed; its later timestamp does not identify the final approver or explain what Ready means. The gap needs a specific answer, not a rule that the latest timestamp wins.

R8 already supplies the next useful question for Alex: who can give final review, and how should the tracker status be resolved? Preserve that request without silently appointing Alex as the approver or promising a review date.

Reject the whole report that overstates progress

Here is the complete deliberately wrong report. It was written as a counterexample, not obtained from an AI system:

Learning library refresh — all work complete

The quick-start handout is approved and has been sent to everyone. The resource index is complete and shared, and all colleagues can open every link. The workshop is confirmed for 2030-05-12.

We are 100% finished and have improved engagement by 20%. No help is needed.

A confident headline does not make the unsupported claims smaller. Repair them against the records:

Repair the report with the complete source packet

Give the writer the complete P0/R1–R8 packet and the complete wrong report, not just an instruction to make the report more cautious. This correction request names what must remain finished, what remains unresolved and the whole output to return:

Repair the complete deliberately wrong report using only the complete
PROGRESS-01 source packet supplied with this request. Return the whole corrected update
for Alex, followed by a separate compact claim-to-record table, not a list
of suggested edits.

Use the reporting period 2030-05-06 through 2030-05-10 and cutoff
2030-05-10 16:00 UTC. These are fictional case dates.
Compare the current state with the previous update P0.

Preserve the completed export and local check of all 24 index entries after
one link replacement. Do not extend that result to sharing or access from
other people's accounts. Preserve the saved handout v3 and its page 3
revision without calling it a reviewed or approved final handout.

Keep both R6 and R7 visible: Ready has no approver, revision identifier or
approval receipt; Dee has not reviewed changed page 3 in v3 or given final
approval. Do not infer that another person approved it, or that Dee is the
only authorized approver. A later timestamp alone cannot settle approval.

Include the R8 request for Alex to confirm who can give final review and
resolve the tracker status. The supported next step is to request that
review after the reviewer is confirmed. Keep the workshop unscheduled and
its date undecided. State that no handout completion date is agreed and
no handout distribution record is supplied.

Remove invented distribution, recipient access, approval, dates, owners,
completion percentages and outcome metrics. Do not quietly downgrade the
completed local check just because final handout approval is unresolved.
Prepare text only: do not send the update, access tools, contact anyone,
change the tracker, schedule the workshop or perform the reported work.

The complete repair request combines that instruction, all source records and the complete wrong report in one copyable file. It needs no earlier chat, account access or missing attachment. The corrected answer is kept out of that input file.

Return a short update Alex can act on

The following is the complete repaired update. It retains the actual change since P0, the local-check scope, the approval conflict and Alex's specific help request. The source table follows separately.

Learning library refresh — update for 6–10 May 2030
Status as of 10 May 2030, 16:00 UTC

Alex,

Changed since the previous update:
- Resource index: export and local link checking have moved from planned to
  complete. All 24 links opened in the local check after one broken link was
  replaced. The index has not been shared; access from other users' accounts
  is not established by these records.
- Quick-start handout: the previous v1 draft is now a saved v3 with page 3
  revised after Dee's feedback on v2. Final review remains unconfirmed:
  the tracker says Ready without an approver, revision identifier or approval
  receipt, while Dee has not reviewed changed page 3 in v3 or given final
  approval. The records do not identify another final approver.

Help needed:
Please confirm who can give final review and resolve the Ready status.

Planned next:
Request that review once the reviewer is confirmed. No handout distribution
record is supplied. The workshop date remains undecided, so it stays
unscheduled. No handout completion date is agreed.

The standalone finished update contains the whole report.

A compact source table for the update

The table explains why each sentence can stay in the update. It is not a second report for Alex to read before understanding the request. Keep it with your working notes, or share it when the recipient wants the supporting detail.

Use the same approach for your own records

Start from your actual reader and their use for the update. Bring the previous report, the records for the current period and the cutoff. For each subject, write the old state, the supported change and the current unresolved point. Keep the relevant record beside the sentence while drafting; you can leave those references out of the short recipient-facing version.

Use verbs that fit the record: saved, reviewed, checked, shared and approved describe different events. If a label conflicts with a person's account, say what each source establishes and ask the person with the relevant authority to resolve the missing point. Do not invent that authority from a job title or assign a deadline because the update would read more neatly with one.

A running log can make the next update easier to assemble. A consulting discussion about weekly reports includes a manual alternative: keep daily notes in the format of the required report. For a small set of records like this one, you can write the update directly from the comparison table. An assistant is optional; it does not replace checking the finished claims against the records.

You can also speak an additional work note if that suits the moment. Read the captured text before adding it to the packet, especially the dates, negations and status words. Speaking is only an optional capture method here; this example does not establish a transcription benefit or an integration that collects records for you.

Before sending your own update, read it as the recipient: can they see what changed, what is still unresolved and the exact help you need? Check the dates and every claim of completion one last time. If there is no new decision or useful change, the existing report or your regular conversation may already be enough.