Template

Weekly status report template

This weekly status report template puts the answer first: is the project on track, at risk or off track, and why, in one line. Then what got done this week, what’s planned for next week, the milestones and their status, risks and issues with an owner, and the decisions you need.

Fill in the builder and the report is laid out as you type, ready to paste into an email or Slack, or to download as a Word document, PDF or Markdown file.

Status report · 7 parts

  1. 01Overall status
  2. 02Done this week
  3. 03Planned for next week
  4. 04Milestones
  5. 05Risks and issues
  6. 06Decisions needed
  7. 07Key numbers

Fill in the template ↓Copy the template ↓See an example ↓

Weekly status report builder

Pick the overall status, say why in a sentence, list what got done and what’s next, and add the milestones and risks. The report appears beside the form with the status at the top. Nothing you type leaves your browser.

Weekly status report builder
Preview ↓

The report

Overall status

This week and next

Milestones

Milestone 1

Risks and issues

Risk 1

For the readers

Preview

Your status report appears here as you fill in the form: the overall status first, then what got done, what’s next, milestones and risks. Or press Fill in an example.

Copy pastes as plain text into email, Slack, Google Docs or Notion. The Word file opens in Word, Pages and Google Docs.

NoteOwl records your weekly project call on your Mac and writes the progress, decisions, blockers and next milestones for you.

What should a weekly status report include?

The overall status and why, what got done, what’s next, the milestones, risks and issues with owners, and the decisions you need. Put the status first and keep the rest to bullet points; it should take two minutes to read.

Overall status
What to writeOn track, at risk or off track, with the reason in one sentence. Many readers stop here.
Done this week
What to writeOutcomes, not activity: what is finished or has moved forward.
Planned for next week
What to writeWhat you’ll deliver before the next report.
Milestones
What to writeThe few dates that matter, each with its status.
Risks and issues
What to writeWhat could go wrong (a risk) or already has (an issue), its impact, its owner and the next step.
Decisions needed
What to writeWhat you need from the readers, from whom, and by when.
Key numbers
What to writeOptional: the figures that show progress, the same ones every week.

A weekly status report template to copy

Paste it into an email or a Slack post and fill it in each Friday. It is plain text, so it keeps its shape anywhere, and most of it carries over from last week’s report.

Send it at the same time every week. A report that doesn’t arrive reads as bad news.

weekly-status-report-template.txt
WEEKLY STATUS REPORT

Project or team:
Week ending:
Prepared by:
To:

OVERALL STATUS: on track / at risk / off track
Why, in one sentence:

DONE THIS WEEK
-

PLANNED FOR NEXT WEEK
-

MILESTONES
Milestone | Due | Done / on track / at risk / late

RISKS AND ISSUES
Risk or issue | Impact | Owner | Next step

DECISIONS NEEDED
- What, from whom, by when

KEY NUMBERS
-

What do on track, at risk and off track mean?

On track: the next milestone will be met without help. At risk: it may slip unless something changes, and you say what. Off track: it will be missed, and you give the new date or the decision you need.

On track (green)
MeansThe next milestones will be met as planned.
What to addNothing more; keep the report short.
At risk (amber)
MeansA milestone may slip unless something changes.
What to addThe risk, its owner, and what would bring it back on track.
Off track (red)
MeansA milestone will be missed.
What to addThe new date, or the decision you need to recover.
Say “at risk” early. A report that jumps from on track to off track loses its readers’ trust.

What does a good status report look like?

Like this one from a design studio to its client after two weeks of interviews: on track, the reason in one line, three things done and three planned, three milestones, two risks with owners and one decision needed by a date.

discovery-status-report.txt
WEEKLY STATUS REPORT

Project: Ferncastle onboarding discovery
Week ending: Friday, October 16, 2026
Prepared by: Maya Rao, Northlight Studio
To: Daniel Okafor, Priya Shah, Marcus

OVERALL STATUS
On track. All twelve customer interviews are done, and the findings presentation is on track for October 30.

DONE THIS WEEK
- Finished the last four customer interviews (12 of 12)
- Tagged every interview in the research board: a rejected ID photo is the top problem
- Shared a draft pilot timeline with Daniel and Priya

