[Communication] What does a good project status update actually include?

Example Answer

A good status update should answer the questions people actually have, not just prove that the PM has been busy. I want someone reading it to know where the project stands against the plan, what changed since the last update, what's most at risk right now, and whether I need a decision or support from them.

I also think the update has to match the audience. An executive probably needs a sharper summary around progress, risk, tradeoffs, and commitments. The team may need more operational detail. But in both cases, the update should reduce uncertainty. If people finish reading it and still don't know what matters, it wasn't a good update.

The other thing I care about is tone. I don't want updates that hide behind green language when the project is wobbling. I'd rather be clear and calm than polished and misleading.

Common Poor Answer to Avoid

"I include red, yellow, or green status, a few bullets, and next steps."

Why it's weak

That sounds like a template, not judgment. Hiring managers want to hear how you decide what matters in the update, not just that you know the format exists.

Why this works

It explains the purpose of status reporting, shows audience awareness, and keeps the answer grounded in useful PM behavior instead of reporting mechanics alone.