How to Write a Weekly Status Update With AI (That People Actually Read)

A weekly status update written with AI takes five minutes, fits on one screen, and gets read, which is more than most can say. The format is three short sections: what got done, what is next, and what is blocked, with a traffic light on top so a busy reader knows in two seconds whether to worry. AI does the condensing; you do the honesty. The updates that get ignored are the ones that bury the one thing the reader needed to know under everything else that happened.

Why do most status updates go unread?

Because they are written for the writer, not the reader. A list of everything you did proves you were busy; it does not tell your manager whether the project is on track. Templates collected by Smartsheet and Reclaim converge on the same shape for a reason: status first, then progress, then what you need from the reader. If your update can be read from top to bottom in under a minute, it will be. Past that, it gets skimmed or skipped.

What should the update contain?

A status line, then done, next, blocked. Start with one line and a colour: green means on track, amber means at risk and here is why, red means off track and here is what I need. Then three short sections, each three to five bullets in plain language: what shipped or moved this week, what happens next week, and what is blocked with a named person or decision that unblocks it. That last section is the one that justifies the whole update; it is where the reader can actually help.

How do I write it with AI in five minutes?

Dump, then structure. Spend two minutes writing everything that happened this week as a messy list: tickets closed, meetings, decisions, surprises, things stuck. Then prompt: 'Turn this into a weekly status update for my manager. One line status with a colour and a reason, then Done, Next, Blocked as short bullets. Plain language, no jargon, under 150 words. Put anything I need from them under Blocked with a clear ask.' Edit for accuracy, especially the colour, then send. The same dump also feeds your self-evaluation at review time, so keep the weekly lists.

How do I keep it honest when the news is bad?

Say the colour first and the reason second. The temptation is to lead with wins and mention the slip at the end, which reads as hiding it. An amber or red status with a one line cause and a proposed fix builds more trust than a green that turns red later. Ask AI to check your draft: 'Does this update make the risk clear in the first line, or is it buried?' It will tell you. For messages that need more care than a status update, our guide on writing difficult messages with AI applies.

Should I send it by email, chat, or a document?

Wherever your reader already looks, in the body, not as an attachment. An update that requires a click gets read less. Paste it directly into the email or channel message, keep the subject line consistent week to week so it is searchable, and send at the same time every week. If several people report to the same manager, agree on one format so the updates can be scanned side by side. Our guide on writing work emails with AI covers subject lines and tone if you send it as mail.

How do I know if the update is working?

Your manager stops asking you questions you already answered. That is the test. If they still ask whether the project is on track, the status line is not clear enough. If they ask what you need, the Blocked section is too vague. Adjust the template, not the length. A status update that keeps growing is a sign the format failed, not that the week was busy.

The best status update answers one question before it is asked: should I be worried?

This Friday, write the messy list, let AI shape it into status, done, next, blocked, and send it under 150 words. Watch how many follow-up questions disappear.