Product managers · problem and fix
How to write a weekly stakeholder status report on Mac for product managers in 2026
A weekly stakeholder status report is a short written update that tells the people who depend on your product what changed, what is at risk, and what you need from them. Most product managers send one every week, and most spend more time on it than it deserves. This page covers what the habit costs, why it drifts, and the fixes you can use on your Mac this week.
The short answer
- A weekly stakeholder status report should follow one fixed shape, fit on one page, and name the decision you need.
- Most of the cost is chasing facts and answering the same questions, not typing the report.
- Pull facts from Linear filters and Slack search, then write them into one living Notion page.
- Schedule the reminder with Shortcuts, and use Slack Workflow Builder if your team already posts updates there.
- Ask Lazur to point, explain or draft, then check every line yourself before you send.
What weekly stakeholder status reports costs you
Time lost to chasing status
Asana puts 60% of time at work into 'work about work', a category that includes chasing the status of work. A status report that exists because people keep asking you is a symptom of that. The cost is not only the writing. It is every reply you send while you look up the answer.
Meetings that repeat the report
Atlassian's State of Teams 2024 says people in poor meeting cultures spend 50% more time in unnecessary meetings than on high-priority work. A status meeting that walks through a report everyone already read is one example. Each one costs the attendees time, and the written report still has to be written.
Focus you do not get back
Microsoft's 2023 Work Trend Index found 68% of workers lack enough uninterrupted focus time. Status work arrives in short bursts between meetings. Those bursts break up the longer stretches of thinking that product decisions need.
Stress you carry into Monday
MIT Sloan Management Review, citing Microsoft, reports that 48% of employees feel burned out. That figure comes from one survey question, so it is not a clinical measure. Still, a report that never feels finished can add to that load.
The hourly rate of your time
The U.S. Bureau of Labor Statistics lists a May 2025 median wage of $102,320 for project management specialists. That is about $49 an hour on a 2,080-hour year, by my arithmetic. Use it as a rough rate, not a payroll figure. No study measures what status reports cost a PM in money terms.
Why it happens
No agreed shape
Without a fixed template, you rebuild the report every week. Each rebuild asks the same questions again: what goes first, how long it runs, and what counts as a risk. The format decision eats time that should go to the facts.
Facts in too many places
Ticket status sits in Linear, discussion sits in Slack, specs sit in Notion, and dates sit in email. Each copy is a manual step, and each step can drop a line. A report built from four sources is slower and less accurate than one built from a single page.
Questions that arrive in chat
Stakeholders ask in chat, in meetings and in email. You answer each one, then write the same answer into the report. The report becomes a second copy of conversations you already had, and it arrives after they have already been read.
Writing to avoid the next question
Many reports grow long because the writer wants to head off questions. Every extra line adds cover, and the reader skims past the one line that needed a decision. No study isolates this pattern for status reports, so treat it as a common habit, not a measured one.
A meeting and a report for one update
Some teams hold a status meeting and also send the written report. Both carry the same facts. Attendees skim the report, and the meeting still runs long, so the team pays twice for one update.
How to fix it
These work with or without any app.
Freeze one template
Use a short set of headings, such as Done, Next, Risks and Asks, in the same order every week. Change the template only when a stakeholder asks a question it cannot answer. A stable shape lets readers scan quickly, and it lets you write faster.
Keep one living page
Keep one page in Notion that you update all week. Each Friday, copy the page, date the copy, and send a link instead of a fresh attachment. The latest version then lives in one spot, and nobody argues about which file is current.
Pull facts from filters, not memory
In Linear, save a view of items that changed this week and read from it. In Slack, search the channel for words such as blocked or waiting. Write only what the filters show. Memory misses things that a filter catches.
Send to the people who act
Keep the direct list short. Put the wider audience on a link, with one line that says what changed. Readers who act on nothing learn to skip the report, so a short direct list protects the read rate.
Turn the status meeting into questions
Keep the attendee list small. Let attendees talk more than the leader. Frame each agenda item as a question, such as which risk needs a call. CBS News quotes meetings researcher Rogelberg for this advice. No controlled trial backs it, so test it for a month before you keep it.
Let a form collect the updates
If your team uses Slack, Workflow Builder can post a status update form to a channel on a schedule. Each person fills in the same fields, and the answers appear in one place. Check Slack's pricing page first, because the plan claim in Slack's 2020 post may be out of date.
Automate the reminder, not the words
Use a Shortcuts Time of Day automation to remind you on the day you write, or set a Reminders item for the same time. The writing stays yours, so the report keeps your judgment. Outlook Schedule Send can hold one email, but it needs an Exchange account.
A weekly stakeholder status report usually has three jobs. It tells people what moved since last week. It flags risks before they become surprises. It asks for decisions or help you cannot make alone. When the report does all three, people stop asking you for updates in chat. When it does none, you spend the week answering the same questions in five places.
What a weekly stakeholder status report costs you
Nobody has measured the exact hours spent on status reports. The closest numbers measure related work. Asana's explainer says people spend 60% of their time at work on 'work about work', and it defines that to include chasing the status of work. That is not skilled work. The survey covered more than 10,000 knowledge workers, and the explainer does not state the survey year.
60%
of time at work goes to 'work about work', a category that includes chasing the status of work
How Work About Work Gets in the Way of Real Work, Asana57%
of Microsoft 365 time spent communicating through meetings, email and chat
2023 Work Trend Index: Will AI Fix Work?, Microsoft WorkLab68%
of workers say they lack enough uninterrupted focus time
2023 Work Trend Index: Will AI Fix Work?, Microsoft WorkLab50%
more time in unnecessary meetings in poor meeting cultures than on high-priority work
State of Teams 2024, Inside AtlassianMeetings add to the bill. Atlassian's State of Teams 2024 says people in poor meeting cultures spend 50% more time in unnecessary meetings than on high-priority work. In many teams, a status meeting that repeats a written report is one example of that. Microsoft's 2023 Work Trend Index found 68% of workers lack enough uninterrupted focus time, which is the time you need to write a clear report at all.
| Source | Figure | What it means for your report |
|---|---|---|
| Asana, work about work | 60% of time at work | Chasing status counts as work about work |
| Atlassian, State of Teams 2024 | 50% more time in unnecessary meetings | Poor meeting cultures pull time away from priorities |
| Microsoft 2023 Work Trend Index | 57% of time communicating | Email, meetings and chat fill most of the week |
| MIT Sloan Management Review | 48% of employees feel burned out | Single-question measure, not a clinical test |
Two more costs are harder to see. MIT Sloan Management Review, citing Microsoft, reports that 48% of employees feel burned out. That figure comes from one survey question, so treat it as a signal, not a diagnosis. On the money side, the U.S. Bureau of Labor Statistics lists a May 2025 median wage of $102,320 for project management specialists. That works out to about $49 an hour on a 2,080-hour year. That division is my arithmetic, not a BLS figure. If a report and its follow-up calls take a few hours each week, that time has a price.
Why status reports take longer than they should
Most reports run long for ordinary reasons. Nobody set a shape for them, so you rebuild the format every Thursday. The facts sit in three or four tools. You open Linear, then Slack, then a doc, then your calendar, and copy each piece by hand. By the time you have the facts, you have lost the energy to explain them clearly.
- No fixed template, so every week starts from a blank page.
- Facts spread across Linear, Slack, Notion and email, so you copy them by hand.
- Stakeholders ask in chat and in meetings, so the same answer gets written two or three times.
- The report tries to cover everything, so nobody finds the one decision they need.
A quick way to see the problem is to open last week's report and count the lines that are new. If most lines repeat what stakeholders already saw, the report is doing copy work. That is the part to fix first. Writing the judgment calls comes after the copying is gone.
A worked example for one product team
Take a team with one product manager, two engineers, and a designer. The PM sends a report every Friday to a short list of stakeholders. Before the fix, the PM opens Linear, scrolls the board, pastes ticket titles into a doc, checks Slack for blocked threads, and then writes a summary from memory. That takes most of an afternoon, and the summary still misses something.
After the fix, the PM keeps one Notion page with four headings: Done, Next, Risks, and Asks. Each heading holds a short list. The PM updates the page on Thursday from Linear filters, not from memory. On Friday the report is a copy of that page, with one line on top that says what changed. The copying takes minutes. The thinking takes longer, because the risks are finally visible.
Fixes you can use this week without buying anything
None of these fixes needs a new tool. Start with the ones that cost nothing but a decision.
- Pick one template and keep it for a month. Change it only when a stakeholder asks a question the template cannot answer.
- Cut the audience. Send the full report only to people who act on something in it. Link it for everyone else.
- Put the report in one place. Send a link each week instead of a new attachment, so there is one version to read.
- Move the status meeting toward questions. CBS News quotes meetings researcher Rogelberg saying to keep attendee lists small, have the leader talk less, and frame agenda items as questions.
- Put the Asks at the top. Stakeholders read the first lines first, and a decision buried at the bottom often waits.
- Automate the reminder, not the writing. A reminder keeps the date fixed without filling the report for you.
Set up a reminder and send on your Mac
Apple's Shortcuts app can run a shortcut at a set time. Open Shortcuts, select the shortcut, and click Edit. Then choose Automation and pick Time of Day. By default the shortcut asks you to confirm before it runs. To let it run without asking, open the shortcut's Info panel, go to Info > Privacy, and turn on Allow Running When Locked.
A shortcut for this can stay simple. Give it one job, such as opening the Notion page that holds your template. Keep the steps short, so the shortcut is easier to fix after an app update changes a menu. If you do not have a database for these pages yet, the Notion guide on creating a database in Notion walks through the basics.
Schedule sends in Outlook and Slack
Outlook for Mac has Schedule Send, but read the limits first. Use Send dropdown > Schedule send. Microsoft's support page documents this for individual messages only, and it needs an Exchange account. It does not work with IMAP or POP accounts such as Gmail. The page does not document recurring sends, so do not count on a repeating report.
Slack's Workflow Builder is the stronger choice if your team already works in Slack. Slack's blog describes a status update template where team members fill in a form and responses post to the channel. It also describes scheduled triggers for recurring workflows. The same post says Workflow Builder is available on any paid plan, but that post dates from March 2020. Check Slack's pricing page before you rely on it.
| Tool | Repeats on a schedule | Watch out for |
|---|---|---|
| Shortcuts Time of Day | Runs at a set time, weekly repeat not confirmed in the guide | Silent when it runs if you allow it |
| Outlook Schedule Send | Not documented for recurring sends | Exchange only, one message at a time |
| Slack Workflow Builder | Yes, scheduled triggers are described | Plan claim comes from a 2020 post |
Where Lazur helps, and where it does not
Lazur is a voice assistant for the Mac that lives in the notch. Hold ⌥ ⌘ to ask about anything on your screen, and Lazur answers out loud. Ask where a button is, and Lazur draws a circle and a label around it. Ask how to do something, and Lazur guides you one click at a time, waiting for each click. Lazur does not click for you. It does not edit files or operate other apps.
For a status report, the useful parts are explaining, pointing and dictating. Hold fn to dictate your Done and Next lists straight into the doc at your cursor. Ask Lazur to draft a summary from notes already on your screen, then check every line before you send it. Lazur also handles everyday actions such as Reminders, Calendar events and notes, so the Friday reminder can sit in the same tool. Lazur is not a plugin for Slack or Notion, and it has no partnership with either.
Lazur listens and looks at the screen only while you hold the shortcut. Audio and the screenshot go to AI providers to answer, and they are not stored. Content is never used to train AI models. Still, check your company rules before you ask any AI tool to read customer data, contract terms, or anything regulated. Your employer's rules come first.
Mistakes that make the report worse
- Writing every update as a new thread. Stakeholders lose the history, so link last week's report at the top.
- Hiding the risk in the middle. Give risks their own heading, even when the news is bad.
- Using vague status words. Write who is blocking the work and what it is waiting for, not 'on track'.
- Sending it to everyone. People who act on nothing learn to skip the report, and then they miss the one line that mattered.
- Skipping a quiet week. Send a short note that says nothing changed and why.
- Pasting sensitive data into any tool. Check your company rules first.
A routine for your first week
Start on Monday. Write the four headings in one Notion page and link last week's report under them. On Tuesday, pull the facts from Linear and Slack into those headings, and fill in only what you know. On Thursday, send the draft to one stakeholder you trust and ask what is unclear. On Friday, send the report, then set next week's reminder before you close your laptop.
What to do next
Pick the cheapest fix first, which is almost always the template. Keep it for a month, then decide what to change. If you want help while you work, see the Lazur page for product managers or the Notion guide for product managers. Lazur has a free trial that does not need a credit card. You can see the plans on the pricing page before you pay.
Faster with Lazur
Where Lazur helps with weekly stakeholder status reports
Hold ⌥ ⌘ and say what you want. Lazur sees your Notion window. Lazur reads what's on screen and writes the draft at your cursor for you to check.
- 1
Hold ⌥⌘ and talk
- 2
Lazur reads what's on screen and writes the draft at your cursor for you to check.
- 3
You stay in Notion. Nothing to copy into a chat window.
More things to say in Notion
- “Ask where the filter button is in this Linear view.”
- “Ask how to set a Time of Day automation in Shortcuts.”
- “Hold fn and dictate your Done list straight into the doc.”
- “Ask Lazur to draft a status summary from the notes on my screen.”
- “Hold ⌥ ⌘ and ask what this Risks line means for the launch date.”
- “Ask Lazur to remind me to send the report on Friday.”
Free for 3 days, then $18/month. Download for Mac
You say“Draft this week's status report from my notes under Done, Next, Risks and Asks.”
Lazur · drafts itLazur drafts short sections from the notes on screen. You fix the wording, remove any guesses, and send it yourself.
What product managers say to Lazur for this
Each one is a single hold of ⌥ ⌘.
“Ask where the filter button is in this Linear view.”
Lazur draws a circle and a label around the control, so you find it without hunting.
Points at it
“Ask how to set a Time of Day automation in Shortcuts.”
Lazur guides you one click at a time and waits for each click. You stay in control of every setting.
Walks you through it
“Hold fn and dictate your Done list straight into the doc.”
Clean, formatted text appears at the cursor in any app. You still read it before you send it.
Types what you say
“Ask Lazur to draft a status summary from the notes on my screen.”
Lazur drafts the text from what is on screen. You check each line, then send the report yourself.
Drafts it
“Hold ⌥ ⌘ and ask what this Risks line means for the launch date.”
Lazur answers out loud, based on what is on your screen. It cannot see threads or tools that are not open.
Explains what's on screen
“Ask Lazur to remind me to send the report on Friday.”
Lazur sets a Reminders item, and Apple Reminders handles the alert.
Handles the small stuff
A plan you can start this week
- Monday
Freeze the template
Write the headings in one Notion page and link last week's report under them. Keep the headings the same for the whole month, and resist the urge to add new sections.
- Tuesday
Pull facts from filters
Open a saved Linear view of changed items and copy only the lines that matter into the headings. Search Slack for blocked and waiting, then fill in only what you can confirm.
- Thursday
Test with one reader
Send the draft to one stakeholder you trust. Ask which line they could not understand and which decision they would need to make. Edit the page based on that answer, not on your guess.
- Friday
Send and set next week
Send the link, then set next week's reminder before you close your laptop. Note any question that came back, because that question shows what the template still misses.
Questions people ask
How long should a weekly stakeholder status report be?
Short enough to read in one sitting. Aim for one page with a few fixed headings. If a stakeholder needs more, link to the detail rather than adding it to the report.
Who should get a weekly stakeholder status report?
People who act on something in it. Send the full report to them, and link it for anyone who only wants to watch. Check the list every month, because the people who need the report change.
Should I send the report or hold a status meeting?
Pick the one that gets decisions made. If the report already answers most questions, a meeting can shrink to the risks and the asks. Test the change for a month before you decide.
Can I schedule the report to send every week on Mac?
Outlook for Mac documents Schedule Send for individual messages, and it needs an Exchange account. Microsoft's page does not document recurring sends. Shortcuts can run a Time of Day automation, but Apple's guide does not confirm a weekly repeat, so test it first.
Is it safe to paste customer data into an AI tool for the report?
Not until you check your company's rules. Lazur listens and looks only while you hold the shortcut, and audio and screenshots go to AI providers to answer without being stored. Your employer's rules still decide what can leave the company.
Does Lazur send the report for me?
No. Lazur drafts and types text, guides you one click at a time, and points at things on screen. You review the text and press send yourself. Lazur does not operate other apps for you.
How do I know if the report is getting better?
Count the questions that come back after each send. If the same questions keep arriving, the report is missing an answer. Track it for a month, then change one thing at a time so you can see what helped.
Sources
- How Work About Work Gets in the Way of Real Work · Asana · checked 2026-11-08
- State of Teams 2024 · Atlassian · checked 2026-11-08
- 2023 Work Trend Index: Will AI Fix Work? · Microsoft WorkLab · checked 2026-11-08
- With Burnout on the Rise, What Can Companies Do About It? · MIT Sloan Management Review · checked 2026-11-08
- Project Management Specialists: Occupational Outlook Handbook · U.S. Bureau of Labor Statistics · checked 2026-11-08
- Research shows unproductive meetings might be ruining your day · CBS News · checked 2026-11-08
- Add automations to Shortcuts on Mac · Apple Support · checked 2026-11-08
- Use Schedule Send in Outlook for Mac · Microsoft Support · checked 2026-11-08
- 5 new Workflow Builder templates for remote teams · Slack · checked 2026-11-08
Fix weekly stakeholder status reports with Lazur, free for 3 days
Hold a key and ask. Lazur sees your screen, points at the button and talks you through it, in any Mac app. No credit card.