The Stakeholder Register: Recording Interest, Influence, and Engagement Needs

The stakeholder register is the project artifact that records who the project’s stakeholders are and what the project knows about each of them — typically name, role, level of interest, level of influence, and communication or engagement needs. It is created during initiation, immediately downstream of stakeholder identification, and it stays a living document for the life of the project. When an exam scenario describes a project manager writing down a list of interested and affected parties with their attributes, the artifact being described is the stakeholder register.

What goes in the register

There is no single mandated column set, but a useful register captures four kinds of information for each entry:

• Identity: name, title, organization, and whether the stakeholder is internal or external. For groups (customers, a farming community, store managers as a class), the entry names the group and a representative contact where one exists.
• Relationship to the project: their role — sponsor, approver, end user, regulator, vendor, affected third party — and why they are a stakeholder: what they can affect, or how the project affects them.
• Assessment: level of interest (how much they care about the outcome) and level of influence (how much power they have over the project), usually rated on a simple scale such as high/medium/low. Some registers add attitude — supporter, neutral, resistor.
• Engagement needs: preferred communication channel and frequency, key concerns, and any expectations that need managing. This is the raw input the communication management plan is built from.

The assessment columns are what make the register more than a contact list. Two stakeholders can hold identical job titles and need completely different handling because one has high influence and low interest (keep satisfied, don’t spam) while the other has high interest and low influence (keep informed, harvest feedback).

Interest vs. influence — and what the pairing tells you

The classic way to act on the ratings is a power/interest grid. Each quadrant implies a default engagement strategy:

• High influence, high interest — manage closely. Sponsors and key approvers live here. Frequent, direct, two-way communication.
• High influence, low interest — keep satisfied. An executive who can kill the project but doesn’t follow it week to week. Concise, occasional, high-signal updates.
• Low influence, high interest — keep informed. End users and support teams often land here — they are also the natural pool of user acceptance testing participants later. Regular updates, feedback channels, early previews.
• Low influence, low interest — monitor. Minimal effort, but keep them on the register: quadrants change as the project evolves.

The grid is derived from the register; it isn’t a separate data source. If the register’s interest and influence columns are honest, engagement planning is almost mechanical.

Stakeholder register vs. RACI matrix

Both artifacts appear in initiation and both involve names in rows, which is exactly why the exam likes to contrast them.

Dimension	Stakeholder register	RACI matrix
Question it answers	Who cares about or can affect the project, and how do we engage them?	Who does what on each task or deliverable?
Scope of people	All interested/affected parties, including external ones with no assigned work	People with assigned responsibility for work items
Key attributes	Interest, influence, engagement needs	Responsible, Accountable, Consulted, Informed per task
Drives	Communication and engagement planning	Role clarity and accountability on execution
Typical entries	Regulators, customers, community groups, sponsors, users	Team members, leads, approvers mapped to tasks

A fire marshal or a donor base belongs in the stakeholder register but would look absurd in a RACI (Responsible, Accountable, Consulted, Informed) matrix — they have no task assignments. Conversely, a developer appears in the RACI for specific work items and may warrant only a lightweight register entry.

Keeping it alive

A register written once at kickoff and never touched again quietly rots — like the risk register, it only earns its keep if it stays current. Practical maintenance habits:

• Update on scope change. New integrations, vendors, or regulatory touchpoints add stakeholders; descoped work removes them.
• Re-rate at phase gates. Interest spikes near delivery; influence shifts with reorganizations. A “monitor” stakeholder in planning may need “manage closely” treatment at go-live.
• Record engagement history. Noting concerns raised and commitments made turns the register into institutional memory when team members rotate.
• Mind the sensitivity. Ratings like “low influence” or “resistor” are candid assessments of real people. Store the register where the team can use it but where it won’t leak into a status deck sent to the stakeholders it describes.

The register’s upstream process — deciding who belongs on the list in the first place — has its own rules and edge cases, covered in stakeholder identification. The short version: anyone who can affect the project or be affected by it earns an entry, including external parties and approval-only departments.

How the PK0-005 exam tests this

• “Name the artifact” scenarios: a project manager lists parties with an interest in or influence over a project — donors, agencies, store managers, customers — and you must identify the resulting document as the stakeholder register, not a RACI, org chart, or communication plan.
• Attribute-recognition scenarios: a document containing each stakeholder’s name, role, interest level, and influence level is described, and the answer hinges on knowing those are the register’s signature columns.
• “Name the process” scenarios: the act of building the list is described and the credited answer is stakeholder identification/analysis, with the register as its output — the exam checks you can tell the process from the artifact.
• Register vs. RACI discrimination: a scenario about engagement or communication needs points to the register; a scenario about who is accountable for a task points to RACI.

Artifact-recognition questions like these run throughout the Project Life Cycle Phases domain — see the full PK0-005 study guide for the complete artifact and domain map. Telling the register from a RACI under time pressure is exactly what PK0-005 practice questions are for.

Quick reference

• The stakeholder register lists each stakeholder’s name, role, interest, influence, and engagement needs.
• It is produced during initiation as the direct output of stakeholder identification.
• Interest = how much they care; influence = how much power they hold. The pairing sets the engagement strategy.
• Power/interest quadrants: manage closely, keep satisfied, keep informed, monitor.
• Register ≠ RACI: the register covers all interested parties and drives engagement; RACI assigns task-level responsibility.
• It is a living document — update on scope changes and re-rate at phase gates.
• Treat candid ratings as sensitive; the register is a working tool, not a publishable report.