The project charter is created and approved during the initiation phase, the first phase of the project lifecycle, before any detailed project plan is built. That ordering matters: the charter authorizes the project to exist, and the plan you write afterward describes how to execute the authorized work. So the charter comes first and the plan follows. Get the sequence backward and you end up planning work nobody has formally approved.
Why the charter sits in initiation, ahead of the planning phase
Phase models vary in naming, but the sequence is consistent across the dominant frameworks. The Project Management Institute's PMBOK Guide structures project work as starting, planning, executing, monitoring and controlling, and closing. The charter belongs to the starting process group, where the project is formally authorized. Detailed planning is a separate process group that follows.
That separation is deliberate. A plan answers how, when, who, and how much. A charter answers whether the project should exist at all. If you reverse the order, the planning team spends weeks building schedules and budgets for an endeavor that may never receive an authorization signature.
The practical consequence is a hard gate. Until an approver with real authority signs the charter, the project has no budget, no assigned project manager, and no sanctioned scope. Anything produced before that signature is pre-work rather than project work.
One nuance trips people up: the charter itself is often drafted by the person who will manage the project, sometimes with a sponsor's input. Drafting is not approval. The document can circulate for weeks while the official sign-off sits pending, and during that gap the project is still not authorized.
What each phase actually produces, from pre-project to closure
Mapping deliverables to phases makes the boundary visible. If a document doesn't appear in the initiation column, it belongs to planning or later.
| Lifecycle phase | Core deliverable | What it authorizes or establishes |
|---|---|---|
| Pre-project | Business case, feasibility study | Whether a charter is worth drafting |
| Initiation | Project charter, stakeholder register (early version) | Formal project existence, sponsor, high-level scope |
| Planning | Project management plan, WBS, schedule, budget baseline, risk register | How the authorized work will be executed and controlled |
| Executing | Deliverables, work performance data | Producing the approved scope |
| Monitoring and controlling | Change requests, performance reports | Keeping execution aligned to the plan |
| Closing | Final acceptance, lessons learned | Formal completion and handover |
Read the table as a sequence of dependencies. The business case justifies a charter. The charter authorizes a plan. The plan governs execution. Each artifact depends on the one above it.
Note that the stakeholder register appears in both columns. Many teams build an early version during initiation to identify who must review the charter, then expand it during planning. That dual placement is why some sources mistakenly list the register as an initiation-only output.
The budget number in the charter is a different animal from the budget in the plan. The charter typically carries an order-of-magnitude estimate with a wide range, while the planning phase produces the cost baseline that spending is measured against. Don't treat the charter figure as a spending limit.
Who writes the charter and who signs it
The person who drafts and the person who approves are usually different, and that split is the control. A project manager or business analyst commonly drafts the charter. A sponsor or a governance body approves it. When the same person does both, you lose the challenge function that catches unfundable projects early.
Approval authority should sit above the project manager's pay grade. In a mid-size company, that's typically a department head, a program manager, or an executive steering committee. In a smaller shop, it may be a single executive who controls the relevant operating budget.
Sign-off isn't always one signature. Regulated industries often need an executive sponsor plus a finance approver plus a compliance or security reviewer. If the project touches customer data, expect a privacy review before the charter is approved. Build those review cycles into your drafting timeline.
The person named as project manager in the charter gains authority the moment it's signed. Before that signature, a project manager assigned to draft the document has no formal decision rights. That gap causes real friction when stakeholders ask early questions the drafter can't answer.
The charter's required elements and the sections drafters most often skip
A workable charter is short but specific. The standard elements cover purpose, measurable objectives, high-level scope and boundaries, key deliverables, assumptions and constraints, primary risks, a summary milestone list, the named sponsor and project manager, approval requirements, and a rough budget or resource envelope. Site-specific templates add organizational references, but those core fields recur.
Two sections are routinely thin. Measurable objectives get written as aspirations β "improve customer experience" β instead of targets with a metric, baseline, and deadline. And explicit exclusions get omitted entirely, which leaves scope boundaries undefined and invites disputes later. Write exclusions down.
High-level risks deserve more than a token line. Name two or three realistic risks and the sponsor's tolerance for them. That single paragraph shapes how much contingency the planning phase builds in.
The charter is not a detailed plan and shouldn't be judged as one. Keep it to a few pages. A skill worth building is reading your own charter draft and asking what a skeptical approver would find vague, then fixing that before the review meeting.
Nine fields that make a charter approvable on the first pass
Approval stalls for predictable reasons. A charter missing measurable objectives, a named sponsor, or explicit exclusions gives the approver nothing to say yes to. Run this checklist before submitting.
1: Purpose statement in two sentences, tied to a specific business problem. 2: Measurable objectives, each with a metric, a baseline value, and a target date. 3: High-level scope statement naming what's included. 4: Explicit exclusions naming what's out. 5: Summary milestones with approximate dates. 6: Budget or resource envelope with an estimate range and a stated basis. 7: Two or three primary risks with the sponsor's tolerance. 8: Named sponsor and named project manager, with their roles described. 9: Approval signature line with authority level and date.
If any line is blank, the approver will ask about it in the meeting. Fill the checklist first, then schedule the review.
Failure handling: if the approver requests changes, capture them in a revision log and re-circulate a tracked version rather than editing in place. If approval is declined outright, file the charter and its rejection notes in the project's pre-work archive. That record prevents the same idea being re-proposed without context.
When a fast-track project still has to pause for approval
Compressed timelines create pressure to start planning before the charter is signed. That pressure is understandable and the exception should be deliberate, never a default. Some organizations allow limited planning work in parallel with charter review, but they almost always gate spending to the pre-approval estimate range.
The licensing work is a common example of parallel activity. Permit applications, site surveys, and vendor capability conversations can often proceed at the applicant's risk while the charter is pending. The key distinction is spending: anything that commits funds past a defined threshold requires the signature first.
The hard stop should always be spending beyond the pre-approval limit. If a project team commits to a vendor contract before the charter is approved, they've created a financial obligation with no authorized project behind it. That's the failure mode, and it's expensive to unwind.
A useful rule for fast-track projects: parallel activity may prepare, but it may not commit. Preparing a draft plan, gathering quotes, or scoping options costs little and loses little if approval is declined. Signing a purchase order does not.
Reading the phase naming of charter and plan across PRINCE2 and PMI
The two dominant frameworks use different labels for the same boundary. PMI's starting process group is what PRINCE2 would split into a project mandate then a project brief. In PRINCE2, the equivalent authorization document is the project brief, approved at the end of the "starting up a project" process, before the "initiating a project" process produces the full project plan.
That difference causes real confusion. A practitioner who learned PRINCE2 may call the authorization document a brief, while a PMI-trained colleague calls the same artifact a charter. The underlying sequence is identical: authorize, then plan.
| Framework | Authorization document | Planning phase begins with |
|---|---|---|
| PMI (PMBOK Guide) | Project charter | Project management plan development |
| PRINCE2 | Project brief, then the charter-like mandate | Initiating a project process |
| Agile (general practice) | Lean business case or product vision | Release and iteration planning |
In agile delivery, the shape changes but the boundary remains. A product vision or lean business case authorizes the workstream, and release planning comes after. Nothing about iterative delivery removes the need for an authorization decision.
For a mixed or hybrid organization, the practical takeaway is to align on which artifact constitutes the authorization before drafting begins. Getting that name wrong at the outset creates confusion in approval meetings, and the charter may be rejected as inconsistent with the governance process on file.
How charter sign-off relates to the baseline and change control
The plan you build after approval becomes the baseline, and the charter is what makes that baseline relevant. A budget baseline has no enforcement power without an authorization document behind it. Change control then compares proposed changes against the baseline the charter authorized.
Treat the charter as a stable high-level document. Changes to scope boundaries, objectives, or the sponsor's identity generally require a formal amendment. Day-to-day changes belong to the plan and flow through change control. Mixing the two creates governance confusion where every minor update triggers a re-approval cycle.
Amendments follow the same approval path as the original. If a steering committee signed the charter, it amends the charter. A project manager cannot amend a document they didn't have authority to approve in the first place.
One practical safeguard: log the charter version, signing date, and approver in a project register during initiation. When disputes arise in execution, the register provides a defensible audit trail of what was authorized and when.
How the sequence shortens or lengthens your project's critical path
Approval timing has a measurable effect on delivery. A charter signed on day 9 rather than day 24 returns 15 working days to the schedule. That arithmetic is why approval timelines belong in project planning assumptions.
At an illustrative loaded cost of $1,200 per team day, a 15-day approval delay costs about $18,000 of idle capacity, assuming the team is staffed and waiting rather than redeployed. Those figures must be replaced with your own loaded rates and staffing assumptions.
The math only holds if the team is genuinely idle during the delay. Many organizations redeploy staff to other work while a charter sits in review, which erases the direct cost but still pushes the project's finish date. State which scenario applies.
Track two dates per project: charter drafted and charter signed. The gap between them is your approval cycle time, and it's the number to shrink if project starts keep slipping while capacity sits unused.
Six errors that stall charters and how each one reads in review
Patterns emerge in review meetings, and each has a fix. Recognize them before submitting.
1: Objectives with no baseline, making success unmeasurable. Fix: state the current metric value alongside the target. 2: Scope described as everything the sponsor mentioned in conversation. Fix: write inclusions and exclusions as separate lists. 3: Sponsor listed by name with no authority to approve spending. Fix: confirm the sponsor's sign-off limit before including them. 4: Budget envelope as a single number with no basis. Fix: show the estimate range and the evidence it came from. 5: Risk section empty or marked "to be determined." Fix: name two plausible risks and the tolerance level. 6: Charter used as a substitute for the plan. Fix: keep it under about four pages and move all execution detail to planning.
A seventh error shows up in the approval meeting itself: presenting the charter without a named decision-maker in the room. Confirm attendance and authority before scheduling, and you avoid the scenario where the document is discussed and no signature can be given.
FAQ
Is the project charter created before or after the business case?
The business case comes first in most structured governance processes, because it justifies why a charter should be drafted at all. In PMI-aligned organizations, the charter references the business case as its rationale. Hybrid setups sometimes draft both in parallel, but the approval sequence still puts the business case before the charter signature.
Can a project manager approve their own charter?
Ordinarily no. The approval authority should sit above the project manager's role, typically with a sponsor, program manager, or governance committee. Self-approval removes the independent challenge that catches unfunded or misaligned projects. Small organizations may technically allow it, but the control is weaker and should be documented.
How long should charter approval take?
That varies widely by organization and project risk level. Simple internal projects may clear in a week or less, while regulated or cross-departmental projects can take several weeks. Measure your own median approval cycle time across the last ten projects to set an expectation rather than importing a benchmark.
What happens if scope is added in the planning phase but not in the charter?
If the addition stays inside the charter's high-level boundaries, capture it in the plan and route it through change control. If it crosses the boundaries or alters measurable objectives, amend the charter through the original approval path. Many scope disputes trace to this exact gap between charter language and plan detail.
Does agile delivery need a charter at all?
Most agile governance still requires an authorization artifact, whether it's called a charter, product vision, or lean business case. It may be one page and lighter than a traditional charter, but the authorization decision remains. Skipping it entirely usually means someone else is approving spending informally, which is harder to audit.
Who should be listed as the charter's sponsor?
The sponsor should be the person with budget authority to fund the project and organizational influence to remove blockers. If the named sponsor can't approve the project's estimated cost, they can't perform the sponsor role effectively. Confirm the sign-off limit before finalizing the document.
Does the charter include the detailed budget?
No. The charter carries an order-of-magnitude estimate with a wide range, not a cost baseline. The detailed budget is built during planning and becomes the spending baseline. Treating the charter estimate as a hard spending limit causes clashes once real costs emerge.