How to show what changed and what needs attention

Some status updates contain fourteen bullet points and somehow leave you knowing less than you did before you opened them.

“Work is ongoing.” “The team continues to collaborate.” “Multiple items are being evaluated.” Okay, but are we on track?

A useful update helps someone understand where the work stands and what they need to do next. They shouldn’t have to schedule a follow-up just to decode it.

Your working team may need task details and handoffs. A client or sponsor may need the delivery outlook, changes since the last update, and any decision that needs their attention.

Put that information first. You can link to the detailed tracker for readers who need to dig further.

Make the current situation easy to find.

“Timeline discussions are ongoing” tells the reader very little. If a delay threatens the deadline, say what is late and how it affects the plan.

For example: “Testing is two days behind because the test environment is unavailable. If access is not restored by Wednesday, the Friday release will need to move.”

Follow that with who is handling it and the next checkpoint: “Jordan is working with IT to restore access and will confirm the release outlook Wednesday afternoon.”

Now the reader knows the problem, the consequence, and when to expect more information. No flashing red PowerPoint required.

You do not need to reinvent your update every week. A few consistent labels make it easier to write and easier to scan.

Here is a fictional example for a project preparing for launch:

Overall status: At risk. The October 5 launch depends on vendor approval by September 30.

Completed: The team finished the configuration review and resolved the two outstanding setup questions.

Next: Integration testing starts October 1, provided the vendor is approved and access is available.

Risk and response: Late approval could delay testing and launch. Priya is confirming vendor availability today and will share a revised schedule if approval slips.

Decision needed: Alex, please approve vendor A or B by September 30 so the team can book the setup slot.

If no decision or support is needed, say that. Nobody should have to guess whether the update contains homework for them.

Report finished work as finished and work still in progress as in progress. “Almost done” can hide everything from one final check to a week of testing.

When something is uncertain, explain what you know and when you will confirm the rest. You can flag a risk before you have every answer.

If an urgent issue needs action today, contact the right person today. Don’t save it for Friday just because that is when the status email goes out.

Before sending, read the opening and the requests on their own. Can someone tell whether the project is on track, what changed, and whether they need to act?

Then remove the activity that doesn’t help explain progress or a problem. “Attended three meetings” probably matters less than the decision those meetings produced.

Your reader should finish with fewer questions about the project. Ideally, they can even get back to their own work.

Thanks for reading. I hope you’re leaving with at least one idea that makes the work in front of you feel a little clearer, simpler, or more manageable.

Until next time — less chaos, more clarity, better work.
— Shania