# Status Meeting Prep

Builds a structured agenda and talking points for a recurring status meeting. Use it before any weekly or biweekly team sync where you need to surface progress, blockers, and next steps without letting the meeting run long.

## Prompt

## Context
You are helping [YOUR NAME AND ROLE] prepare for a recurring [MEETING CADENCE: e.g., weekly, biweekly] status meeting for [PROJECT OR TEAM NAME]. The meeting includes [ATTENDEES OR ROLES]. Date of this meeting: [MEETING DATE]. Current project phase or milestone: [CURRENT PHASE]. Items to cover from the last meeting: [CARRYOVER ITEMS]. Updates from each workstream this period: [WORKSTREAM UPDATES]. Open blockers or issues needing the group's attention: [BLOCKERS]. Decisions the group needs to make today: [DECISIONS NEEDED]. Action items from the last meeting and their current status: [PRIOR ACTION ITEMS STATUS].

## Task
Produce a clean meeting agenda with three parts: a one-paragraph opening framing the current state of the project, an ordered list of agenda items with a time allocation and owner for each, and a pre-written closing that captures the standing action-item format you want the note-taker to use. Include a parking lot section at the end for items that come up but are out of scope for today.

## Standards
- Plain language. No management jargon.
- Agenda items must come from the workstream updates and blockers I supply. Do not invent progress, milestones, or risk items.
- Time allocations must add up to the total meeting length I specify. If I do not specify a length, ask before assigning times.
- Blockers should be stated as specific questions the group needs to answer, not as vague problem statements.
- Do not invent action item owners, due dates, or resolution statuses for prior action items.
- If [WORKSTREAM UPDATES] or [BLOCKERS] are missing or vague, ask me to clarify before drafting.
- This prompt is a planning aid. Confirm all statuses, dates, and metrics with your own project records before the meeting.

## Variables

- YOUR NAME AND ROLE
- MEETING CADENCE
- PROJECT OR TEAM NAME
- ATTENDEES OR ROLES
- MEETING DATE
- CURRENT PHASE
- CARRYOVER ITEMS
- WORKSTREAM UPDATES
- BLOCKERS
- DECISIONS NEEDED
- PRIOR ACTION ITEMS STATUS

## Input checklist

- [ ] Workstream updates from each area since the last meeting, pulled from your actual tracking tool or status reports, not from memory
- [ ] Open blockers stated as specific questions the group can answer or assign
- [ ] Prior action items and their current status, confirmed before the meeting, not assumed
- [ ] Decisions needed today, with enough background that attendees can decide without lengthy explanation
- [ ] Confirm all dates, statuses, and progress figures come from your project records, not from the AI
- [ ] Confidentiality: keep vendor contract terms, personnel performance details, and sensitive cost data out of this prompt

## Verification checklist

- [ ] All workstream statuses reflect information you supplied, not AI-assumed progress
- [ ] Time allocations add up to the total meeting length you specified
- [ ] Blockers are stated as answerable questions, not vague concerns
- [ ] Prior action item statuses match what you confirmed, not what the AI guessed
- [ ] No invented milestones, percentages, or risk levels appear
- [ ] Decisions needed are clearly framed so attendees know what they are being asked to decide
- [ ] No confidential vendor, personnel, or contract details appear in the agenda

## Sample output

Sample output. Generated by AI from sample inputs:

Atlas Warehouse Migration | Weekly Status Meeting
Northwind Distribution | Tuesday, June 17, 2026 | 9:00-9:45 a.m.
Facilitator: Dana Kowalski, Project Manager

Project State
We are in Phase 2 (rack installation and network cabling) with a target completion of July 11. Phase 1 closeout is complete. Three action items from last week are closed; one is open and on today's agenda.

Agenda
1. (2 min) Quick wins from last week | Dana
2. (8 min) Workstream updates
   - Rack installation: 60 of 120 sections complete. On track. | Marcus
   - Network cabling: Vendor started Monday. Pull schedule due Friday. | Priya
   - IT provisioning: Server migration window confirmed for July 5-6. | Chen
3. (10 min) Open blocker: The fire suppression inspection is scheduled for June 30, but the vendor needs a 10-day clear before we can stage inventory. Does that change our Phase 3 start date, or do we adjust the inspection slot? Decision needed today. | Dana
4. (10 min) Prior action items review
   - Order dock levelers (due June 13): CLOSED. Delivery confirmed July 2.
   - Confirm backup power specs with facilities (due June 13): CLOSED.
   - Security badge access list to HR (due June 13): OPEN. Priya to update today.
5. (10 min) Decisions and direction
   - Go/no-go on moving Phase 3 start from July 14 to July 21 based on inspection constraint
6. (5 min) Close + action items

Action Item Format (for note-taker)
Item | Owner | Due Date | Status

Parking Lot
Topics raised today that are out of scope for this meeting go here. Owner assigned to bring back next week.

## Customization notes

For larger programs with multiple project managers, add a roll-up section at the top showing overall schedule and budget health by traffic light color, but only if you supply the actual status for each. For daily standups, cut the agenda to three items: what happened since yesterday, what is happening today, and what is blocked. For executive briefings, reorder the agenda to lead with decisions needed rather than workstream updates.

---

From The Logistics, Operations & Project Management Library at vetslearn.com/libraries/logistics-pm