Weekly Status Report Template: 4 Formats + Examples

A useful weekly status report answers four questions: what changed, what result did it produce, what is blocked, and what happens next? Start with the short template below, then choose one of four versions for an individual update, project team, leadership summary, or blocker.

Weekly Status Report Template

Copy and adapt this format:

Week of: [date range]
Project or team: [name]
Overall status: [On track / At risk / Blocked] — [one-sentence reason]

Completed and results
- [Work completed] — [measurable result or current outcome]

Blockers or decisions needed
- [Issue] — [impact]. Need [person/team] to [action] by [date].

Next week
- [Next step] — [owner] — [target date]

Keep the update brief enough to scan. Add a detail only when it helps a reader understand progress, risk, or a decision they need to make.

Already have daily notes? Draft a weekly report from your notes with AiDocX. Review and edit the result before sharing.

Choose the Right Weekly Report Format

Format	Best for	Lead with
Individual update	A personal check-in or manager 1:1	Your strongest outcome
Project team report	A cross-functional project	Overall status and milestones
Leadership summary	An executive or stakeholder who needs the decision-level view	The headline, risk, and ask
Blocker update	Work waiting on a decision or dependency	The impact and exact help needed

Use the format your team already expects if it has a required reporting process. These templates are starting points, not a replacement for internal policy.

1. Individual Weekly Status Report

Use this when you need to show your own progress without turning the update into a diary of every task.

Name:
Role or project:
Week of:

Summary:
[One or two sentences on the most important outcome and current status.]

Completed:
- [Deliverable or task] — [result]
- [Deliverable or task] — [result]

Blocked or at risk:
- [Issue, impact, and help or decision needed]

Next week:
- [Priority] — due [date]
- [Priority] — due [date]

Example: “Completed the first review of the onboarding guide and resolved 6 of 8 comments. The remaining two need a decision from Legal by Thursday. Next week: publish the approved guide and brief the support team.”

The example is illustrative. Replace the details with verified work and dates from your own project.

2. Project Team Weekly Status Report

Use this when several people contribute to one project and readers need to see milestones, dependencies, and changes in project health.

Project:
Reporting period:
Owner:
Overall status: [On track / At risk / Blocked]

Progress this week:
- [Milestone or deliverable] — [owner] — [status]

Results or measures:
- [Measure] — [current value] — [baseline or target] — [date checked]

Risks and dependencies:
- [Risk or dependency] — [impact] — [owner] — [next action]

Decisions needed:
- [Decision] — [decision-maker] — needed by [date]

Next week's milestones:
- [Deliverable] — [owner] — [target date]

If you include a percentage complete, say what it measures. “Design is 80% complete” is hard to interpret unless the team knows which work is included and what remains.

3. Leadership Weekly Summary

Use this version for readers who need the result and the decision, not a task-by-task log.

Headline:
[Most important change this week]

Status:
[On track / At risk / Blocked] — [reason in one sentence]

Results:
- [Outcome and evidence]
- [Outcome and evidence]

Risk or trade-off:
- [What may change, who is affected, and by when]

Ask:
- [Decision or support needed] — [owner] — [deadline]

Next week's focus:
- [One to three priorities]

Put the ask near the top when a decision is time-sensitive. If no action is needed from leadership, say so rather than leaving readers to infer it.

4. Blocker and Decision Update

Use this when the main purpose of the report is to get work unstuck. Name the dependency and make the request specific.

Blocked work:
[Task or deliverable]

Blocker:
[What is missing or waiting]

Impact:
[What cannot proceed, and the schedule or scope affected]

Decision or help needed:
[Specific action] from [person or team]

Needed by:
[Date and time, if relevant]

Work continuing in parallel:
[What can still move forward]

Next check-in:
[Owner and date]

“Waiting on feedback” does not tell the reader how to help. “Need Product to choose option A or B by Wednesday so Engineering can finalize the handoff” gives the dependency, decision-maker, and deadline.

Worked Example: A Concise Project Update

The sample below uses a fictional project and made-up figures to show how the sections fit together.

Project: Vendor onboarding pilot
Week of: October 5–9
Status: At risk — the final import depends on a missing vendor identifier.
Completed: Validated the intake form with the pilot team and fixed the two highest-priority field errors.
Result: In this fictional example, submissions with missing required fields fell from 12 to 4 per 100 after validation was added.
Help needed: Operations to provide the vendor identifier list by October 15.
Next week: Add the import check, then rerun the pilot with the updated list.

The measure has a unit and a comparison. The blocker names an owner and a date. If the report went to a different audience, you could keep the same facts and shorten the detail.

How to Write a Weekly Report People Can Use

1. Collect notes during the week. Capture decisions, finished work, results, and unresolved issues as they happen. A short note is more reliable than reconstructing five days from memory.
2. Lead with outcomes. Group related tasks under the result they produced. Keep routine activity only when it explains a milestone, risk, or decision.
3. Make measures understandable. Include the unit, timeframe, and comparison point. If a number is estimated, label it as an estimate.
4. Turn blockers into requests. State the impact, the person who can help, the action needed, and the date.
5. Review before sending. Check names, dates, figures, status labels, and whether the next step has an owner. Remove sensitive details that the audience does not need.

A status label should be explained in plain language. “At risk” is useful when you say what is at risk and what would return the work to plan. Keep the report factual and separate confirmed results from forecasts.

Draft a Weekly Report from Your Notes

If you already keep daily notes or task updates, AiDocX can turn them into a structured weekly report with completed work, results, blockers, and next steps. Review the draft for accuracy, edit it, then export it as PDF or Word or share it as a live link.

Try the AiDocX AI weekly report generator

The templates and example in this guide are illustrative. Verify every status, figure, owner, and date against your team's source of truth before sharing a report.