How to write a weekly project status report
Write a weekly project status report from a task export. Show what changed, flag blockers that threaten milestones, and name who needs to decide by when.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What a weekly project status report is
A weekly project status report is a one-page account of where a project stands at the end of a reporting week. It tells the reader whether the next commitment still holds, what changed since the last update, and which decisions need an answer. A task export supplies the counts and dates. Owner notes explain the dependencies and decisions those records may leave implicit. Together they show what changed and where the assessment depends on judgment.
A project update from tickets is useful to leadership when it connects individual tasks to project milestones, the dates or outcomes you have agreed to deliver. A launch sponsor may need to decide scope while workstream leads coordinate a blocked handoff. Start from one project and one week so the comparison has a clear basis. Make your overall assessment as of the export cutoff and call out any limits that affect how much readers can infer.
What it does for the business
- Get a decision while both options are still openA named decision owner can review the options before a workstream runs out of time. A deadline tied to a handoff clarifies when that choice affects the schedule.
- Put help where it can change the scheduleA short account of what is stuck and who can clear it lets managers direct support to the dependency holding up the next milestone. It also reveals work that needs an owner.
- Make better use of the status meetingShare the written progress and evidence before the meeting so attendees can read at their own pace. Use the time together to settle tradeoffs and get commitments from the people who own the next steps.
- Keep a usable history of changesDated snapshots and consistent counts help you explain when a promise moved and what evidence you had at the time. If a dependency repeatedly slips, that record gives you a starting point for planning a handoff differently on the next project.
Weekly project status report, step by step
Set the reporting week and reconcile the task export
A count describes the project as it stood at the cutoff used to calculate it.
What to do
- Choose the project, audience, and reporting cutoff. Take the as-of date from a dated export or confirm it with the project lead. Record the date and what supports it. Keep an export that mixes projects out of the count until you can identify the right rows.
- Save the current export and the previous snapshot of the same project. Match tasks by their stable IDs across weeks so a renamed ticket keeps its history. If you have only the previous status report, write down which aggregate counts it can support and leave individual changes unverified.
- Read the headers and check how the tool represents completion, blockers, assignees, and dates. Confirm ambiguous date formats and look for blank or rejected rows. Check the export filters for excluded statuses or workstreams before treating its total as the full project scope.
- Calculate tasks completed during the week separately from all tasks currently done. Count open, blocked, and overdue tasks using their own rules. An overdue task can also be blocked, so keep those flags visible and avoid adding overlapping counts to get the total.
- Spot-check a task completed near the cutoff and one reopened since the previous export. Disclose scope and status changes beside the comparison.
Why
An export taken midweek says little about what happened after it was saved. A renamed status or a filtered workstream can also change the reported total while the underlying work stays the same. Document the count rules so each week uses the same basis.
Find what changed the outlook
A single blocked dependency can put the next milestone at risk.
What to do
- Review changes since the previous snapshot and read the owners' updates. Group completed work by workstream. Call out what the completed items let the team do next when the evidence supports it, such as starting acceptance testing after a required handoff.
- Read every open task flagged as blocked, overdue, unowned, or stale. A stale task has gone without an update beyond the agreed interval. Ask its owner what is holding up the work, when that began, and what action would let it proceed.
- Trace project blockers to the milestones they affect. The critical path is the sequence of dependent tasks that controls the earliest possible finish. Check the dependency and the time available before the next commitment. Record the old and new dates on rescheduled tasks that affect the plan.
- Turn each escalation into a decision someone can make. State the options, name the person with authority, and work back from the affected handoff to find the latest useful answer date. Separate a request for a decision from a task the team can already carry out.
- Give one overall assessment with its reason. Use on course when the evidence supports the current plan. Use at risk when a named action by a stated date can preserve the target. Use off course when the team needs to change the delivery date or scope.
Why
The status count measures work recorded in the system. The assessment measures whether the project can still meet its commitment. For example, finishing several independent tasks can improve the count while an overdue approval consumes the time available before testing. Connecting the open task to the affected milestone lets readers see why the outlook changed and what could change it again.
Write the one-page update in decision order
A reader should be able to find their decision and deadline at a glance.
What to do
- Open with one sentence that gives the overall state and names its main cause. Use the project or milestone name your audience recognizes. Give the concrete condition for holding the date when the project is at risk.
- List decisions first in your status report template. Give each its own numbered entry with the question, viable options, decision owner, and deadline. Spell out weekdays with dates so the reader can place the decision in the working week.
- List the blockers and risks with their task names, owners, and next steps. Name the affected handoff or milestone. Use the ticket reference for traceability and explain the issue in plain words for readers who do their work outside the project tracker.
- Show what finished this week, the progress counts, and the previous week's comparable figures. Follow that with the tasks due in the next seven days. Close with the source date, what you used for comparison, and what evidence was unavailable.
- Read it once as the intended recipient. Remove detail that can live in the tracker without making any decision harder to understand. Prepare a message draft with the same evidence, owners, and dates so it can be reviewed before it is shared.
Why
A sponsor may only read the opening, while a workstream owner may need the task reference. Put the decision first and keep the evidence easy to find.
Check the claims against the source and hand off
Every figure and decision in the update should have evidence a second reader can find.
What to do
- Give a reviewer the draft, the calculated counts, the comparison, and the task evidence. Have them check every reported figure against its source and trace each named blocker and decision to a task. Verify any old and new dates along the way.
- Check the conclusion from the reader's perspective. For an at-risk assessment, make sure the stated action, authority, and deadline together could preserve the target. Check the flagged tasks for any missing item that could change that judgment.
- Make corrections in the status and the message draft together. Check that both still use the same cutoff, comparison, and decision dates. Carry forward any evidence gap that still limits the assessment so the person circulating the report can explain it.
Why
A sentence can become misleading when you shorten it even if the original analysis was right. A reviewer can catch a cumulative total labeled as weekly progress or a risk presented as a confirmed missed date. The review also checks whether the report contains enough context to support the decision it asks for.
Common mistakes
- Counting total completions as weekly progressUse completion dates within the reporting window for weekly progress and give the cumulative count its own label.
- Treating every overdue task as a milestone riskTrace the task to a named commitment and check the time available before that commitment moves.
- Comparing totals across different filtersRecord a change in scope or status mapping before using the totals to claim movement.
- Leaving a decision with a groupName the person with authority to decide and state when their answer is needed for the affected work.
- Dropping the evidence limitsState the export cutoff, missing history, and any gap that affects the reliability of a count or schedule assessment.
What a good result looks like
- One sentence gives the overall state and the specific reason for it.
- Each decision gives the options, a named owner, and a date tied to the plan.
- Each blocker or risk names the task, its effect, the owner, and the next step.
- Every progress figure has a consistent definition and a path back to the source.
- The report states next week's due work, the cutoff, and the quality of last week's comparison.
And then what? Using the result
- Send the reviewed update to stakeholders and put the decision requests in front of the people who can answer them.
- Record each answer and its date, then update the affected scope, owner, or milestone in the project plan.
- Ask workstream owners to correct stale dates and missing assignments before the next reporting cutoff.
- Save the export and the final update so the next report can compare the same project on a documented basis.
When to run it
- Before the regular project reviewCirculate the report ahead of the meeting. Bring the named options into the discussion so participants can arrive ready to decide.
- When a milestone depends on several teamsUse it to identify the handoff with the least time available and make clear which owner can clear the dependency.
- When you take over a projectUse the first export and owner notes to establish the current position. Mark any historical comparison that the available records cannot support.
Questions people ask
How do you write a weekly project status report?
Reconcile one week's task export, read the changes and owner notes, and write a one-page update that leads with the overall state and decisions needed. Include progress, risks, next week's due work, and the evidence cutoff. Verify each figure and task reference before sharing.
What should a weekly status report include?
Include the overall state, decisions needed, blockers and risks, progress against the previous week, next week's due work, and evidence limits. A sponsor should be able to see what they need to decide even if they never open the tracker.
What is the difference between a blocker and a risk?
A blocker is a current obstacle stopping work, while a risk is an uncertain event or condition that could affect a commitment. A blocked task becomes a milestone risk when the time available to clear it may run out before a required handoff.
How do you report project status without last week's export?
Report the current snapshot and use comparable figures from the previous report where their definitions are clear. Mark changes that require task-level history as unavailable. Save this week's export so you have a dated baseline for the next comparison.
How do you decide if a project is at risk?
Call it at risk when the target remains feasible if someone clears a specific blocker or makes a decision by a stated date. If the evidence shows that meeting the commitment now requires changing scope or the delivery date, use off course and name the choice the team faces.
Can 10folds send the weekly project status report?
10folds prepares a one-page status and a message draft for you to review and send. The draft carries the same project state, decisions, blockers, progress, and evidence limits as the report.
More jobs in Ops
Write the weekly project status, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac