Blog
weekly status report templateweekly status reportstatus report example

Weekly Status Report Template (and AI Prompt to Fill It)

Copy a weekly status report template, see a worked example, and use an AI prompt to turn messy notes into a clear update in about 5 minutes.

Portrait of Luis Chavez-Mattos
Edited by Luis Chavez-Mattos, Director, Product··RSS

For Managers, Operations and Engineering

A person feeds a chaotic pile of scribbled notes into a giant status report document that instantly organizes the handwriting into neat, printed bullet points.

What should a weekly status report template include?

A weekly status report should answer five questions for a busy reader: how is it going overall, what got done, what happens next, what is in the way, and what do you need from me. The template below covers all five on one page, in an order that lets a manager read the top three lines and stop if they want to. AI can draft it from your raw notes in a couple of minutes. You spend the rest of the time checking it.

TL;DR

  • A good weekly status report fits on one screen: an overall status, a two-sentence summary, done, next, risks, and decisions needed.
  • Put the overall status color and the reason first. Most readers never get past the top.
  • Risks and decisions are the most valuable part. Each one should name an owner, a date, and the specific ask.
  • AI is good at turning messy notes into a clean structure. It is bad at knowing what is true, so you verify every name, number and date before sending.
  • Keep a running log during the week. A status report written from memory on Friday afternoon is slow and incomplete.
  • Don't paste confidential material into an AI tool your company hasn't approved. Check your policy first.

What does a weekly status report template look like?

