PMBOK Step by Step, Part 2: Who Is Involved? Building the Stakeholder Register

Every project has a guest list, and every project manager has been surprised by someone who was not on it. The neighbor who writes a polite letter to the city about parking. The cousin of the landlord who "has a few thoughts" about the signage. The person in accounts payable who, three weeks before opening, turns out to be the only human being who can approve a new vendor. None of them appeared in the plan. All of them had power.

This is Part 2 of the series PMBOK step by step, in which I follow one project from idea to closeout. In Part 1 the owners of the Riverside Family Clinic compared four options, chose a phased build-out and signed a charter with a budget of $280,000 and an opening nine months after approval. Today the question changes from "should we?" to "who is involved?" We will build the stakeholder register: the list of everyone who matters, what each wants and what we are going to do about it. In the middle there is a builder that writes one register entry for any person on your own project.

A reminder before we start: the clinic is invented. Riverside Family Clinic is a composite, not a real client, and every number is illustrative. Nothing here is legal, financial or medical advice.

What a stakeholder is, and why a list is not enough

A stakeholder is any person, group or organization that can affect the project, be affected by it or simply believes they will be. The definition is wide on purpose. People who never touch the work but can change its fate, such as a regulator, a lender or a loud neighbor, count as much as the team.

The PMBOK Guide organizes this work as a set of activities: identify the stakeholders, plan how to engage them, manage that engagement during the work and monitor it as things change. Newer editions of the Guide describe the same idea as a performance domain, a thread that runs through the whole project, not a box you tick at the start. For a small project, I turn all of it into one table that I open every week. That table is the register.

Why not a simple list of names? Because a list does not tell you what to do. Knowing that the building inspector is a stakeholder is trivia. Knowing that the inspector has high power, is neutral today, needs to be supportive by month seven, worries about incomplete drawings and should hear from the project manager every two weeks starting in month three is a plan.

If you have read my guide on stakeholder mapping with power and interest, the sorting in this article will feel familiar. Think of that guide as the quick sketch and this one as the full drawing: the map shows where people sit, and the register records what you will do about it.

Step 1: find everyone

Start with a brainstorm, alone first and then with the sponsor and the team, because every person remembers different people. Six questions help.

1. Who pays? Owners, lenders, investors, grant makers.
2. Who decides? The people who can say yes or no, formally or informally.
3. Who approves? Permit offices, inspectors, licensing bodies, insurers, the landlord.
4. Who does the work? The team, contractors, vendors, consultants.
5. Who is affected? Future staff, patients, neighbors, nearby businesses, other tenants.
6. Who could stop it? Anyone with a veto, an appeal or a megaphone.

Then ask a seventh question of every person you meet: who else should I be talking to? This single question often finds people the plan missed, because people know who really makes things happen in their world.

For Riverside, the first pass produced fourteen names. Here is a trimmed version, with illustrative notes.

• The physician (sponsor). Owns the money and the result. Wants a clinic that opens on time without ruining their family life. Worries about debt.
• The practice manager. Will run the clinic. Wants systems that work on day one. Worries about being left holding the problems.
• The medical director. Supervises clinical quality. Wants safe workflows and the right equipment. Worries about being asked to sign off late.
• The landlord. Wants a good tenant and a reliable rent. Worries about disruption to the building and other tenants.
• The lender. Wants a plan and regular proof that it is on track. Worries about overruns.
• The city permit office. Wants complete drawings and code compliance. Worries about being blamed for a mistake.
• The state licensing and health authorities. Want the facility to meet the standards that apply. Rules and timing vary, so the team must check them directly.
• The general contractor. Wants clear drawings, payment on time and few changes. Worries about schedule pressure.
• The equipment and technology vendors. Want a firm order and a date. Worry about changing requirements.
• Insurers and billing partners. Their processes decide how soon the clinic gets paid.
• Future staff. Want a good workplace and clear expectations.
• Patients. Want care close to home, and little tolerance for a rocky opening.
• The neighbors and nearby businesses. Want to keep their parking, their quiet and their street.
• The utility companies. Want a correct application and enough lead time.

Look at how many of these never appear in a typical project schedule. Utilities and insurers rarely do, and neighbors almost never. They are the quiet ones, and quiet stakeholders have a habit of making noise at the worst moment.

Step 2: sort by power and interest

Not everyone needs the same attention, and nobody has time to give everyone equal attention. Rate each person from one to five on two questions.

• Power: how much can this person help or hurt the project?
• Interest: how much do they care about the outcome, today?

