September 7, 2026 · 7 min read
TL;DR: The stakeholder register and its analysis tools appear in 33 answer options across the bank and are keyed 13 times. Every keyed instance has someone who is new, missing or not yet understood. Every distractor uses the register to do something it cannot do: postpone a conversation, substitute for a strategy, or answer a question that belongs to a different artefact.
The register is one of the first artefacts candidates learn and one of the most reflexive wrong answers on the exam. The reflex is not wrong about the artefact. It is wrong about timing, and the bank's explanations are unusually clear about which side of the line a scenario sits on.
When a person is missing from it, or when nobody has yet worked out who matters.
Someone new or overlooked. A vice president of operations joined last month and has reservations about a dashboard sixty per cent of the way through a build. The keyed answer meets them to understand the concerns and adds them to the register. Telling the operations group the layout was approved at initiation is described in the explanation as the reflex answer of a well-run project, and the wrong instrument, because the VP has asked for a say, not submitted a change. A newly appointed director proposes a scope item at a steering meeting, and the keyed answer updates the register with the new stakeholder's details before anything else, because an influential person the project has no entry for is not being analysed or engaged by anyone. A new CRM will auto-generate the reports payroll uses for commissions and feed the support team's warranty system. The keyed answer adds both teams to the register and the communications even though their involvement is indirect. The test is impact, not use.
A key voice left out. An environmental expert was not included in the preliminary discussions on an impact assessment, and the question asks which document needs revision. The register, because every downstream artefact is built from it: no engagement strategy is planned for a person nobody identified.
Nobody has analysed anyone yet. A new project manager on a multi-country security project is asked how to start gathering requirements. Keyed is a stakeholder analysis, because regional policy is what will differentiate one group's needs from another's. On a client's premises inside a matrix organisation, stakeholders' interests genuinely differ, and the keyed answer performs the analysis and acts on it rather than picking a group to obey. When direct persuasion of a blocking department head has already failed, the keyed answer uses stakeholder analysis to find a senior stakeholder aligned with the project who can influence them.
When the analysis has already been done, when updating the register postpones a conversation that is due, or when the gap belongs to a different artefact.
The analysis is already done. Conflicting requirements among stakeholders are causing technical and operational problems, and running a stakeholder analysis is offered. It loses to negotiating the conflicting requirements directly, because by the time the project manager acts the holders of the conflict are known and the analysis would re-derive what is known. The charter is approved, the analysis has revealed influential executives raising concerns about progress, and running an impact/influence analysis across all stakeholders is offered. It repeats work the stem says is finished. Keyed is building the plan and reviewing it with those executives regularly.
The register postpones a conversation. A residents' association has publicly said it expects to be consulted on a decision the project intends to make internally. Adding them to the register and assessing their influence before responding is offered and loses to meeting them to set out which decisions are open to them. The explanation says it plainly: that option analyses a stakeholder who has already announced themselves and postpones the conversation that is due. Department heads are skipping sessions and telling staff to keep using old spreadsheets, and building a power/interest grid to decide who to prioritise loses to meeting them, because the grid is a planning tool for deciding who to engage, not a response once resistance is visible and the individuals are identified. A stakeholder's doubt about a regulatory timeline has been confirmed as well founded, and noting the concern in the register loses to a change request against the schedule baseline.
Common trap: reaching for the register when the gap is in the engagement plan. The stakeholder engagement assessment matrix shows an influential stakeholder is resistant where the project needs them supportive. Making sure the register is up to date is offered and loses to developing a strategy for that stakeholder and recording it in the engagement plan. The explanation draws the line: updating the register documents the person without acting on the gap. The bank offers the register as a place to record something instead of acting on it six times across the slice, and every one of them is explained rather than just marked wrong.
The register records who matters and how much. Everything about strategy, channel, assignment or approach belongs to a document built from it.
| The question is about | The keyed artefact | The register loses because |
|---|---|---|
| Who has an interest, and how much influence | Stakeholder register | It wins here |
| How to move one stakeholder from resistant to supportive | Stakeholder engagement plan | It records people, not strategies |
| How a release announcement should be made | Communications management plan | It does not record how anyone agreed to be reached |
| Who does what inside the team, with what authority | Roles and responsibilities in the resource plan | It lists interested parties, not assignments |
| Which development approach the project uses | Project management plan | It says nothing about cadence |
| Whether the project is worth funding | Business case | It is built from that document, not the other way round |
Two rows deserve a note. A stakeholder complained they never received a fire-suppression test report, and the question asks which tool, kept current, would have ensured they got it as a matter of course. The keyed answer is the register, because it holds each stakeholder's communication requirements and the communications plan is built from it. The communication log is the closest miss and only a record. But when the deliverables are accepted and the remaining task is to announce the release in the manner stakeholders agreed, the keyed answer is the communications management plan, and the register loses because it lists who to reach without recording how. The register feeds the plan. It does not replace it.
The classification row also carries two definitional items: assessing stakeholders by power, urgency and legitimacy is the salience model, and the engagement assessment matrix is the one tool in the family that plans engagement rather than classifying anyone.
When is updating the stakeholder register the keyed answer? When someone who can affect or be affected by the project is not on it: a vice president who joined last month, a payroll team whose reports the new system will generate, a director who appears at a steering meeting proposing scope. Identification runs for the whole project, not once at initiation.
When is a stakeholder analysis the wrong answer? When the analysis has already been done. If the stem says the stakeholders are known, their positions are known and the conflict is visible, re-running the analysis re-derives what is known and defers the negotiation that is the actual work.
What is the difference between the stakeholder register and the stakeholder engagement plan? The register records who the stakeholders are, with their interest, influence and classification. The engagement plan records the strategy for moving each one from their current level of engagement to the level the project needs. A gap found by the engagement assessment matrix is answered in the plan, not the register.
Should a new project copy a similar past project's stakeholder register? No. The bank keys using the earlier project's lessons learned to guide this project's register, and rejects adopting the old register, because a year later the cast of stakeholders may well have changed.
PMP Practice's 2,141 questions are certified against PMBOK 8 and the July 2026 ECO, with every wrong answer explained rather than just marked wrong. Start the free 20-question sample — no card, no signup required to try it.
Related reading: The Stakeholder Engagement Assessment Matrix: Unaware to Leading and Stakeholder Resistance: 17 Scenarios, and the Answer Is Always to Go and Ask Them Why. Stakeholder tasks are mapped on the People domain study page.
When is updating the stakeholder register the keyed answer?
When someone who can affect or be affected by the project is not on it: a vice president who joined last month, a payroll team whose reports the new system will generate, a director who appears at a steering meeting proposing scope. Identification runs for the whole project, not once at initiation.
When is a stakeholder analysis the wrong answer?
When the analysis has already been done. If the stem says the stakeholders are known, their positions are known and the conflict is visible, re-running the analysis re-derives what is known and defers the negotiation that is the actual work.
What is the difference between the stakeholder register and the stakeholder engagement plan?
The register records who the stakeholders are, with their interest, influence and classification. The engagement plan records the strategy for moving each one from their current level of engagement to the level the project needs. A gap found by the engagement assessment matrix is answered in the plan, not the register.