A project update helps people understand what has happened since an initiative was announced. It should be useful even when progress is slower than expected. Clear information about completed work, delays and next steps is more valuable than repeatedly saying the project is going well.
Return to the original commitment
Start with the project’s stated purpose and the period covered by the update. Identify what was planned for that period, then describe what has actually been completed. Separate work in progress from finished work.
Use numbers only when you know what they measure. The number of people invited, the number who attended and the number who completed an activity describe different things. Keep that distinction visible rather than selecting the largest figure for the headline.
Explain changes plainly
If a task moved or a date changed, explain the reason at the level you can substantiate. Avoid naming someone as responsible for a delay without checking the account and giving appropriate context.
Describe what the team has learned and what it is doing next. If a decision is still pending, say so. Readers should be able to distinguish a confirmed plan from an option under discussion.
Give people a practical next step
Include the next confirmed date, a reliable contact or the place where updates will be published. If you are asking for help, define the task and how an interested person should respond. Broad requests for everyone to get involved are harder to act on.
Keep previous updates available where practical so readers can understand the sequence. Correct earlier errors visibly instead of allowing conflicting accounts to circulate.
To suggest a follow-up story for the Intsetse FM blog, prepare a short summary and supporting details. Our community story-pitch guide explains how to organise the first message, and the contact page provides the station’s enquiry route.