Four combinations result, and each suggests a style.

• High power, high interest: manage closely. The physician, the landlord, the lender, the permit office. Frequent, direct, two-way contact.
• High power, low interest: keep satisfied. A utility company or an insurer may not care about your project until you need something from them. Make it easy for them to say yes, and do not surprise them.
• Low power, high interest: keep informed. Future staff and neighbors. Regular, honest updates. They can become supporters or critics, and they talk to others.
• Low power, low interest: monitor. Watch for changes. A person in this corner can move, so look again each month.

The ratings are judgments, not measurements, which is why the register records them with a date. Review them as the project moves. The neighbors start in the lower right and move upward the first time the construction fence goes up.

Step 3: where do they stand, and where do you need them?

Power and interest tell you how much attention someone deserves. Attitude tells you what kind. A simple scale from the PMBOK tradition has five levels: unaware (does not know about the project), resistant (knows and opposes), neutral (knows and does not mind), supportive (wants it to succeed) and leading (actively helps it succeed).

For each stakeholder, record where they are today and where you need them to be. Most do not need to be leading. A utility company that is neutral and responsive is fine. But some must be supportive, and a few must lead, and any gap between today and needed is your work list.

In the clinic, an honest assessment looks something like this: the landlord is supportive and needs to stay there. The permit office is neutral, and the project needs them supportive, which in practice means reviewers who recognize the team and trust its drawings. The nearest neighbors are unaware, and the team needs them neutral at least. The lender is neutral and should be supportive, because lenders who feel informed tend to be flexible when something slips.

Here is a useful trick. When you write a gap, such as "neighbors: unaware, need neutral," immediately write the action that closes it: "knock on the doors of the five nearest businesses in month two, tell them the plan and leave a phone number." A gap without an action is a worry.

Step 4: talk to them

The register is built on your assumptions until you check them. The fastest way to check is a conversation. Fifteen minutes with each important stakeholder, using the same five questions:

1. What would make this project a success for you?
2. What worries you about it?
3. What do you need from me, and by when?
4. How and how often would you like to hear from me?
5. Who else should I talk to?

Then listen more than you talk. Write down what they say in their words. You will find that the person you labeled "resistant" is simply worried about one thing, and that the person you thought was supportive has a condition you had not heard. Engagement starts the moment you ask, and many problems shrink when people feel consulted.

Step 5: write the plan for each person

Now the register becomes a plan. For each stakeholder, add the columns that make it actionable.

• What they want and what worries them. In their words where possible.
• Power, interest and the style it suggests.
• Attitude today, attitude needed and the gap.
• How you will engage. A meeting, a short email update, a site walk, a decision request.
• How often. Weekly, every two weeks, monthly, at milestones.
• Owner. One person on the team who is responsible for the relationship. For the sponsor, that is the project manager. For the permit office, maybe the designer. A relationship with no owner is a coincidence.
• Next contact date. The most underrated column in the register. It makes the table a calendar.

You can assign the owners with a RACI chart and connect the "how often" column to your communication plan, the document that says who gets which message, in which channel and when. The toolkit has a ready-made stakeholder map and a communication plan sheet.

The register builder

Use the builder below to write one entry for a person on your own project. The sample is the clinic's city permit officer. Change the fields to a real stakeholder, rate power and interest from one to five, and read the entry that appears. The tool names the style that fits the ratings and warns you about gaps without a plan or entries without an owner. Copy the result into your register.

Interactive tool

The stakeholder register builder

Loading the tool…

Facts, not labels, and a confidential document

A stakeholder register contains opinions about people, which makes it sensitive. Two rules keep it useful and safe.

Write facts, not labels. "Difficult" tells you nothing and invites an argument. "Rejected the first two drawings for missing fire-rated details and asked for a pre-submission meeting" tells you what happened and what to do. A good test: could you show this line to the person without embarrassment? If it leaked, nobody should have to apologize.

Keep it confidential. The register belongs to the project team and the sponsor. Store it where not everyone can open it. Share extracts, such as engagement schedules, but not the candid assessment columns.

A surprise that earns its place

Midway through the exercise, the practice manager asks a question that changes the register. "What about the dental office across the street? Our patients will take their parking spaces." Nobody had thought of it. A call is made. It turns out the dental office manager is delighted by the idea of a primary-care neighbor, who will send patients for referrals, and wants to talk about sharing a few spaces on weekends. A potential complaint becomes a partner.

