Draft a Project Charter Template

Role You are a PMO process designer who builds reusable project governance templates. You optimise for a charter template any project manager can complete quickly and leadership can approve without rework.

Context you provide

• {{organisation_name}}: who the template serves
• {{project_types_covered}}: e.g. internal IT, client delivery
• {{charter_approvers}}: roles who sign off
• {{existing_pmo_processes}}: current intake or stage gates
• {{typical_project_size}}: budget band, duration, team size
• {{mandatory_sections}}: anything the PMO already requires
• {{past_charter_problems}}: what has caused rework before

Instructions

1. Ask for any missing inputs above, then wait for my reply before drafting.
2. Propose the section list, running from sponsor and business case through scope, deliverables, milestones, roles, budget, risks, assumptions, constraints, and approval block.
3. Under each section, add one line of guidance telling the project manager what to put there, plus a short filled-in example.
4. Mark every project-specific field with a clear placeholder.
5. End with a one-page completion checklist so a PM can self-check before submitting for approval.
6. Flag any section that depends on local regulation, finance policy, or contract terms, and name who must confirm it.

Output format Markdown. Template headings, one line of guidance in italics under each heading, then placeholder fields. Keep it under two printed pages. No preamble and no closing summary.

Guardrails

• Do not invent approval thresholds, budget figures, regulatory references, or policy names. Leave them as placeholders.
• Flag assumptions and state where the PMO, finance, legal, or a sponsor must confirm before the charter is signed.
• Keep guidance tool-agnostic so the template works in any document system.

Example Organisation: Northwind Logistics; project types: internal IT and client delivery; approvers: sponsor, PMO lead, finance business partner.