Turn rough project notes into a status update your team can use

“Possible launch Friday” and “launch confirmed for Friday” are only a few words apart. They give your team very different instructions.

Try this: a draft is finished, an import is failing, and the help page has no owner. Turn those rough notes into an update a teammate can act on without accidentally approving the launch or assigning somebody extra work.

Try it with your writing assistant, or write directly in the Word worksheet. Keep the source IDs beside each statement while you check it. For example, [S3] points to note S3. Then compare your version with the worked answer below.

The five source notes

• S1: Landing-page draft done. No client approval yet.
• S2: Ana to send draft to client Tuesday, October 27, 2026.
• S3: Spreadsheet export passed three sample checks. Import into the next system still errors.
• S4: Possible launch Friday, October 30. Proposed, not confirmed.
• S5: Help page needs an owner. Nobody assigned.

Source S3 describes two separate steps. The spreadsheet can export successfully while the next system still has trouble importing the file. Both details belong in the update.

Compare with the worked answer

Your wording can differ. Check whether it preserves these facts and open questions.

Status: The landing-page draft is complete, but client approval has not arrived [S1].

• Ana is listed to send the draft to the client on Tuesday, October 27, 2026 [S2].
• The spreadsheet export passed three sample checks, but the next-system import error remains unresolved [S3].
• Friday, October 30 is a proposed launch target that has not been confirmed [S4].
• The help page has no assigned owner [S5].

Questions to resolve: Who owns the import issue [S3]? Who will take the help page [S5]? Can the team confirm the proposed launch date [S4]?

A reader who only needs the current status and one open issue could use a shorter update:

The landing-page draft is done, but client approval has not arrived [S1]. The spreadsheet export passed three sample checks, but the import into the next system still errors [S3].

Choose the length that fits the reader. Keep accurate statements and add only the context they need.

Practice spotting four errors

The following draft contains four deliberately planted errors. Compare it with S1–S5 before reading the findings.

The client approved the landing page. The data import has been tested successfully, and launch is confirmed for October 30. Ana owns the help page.

Use the same check next week

Before sharing your update, compare every status, date, number, owner, approval, and commitment with its source. Turn missing information into a question. Keep the notes available to your reviewer, following your team's retention rules.

For your next real update, start with the date or assignment a colleague is most likely to act on. Find the note that supports it. If the note says “possible,” keep that word until someone with authority confirms the decision.

For a broader process check, read How Do You Test an AI Workflow Before Your Team Relies on It? and try the free ten-case worksheet. To practice reviewing evidence, see How Do You Train a Human Reviewer for AI-Assisted Work?. For interruptions in an AI-assisted process, see testing the manual fallback.

For more practical examples by email, see the Frontline AI Brief. It sends at most two emails a month, with a confirmation step before you subscribe.