Back to blogYour AI Chief of Staff · Run the system

How to write a status update that actually gets read

Answer the question your manager is really asking: should I be worried about anything?

Most status updates describe activity rather than status. They are too long, bury risks, and are written for the person who did the work rather than the person reading it.

Use three sections: this week’s outcomes, status and risks, and next week. State results rather than activity. Put blockers and decisions near the top. Keep the update short enough to read carefully.

Tell your AI what happened in ordinary language, then ask it to frame the update around outcomes, risks, and next actions. Review the choices before sending.

A clear update builds a durable reputation: this person knows what is happening and can explain it.

This is part of the Your AI Chief of Staff series, a practical guide to building a personal operating system for knowledge work.

Read the full series at Your AI Chief of Staff