The project charter is created and approved during the project initiation phase, the first formal phase of the project life cycle. Before any detailed schedule, budget baseline, or work breakdown structure exists, the sponsoring organization authorizes the project by producing and signing this document. Approval of the charter is what converts an idea into an officially sanctioned project with a named manager and defined authority. Everything downstream, from requirements gathering to closure, depends on that early authorization decision.
The Authorizing Mechanism
A project charter works because it transfers authority downward. The sponsor, an executive or governing body with control over money and people, signs a document that names a project manager and grants that person the right to apply organizational resources to the work. Without that signature, a project manager has responsibility but no formal power, a mismatch that predictably produces conflict over staffing and budget.
The charter precedes detailed planning because planning costs money. Someone must decide the project is worth exploring before analysts, architects, and schedulers spend weeks producing baselines. The charter is therefore deliberately thin on detail: it states the business need, the high-level scope, measurable objectives, key milestones, the budget envelope, and the sponsor's name. It is not a plan. It is the permission to plan.
Approval happens inside initiation, not after it. In process terms, the charter is the primary output of the phase, and the phase ends when the document is authorized and the project manager is assigned. The Project Management Institute's PMBOK Guide frames this as the boundary between the pre-project world and the project world. Watch for a subtle sequencing error: teams sometimes draft a charter during a feasibility study and then treat it as approved. Drafting and approving are different events, and only the second one starts the clock.
Quantified Context: Timelines and Thresholds
Initiation is short relative to execution, but its duration varies enormously with governance weight. A small internal software project may move from concept to an approved charter in 5 to 10 business days. A regulated infrastructure or medical-device program can spend 4 to 12 weeks in initiation, mostly in business-case review and financial sign-off.
Thresholds matter more than calendars. Many organizations require charter approval by a steering committee when the requested budget exceeds a set level, commonly USD 50,000 to USD 250,000 depending on company size. Below that level, a single executive sponsor may authorize the project alone. These financial thresholds are the practical gatekeepers, and they should be written down before initiation begins, not negotiated project by project.
Money spent in initiation is small but disproportionately influential. A typical initiation effort consumes well under 5 percent of the total project budget while locking in the scope boundaries and success criteria that later drive most of the spending. A charter approved in a two-week window can shape two years of work.
Time Course of Charter Development
| Stage | Typical duration | Output | Common failure mode |
|---|---|---|---|
| Business case drafted | 1–3 weeks | Need and benefit statement | Optimistic benefits with no owner |
| Sponsor identified | Days to 2 weeks | Named accountable executive | Sponsor in name only |
| Charter drafted | 3–10 business days | Draft charter document | Scope described as a solution |
| Stakeholder review | 1–3 weeks | Comments and revisions | Silent dissent surfaces later |
| Financial and legal review | 1–4 weeks | Budget envelope, risk acknowledgment | Threshold approval bypassed |
| Formal approval | 1 day to 2 weeks | Signed charter, named PM | Verbal approval treated as final |
| Transition to planning | Immediate | Kickoff, planning team formed | Planning starts before signature |
The table exposes the counterintuitive detail: most of initiation is not writing. It is convincing. The document itself may take a week; the social and financial consensus around it takes far longer.
Edge Cases and Organizational Variants
Predictive, waterfall-style organizations place the charter squarely in initiation and expect a signature before planning begins. Agile organizations still need authorization, but they often express it as a lightweight vision statement and funding envelope rather than a detailed charter. The phase is the same; the artifact is thinner. Do not conclude that agile teams skip authorization. They compress it.
Two edge cases break the clean pattern. First, projects that begin as emergencies, such as outage recovery or regulatory remediation, may receive retrospective charters after work has already started. This is common and risky, because authority and scope get reconstructed from memory. Second, programs and portfolios often charter projects in batches, so the individual charter inherits constraints from a higher-level portfolio decision. In that case the project manager's negotiating room on scope and budget is already limited at the moment of approval.
Regulated industries add external gates. A medical-device company may hold internal charter approval until a design-control or quality review confirms the project fits its regulatory pathway. The charter phase then nests inside a compliance sequence rather than standing alone.
Misconceptions Worth Correcting
The most durable misconception is that the charter is a detailed plan. It is not, and a charter thick with task lists usually signals that planning was done too early and by the wrong people. A second misconception treats the charter as fixed forever. Scope changes after approval are handled through change control, but the charter itself can be formally amended when the business need shifts, and pretending otherwise just drives changes underground.
A third error is confusing the charter with the business case. The business case justifies the investment; the charter authorizes the work. The same team may write both, which blurs them in practice, but approval of one does not automatically approve the other. Finally, people assume the project manager writes the charter. Often the sponsor does, or the two collaborate, and the manager's involvement in drafting is a privilege of early influence, not a requirement.
Red-flag warnings to watch for:
A charter with no named sponsor, or a sponsor who never attends reviews. Objectives written as activities ("build a portal") rather than outcomes ("cut order processing time by 40 percent"). A budget range so wide it authorizes nothing, such as "somewhere between USD 200,000 and USD 2 million." Approval recorded verbally with no written record of who authorized what. A project manager assigned after planning has already started.
Practical Actions Before Sign-Off
Concrete steps reduce the chance that initiation becomes theater. Use these as a checklist, and reconcile any conflicting thresholds before circulating the draft.
Confirm the approval authority in writing: who signs, at what budget level, and with what quorum if a committee is involved. Write objectives with a number, a baseline, and a date so success is testable. Define out-of-scope items explicitly; scope exclusion prevents more disputes than scope description. Name the sponsor and record their accountability for benefits, not just for signing. List the top 3 to 5 initial risks and the assumptions the budget depends on. Get the signature before scheduling planning workshops, and store the signed version in a controlled location.
On threshold reconciliation: if finance requires steering-committee approval above USD 100,000 and your governance policy says USD 75,000, apply the lower one until the documents agree. Conflicting thresholds are an authorization defect, and auditors will treat an approval under the wrong rule as no approval at all.
Limits of the Charter Model
The charter cannot substitute for stakeholder alignment. A signature obtained by escalation, without genuine sponsor commitment, produces a document that survives audit but fails in execution. Nor does the charter guarantee good scope; it only records the scope someone was willing to authorize at a point in time. Organizations with weak portfolio governance may approve charters so routinely that the gate has no filtering function, which is a process failure the document cannot fix.
There is also a real trade-off between speed and rigor. Compressing initiation to days buys momentum and loses the dissent that review would have surfaced. The right answer depends on reversibility: cheap-to-cancel projects tolerate fast approval, while high-commitment programs justify weeks of scrutiny. The charter's value lies in making that trade-off explicit rather than accidental. It marks the moment an organization decides, in writing, to spend real resources on a defined outcome.
For organizations in regulated, financial, or safety-critical sectors, how a charter is approved and recorded may carry legal and compliance consequences. This article is general educational information, not legal, financial, or compliance advice, and it does not promise any project outcome. Consult a qualified professional familiar with your jurisdiction and industry before relying on these practices for formal governance decisions.