What did the project set out to do?
Describe a specific need and the agreed scope of the activity. Say who coordinated it and which period the update covers. Avoid suggesting that a single event solved a wider problem. Readers should be able to distinguish the immediate task from the longer-term ambition that inspired it.
What actually happened?
Use records the team has checked. If a number is an estimate, label it as one. Explain any change of plan without hiding practical difficulties. Where resources or donations are discussed, direct readers to the organisation's own published records and contact process rather than presenting an informal message as an audited statement.
What happens next?
Name the remaining work and say whether further help is currently requested. An update should not imply urgency when there is no confirmed need. Include a way to ask questions or correct an error. Clear reporting makes it easier for supporters to understand their role and for organisers to receive useful feedback.
