Project update dispatch template
By Kivrelune Studio

Project update dispatch
Send a compact update centered on what has changed since readers last heard from the team.
Since the last update
Previously we expected [state]. We now know [new fact]. Evidence: [source]. The change affects [audience, milestone or assumption].
This week’s movement
Shipped or accepted: [result]. In progress: [work]. No-progress item and reason: [detail]. Keep unchanged background in the linked project brief.
Action for readers
[Person or team], please [action] by [date]. Next update on [date] or earlier if [trigger]. Full working record: [location].
Using this template
Start with the fact that changed since the previous dispatch and explain whose work it affects. Give readers just enough delivery evidence to understand the change and make any requested response easy to complete before the deadline.
Questions & answers
Looking for more help? Visit the Help center.
What should an update say if little has changed?
Confirm the current milestone, identify the work being verified and report any pending decision. Point readers to the next event likely to produce meaningful new information.
What is included in this template?
Since the last update · This week’s movement · Action for readers. Each section includes prompts you can adapt to your team.
How can the project team keep this current?
Give each open decision an owner and a due date. At the next checkpoint, update the milestone and record the work that changed since the last review.
How do I use my own copy?
Choose “Start with this doc” to open an editable copy on this device. You can also copy the Markdown or download the file and use it in your own editor.

