The PMBOK® Guide, Eighth Edition, from PMI®, groups its processes into five focus areas, and Initiating is the first. It answers three questions before serious money is spent: why are we doing this, who is authorizing it, and who cares about it? For an owner, Initiating happens more than once. It happens when the project is approved, and it happens again at the start of each phase, including the weeks between tender close and the construction kickoff.
Learning outcomes
- Name the five focus areas and explain why they are not the same as project phases.
- Describe the purpose of the Initiating focus area and the two processes most closely tied to it.
- Draft a one-page phase charter for an owner's construction phase.
- Plan the initiating work for Northgate's construction phase between tender close and kickoff.
The lesson
Focus areas, not phases
The Eighth Edition brings back process guidance that the Seventh Edition had dropped, in a deliberately less prescriptive form: 40 processes, each described by inputs, tools and techniques, and outputs. They are organized two ways. By performance domain (governance, scope, schedule, finance, stakeholders, resources and risk), and by focus area: Initiating, Planning, Executing, Monitoring and Controlling, and Closing. Lesson 3 showed how the layers fit together.
Readers who studied for the PMP® exam on the Sixth Edition will recognize the five names from the old process groups. The intent is similar, but the framing has shifted: focus areas describe the kind of attention a piece of work needs, not a stage the project passes through once. A focus area can repeat, overlap with others and loop back. A project in construction is mostly executing and controlling, but when a new phase or a major new package starts, initiating work happens again. Treating focus areas as phases is a common misreading.
What Initiating is for
Initiating work defines and authorizes a project or a phase. In plain terms it produces four things:
- A reason: the business need and the outcomes the project or phase must deliver, tied back to the business case (lesson 7 covered outcomes versus outputs).
- Authority: a named sponsor who commits funds, and a named project manager with stated authority.
- Boundaries: high-level scope, key milestones, budget, constraints and assumptions, and what is out of scope.
- People: who is affected, who can influence the result, and what they expect.
Initiating is short compared with planning, but it sets the frame planning works inside. A phase that starts without a clear sponsor or success criteria will spend its planning effort arguing about what it is for.
The two processes most tied to Initiating
Published summaries of the 40 processes list an Initiate Project or Phase process in the governance domain and an Identify Stakeholders process in the stakeholders domain. These are the two that carry the initiating work described above. Initiate Project or Phase produces the authorizing document, traditionally called the project charter, which formally starts the project or phase and gives the project manager authority to use resources. Identify Stakeholders produces a list of the people and organizations involved or affected, with their interests and influence, usually called a stakeholder register. Both are revisited later: stakeholders are identified throughout the project, and a phase charter is reissued for each phase.
Notice the domains. The charter sits in governance, which the Eighth Edition made a domain of its own, and that placement says something: the charter is a governance instrument. It records who decided to proceed and on what terms, and it is the yardstick for later decisions about change.
Initiating on the owner's side
On a design-bid-build building project, the owner initiates the whole project long before design, with a business case and approval to spend. Then it initiates each phase. The construction phase is a big one: the contract is about to be signed, the owner's team grows, and new stakeholders arrive (the contractor, its trades, the municipality's inspectors, neighbours). The construction phase charter is the owner's internal document. It does not replace the contract; it states what the owner is trying to achieve with it and who on the owner's side can decide what.
Northgate worked example
Northgate Distribution Centre (fictional) is a $38.0 million construction budget for Northgate Logistics Inc. (fictional): a $34,950,000 CCDC 2-2020 Contract Price with Halvorsen Builders Ltd. (fictional) and a $3,050,000 owner contingency, with Ridgeline Architects Inc. (fictional) as prime consultant. Facts are from the Northgate fact sheet.
The initiating window
Tender closed on Tuesday December 8, 2026. The contract is executed at M0, Monday January 11, 2027, and the kickoff meeting is M1, Tuesday January 19, 2027. The owner's construction-phase initiating work fits into those six weeks. Figure 2 shows a plan; the intermediate dates are illustrative. The handoff content itself is covered in the construction-phase track (handoff and kickoff lessons).
View the data
| Date | Event | Status |
|---|---|---|
| Tue Dec 8, 2026 | Tender closed | Fact sheet |
| Fri Dec 18, 2026 | Award recommendation to sponsor | Illustrative |
| Mon Jan 11, 2027 | M0: contract executed | Fact sheet |
| Thu Jan 14, 2027 | Stakeholder register, first issue | Illustrative |
| Fri Jan 15, 2027 | Construction-phase charter signed | Illustrative |
| Tue Jan 19, 2027 | M1: kickoff meeting | Fact sheet |
The order matters. The sponsor signs the phase charter before kickoff so that the owner's project manager walks into M1 with authority already settled: what they can approve, which milestones the owner is holding Halvorsen to, and who the owner's decision-makers are. Signing the charter after M0 is fine: the contract fixes Halvorsen's obligations, and the charter fixes the owner's internal ones.
A one-page phase charter
Figure 3 shows the sections of Northgate's construction-phase charter. Everything on it comes from the fact sheet except the authority limits, which are illustrative and match the decision-rights matrix in lesson 9.
The first stakeholder register
The construction phase brings stakeholders the design phase barely touched. A first register for Northgate would include the Northgate sponsor and operations team; Ridgeline and its subconsultants; Halvorsen and its key trades; the City of Vaughan building department; the racking supplier under the owner's separate contract; the owner's insurer (which cares about the ESFR sprinkler system); utilities for permanent power at M7; and neighbours affected by truck traffic. For each, the register records their interest, their influence and the owner's contact. It will grow; the point of issuing it at initiation is to stop the obvious ones from being forgotten.
Owner's move
- Initiate each phase, not just the project. Issue a short phase charter at the start of design, procurement and construction.
- Sign before kickoff. Have the sponsor approve the construction-phase charter before M1 so authority is settled when the team meets.
- Make success measurable. Use milestone dates, budget figures and safety goals, not "deliver a quality building".
- Write down the assumptions. Separate contracts, calendars and permits belong in the charter, where they can be tested later.
- Start the register early. Issue the first stakeholder register in the initiating window and update it at each phase.
Common mistakes
- Treating focus areas as phases. Initiating is not "done" once the project is approved; each phase needs it.
- Letting the contract stand in for the charter. The contract binds the contractor; the charter binds the owner's own team.
- A charter without authority. Naming a project manager without stating what they can approve.
- Vague success criteria. If nobody can say whether the phase succeeded, nobody can steer it.
- A stakeholder list of only the contract parties. Municipalities, insurers, utilities and neighbours drive real risk.
Quick quiz
Which list names the five focus areas of the Eighth Edition?
- Governance, scope, schedule, finance, risk
- Initiating, Planning, Executing, Monitoring and Controlling, Closing
- Concept, design, tender, build, close
- Value, quality, leadership, sustainability, culture
How do focus areas differ from phases?
- They are identical
- Focus areas can repeat and overlap within each phase
- Focus areas happen once, in order
- Phases are optional, focus areas are not
Which performance domain holds the Initiate Project or Phase process in published summaries?
- Scope
- Finance
- Governance
- Risk
What does a phase charter give the owner's project manager?
- Control of the contractor's means and methods
- Formal authority to apply resources to the phase
- The right to certify payment
- A replacement for the contract
Why sign Northgate's construction-phase charter before M1?
- The contract requires it
- So authority is settled before the team meets
- To delay the kickoff
- So Halvorsen can sign it
Show answers and explanations
- B. Option A lists performance domains; option D lists principles.
- B. Focus areas describe the kind of work, which recurs; phases are stages in time.
- C. The charter is a governance instrument, and the process sits in the governance domain.
- B. The charter authorizes the phase and the project manager's use of resources; it cannot override CCDC 2 roles.
- B. The kickoff is where commitments are made; the owner's side should know its limits first.
Key terms
- Focus area
- One of five groupings of PMBOK Guide 8 processes by the kind of attention work needs: Initiating, Planning, Executing, Monitoring and Controlling, Closing.
- Initiating
- The focus area that defines and authorizes a project or phase.
- Project charter
- The document that formally authorizes a project or phase and the project manager's authority.
- Phase charter
- A charter issued for one phase, such as construction, within an approved project.
- Stakeholder register
- A list of people and organizations involved in or affected by the project, with their interests and influence.
- Sponsor
- The person who provides funding and authority for the project and is accountable for its business case.
References
- Project Management Institute, PMBOK® Guide, Eighth Edition (product page: seven performance domains, reintroduced non-prescriptive processes).
- PMExams, PMBOK 8: the full process map (third-party summary of the 40 processes by performance domain).
- PMExams, PMBOK 8 focus areas (focus areas recur and overlap; not phases).
- 4PMTI, What is the PMBOK 8th edition? Principles, domains, focus areas, and what changed.
- Mark Whitfield, PMBOK Guide 8th edition (May 2026; five focus areas, 40 processes with inputs, tools and techniques, and outputs).
Verified on November 6, 2026.
Next lesson in this trackFocus area: PlanningPMI, PMP and PMBOK are registered marks of the Project Management Institute, Inc. Oracle and Primavera are trademarks of Oracle. Microsoft Project is a trademark of Microsoft. BRC Academy is not affiliated with or endorsed by these organizations.