Write a team status update without invented facts

You have gathered notes throughout the week, and your team is waiting for a clear status update. AI can quickly turn notes into a polished message. It may also add a deadline, assign an owner or present an open question as a decision because that sounds natural. Keep the request grounded in your notes and check the result so every name, time and decision in the update can be found there.

What a good status update includes

• Status: what has happened and where the work stands.
• Next steps: what happens next. Name an owner and time only if they have been agreed.
• Open decisions: what has not been decided yet and who will decide, if known.
• Needs: what is needed from each person to move the work forward.

Create an update in five steps

1. 1

   Gather facts from the notes

   Pull out events, agreed owners, times and open questions from the notes.

2. 2

   Write the request

   Specify the audience, structure and length. Add a boundary: use only the information provided and mark any missing owner or time as open.

3. 3

   Check names, times and responsibilities against the notes

   Review the draft sentence by sentence. Every name, date, time and responsibility must appear in the notes.

4. 4

   Keep open items open

   Check that an open decision is still open and that the draft does not present it as settled. Turn missing information into questions.

5. 5

   Ask for a focused correction

   Ask the assistant to remove or correct the specific issues you found and leave everything else unchanged.

Example: Project Aurora

The project and names in this example are fictional. The notes say: the interface draft is complete, testing starts next Monday, the customer demo is Friday at 14:00, Mira owns testing and Oskari is preparing the demo. Whether to present the reporting view at the demo has not been decided.

Write a clear weekly update for a fictional six-person team about a project called Aurora. This week’s facts: the interface draft is complete, testing starts next Monday and the customer demo is Friday at 14:00. Mira owns testing and Oskari is preparing the demo. It has not yet been decided whether to present the reporting view at the demo. Use the headings Status, Next steps and Open decision. Write no more than 150 words, add no facts and clearly mark the open decision. If an owner or time is missing, mark it as open.

The AI replied, for example: “Status: the interface draft is complete. Next steps: Mira starts testing on Monday and reports the results on Wednesday at 12:00. Oskari is preparing the customer demo for Friday at 14:00. Open decision: the reporting view will be presented at the demo.”

• Added detail: a Wednesday noon report is not in the notes. Remove it.
• An open decision is presented as settled: the notes say that presenting the reporting view has not been decided. Turn it into a question.
• The other names and times are in the notes.
• Follow-up request: “Remove the Wednesday report because it is not in the notes. Turn the open decision into a question: Will we present the reporting view at the demo? Leave everything else unchanged.”

Once the facts are right, you can improve the format in the same conversation.

Keep every name, time and supplied fact unchanged. Make the message easier to scan: write the status and next steps as three short bullets, then end with one question to the team about the open decision on the reporting view.

Write a weekly update of fewer than 150 words for a six-person team. Start with the status, then next steps and one open decision. Use only the supplied names, times and facts. Mark missing information as open questions.

Common pitfalls

• An invented owner or time appears in the draft. AI can easily fill in missing information. Check every name and time against your notes and remove anything they do not contain.
• An open decision becomes settled. “The reporting view will be presented at the demo” already sounds like a decision. Phrase the open item as a question and say who will decide, if known.
• The tone promises more than you know. Words such as “definitely” or “on schedule” sound like commitments that are not in the notes. Describe the status as the notes state it.
• Confidential information remains in the notes. Before sharing them with AI, remove customer, employee and contract details the update does not need. Use a service approved by your workplace.

Check before sending

• Can you find every name, date, time and responsibility in the notes?
• Are open decisions still open?
• Can the recipient see what is needed from them?
• Does the update sound only as certain as the information warrants?