Write my weekly project update from Slack, email and the board

Project managers describe rewriting the same project information for different audiences. Standard reports help, but special views and short explanations still require manual work. Updates arrive as Slack messages, emails and board changes rather than as one packet, so the same facts are collected again for every report.

An assistant may reduce repeated drafting from updates scattered across Slack threads, emails and board cards. It cannot establish the true project state or replace the manager’s review of the approved plan. Use one agreed short template or an existing dashboard. Practitioners already use standard sections and manually review exceptions; reporting can be useful thinking time, not simply an administrative burden. Pending decisions appear in their own section with the owner, the version concerned and the work waiting.

You stay in charge. Confirm current status, baseline dates and material risks with the project owners. Approve the brief before sharing; decide whether reporting changes or escalation are needed. Confirm approval authority before treating any message as sign-off; silence is never permission.