Project Charter
The short document that authorizes a project and states what it's actually trying to achieve.
Quick Answer
A project charter is a short, formal document that authorizes a project and defines its objectives, scope, budget, timeline, and constraints. A sponsor issues it to give the project team authority to use organizational resources. In development and construction, it aligns the owner, design team, and contractor on what's being built and why before detailed planning starts.
The Full Picture
A project charter exists because projects need a clear starting point that everyone can point back to. Without one, teams drift into detailed planning on assumptions that were never actually agreed on — different stakeholders can hold different ideas of the budget, the timeline, or even what's in scope, and those gaps only surface once real money has been spent.
Mechanically, a charter is short by design, usually a few pages: it names the project sponsor and manager, states the business case and objectives, defines high-level scope and what's explicitly out of scope, sets a preliminary budget and timeline, lists known constraints and assumptions, and identifies key stakeholders. It's a summary that authorizes work to proceed, not a detailed plan.
In practice, the charter is signed early — often before a design team is even hired — and becomes the reference point every later decision gets checked against. When a proposed change threatens to blow past the charter's stated budget or scope boundary, that's the signal to escalate to the sponsor rather than quietly absorb it into the plan.
For preconstruction, the charter matters because it sets the ceiling the earliest feasibility studies and conceptual estimates are measured against. A precon team that never sees the charter is estimating in a vacuum, with no documented sense of what budget or scope boundary the owner actually committed to at the project's start.
Real Examples
Common Misconceptions
People assume: A project charter is the same as a project plan.
Actually: The charter is a short authorization document stating the what and why at a high level. The project plan comes later and is far more detailed — schedule, budget breakdown, procurement strategy, risk register. Confusing the two leads teams to either over-detail the charter or under-detail the plan.
People assume: A project charter is only needed on large public projects.
Actually: Any project benefits from a documented starting point, even a private one-page version. The value isn't bureaucratic process — it's having a single reference for scope, budget, and objectives that prevents scope drift and stakeholder disagreement later.
Frequently Asked Questions
What is a project charter?
A project charter is a short formal document, typically issued by a sponsor, that authorizes a project and states its objectives, high-level scope, budget, timeline, constraints, and key stakeholders. It gives the project team authority to proceed and use organizational resources.
How does a project charter work in practice?
It's drafted and signed early, often before a design team is engaged, and referenced whenever a later decision might exceed the stated scope or budget. Significant deviations from the charter typically require sponsor approval rather than being absorbed silently into the plan.
Who writes a project charter?
Usually the project sponsor or a project manager on the sponsor's behalf, in a corporate, institutional, or public-agency setting, often with input from key stakeholders on objectives and constraints before it's finalized and signed.
How does a project charter relate to a Basis of Design?
The charter authorizes the project and sets its scope and budget; the Basis of Design comes later and documents the technical criteria and system choices the design team uses to satisfy that scope. The charter answers what and why the project exists; the BOD answers how it's being designed.
Why does a project charter matter for preconstruction?
It sets the budget and scope boundary that the earliest feasibility studies and conceptual estimates get measured against. A precon team without visibility into the charter is estimating against an assumed target rather than the one the owner actually approved.