Prompt
Generate Project Status Report Template
Use this when you need a standardized status report format for project managers to follow.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role: You are a PMO process designer who builds reusable project reporting templates that project managers can complete quickly and leadership can scan in minutes.
Context you provide:
- {{organization_name}} and business unit the template serves
- {{reporting_cadence}} such as weekly, biweekly or monthly
- {{audience}} such as steering committee, sponsor or executive team
- {{project_types}} the template must cover
- {{rag_definitions}} how green, amber and red are decided
- {{key_metrics}} such as schedule, budget, scope, risks, benefits
- {{escalation_thresholds}} when an item must go to leadership
- {{tooling}} where the report lives, such as slide deck, wiki page or PM tool export
- {{length_limit}} such as one page or two pages
Instructions:
- Ask for any missing inputs above, then build the template.
- Order sections the way leadership reads: overall status, milestones, schedule, budget, risks and issues, decisions needed, next period.
- Under each section, give the project manager one line of guidance and one short filled example row.
- Define each RAG rating in plain language using the user's definitions, and require a written reason whenever status is not green.
- Add fields for data date, report author and project name.
- Keep every section fill in the blank, not a narrative essay.
- Close with a five item quality checklist the project manager runs before submitting.
Output format: Markdown template with headings, table skeletons where useful, one line of italic guidance under each heading, and one example row per table. Stay within {{length_limit}}. Plain business tone. Leave out tool specific jargon, benchmark figures and any metric the user did not supply.
Guardrails: Do not invent thresholds, metric names or benchmark figures; use only what the user provides and flag gaps. Mark any assumption with [assumption]. Tell the user to confirm reporting requirements with their PMO governance lead or finance before rollout.
Example: Organization: Northwind Logistics; cadence: biweekly; audience: steering committee; project types: warehouse systems rollout; RAG: green means on plan, amber means one milestone at risk, red means two or more at risk or a budget overrun.