Start with a short progress summary
Open with the current state of the project. A simple statement such as “The project is in the implementation phase” gives the client context before the details.
List what was completed
Describe finished work in concrete terms. Mention deliverables, approved items, completed milestones, or other observable results rather than vague statements such as “made good progress.”
Explain what happens next
Give the client a short list of the next tasks or milestone. If the next phase depends on their feedback, make that dependency explicit.
Call out blockers and risks
If something is delaying work or could affect the timeline, say so early. Explain the practical impact and what would resolve it. Separate confirmed blockers from risks that are only possibilities.
Make client action items obvious
Put approvals, files, decisions, or other client responsibilities in a distinct section. Include a requested date when timing matters.
Keep the update consistent
For recurring projects, use the same structure each week or at each milestone. Consistency makes changes easier to spot and reduces the time needed to write the update.
Example structure
- Progress summary
- Completed work
- Upcoming work
- Blockers or risks
- Client action items
- Next milestone or date
Keep status updates separate from scope changes
A status update can identify a change, but a new request should be documented and approved through your normal change process. Record the effect on scope, price, and timeline rather than quietly absorbing additional work.