A project charter is the founding document of a project — the agreement between the project team and the sponsoring organization about what the project will do, what it will cost, how long it will take, and what success looks like. A good project charter prevents most of the disputes that derail projects later. A bad one — vague in scope, silent on constraints, unclear on governance — creates the conditions for those disputes and provides no basis for resolving them.
What the Charter Must Contain
The project charter that consistently gets executive sign-off and stays signed off throughout the project contains six essential elements. First, a problem statement — a clear, concise description of the specific business problem or opportunity the project addresses, in terms the executive audience can validate from their own experience. Second, a scope statement — an explicit definition of what is included in the project and, critically, what is excluded. The exclusions are as important as the inclusions; they prevent scope creep and manage expectations. Third, a success criteria statement — how the organization will know the project succeeded, expressed in measurable terms. Fourth, a budget and timeline — the investment required and the time it will take, with the assumptions that underpin both. Fifth, a risk statement — the top five project risks and the planned responses. Sixth, a governance structure — who is sponsoring the project, who is making decisions, and how conflicts are escalated.
The Scope Statement That Prevents Disputes
The scope statement that prevents disputes is the one that is specific enough to make boundary questions easy to answer. “The project will implement modules for financial accounting, accounts payable, accounts receivable, and fixed assets” is a scope statement. “The project will implement the finance function of the ERP system” is not — it leaves the boundary question open for everyone to answer differently. When scope disputes arise in an ERP project, the question is almost always: was this in scope? The answer should be findable in the charter.
Getting Real Sign-Off
Executive sign-off on a project charter means something only if the executive has read and understood what they are signing. The charter review meeting should walk through each element explicitly, invite challenges to the scope and success criteria, and surface the reservations or conditions that executives have before, not after, the project starts. A charter signed without genuine engagement is a document — not a commitment. When the project encounters difficulty and the sponsor needs to make a hard call, the quality of the initial charter conversation determines whether they make it from a position of informed commitment or confused surprise.