Project Charter

A project charter is the founding document of a project. In a page or a few, it states why the project exists (the business case or problem), what it will achieve (objectives and high-level scope), what it will not cover, who the main stakeholders and sponsor are, and what authority the project manager holds over budget and resources. Approved by the sponsor, it formally authorises the work to begin and gives the project manager a clear mandate to act.

The charter’s value is alignment and authority at the outset. It forces the sponsor and key stakeholders to agree, in writing, on what the project is actually for before work starts — which surfaces disagreements early, when they are cheap to resolve. Later, it becomes the anchor against which scope changes and disputes are judged: when someone asks whether a new request belongs in the project, the charter is where the answer starts. A project that begins without this shared understanding is far more prone to drift and conflict.

In HR and GCC programmes, a charter is a simple way to give a significant initiative firm foundations. Chartering a GCC set-up, an HR transformation, or a major hiring programme pins down the objectives, the boundaries, the sponsor, and the decision rights before the many stakeholders involved start pulling in different directions. It is especially useful in these settings because People programmes so often suffer from vague scope and unclear ownership — the very things a charter is designed to fix — and it pairs naturally with a RACI to make ownership explicit.