Planning & Productivity · AI Prompt
Create a Project Status Update
Turn verified project progress, milestones, blockers, decisions, owners, and next steps into a stakeholder-ready status update without inventing completion, dates, or commitments.
Context → structured prompt → explicit AI handoff
Runs in this browser. No upload by this page. External AI handoff is explicit. Review before sharing.
Configure prompt
Additional options
What you’ll need
- Project context plus verified progress, blockers, decisions, and next-step information
- Audience and reporting period
What you’ll get
- Overall status based on supplied facts
- Progress and completed work
- Milestone status
- Blockers and risks
- Decisions and changes
Prompt preview
Review or edit the generated prompt before you copy it or explicitly open an AI chat.
ChatGPT opens with the current prompt prepared. Gemini copies the current prompt, then opens Gemini so you can paste it. Keep secrets and sensitive information out of URL-carried prompts.
What this AI prompt does
This builder creates a project-status prompt from verified progress, milestone information, blockers, decisions, ownership, and next steps. It helps transform scattered workstream notes into a stakeholder-ready update that makes current state, attention items, and asks easy to scan.
The prompt is evidence-led: it should not manufacture completion percentages, dates, owner commitments, 'on track' labels, or resolved blockers. When status is missing or conflicting, the output should preserve the uncertainty and identify the information needed before a stronger statement is made.
When to use it
- You need a weekly, biweekly, milestone, client, or leadership update for work that is still active.
- Several workstreams need to be summarized without burying blockers and decisions under a long activity list.
- Stakeholders need to know what changed since the previous update, what is at risk, what decisions are required, and what happens next.
- You want one status format that can be concise for executives while still preserving enough factual detail for project owners.
What to include for better results
Status reporting works best when facts are timestamped and tied to the reporting window. Supply what has actually happened, what remains open, and which dates or owners are confirmed.
- State the project objective, reporting period, major milestones, and the verified work completed or advanced during that period.
- List blockers, risks, dependencies, decisions, and changes with current status and owner only when those details are known.
- Provide next steps, target dates, and asks that have actually been agreed; use TBD or an open question where commitment is missing.
- If you use a status label such as green/yellow/red, define the criteria or ask the model to derive no label when the evidence is insufficient.
Worked example
Project notes: A software implementation with three workstreams: configuration complete, data migration testing two days behind the planned internal date, training scheduled, one client data question unresolved, and owners supplied for the next actions.
Goal: Create a concise client-facing weekly update that explains the testing delay and required client input without inventing a new completion date or claiming the overall project is on track.
Expected result: A factual status summary, progress by workstream, milestone notes, blocker and dependency section, decisions or asks, confirmed next steps with owners, and explicit unknowns that require follow-up.
How the prompt stays grounded
The prompt should preserve the reporting period and distinguish completed work from work in progress. Phrases such as 'complete,' 'approved,' 'blocked,' 'on track,' and 'due' should reflect supplied evidence or defined status criteria, not stylistic assumptions.
A status update can summarize risk and impact, but it should not create commitments on behalf of owners. When a next step lacks an approved owner or date, the output should show that gap rather than making the document look tidier than the project really is.
Limitations
- This Builder does not connect to project-management systems, calendars, issue trackers, source control, or team communications and cannot verify current status automatically.
- A concise update may omit operational detail. Link or reference the underlying project artifacts when stakeholders need the evidence behind a summary.
- Status labels are only useful when the team shares definitions. Without criteria, a color or percentage can create false precision.
Common questions
Should I include everything completed this week?
Include work that changes stakeholder understanding of progress, scope, timing, risk, decisions, or next steps. A status update is not necessarily a complete activity log.
Can it assign an overall green/yellow/red status?
Only if you provide the criteria and enough evidence. Otherwise the output should describe the facts and leave the label unset or marked for human review.
What if a date is likely but not confirmed?
Describe it as tentative or TBD according to your source notes. Do not turn an estimate into a commitment.
When should I use the final handoff Builder instead?
Use a final summary and resource handoff when the project is closing or transferring. Use this Builder while work is still active and stakeholders need current-state visibility.
Related AI Prompts
Use a neighboring Builder when the job changes materially rather than stretching this prompt beyond its intended task.
Privacy and handoff
Project notes and status facts are assembled into the prompt locally. Mycelgrid does not read your project-management system, issue tracker, calendar, or team messages automatically.
Remove credentials, private customer or employee information, confidential financials, sensitive incident details, unreleased product information, and other data that the external AI service does not need to draft the update.