Project Status Report
OPEN SAMPLE Turns your raw project notes into a formatted status report ready for distribution. Use it at the end of any reporting period when you need a clean document without spending an hour writing from scratch.
ROLE ·PROJECT NAME ·REPORTING PERIOD ·AUDIENCE ·OVERALL STATUS ·ACCOMPLISHMENTS ·INCOMPLETE WORK ·NEXT PERIOD PLAN ·SCHEDULE STATUS ·BUDGET STATUS ·RISKS AND ISSUES ·DECISIONS NEEDED ·PREPARER NAME
## Context
You are assisting a [ROLE: e.g., project manager, logistics coordinator, operations lead] who needs to produce a status report for [PROJECT NAME] covering [REPORTING PERIOD: e.g., Week 3, June 1-7]. The audience is [AUDIENCE: e.g., the project team, the program manager, the client]. Overall status: [OVERALL STATUS: Red, Amber, or Green]. This status was determined by the person running the project, not by the AI.
Project notes to work from:
- Accomplishments this period: [ACCOMPLISHMENTS]
- Planned work not completed and reason: [INCOMPLETE WORK]
- Planned work for next period: [NEXT PERIOD PLAN]
- Schedule: [SCHEDULE STATUS: e.g., on track, 3 days behind]
- Budget: [BUDGET STATUS: e.g., within budget, $4,200 over]
- Open risks and issues: [RISKS AND ISSUES]
- Decisions needed: [DECISIONS NEEDED: or "none"]
## Task
Produce a status report with these sections:
1. Header: project name, reporting period, date, prepared by [PREPARER NAME], overall status (Red/Amber/Green).
2. Summary: two to three sentences on where the project stands. Lead with the most important fact.
3. Accomplishments: bulleted list from my notes.
4. Next period plan: bulleted list from my notes.
5. Schedule and budget: one line each, restating the status I provided.
6. Risks and issues: each as a short entry with description and current action.
7. Decisions needed: if any, state them clearly with the owner and needed-by date I supply.
## Standards
- Restate all dates, dollar figures, percentages, and statuses exactly as I provided them. Do not compute, estimate, or adjust any number.
- Overall status (Red/Amber/Green) must match what I set above. Do not reassess it.
- Plain, direct language. One idea per sentence. Under 400 words for the full report.
- Do not invent accomplishments, risks, or issues not in my notes.
- If a section field above is blank, write "None reported" for that section and do not fill it in.
- If any named input is missing or ambiguous, ask me before drafting rather than guessing.
BEFORE YOU RUN IT
- Your own notes from the reporting period: what got done, what did not, and what is next
- The overall status (Red, Amber, or Green) set by you, based on actual schedule and budget data, not the AI
- Schedule and budget figures pulled from your project records, not estimated
- Any open risks, issues, and decisions needed, with owners and dates you can confirm
- Confirm that all dates, dollar figures, and percentages come from your project records, not from memory or AI output
- Privacy step: keep vendor names, personnel details, and contract values out of the prompt unless your organization has approved this tool for that data
VERIFY BEFORE IT LEAVES YOUR HANDS
- Overall status (Red/Amber/Green) matches your independent assessment, not whatever the AI produced
- Every dollar figure and date in the report matches your project records exactly, recheck each one
- No accomplishment, risk, or issue appears that you did not supply in your notes
- Schedule and budget status lines restate your words, not a reinterpreted version
- Decisions-needed section names the correct owner and a real deadline, not a placeholder the AI invented
- Word count: trim the summary if it runs past three sentences
- Check for invented percentages or completion figures: the AI fills gaps with plausible-sounding numbers
Sample output
Sample output. Generated by AI from sample inputs:
Project Status Report
Project: Atlas Warehouse Migration
Prepared by: Dana Ruiz, Project Manager
Reporting Period: Week 3, June 1-7, 2026
Overall Status: AMBER
Summary
The Atlas migration is three days behind the baseline schedule due to a delayed rack delivery from the vendor. Electrical rough-in is complete and all staff have completed safety orientation. Recovery plan is in place; the team expects to return to schedule by June 14 if the racks arrive as now confirmed.
Accomplishments
- Electrical rough-in completed in all four aisles (June 3)
- 47 of 50 staff completed forklift safety orientation
- Interim storage layout finalized and signed off by operations lead
Next Period Plan
- Receive and stage rack shipment (ETA June 9)
- Complete remaining 3 safety orientations
- Begin rack assembly in Aisles 1 and 2
Schedule: 3 days behind baseline. Recovery plan active; revised milestone dates distributed June 6.
Budget: Within approved budget. No variances to report this period.
Risks and Issues
- Rack delivery delay (Northwind Shelving): Racks originally due June 2 now confirmed for June 9. Vendor confirmed in writing. Monitoring closely.
- 3 staff not yet oriented: Rescheduled for June 8.
Decisions Needed
- None this period.
CUSTOMIZATION For programs with multiple projects, add a one-line rollup table at the top showing each project's status and owner. If your organization uses a specific template, feed that structure into the Task section and the AI will follow it. For classified or sensitive programs, run the prompt with sanitized notes and restore proper nouns in the final document before distribution.
Executive Update
OPEN SAMPLE Writes a one-paragraph executive update from your project notes. Use it when a senior leader needs the bottom line fast and does not need the full status report.
ROLE ·PROJECT NAME ·EXECUTIVE AUDIENCE ·REPORTING PERIOD ·OVERALL STATUS ·CURRENT SITUATION ·KEY DEVELOPMENT ·KEY ISSUE OR RISK ·EXECUTIVE ACTION NEEDED ·SCHEDULE STATUS ·BUDGET STATUS
## Context
You are assisting a [ROLE] who needs a brief executive update on [PROJECT NAME] for [EXECUTIVE AUDIENCE: e.g., the Deputy Director, the VP of Operations, the client executive]. The update covers [REPORTING PERIOD]. Overall status: [OVERALL STATUS: Red, Amber, or Green].
Key facts to include:
- Where things stand: [CURRENT SITUATION]
- The most important thing that happened: [KEY DEVELOPMENT]
- Any issue or risk the executive needs to know about: [KEY ISSUE OR RISK: or "none"]
- Any decision or action needed from the executive: [EXECUTIVE ACTION NEEDED: or "none"]
- Schedule and budget standing: [SCHEDULE STATUS], [BUDGET STATUS]
## Task
Write one tight paragraph of four to six sentences. Lead with the overall status and the most important fact. Follow with any issue the executive must know. End with the decision or action needed, if any. If no action is needed, close with one sentence on what happens next.
## Standards
- Four to six sentences only. No bullet points, no headers, no attachments referenced.
- Restate all figures, dates, and statuses exactly as I provided them. Do not interpret, estimate, or adjust them.
- Plain language an executive outside the project can understand in 30 seconds.
- No jargon, no project-management acronyms. Spell out any term that is not universally understood.
- Do not add context, background, or reassurance I did not supply.
- If any key fact above is missing, ask me before drafting.
BEFORE YOU RUN IT
- The one or two facts that matter most to this executive, from your own assessment
- Overall status (Red, Amber, or Green) set by you, not by the AI
- Schedule and budget figures from your project records, not estimated
- Any decision or action you are genuinely asking the executive to take
- Confirm all figures and dates come from your project records
- Privacy step: keep personnel details and sensitive contract terms out of the prompt unless your organization approves this tool for that data
VERIFY BEFORE IT LEAVES YOUR HANDS
- The overall status in the paragraph matches what you set, not a reassessment by the AI
- Every figure and date matches your project records exactly
- The executive action item is something you are actually asking for, not a filler placeholder
- No acronym or technical term appears that the executive would not know
- Sentence count: trim to six sentences if the AI ran over
- No invented context or background that you did not supply
Sample output
Sample output. Generated by AI from sample inputs:
The Atlas Warehouse Migration is AMBER this week. Rack delivery from Northwind Shelving arrived three days late, putting the installation schedule three days behind the June 20 baseline completion date. The vendor has confirmed a revised delivery for June 9, and the project team has a recovery plan in place to close the gap by June 14. The project remains within the approved budget with no cost variances this period. No executive decision is needed at this time; the team will report status again on June 13.
CUSTOMIZATION For organizations with a standard exec update format (traffic-light icon, one-line header, paragraph body), prepend those formatting requirements to the Task section. If the executive receives multiple project updates in one email, add a project name header so they can scan. Pair this with the full status report prompt when both a short version and a detailed version are needed in the same cycle.
Steering Committee Deck Outline
Outlines a steering committee presentation so you know exactly what goes on each slide before you open PowerPoint. Use it when a steering committee meeting is scheduled and you need a logical, audience-ready flow.
FREE WITH ACCOUNT RAID Log Builder
Builds a formatted RAID log (Risks, Assumptions, Issues, Dependencies) from your notes. Use it at project kickoff or when the existing RAID log has gone stale and needs a full refresh.
FREE WITH ACCOUNT Escalation Memo
Writes a clear, factual memo escalating a blocker to leadership when you need a decision or resource that is above your authority. Use it when a project issue has stalled and waiting longer will cost time, money, or safety.
FREE WITH ACCOUNT Weekly Team Update
Writes the weekly internal message that keeps your project team aligned on what happened, what is next, and what to watch. Use it every week to replace the ad-hoc message you are otherwise typing from scratch.
FREE WITH ACCOUNT Milestone Announcement
Writes a brief announcement when a project milestone is reached. Use it to recognize the team's work, close the loop with stakeholders, and document the completion in a shareable format.
FREE WITH ACCOUNT Schedule Slip Notification
Writes a direct, factual notification when a milestone or delivery date is going to slip. Use it as soon as you know the date will not hold, not after it passes.
FREE WITH ACCOUNT Dashboard Narrative
Writes the plain-language explanation that makes a metrics dashboard useful. Use it when you have a dashboard of numbers and need a short narrative that tells decision-makers what the numbers mean and what to do about them.
FREE WITH ACCOUNT Stakeholder Update Email
Writes a tailored update email for a specific stakeholder based on their role and interests. Use it when a standard status report is too detailed or not tailored enough for the person you are writing to.
FREE WITH ACCOUNT Status from Standup Notes
Converts your standup meeting notes into a formatted project status entry. Use it when you have a quick set of raw notes from the daily or weekly standup and need to roll them up into something shareable.
FREE WITH ACCOUNT
Bad-News Project Memo
OPEN SAMPLE Drafts a clear, factual memo delivering bad news on a project: a missed milestone, a budget overrun, or a schedule slip. Use it when the news is real and the team or sponsor needs to hear it without spin.
YOUR NAME OR ROLE ·PROJECT NAME ·AUDIENCE ·BAD NEWS SUMMARY ·ROOT CAUSE ·IMPACT ·RESPONSE ACTIONS ·NEXT DECISION OR DATE
## Context
You are a project communications assistant helping [YOUR NAME OR ROLE] draft a memo that delivers bad news on [PROJECT NAME]. The audience is [AUDIENCE: team, sponsor, client, or leadership]. The news is [BAD NEWS SUMMARY]. The memo must be honest and complete without being alarmist. Readers need the facts, the cause, the impact, and what happens next.
Project: [PROJECT NAME]
Audience: [AUDIENCE]
Bad news: [BAD NEWS SUMMARY]
Root cause or contributing factors: [ROOT CAUSE]
Impact on schedule, budget, or scope: [IMPACT]
Response actions already taken or planned: [RESPONSE ACTIONS]
Next decision or checkpoint: [NEXT DECISION OR DATE]
## Task
Draft a memo with these sections: Situation, What Happened, Impact, What We Are Doing, What We Need from You (if anything), Next Update.
## Standards
- Lead with the news in the first sentence. Do not bury it.
- State impact in concrete terms: days delayed, dollars over budget, scope removed. Use only figures from [IMPACT].
- Root cause should be factual, not defensive. One paragraph.
- Response actions are specific: who is doing what, by when. Use only actions from [RESPONSE ACTIONS]. Do not invent commitments.
- Tone is professional and direct. No hedging language that softens the facts into ambiguity.
- Under 400 words.
- Do not invent dates, costs, percentages, or status ratings not provided in the inputs above.
- If any named input is missing or ambiguous, ask before drafting.
BEFORE YOU RUN IT
- Confirmed statement of the bad news: missed milestone, overrun amount, or scope change, from your project records
- Root cause documented before writing, even a one-sentence working theory
- Impact figures pulled from your schedule or budget baseline, not estimated from memory
- Response actions already decided on, with owners and dates confirmed by those owners
- All dates, costs, and percentages must come from your project records, not generated by AI
- Confidentiality: keep vendor contract amounts, personnel details, and customer-specific data out of the prompt
VERIFY BEFORE IT LEAVES YOUR HANDS
- Impact figures match your project baseline exactly: days, dollars, and scope items are not rounded or estimated by AI
- Root cause statement is factual and does not assign blame that your records cannot support
- Response actions list only commitments that owners have actually agreed to, not hoped-for actions
- No dates appear in the memo that you did not provide in the inputs
- The memo leads with the actual news, not a softening paragraph that buries the lede
- Tone check: the memo is honest without being catastrophizing; a status rating (red/amber/green) appears only if you supplied one
- Word count and section structure confirmed before sending
Sample output
Sample output. Generated by AI from sample inputs:
MEMO
To: Atlas Warehouse Migration Steering Committee
From: Project Manager, Dana Reyes
Date: June 13, 2026
Subject: Schedule slip, Atlas migration Phase 2
Situation. Phase 2 of the Atlas warehouse migration will miss its June 20 go-live date. The new target date is July 11, 2026, a 21-day slip.
What Happened. The network infrastructure upgrade required by Northwind IT took 14 additional days due to a permit delay from the building owner. A vendor configuration error discovered on June 9 added 7 more days of rework. Both issues surfaced after the May 30 schedule baseline was set.
Impact. Go-live moves from June 20 to July 11. The delay pushes the Phase 3 kickoff by three weeks. No budget overrun is projected at this time; the vendor rework is covered under the existing contract warranty.
What We Are Doing. Northwind IT completed the network upgrade on June 12. The vendor is correcting the configuration error with a completion target of June 18. Daily stand-up calls resume Monday to monitor progress.
What We Need from You. Confirm the July 11 go-live date is acceptable or advise of any downstream constraints by June 17.
Next Update. Written update on June 20 with a revised go/no-go assessment.
CUSTOMIZATION For a sponsor audience, keep the memo short and move detail to an attached log. For a team audience, expand the What We Are Doing section with task-level assignments. If the project uses a formal change control process, note that a change request is being submitted separately. Adjust the tone for government contracts, which may require more formal language and reference to contract clauses.
All 135 prompts in this library are free with a VetsLearn account: every prompt, every checklist, synced to your account.
Unlock free with an account → Change Communication
Drafts a communication that explains a project change to affected stakeholders: what changed, why, what it means for them, and what they need to do. Use it after a change request is approved and before the change takes effect.
FREE WITH ACCOUNT Go-Live Communication
Drafts the announcement that a system, process, or service has gone live. Use it on go-live day or the day before to tell stakeholders what is now active, how to access it, and where to get help.
FREE WITH ACCOUNT Project Postmortem Summary
Turns raw postmortem notes, survey data, and team input into a structured summary: what went well, what did not, root causes, and lessons that apply to the next project. Use it after a project closes or a major phase ends.
FREE WITH ACCOUNT Decision Request Memo
Drafts a memo that presents a decision clearly: the question, the options with their trade-offs, and the recommendation with a rationale. Use it when a project or operational issue needs a decision from leadership and the meeting or email needs to be productive, not just informational.
FREE WITH ACCOUNT Monthly Operations Report
Drafts a monthly operations report from raw data and notes: performance against targets, key events, issues, and the path forward. Use it at month-end when the data is in and leadership needs a clear picture in writing.
FREE WITH ACCOUNT Customer-Facing Status Update
Drafts a status update written for an external customer or client: clear on facts, honest about issues, and focused on what the customer needs to know and do. Use it when a project or service has a customer who expects regular written updates.
FREE WITH ACCOUNT RAG Status Rationale
Drafts a written rationale for a red, amber, or green project status rating, grounding the rating in specific facts. Use it when a dashboard color alone is not enough and the audience needs to understand exactly why the rating is what it is.
FREE WITH ACCOUNT Meeting Recap and Actions
Turns rough notes from a project or operations meeting into a clean recap: decisions made, actions assigned, and next meeting. Use it within 24 hours of the meeting, while the context is still intact.
FREE WITH ACCOUNT Program Roll-Up Report
Combines status from multiple projects into a single program-level report for leadership: which projects are on track, which have issues, and what decisions the program needs. Use it when you own a portfolio or program and leadership needs one view across all of it.
FREE WITH ACCOUNT All 135 prompts in this library are free with a VetsLearn account: every prompt, every checklist, synced to your account.
Unlock free with an account → No prompts match your search. Try a different word.