WEEKLY PROGRESS REPORT
A weekly progress report shows movement over time. It tells the reader what finished, what advanced, what is still underway, and whether the work is keeping pace with the plan.
Progress is about change. A useful report does more than list tasks: it shows how far the work moved during the week and what that means for the larger plan.
That can be simple. If a redesign moved from wireframes to approved desktop screens, say that. If a migration remains at 60% because a dependency slipped, keep both the progress and the delay visible.
Use percentages only when the team actually tracks them. “About two-thirds complete” may be more truthful than “67% complete” if the source does not support an exact number.
COPYABLE TEMPLATE
This structure works well for projects and workstreams where the reader needs to understand movement from one week to the next.
What materially moved this week and whether the plan changed.
COMPLETED EXAMPLE
This example reports a website redesign. Notice that the report says what changed relative to the plan instead of treating every task as equal.
Desktop design moved from review to approval this week, while mobile work is still in progress. Front-end implementation can start on the approved pages, but the content handoff is running about three days late and may affect the next milestone.
PROGRESS VS. STATUS
A progress report is useful when the reader wants to see movement against a plan. A status report is more useful when the question is whether the work is healthy, at risk, or blocked right now.
“Desktop design approved. Mobile review is still open. Content handoff is three days late.” Focus: what moved and what did not.
“Overall status: At risk. The content delay may push the next milestone unless final copy arrives by Thursday.” Focus: current condition and impact.
If project health and decisions matter more than week-over-week movement, use the weekly status report guide instead.
HOW TO WRITE IT
Progress only makes sense relative to something: last week, a milestone, a target, or a defined stage.
Do not make active work look finished just to make the report cleaner.
“Copy is late” is useful context. “Copy is three days late and may delay integration” tells the reader why it matters.
Next-week priorities should follow naturally from what remains unfinished, blocked, or ready to move.
Bring the raw updates together first, then review the report for status, evidence, and next steps.