Project Charter

A business wants a new warehouse system: sales imagines a customer portal, operations expects barcode scanning and finance expects reporting. If nobody authorizes the aim and boundaries, each team can start a different project under the same name.

A charter states the business need, such as fewer picking errors, shorter order-processing time or a new reporting capability, and a measurable outcome is more useful than 'modernize operations'. Name the project sponsor and manager, since the sponsor must have the authority to support the work and decide major changes, and the project manager needs to know which people, funds and decisions they can direct.

PMI describes a charter as the project initiator's or sponsor's authorization of the project and the manager's authority to apply organisational resources, and the exact format can vary. Exclude unrelated customer-app redesign unless it is separately approved, because clear exclusions stop plausible requests from silently expanding the job.

Give an initial budget range and time horizon where possible; these are planning boundaries, not false precision. At initiation, a detailed estimate may still depend on discovery, so state what is known and what must be tested.

Record assumptions, such as existing scanners being reusable or data being cleaned within a month, and if those assumptions fail the sponsor should decide whether to change scope, cost or deadline. Identify key stakeholders and dependencies, since another supplier's interface might need to be ready before the new system can be deployed.

Describe success criteria at a level the sponsor can judge: 'Reduce monthly picking errors from 120 to fewer than 40 within three months of rollout' is more testable than 'better accuracy', and the baseline and measurement owner should be recorded if available. Set decision gates, because discovery could be authorized first with a later approval for implementation once costs and technical risk are known, and the initial charter should not imply permission for later spending if that was not granted.

A charter is shorter and earlier than a project plan, which develops tasks, detailed schedule, dependencies, staffing and controls, while the charter tells the planner what the project is meant to accomplish and what authority exists. It also differs from a contract: an external supplier agreement may set payment, remedies and legal obligations, whereas an internal charter aligns the organisation's project authority.

One document may refer to the other, but do not assume they have the same legal effect. If the project manager drafts the charter, the sponsor still must approve or issue it, and PMI's project-charter discussion notes that the manager need not be its author, because the test is real authorization, not which person typed the text.

Use the charter in project reviews to ask whether the work still supports the business need, whether scope is expanding and who can authorize a trade-off, since a charter forgotten after kickoff cannot help settle later disputes. Keep it readable, as a few pages may be enough for a modest internal project while a large programme may need linked business cases and risk registers; for a business owner the charter is a decision record of why the work exists, what its first boundaries are and who may use resources, so approve it before a team treats an attractive idea as a funded commitment.