A stakeholder register for a zoning-software rollout lists each council liaison with influence level and engagement approach. What is the register documenting?
Select an answer to reveal the explanation.
Short Explanation
A stakeholder register is the cast list plus the game plan for each character—who they are, how much clout they have, and how you will keep them informed or involved. Council liaisons get lines in that cast list.
Full Explanation
A stakeholder register documents who the stakeholders are, characteristics such as interest or influence, and how the team plans to engage them. Listing each council liaison with influence level and engagement approach on a zoning-software rollout matches that purpose and supports tailored communication. Saying it documents only software defect severity codes fails by concept: defect codes belong in quality or issue tracking tools, not in stakeholder identification. Saying it documents critical path activities owned by each liaison fails because the project schedule—not the stakeholder register—owns critical path activities and durations. Saying it documents the product backlog order for every zoning permit workflow fails because backlog prioritization is a product or scope artifact, not the stakeholder register. Exam caveat: CAPM stakeholder questions test that engagement strategy is tailored using register data—influence and interest—not a single undifferentiated blast to everyone on the email list. Operational check: maintain liaison influence and interest fields, define engagement approaches such as briefings, workshops, and reports, and update the register when roles or attitudes change during the rollout.