Copy this and save it somewhere you can reach it every Friday (or Monday, whatever your team's rhythm is).

WEEKLY STATUS REPORT
Team / project: [name]
Week of: [date]
Author: [your name]

OVERALL STATUS: [Green / Yellow / Red]
Why: [one sentence explaining the color]

SUMMARY
[Two sentences. What moved this week, and the one thing the reader
should know if they read nothing else.]

DONE THIS WEEK
- [Outcome, not activity. Include a number or result where you have one.]
- [Outcome]
- [Outcome]

NEXT WEEK
- [Planned item] (owner, target date)
- [Planned item] (owner, target date)

RISKS AND BLOCKERS
- [What could go wrong or is already in the way]
  Impact: [what happens if it isn't fixed]
  Owner: [who is handling it]
  Needed by: [date]

DECISIONS / HELP NEEDED
- [Specific question or request] from [person or group] by [date]

METRICS (optional)
- [Metric]: [this week] vs. [last week or target]

FYI
- [Anything that doesn't need action: PTO, holidays, org changes]

Three choices in this template matter more than the rest.

Status first. A reader who sees "Green" with a clear reason can move on. A reader who sees "Red" knows to keep reading. Burying this on page two is the most common mistake in status reports.

Outcomes, not activities. "Attended vendor calls" tells the reader nothing. "Vendor confirmed the delivery date of March 14" tells them something they can act on.

Risks with owners and dates. A risk with no owner is a complaint. A risk with an owner, an impact and a deadline is something your manager can help with.

What do Green, Yellow and Red actually mean?

Teams argue about this constantly, so define it once and put it in the report or your team wiki. A workable set of definitions:

StatusMeaningWhat the reader should do
GreenOn track for the committed date and scope. No help needed.Nothing.
YellowAt risk. You have a plan to recover, but something could slip.Be aware. Possibly help with a listed item.
RedWill miss the date or scope without a change or outside help.Read the whole report and respond to the ask.

Be honest about Yellow. Reports that are Green for eight weeks and then suddenly Red erode trust faster than any single slip. If you're unsure between two colors, pick the more cautious one and say why.

How do I write a weekly status report in 5 minutes with AI?

The five minutes only work if your inputs are ready. Here is the routine.

  1. Keep a running log all week (30 seconds a day). Open a note and add one line whenever something finishes, breaks, gets decided or gets blocked. Don't format it. "Tue: vendor confirmed 3/14 delivery. Priya out Thurs. Test env down again, 2nd time." That's enough.
  2. On report day, paste the log, last week's report and the template into your AI tool (1 minute). Last week's report gives the AI your tone and lets it carry forward open risks.
  3. Run the prompt below (1 minute). The model returns a filled-in draft and a list of things it couldn't determine.
  4. Check the draft against your notes (2 minutes). Use the checklist in the next section. This is where you earn your signature on the report.
  5. Send it, and save it. Next week's report starts from this one.

If you don't keep a log, you can still use the prompt. Paste in whatever you have: calendar entries, a chat thread, ticket titles, meeting notes. The draft will have more gaps for you to fill in.

If an AI note taker like Scribbl records your meetings, paste its summaries in too. Much of a status report starts in meetings.

What AI prompt turns my notes into a status report?

Paste this, replace the bracketed parts, and put your raw notes at the bottom.

You are helping me write a weekly status report for my manager
and stakeholders. Use the template below exactly.

RULES
- Use only facts in my notes. Do not invent names, numbers, dates,
  or outcomes. If something is missing, write [CONFIRM: what's missing].
- Write outcomes, not activities. Lead each "Done" bullet with the result.
- Keep the whole report under 250 words. Plain language, no jargon,
  no filler like "continued to work on".
- Overall status: use Green if on track, Yellow if at risk with a
  recovery plan, Red if a date or scope will be missed without help.
  Pick the status the notes support, and give a one-sentence reason.
  If you're unsure, choose the more cautious color and say why.
- Carry forward any risk from last week's report that my notes don't
  say is resolved.
- For every risk, include impact, owner, and needed-by date. If any
  is missing, mark it [CONFIRM].
- Under "Decisions / help needed", phrase each item as a specific
  request to a named person or group.
- After the report, add a section called "Check before sending" listing
  every [CONFIRM] item and anything in my notes that seemed to
  contradict last week's report.

TEMPLATE
[paste the template from above]

LAST WEEK'S REPORT
[paste]

MY NOTES THIS WEEK
[paste raw notes, however messy]

The "Check before sending" instruction is the useful part. It makes the model tell you where it was guessing instead of quietly filling the gap.

What does a filled-in example look like?

Here is a fictional example: a manager running an internal laptop refresh for a 400-person department.

Raw notes pasted in:

Mon: kickoff w/ vendor, they confirmed 3/14 delivery for batch 1 (150 units)
Tue: imaging process tested on 5 units, 2 failed on the VPN client
Tue: Dev says fix is a config change, should be done soon
Wed: finance asked about budget, we're about 8% over on accessories
Thu: Priya out. Sam covering helpdesk comms
Thu: sent notice to floors 2 and 3 about swap schedule, floor 4 still needs one
Fri: need decision from Dana on whether to approve extra accessory spend

AI draft after running the prompt:

WEEKLY STATUS REPORT
Team / project: Laptop refresh
Week of: [CONFIRM: date]
Author: [CONFIRM: name]

OVERALL STATUS: Yellow
Why: Batch 1 delivery is confirmed, but the imaging process is failing
on the VPN client and accessory spend is over budget.

SUMMARY
Vendor confirmed March 14 delivery of the first 150 laptops. Imaging
failed on 2 of 5 test units, and a fix is pending.

DONE THIS WEEK
- Vendor confirmed March 14 delivery for batch 1 (150 units).
- Tested imaging on 5 units. 3 passed, 2 failed on the VPN client.
- Sent swap-schedule notices to floors 2 and 3.

NEXT WEEK
- Deploy VPN config fix and retest imaging
  (owner: [CONFIRM], target: [CONFIRM])
- Send swap-schedule notice to floor 4 (owner: [CONFIRM])

RISKS AND BLOCKERS
- Imaging fails on the VPN client on some units.
  Impact: batch 1 can't be deployed on arrival.
  Owner: Dev. Needed by: [CONFIRM: before 3/14 presumably]
- Accessory spend is about 8% over budget.
  Impact: [CONFIRM]
  Owner: [CONFIRM]. Needed by: [CONFIRM]

DECISIONS / HELP NEEDED
- Dana: approve or decline the additional accessory spend by [CONFIRM].

FYI
- Priya out Thursday. Sam covered helpdesk communications.

CHECK BEFORE SENDING
- Week date, author name
- Owners and dates for next-week items
- Date Dana's decision is needed
- Impact of the budget overage
- Notes say the fix "should be done soon." I did not turn that into a date.

Notice what the AI did well: it put Yellow first with a reason, turned scattered notes into outcomes, and made a clear ask of Dana. It also refused to invent a date for the fix, which is exactly what you want. Your job is to fill in the blanks. Ask Dev for a real date, and pick a decision deadline for Dana. Then, only if you know it, change "Yellow" to "Red" or keep it.

What should I check before sending an AI-written status report?

Read the draft against your notes, not against your memory. Go through this list:

  • Every number. Unit counts, percentages, budget figures and dates. Models sometimes round, swap, or combine figures.
  • Every name and owner. Make sure the right person is attached to each item, and that nobody was assigned work they didn't agree to.
  • The status color. Ask yourself whether you would defend this color in a meeting. The AI doesn't know your politics, your stakeholders' history or what you promised last month.
  • Completed vs. in progress. AI often turns "started" or "should be done soon" into "completed." Check each Done bullet.
  • Tone. Delete anything that sounds more confident or more alarmed than you are.
  • Anything sensitive. Personnel issues, customer names, legal or financial details that don't belong in a broadly forwarded email.
  • The ask. Would the person you're asking know exactly what to do and by when?

Where should I not trust AI for status reports?

AI doesn't know what happened this week. It only knows what you told it, so the following are your responsibility.

Judgment calls. Whether a slip is Yellow or Red, whether to escalate, how to frame bad news. Use AI to draft options, then decide yourself.

Facts you didn't supply. If a date, owner or number isn't in your notes, the model may fill it in plausibly. The prompt above reduces this but doesn't eliminate it.

Confidential information. Many companies restrict what can go into public AI tools. Check your company's policy and use the approved tool. If you're unsure, remove names, customer details and financial figures before pasting, and put them back afterward.

Accountability. The report goes out under your name. "The AI wrote it" won't help if a date is wrong.

How do I adapt the template for my role?

The structure stays the same. Change what goes in the metrics section and what counts as "done."

RoleWhat to emphasize
ManagerTeam outcomes, headcount or capacity changes, decisions you need from leadership
OperationsVolume, error or backlog numbers against target, process changes, vendor issues
EngineeringShipped changes, incidents, technical risks with plain-language impact, upcoming releases
ITTickets closed vs. opened, outages, rollouts in progress, security or patch deadlines
Project leadMilestones against the plan, scope changes, budget, dependencies on other teams

If your report goes to senior leaders, cut it to the status, summary, risks and decisions. If it goes to your own team, the Done and Next sections can be longer. Many people keep one long version and one short version, and ask the AI to produce the short one from the long one: "Rewrite this as five lines for a VP who will read it on their phone."

Can I build a status report tracker instead of writing emails every week?

If your team sends dozens of these reports, the weekly email gets clumsy. Someone has to chase updates, paste them into a document, and summarize. With Remy, you can describe a small internal tool in plain English: a form where each team member submits their weekly update, a database that stores them, a rollup page for the manager showing status by project, and a scheduled reminder email on Fridays. Remy builds and deploys the app, with sign-in and a database included. You own the code. It's a paid platform ($99 a month, with AI usage billed at cost), so it makes sense when several people would use the tool every week.

Frequently Asked Questions

5 questions

How long should a weekly status report be?

One screen, usually under 250 words. If the reader has to scroll or open an attachment, many won't. Put the status and the ask at the top, and keep detail in a linked document for anyone who wants it.

What day should I send a weekly status report?

Pick a consistent day and time so readers learn when to expect it. Friday morning works for summarizing the week. Monday morning works if your stakeholders plan their week from it. Whichever you choose, don't skip weeks, because a missing report reads as a bad sign.

Can AI write a weekly status report automatically without my input?

Only if it has access to your work systems, and even then it will miss context such as verbal decisions, stakeholder concerns and the reasons behind a slip. The most reliable setup is a short running log from you, a draft from AI, and a quick review before sending.

What is the difference between a status report and a progress report?

In practice the terms overlap. A status report is typically short, recurring and focused on where things stand now (color, risks, next steps). A progress report tends to be longer and compares work completed against the original plan over a longer period. The template above is a status report. For monthly or milestone reviews, add a section comparing progress against the plan.

Should I include bad news in a weekly status report?

Yes, early and plainly. State what happened, what it affects, what you're doing about it, and what help you need. Readers handle a Yellow flagged this week far better than a Red they learn about for the first time next month.

How we source, write, and correct our articles. Editorial standards

Related articles

Straight to your inbox.
New pieces as they publish. No noise.