From a loose walkthrough to a procedure someone can follow

Publish the weekly client status update

Purpose: turn the delivery team's weekly project notes into one accurate client update without exposing internal comments.

Prerequisites

• Current project board with this week's completed and blocked items
• Client update template in the shared workspace
• Named internal approver available before the send deadline

Procedure

1. Open the project board and filter activity to the current Monday-through-Friday period.
2. Copy completed client-visible items into the Completed this week section. Rewrite internal shorthand in plain language; do not include private comments or staff names unless the client already uses them.
3. Move unfinished items into either In progress or Blocked. Add the owner and next expected action for each item.
4. For every blocked item, identify whether the next action belongs to the agency or the client.

5. Add the next milestone and its current target date. If the date changed, include the reason already approved for client communication.
6. Remove empty headings, internal links, draft notes, and comments from the client version.
7. Send the draft to the named internal approver with the subject Approval needed: [Client] weekly update.
8. Apply approved corrections, send through the normal client channel, and record the sent link or message URL on the project board.

Common mistakes

• Reporting activity instead of an outcome the client can understand
• Leaving a blocker without a named next action
• Copying internal comments, private links, or unapproved delivery dates
• Sending the update without recording where the final version lives

Completion checklist

• Every completed item is client-visible and written in plain language
• Every blocker has one owner and one next action
• Dates match the approved project plan
• No internal comments, credentials, or private links remain
• The approver signed off and the sent update is logged