PLANNED FOR NEXT WEEK
- Turn the findings into the October 30 presentation
- Prototype two camera auto capture flows
- Prepare the pilot kickoff agenda with Priya

MILESTONES
- Twelve customer interviews (Oct 16, 2026, Done)
- Findings presentation (Oct 30, 2026, On track)
- Pilot kickoff (Nov 2, 2026, At risk)

RISKS AND ISSUES
- Grace hasn’t signed off the pilot risk checklist yet (High, Priya Shah, Priya raises it at Tuesday’s risk meeting)
- The Android test build came late, so only four interviews saw it (Medium, Marcus, Pilot builds a week before they’re needed)

DECISIONS NEEDED
- Daniel: confirm November 2 for the pilot kickoff, by October 23

KEY NUMBERS
- Interviews completed: 12 of 12
- Participants who had an ID photo rejected: 9 of 12

How do you write a weekly status report?

Start from last week’s report, decide the status first, list outcomes rather than tasks, raise risks early with an owner, and ask for decisions with a date. Send it at the same time every week.

  1. 1

    Copy last week’s

    Most milestones and risks carry over, so update them instead of starting fresh.

  2. 2

    Decide the status first

    On track, at risk or off track, and one sentence on why.

  3. 3

    Write outcomes

    “Finished the last four interviews”, not “worked on interviews”.

  4. 4

    Give every risk an owner

    Each risk gets an owner and a next step; raise it while it is still a risk.

  5. 5

    Ask for decisions

    Say exactly what you need, from whom and by when.

  6. 6

    Send it on time

    Same day and time every week, to the same readers.

Can NoteOwl write the status report from your project meetings?

It writes the raw material. Record the week’s project call on your Mac and choose Summarize as → Project Log: NoteOwl writes the progress since the last update, the decisions taken, the blockers and the next milestones from what was said.

  • Project Log template

    Progress, decisions, blockers and next milestones, in the order a status report needs. See the project update template.

  • Action items with dates

    Every action agreed on the call, with its owner and due date, on NoteOwl’s action items board.

  • What changed, recalled

    Ask NoteOwl what changed since last week’s call and it answers from your recordings, citing each passage. See chat with your meetings.

FAQ

Questions about weekly status reports

What is a weekly status report?

A weekly status report is a short update to a manager, client or sponsor on how a project is going: the overall status, what got done, what’s next, the risks and the decisions needed. NoteOwl’s free builder lays one out for you.

What is the difference between a status report and a project update?

They overlap. A status report is a regular, structured check on schedule and risk, usually weekly. A project update can come at any time and is often more of a story, such as the notes from a project meeting.

How long should a weekly status report be?

One screen. If the reader can’t see the status, the risks and the decisions you need without scrolling, cut the detail or link to it.

Who should get the weekly status report?

The people who need to act or decide: the sponsor, the client, and the managers of the teams involved. Keep the list the same every week, and send the detail separately to anyone who wants it.

Can I use this weekly status report template in Outlook or Word?

Yes. Copy it as plain text into an Outlook or Gmail email, or download it from the builder as a Word document or PDF to attach. The Markdown version pastes into Notion or a GitHub issue with its headings.

Can NoteOwl help with a weekly status report?

Yes. Record your weekly project call on your Mac and choose the Project Log template: NoteOwl writes the progress, decisions, blockers and next milestones from what was said, and lists every action item with its owner. No bot joins the call.

Let NoteOwl write up your project meetings

Free to download. Runs entirely on your Mac.

macOS 26 or later · Apple Silicon (M1 or newer) · 16 GB memory minimum, 24 GB recommended

About NoteOwl

NoteOwl is private AI meeting notes and memory for the Mac. It captures meetings without a bot joining the call, labels every speaker, writes summaries and action items, and builds a memory of every conversation that you can chat with — fully offline, because the speech recognition and the AI run on the Mac itself. Dictation into any app is free; Pro is a one-time purchase.

NoteOwl pricing: what’s free and what Pro adds

Last updated