# Project Charter

Drafts a project charter from your goals, constraints, and stakeholder list. Use it at the start of any project to get sponsor alignment and scope boundaries written down before work begins.

## Prompt

## Context
You are a project management assistant helping me draft a project charter for [PROJECT NAME] at [ORGANIZATION NAME]. The project sponsor is [SPONSOR NAME AND TITLE]. The project manager is [PM NAME AND TITLE]. The target completion date is [TARGET COMPLETION DATE]. The project addresses this business need or problem: [BUSINESS NEED OR PROBLEM]. Budget ceiling: [BUDGET CEILING]. Key stakeholders: [STAKEHOLDER LIST].

## Task
Draft a project charter with these sections:
1. Project purpose: one paragraph. What problem this solves and why it matters now.
2. Scope summary: what is included and what is explicitly excluded.
3. Objectives: three to five measurable outcomes, each written as "By [TARGET COMPLETION DATE], [measurable result]."
4. Key deliverables: a bulleted list.
5. Constraints and assumptions: two separate bulleted lists.
6. Stakeholders: a table with name, role, and interest in the project.
7. High-level timeline: four to six milestone rows with milestone name and target date.
8. Budget ceiling: state the figure and note that detailed estimates follow in the planning phase.
9. Authority and approval: who approves scope changes and who signs off on completion.

## Standards
- Plain professional language. Short paragraphs.
- Do not invent dates, dollar figures, percentages, or metrics I did not provide. Where a field is needed and not given, write "[TO BE CONFIRMED]" and flag it.
- Objectives must be specific and measurable. If the business need as stated does not support a measurable objective, flag it rather than invent one.
- Keep the full charter under 600 words.
- This is not legal or financial advice. Contracts and budgets require review by the appropriate authority.
- If any named input is missing or ambiguous, ask before drafting.

## Variables

- PROJECT NAME
- ORGANIZATION NAME
- SPONSOR NAME AND TITLE
- PM NAME AND TITLE
- TARGET COMPLETION DATE
- BUSINESS NEED OR PROBLEM
- BUDGET CEILING
- STAKEHOLDER LIST

## Input checklist

- [ ] Project name, sponsoring organization, and the business problem the project solves
- [ ] Sponsor and PM names with titles, and a list of key stakeholders and their roles
- [ ] Target completion date and approved budget ceiling from your planning documents
- [ ] Any known constraints (regulatory, technical, resource) and assumptions already agreed to
- [ ] Confirm all dates, budget figures, and metrics come from your actual planning records, not estimated by the AI
- [ ] Keep personnel details, contract values, and vendor names out of the prompt unless your AI tool is approved for that data

## Verification checklist

- [ ] Every date in the charter was supplied by you, not generated by the AI
- [ ] Budget ceiling matches your approved authorization document exactly
- [ ] Objectives are measurable as written; reject any objective the AI made up that you did not supply
- [ ] Scope exclusions cover the boundaries you actually discussed with the sponsor
- [ ] Stakeholder table matches your actual roster; AI does not know your org chart
- [ ] Every [TO BE CONFIRMED] placeholder is resolved before the charter goes to the sponsor for signature
- [ ] No confidential personnel or contract details were included in the prompt or appear in the output

## Sample output

Sample output. Generated by AI from sample inputs:

Project Charter: Atlas Warehouse Consolidation
Northwind Industrial Supply | Prepared June 2026

Project purpose
Northwind operates two regional warehouses that were never designed to work together. Duplicate inventory, split shipments, and redundant staffing cost the company time and money every week. This project consolidates operations into one upgraded facility by end of Q3 2026, reducing per-order fulfillment time and eliminating duplicate overhead.

Scope summary
In scope: physical relocation of inventory from Site B to Site A, rack installation, updated inventory management system configuration, and staff redeployment plan.
Out of scope: system procurement (already contracted), HVAC upgrades at Site A, and any customer-facing portal changes.

Objectives
- By September 30, 2026, complete physical consolidation of all Site B inventory into Site A.
- By September 30, 2026, achieve a picking error rate no higher than the current Site A baseline of [TO BE CONFIRMED].
- By October 31, 2026, reduce fulfillment labor hours per order by [TO BE CONFIRMED] percent compared to the pre-consolidation combined baseline.

Key deliverables
- Finalized floor layout plan for Site A
- Completed rack installation
- Migrated and reconciled inventory records
- Staff redeployment plan with training schedule
- Consolidated operations go-live sign-off

Constraints
- Budget ceiling: $220,000 (approved)
- Site B lease expires October 1, 2026 (hard deadline)
- No fulfillment disruption during peak August order period

Assumptions
- Site A rack permits are approved by July 15
- Current Site B staff will be offered positions at Site A
- Inventory system vendor will support migration with two on-site days

Stakeholders
| Name | Role | Interest |
|---|---|---|
| Dana Rosenthal | VP Operations (Sponsor) | On-time delivery, cost control |
| Marcus Webb | Warehouse Director (PM) | Operational continuity |
| Yolanda Ferris | IT Manager | System migration |
| Site A and B Supervisors | Operations leads | Staff transition |

High-level timeline
| Milestone | Target date |
|---|---|
| Charter approved | June 20, 2026 |
| Floor layout finalized | July 10, 2026 |
| Rack installation complete | August 1, 2026 |
| Inventory migration complete | September 15, 2026 |
| Go-live | September 30, 2026 |
| Site B cleared | October 1, 2026 |

Budget ceiling: $220,000. Detailed estimates to follow in the planning phase.

Authority: Scope changes require written approval from Dana Rosenthal. Project completion sign-off: Dana Rosenthal and Marcus Webb.

Note: Two objectives contain [TO BE CONFIRMED] placeholders. Confirm baseline metrics before sponsor signature.

## Customization notes

For government or defense projects, add a section for applicable regulations, contract numbers, and contracting officer information. For smaller projects, trim the stakeholder table to three rows and drop the budget narrative. If your organization has a standard charter template, paste the section headers into the Context block and the AI will follow that structure instead.

---

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