reph

Templates · Operations & projects

Weekly status update template

Progress, next steps, risks and asks for stakeholders

Start with this template →Sign in

Opens on reph with the template ready to start. No account needed; sign in to keep your document.

Use it when

Stakeholders need a predictable weekly read on a project's progress, risks and asks without joining every meeting

Who it's for

ManagerProduct managerOperations

Filled example

The template filled in for a made-up company, so you can see what good looks like.

Driftwood data warehouse migration, week 6

Author: Kenji Moreau · Date: 2026-07-17

Overall status

🟡 Yellow: on track for the September 30 cutover, but the finance reporting backfill is a week behind and needs a decision (see Asks).

Progress
58%
▲ +9%
Milestones on track
4 of 5
Open blockers
2
▲ +1

Accomplished

  • Migrated the orders and inventory pipelines to the new warehouse; both ran in parallel all week with zero row-count mismatches
  • Retired 14 legacy cron jobs that had no downstream consumers
  • Finished the access review: 212 warehouse users mapped to 9 roles

Planned next week

  • Start the finance reporting backfill (2019 to 2023)
  • Dry run of the cutover runbook with the on-call team on Thursday
  • Migrate the marketing attribution pipeline

Metrics

Metric This week Last week
Pipelines migrated 23 of 40 19 of 40
Dashboards repointed 61 of 118 44 of 118
Nightly load time (new warehouse) 38 min 52 min
Row-count mismatches 0 3

Risks & blockers

Risk/Blocker Impact Owner Needs
Finance backfill needs a frozen month-end snapshot that finance has not provided Backfill slips a week, cutover buffer shrinks to 5 days Kenji Moreau Snapshot from finance by July 22
Two analysts still write to legacy tables directly Data drift after cutover Sofia Lindqvist Agreement to revoke write access on Aug 1

Asks

  • Finance (Hannah Pryce): approve a frozen June 30 snapshot by Wednesday so the backfill can start.
  • Analytics leads: confirm the August 1 date for revoking legacy write access.

The template

Show the blank template

Weekly status update

Author: [your name] · Date: [date]

Overall status

🟢 / 🟡 / 🔴 and one line on why, especially if it's not green.

Progress
0%
▲ +0%
Milestones on track
0 of 0
Open blockers
0
▲ 0

Accomplished

What actually shipped or closed this week, not "worked on."

Planned next week

The two or three things that will move next week, so readers can check back.

Metrics

The numbers that show whether the work is moving the needle, not just happening.

Metric This week Last week

Risks & blockers

Risk/Blocker Impact Owner Needs

Asks

Anything you need from a reader to unblock next week: a decision, a review, an intro.

Questions

How long should it be?
One screen; link out to detail instead of pasting it
When is a status yellow?
When a date or goal is at risk but there is a plan; red means it will slip without help
Who is the audience?
Stakeholders who skim, so put the status and asks first

Fill it with your agent

Connect Claude to reph over MCP, then paste this. The draft arrives as suggestions you accept or reject section by section. How to connect Claude.

Find my reph doc "Weekly status update" with search_docs, then read it with read_doc. Draft this week's update from the project tracker, merged pull requests, team channel and last week's status doc. Fill the KPI block and metrics table with real numbers only, and list only what actually shipped. File it with suggest_edit, one replace_section op per section (heading line kept) so each can be accepted alone. Ask each open question (unsourced numbers, the overall status color) with add_comment quoting that section's heading line, then call request_review with a one-line summary.

Related templates

Start with this template →Sign in