# Your Weekly Status Update Is Already in This Week's Meetings > A copy-paste AI prompt that writes your weekly status update from the week's meetings: decisions, progress, risks, blockers and asks. Paste or MCP version. - URL: https://www.getvoibe.com/resources/weekly-status-update-from-meetings-prompt/ - Author: Bala - Published: 2026-11-07 ## Weekly Status Update From Meetings: The Quick Answer Friday afternoon, someone asks for the weekly status update. You scroll back through five stand-ups and a project sync, trying to remember what was decided on Wednesday. The prompt below writes the weekly status update from the week's meetings. It returns a headline, decisions, progress, risks and blockers, next week's plan and any asks, in under 250 words. It is written for team leads, project and engineering managers, and agency account leads. The input comes from your meeting notes. Voibe Work, the meeting-notes plan we build, takes notes with no bot in the call, and any other transcript works too. - **The paste version** works in ChatGPT, Claude or Gemini, with one meeting or a few summaries pasted under it. - **The MCP version** uses Voibe Meeting MCP, a Voibe Work feature that connects AI apps to your meetings. Claude Desktop, Anthropic's desktop app for Claude, reads the whole week of meetings itself. One rule in the prompt comes from my own view. The AI never picks the overall status: on track, at risk or off track. It leaves a [CHECK] marker there, the prompt's flag for anything you need to confirm. The reader holds you to that call, not the assistant. ### Key takeaways | Question | Answer | | --- | --- | | **What does the prompt produce?** | A weekly status update with a headline, overall status, decisions, progress, risks and blockers, next week and asks, under 250 words | | **Who is it for?** | Team leads, project and engineering managers, and account leads who report on a week of meetings | | **One meeting or the whole week?** | The paste version handles one meeting or a few pasted summaries. The MCP version reads every meeting in the week | | **Who sets the status?** | You do. The prompt leaves on track, at risk or off track as a [CHECK] item | | **What stays out?** | Anything said in a one-on-one meeting (1:1), and anything about a person's health, pay or performance | > **Key takeaway:** The weekly status update prompt turns a week of stand-ups, syncs and planning meetings into a headline, decisions, progress, risks and blockers, next week and asks, under 250 words, with the overall status left for you to set. ## The Weekly Status Update Prompt to Copy: The Paste Version The paste version works in any AI assistant. Copy each meeting's summary from Voibe Work, or from wherever your notes live, and paste it between the marker lines. Put the meeting name and day at the top of each summary. The prompt uses them to date decisions and to tell an old blocker from a new one. ``` Write a weekly status update from the meeting notes below. The reader is a manager who was in none of these meetings and has two minutes. Plain language, under 250 words. Sections, in this order: 1. Headline: one sentence on where the work stands this week. 2. Overall status: write [CHECK: on track, at risk or off track is your call]. Do not choose it yourself. 3. Decisions: each decision made this week, who made it, and the meeting and day it was made. 4. Progress: work finished this week, then work in progress with its owner. 5. Risks and blockers: what is stuck, what it affects, who can unblock it, and the day it was first raised. 6. Next week: planned work and commitments, with dates only where someone stated them. 7. Asks: help the reader can give, or none. Rules: - Use only names, dates, figures and commitments that appear in the meetings. Never invent a deadline or an owner. - List a decision only if someone agreed to it. A topic that was only discussed is not a decision. - If a blocker raised early in the week was resolved later, list it under Progress as resolved, not under Risks. - Leave out anything about a person's health, pay or performance, and anything said in a 1:1. - If an owner, a date or whether something was decided is unclear, write [CHECK: what is unclear]. - End with a list of every [CHECK] item, or none. --- NOTES START --- [paste each meeting's summary or transcript, with the meeting name and day at the top] --- NOTES END --- ``` ### Why the prompt is built this way - **A reader who wasn't there:** naming the reader keeps the update free of meeting shorthand. The two-minute limit keeps it short. - **Decided versus discussed:** an assistant will happily turn a long discussion into a decision. The prompt lists a decision only when someone agreed to it. - **Blockers that cleared:** a blocker from Monday that was fixed on Tuesday belongs under Progress. Reporting it as a risk on Friday makes the week look worse than it was. - **No 1:1 content:** a status update goes to a wide audience. Anything from a 1:1, or about someone's health, pay or performance, stays out. - **[CHECK] markers:** the AI writes [CHECK: what is unclear] instead of guessing an owner or a date. The list at the end shows you what to confirm. Whatever you paste into an assistant goes to the company behind it, under that company's terms. That means OpenAI for ChatGPT, Anthropic for Claude and Google for Gemini. ## Paste Version or MCP Version for a Weekly Update Pick the version by how many meetings the week holds. A team with one weekly sync can paste one summary. A team with daily stand-ups and two syncs will find the MCP version faster. | Your week | Use | | --- | --- | | One weekly team meeting | The paste version, with that meeting's summary | | Two or three meetings | The paste version, with each summary pasted under the prompt | | Daily stand-ups plus syncs and planning | The MCP version, in Claude Desktop | | A quick question about one meeting, such as what was agreed on Wednesday | Chat with your meetings, inside Voibe Work | Chat with your meetings is the chat built into Voibe Work. It answers from one meeting, runs on Voibe's zero-retention cloud, and stores nothing you ask. If your stand-up notes already follow one format, both versions work better. Our [stand-up meeting notes template](https://www.getvoibe.com/resources/standup-meeting-notes-template/) gives every stand-up the same done, doing and blocked sections. ## The MCP Version: Let Claude Read the Whole Week of Meetings The MCP version uses Voibe Meeting MCP, the Voibe Work feature that lets AI apps such as Claude read your meetings. MCP, short for Model Context Protocol, is the standard AI apps use to connect to other software. With it connected, Claude reads the week's stand-ups and syncs itself and writes the update. The [Model Context Protocol site](https://modelcontextprotocol.io/) describes MCP as an open-source standard for connecting AI applications to external systems. ### Connect Meeting MCP to Claude Desktop 1. **Open the Meeting MCP panel:** in Voibe Work, click MCP on the Meetings page. Check that the switch labelled Let AI apps use your meetings is on. 2. **Add it to Claude:** on the Claude tab, click Add to Claude, and Claude Desktop opens. 3. **Install it:** when Claude shows Voibe Meeting MCP, click Install, and the connection is done. Meeting MCP comes with Voibe Work and the 7-day trial, not with Voibe Free or Voibe Dictation. The [Meeting MCP launch post](https://www.getvoibe.com/resources/voibe-meeting-mcp/) covers what the panel shows. ### The MCP version of the prompt ``` Read this week's team meetings about [project] in Voibe, from Monday 2 November to Friday 6 November: the daily stand-ups, the project syncs and any planning meetings. Before the update, list the meetings you read, with each one's day and title, so I can check you picked the right ones. Skip 1:1s and any meeting that is not about [project]. Then write a weekly status update. The reader is a manager who was in none of these meetings and has two minutes. Plain language, under 250 words. Sections, in this order: 1. Headline: one sentence on where the work stands this week. 2. Overall status: write [CHECK: on track, at risk or off track is your call]. Do not choose it yourself. 3. Decisions: each decision made this week, who made it, and the meeting and day it was made. 4. Progress: work finished this week, then work in progress with its owner. 5. Risks and blockers: what is stuck, what it affects, who can unblock it, and the day it was first raised. 6. Next week: planned work and commitments, with dates only where someone stated them. 7. Asks: help the reader can give, or none. Rules: - Use only names, dates, figures and commitments that appear in the meetings. Never invent a deadline or an owner. - List a decision only if someone agreed to it. A topic that was only discussed is not a decision. - If a blocker raised early in the week was resolved later, list it under Progress as resolved, not under Risks. - Leave out anything about a person's health, pay or performance, and anything said in a 1:1. - If an owner, a date or whether something was decided is unclear, write [CHECK: what is unclear]. - End with a list of every [CHECK] item, or none. ``` Replace [project] with your project's name, and change the dates each week. The meeting list at the top shows whether Claude read the right meetings before you trust the update. The prompt skips 1:1s on purpose. A 1:1 belongs to the two people in it, and our [One-on-One meeting notes template](https://www.getvoibe.com/resources/one-on-one-meeting-notes-template/) keeps those notes separate. ## Worked Example: An Invented Week Becomes a Status Update The week below is invented for illustration. A four-person team is redesigning an online checkout, and the input is three short meeting summaries pasted under the paste version. ``` Checkout redesign, week of 2 November Monday stand-up - Ana: finished the new address form. Today: the payment step. - Joel: blocked, waiting on staging access from IT. - Sam: writing tests for the address form. Wednesday project sync - Decided: the redesign launches to 10% of users first, not to everyone. Priya decided. - Joel: staging access arrived Tuesday. Now building the order summary. - Risk: the payment provider's new API version is not in its sandbox yet. Priya to ask the provider by Friday. Friday stand-up - Ana: payment step done, in review. - Sam: address form tests passing. Next week: payment step tests. - Joel: order summary half done, expects to finish Tuesday. - Priya: the provider says its sandbox gets the new API version next Wednesday. ``` ### What the prompt returns ``` Headline: The checkout redesign's address form is built and tested, and the payment step is in review. Overall status: [CHECK: on track, at risk or off track is your call] Decisions - The redesign launches to 10% of users first, not to everyone (Priya, Wednesday project sync). Progress - Done: new address form (Ana), with tests passing (Sam). - Done: payment step, now in review (Ana). - Resolved: Joel's staging access arrived Tuesday. - In progress: order summary (Joel), half done. Risks and blockers - The payment provider's new API version is not in its sandbox yet. What it affects: [CHECK: not stated in the meetings]. The provider says the sandbox gets it next Wednesday (Priya, Friday stand-up). First raised Wednesday. Next week - Payment step tests (Sam). - Order summary, expected Tuesday (Joel). - Provider sandbox update, expected Wednesday. Asks - None. [CHECK] items - Overall status. - What the provider risk affects. ``` ### What to notice in the output - **The blocker moved:** Joel's staging access was a blocker on Monday and arrived on Tuesday. The update lists it under Progress as resolved. - **The status is yours:** the provider risk could make the week at risk or on track, depending on your launch date. The prompt leaves that call to you. - **Nothing was added:** every name, day and figure in the update, including the 10% launch, comes from the three summaries. Nobody said what the provider risk affects, so the AI marked it [CHECK] instead of guessing. ## How to Adapt the Weekly Status Update Prompt The same week of meetings can feed several updates. Change the reader line and the word limit first, then the sections. ### Change the reader - **An executive:** set the limit to under 100 words, and keep only the headline, the status, the top risk and the asks. - **A client:** set the limit to under 200 words. Keep progress, next steps with dates and what you need from the client. Leave out internal blockers and who said what inside the team. - **The team channel:** add a short block per person and keep ticket IDs exactly as spoken. ### Change the period or the meetings - **A sprint or a month:** change the date range in the MCP version, and add a section for what changed since the last update. - **Client projects:** point the MCP version at the week's client calls instead of internal syncs. The [meeting follow-up email prompt](https://www.getvoibe.com/resources/meeting-follow-up-email-prompt/) covers the message after a single call. - **Open actions only:** if the reader wants a to-do list rather than a narrative, use the [meeting action items prompt](https://www.getvoibe.com/resources/meeting-action-items-prompt/). It lists owner, task and due date for every open action. Work that should become tickets needs a different output. The [meeting notes to tickets prompt](https://www.getvoibe.com/resources/meeting-notes-to-tickets-prompt/) drafts tickets with acceptance criteria from the same meetings. ## What to Check Before You Send the Weekly Update Read the update against the meetings before it goes out. A status update gets forwarded, so a wrong date or owner travels further than it would in a chat. 1. **Set the overall status:** replace the [CHECK] marker with on track, at risk or off track, in your own judgment. 2. **Confirm each decision:** open the meeting it came from and make sure someone agreed to it, rather than only raising it. 3. **Check owners and dates:** every name and deadline should match what was said. Voibe Work's transcript puts a time next to every line, which makes this quick. 4. **Refresh the blockers:** a blocker can clear after Friday's meeting. Ask the owner before you report it as open. 5. **Read it as the recipient:** for a client or an executive, remove internal names, disagreements and anything you wouldn't want forwarded. Clear every item on the [CHECK] list at the bottom before you send. An update with a stray marker tells the reader nobody read it first. ## Run the Weekly Status Update Prompt on Your Voibe Work Meetings Voibe Work records the meetings this prompt reads. It captures stand-ups, syncs and planning meetings from your Mac or Windows PC, and no bot joins the call. That works in Zoom, Microsoft Teams, Google Meet, Webex, Slack huddles or any other meeting app. It also records in-person meetings through your computer's microphone. Our guide to [recording an in-person meeting on your laptop](https://www.getvoibe.com/resources/how-to-record-an-in-person-meeting-on-your-laptop/) covers a stand-up held around a desk. ### Where the input comes from - **Transcript and summary:** each meeting gets a transcript with speaker labels and a time on every line, plus a summary. Voibe Work summarizes each meeting with a template for its type, such as client intake or investment committee. You can also create your own template. - **For the paste version:** copy each summary in one click, or export it as a PDF. Then paste it under the prompt. - **For the MCP version:** connect Meeting MCP to Claude Desktop once, and Claude reads the week's meetings itself. ### What happens to the meetings and the notes Meeting audio is processed by open-source models on zero-retention cloud providers and deleted as soon as processing completes. The transcript and summary are saved on your computer, not on Voibe's servers, and never used to train AI. Processing runs in the cloud, so meeting notes need an internet connection. The Meeting MCP panel puts it in these words: “Apps you connect can read your meeting titles, summaries and transcripts. Your dictation is never shared. What an app reads goes to the company behind its AI, for example Anthropic for Claude. None of it goes through Voibe's servers.” With the paste version, what you paste into an assistant goes to that AI company under its terms. Turning off Let AI apps use your meetings stops every AI app at once. Our guide to [giving Claude access to your meeting notes](https://www.getvoibe.com/resources/how-to-give-claude-access-to-meeting-notes/) compares the routes. When recording starts, Voibe reminds you to tell everyone you're taking notes. Following the [recording consent rules](https://www.getvoibe.com/resources/ai-notetaker-recording-consent-laws/) for each person's location is your responsibility. ### What it costs Voibe Work costs $19 a month, $149 a year or $399 lifetime per seat. One seat covers Mac and Windows. Every new account starts with a 7-day trial of every Voibe Work feature, Meeting MCP included. The trial needs no credit card and makes no automatic charge. After the trial the account moves to Voibe Free, which covers dictation but not meeting notes. New to Voibe Work? The [first-week setup guide](https://www.getvoibe.com/resources/getting-started-with-voibe-work/) walks you through it. ## Weekly Status Update Prompt FAQ ### The prompt **What should a weekly status update include?** A headline, the overall status, decisions, progress, risks and blockers, next week's plan and any asks. The prompt keeps all of that under 250 words. **Why doesn't the AI set the overall status?** On track, at risk or off track is a judgment your reader holds you to. The prompt leaves it as a [CHECK] item for you to fill in. **Can I write a status update from one meeting?** Yes, paste that meeting's summary under the paste version. The sections still work for a single weekly sync. ### The MCP version **Can Claude read a week of meetings on its own?** Yes, in Claude Desktop with Voibe Meeting MCP connected. The paste version covers one meeting or a few pasted summaries in any assistant. **Will Claude include my 1:1s?** The MCP version tells Claude to skip 1:1s and list the meetings it read, so you can check before you send. ### Voibe Work and privacy **Does Voibe Work join stand-ups as a bot?** No, it captures each meeting from your Mac or Windows PC. Voibe reminds you to tell everyone you're taking notes when recording starts. **Where are the meeting notes kept?** On your computer, not on Voibe's servers, and the audio is deleted once processing completes. What a connected AI app reads goes to the company behind it. **How much does Voibe Work cost?** It costs $19 a month, $149 a year or $399 lifetime per seat. A 7-day trial of every feature needs no credit card. ## Let the Week's Meetings Write Friday's Update The week's meetings already hold the decisions, progress and blockers your update needs. Paste one meeting under the paste version, or connect Meeting MCP and let Claude read the whole week. Keep the decided-versus-discussed rule and the blank status when you edit the rest. More prompts for other jobs, including [feature requests from customer calls](https://www.getvoibe.com/resources/feature-requests-from-customer-calls-prompt/), are in our [AI prompts for meeting notes](https://www.getvoibe.com/resources/ai-prompts-for-meeting-notes/) library. ## Frequently asked questions ### What should a weekly status update include? A weekly status update should include a one-sentence headline, the overall status, the decisions made that week, progress on finished and in-progress work, risks and blockers with who can unblock them, next week's plan and any asks for the reader. Voibe's prompt keeps it under 250 words for a reader who was in none of the meetings. ### Can ChatGPT write a weekly status update from meeting notes? Yes. Copy the paste version of the prompt into ChatGPT, Claude or Gemini with each meeting's summary between the marker lines, with the meeting name and day at the top of each. What you paste goes to that AI company under its terms. ### Can Claude write a status update from a whole week of meetings? Yes, with Voibe Meeting MCP connected to Claude Desktop. Meeting MCP is a Voibe Work feature that lets AI apps such as Claude read your meetings, so Claude reads the week's stand-ups and syncs itself. The MCP version asks Claude to list the meetings it read before it writes the update. ### Should AI decide whether a project is on track? No. Voibe's prompt leaves on track, at risk or off track as a [CHECK] item for you to set, because the reader holds the person sending the update to that judgment. The AI fills in the decisions, progress and blockers from the meetings. ### How do I stop the AI from inventing decisions or deadlines? Tell it to use only names, dates, figures and commitments that appear in the meetings, to list a decision only if someone agreed to it, and to write [CHECK: what is unclear] instead of guessing. Then check each decision and date against the meeting before you send. ### What can an AI app see when I connect Voibe Meeting MCP? The panel says apps you connect can read your meeting titles, summaries and transcripts, and your dictation is never shared. What an app reads goes to the company behind its AI, for example Anthropic for Claude, and none of it goes through Voibe's servers. One switch stops every AI app at once. ### Does Voibe Work need a bot to record stand-ups and syncs? No. Voibe Work captures meetings from your Mac or Windows PC in Zoom, Microsoft Teams, Google Meet, Webex, Slack huddles or any other meeting app, with no bot in the call, and records in-person meetings through the computer's microphone. Voibe reminds you to tell everyone you're taking notes, and following consent rules is your responsibility. ### How much does Voibe Work cost? Voibe Work costs $19 a month, $149 a year or $399 lifetime per seat, and one seat covers Mac and Windows. Every new account starts with a 7-day trial of every Voibe Work feature, including Meeting MCP, with no credit card and no automatic charge. ## Related - [AI Prompts for Meeting Notes](https://www.getvoibe.com/resources/ai-prompts-for-meeting-notes/): Every prompt in the library, grouped by job. - [Standup Meeting Notes Template](https://www.getvoibe.com/resources/standup-meeting-notes-template/): Done, doing and blocked, the same way every day. - [Meeting Action Items Prompt](https://www.getvoibe.com/resources/meeting-action-items-prompt/): Owner, task and due date for every open action. - [Introducing Voibe Meeting MCP](https://www.getvoibe.com/resources/voibe-meeting-mcp/): Ask Claude and ChatGPT about all your meetings. - [How to Give Claude Access to Your Meeting Notes](https://www.getvoibe.com/resources/how-to-give-claude-access-to-meeting-notes/): Four routes, and what Anthropic sees in each. - [Getting Started With Voibe Work](https://www.getvoibe.com/resources/getting-started-with-voibe-work/): Your first week of meeting notes, from install to your first template.