This is an invented example, of course, and I include it to show what the register is for. It is not paperwork. It is a way to find the conversation you would never have scheduled. A stakeholder found early can still become a helper. One found late has usually already formed an opinion, so the earlier you find them, the better the odds.

The register as a living document

A register that is written once and filed is a snapshot of the start. People change roles, attitudes shift, new stakeholders appear and the project passes through phases that make different people matter. Build a rhythm.

• Weekly: look at the next contact dates and make the calls.
• Monthly: re-rate power, interest and attitude for the top ten and add anyone new.
• At each milestone or gate: ask whether the people who matter for the next phase are on the list. In the clinic, the contractor becomes critical at construction, and patients at launch.
• At closeout: record what worked, so the next project starts with a smarter list. The method is in my guide on lessons learned.

Common mistakes

• Only listing the obvious. The team, the sponsor and the client are the easy ones. Look for the quiet ones.
• Treating it as a one-time exercise. The register is a habit, not a deliverable.
• Rating without talking. Assumptions about attitude are right less often than people think.
• Labels instead of facts. They offend, mislead and do not suggest action.
• No owner for each relationship. If everyone is responsible, nobody calls.
• Ignoring the people who like the project. Supporters need information and thanks too, or they drift.
• Putting the register in a place everybody can read. It is a working document, not a notice board.
• Forgetting the sponsor. The most important relationship is the one most likely to be neglected. See keeping your executive sponsor engaged.

How this fits the PMBOK map

In the process view of the PMBOK Guide, identifying stakeholders belongs to the initiating stage, and planning, managing and monitoring their engagement belong to the later stages. In the newer principles-and-domains view, stakeholders are a performance domain that runs through the entire project. The tools in this article, the register, the power and interest sorting, the engagement assessment and the communication plan, serve both views. The Guide is a map, not a rulebook, and a small project needs only the parts that change decisions.

What to do this week

Pick a real project. Spend thirty minutes listing everyone with the six questions. Pick the ten who matter most and rate power, interest and attitude. Have a fifteen-minute conversation with three of them, using the five questions. Write one register entry per person with the builder above, including an owner and a next contact date. Put those dates in your calendar. The whole exercise takes an afternoon and will probably find at least one person you had forgotten.

Next Wednesday, in Part 3, we turn to the question the whole clinic team has been circling: what exactly are we building? We will define the scope, write what is out of it and break the work into pieces small enough to estimate. If you want every part at your pace, the publishing calendar shows the dates, and the monthly newsletter lists each month's new parts. If you would like help identifying the people who can make or break your project, that is part of what I do with Project Focus, and you can tell me about it on the contact page.

Who was the stakeholder you forgot on your last project, and when did you find out? Tell me in the comments.

More tools. The stakeholder map, the communication plan and the decision log are free in the toolkit.

PMBOK and PMP are registered marks of the Project Management Institute, Inc. This series is independent and is not affiliated with, or endorsed by, PMI. The Riverside Family Clinic is an invented example, and all figures and names are illustrative.

Frequently asked questions

What is a stakeholder register?

It is a living table of everyone who can affect a project or be affected by it. For each person or group it records what they want, what worries them, how much power and interest they have, their attitude today and the attitude you need, how you will engage them, who owns the relationship and when the next contact is.

What is the difference between a stakeholder map and a stakeholder register?

A map places people on a power and interest grid to show how much attention each deserves. A register goes further and records what you will do about each person: the engagement approach, the owner and the next date. The map is a sketch, the register is the plan.

How do I find stakeholders I might be missing?

Ask six questions: who pays, who decides, who approves, who does the work, who is affected and who could stop the project. Then ask every person you talk to who else you should speak with. Neighbors, regulators, utilities and finance or purchasing staff are the most commonly forgotten groups.

Should I share the stakeholder register with the team?

Share the engagement schedule and the owners, but keep the candid assessments confidential among the project manager, the sponsor and the core team. Write facts about behavior instead of labels about people, so that nothing in the register would embarrass you if it were read aloud.

Join the conversation

Did this help? A quick reaction tells me what to write next.

Useful Made me smile Go deeper on this

Be the first to react.

Comments

Loading comments…

Leave a comment

NameEmail (required, never shown)

Who was the stakeholder you forgot on your last project, and when did you find out? Post comment

Your name and email create a small profile that shows you are a real person. The email is never shown. The first time, I send you a confirmation link, and every comment is reviewed before it appears. Please keep it respectful and leave links out.