Stakeholder Register

Phase: Pre-sales and initiation | Audience: Internal | Project: WEB-2026-01 Corporate Website Development

Understand it first

In simple words: The Stakeholder Register lists everyone who can affect or is affected by the project, what they care about, how much influence they have and how we will keep them engaged.

Think of it like: Planning a wedding, you note who must approve the menu (parents), who only needs an invitation (distant relatives), and who can cancel everything (whoever is paying).

When is it created?	Initiation, updated at every phase (6 Oct 2026)
Who prepares it?	Project Manager
Who approves or uses it?	Internal use; reviewed with the sponsor
What happens next?	Feeds the Communication Plan and RACI

How it connects to other documents

Engagement strategies decide meetings in the Communication Plan.
Decision-makers become 'Accountable' in the RACI Matrix.
Missing a stakeholder caused a real problem later (the MD's design change, see the Issue Log).

The sample document

Below is the actual document for project WEB-2026-01. Read the purpose first, then go through each numbered section.

Issued by: [Your Company] Technologies Pvt. Ltd.

Purpose: Everyone who affects or is affected by the project, what they care about and how we will engage them.

Item	Detail
Document no.	WEB-2026-01/SR
Version	1.0
Date	6 Oct 2026
Owner	Project Manager
Audience	Internal
Phase	Pre-sales and initiation

1. Register

ID	Stakeholder	Organisation	Role in project	Interest	Influence	Engagement strategy
S1	Head of Marketing	Client	Project sponsor; approves designs, UAT and payments	High	High	Manage closely: weekly call, milestone reviews
S2	Managing Director	Client	Final say on brand and look	Medium	High	Keep satisfied: show designs before sign-off
S3	Marketing Executive	Client	Day-to-day contact; supplies content; future site editor	High	Medium	Keep informed: daily email, training
S4	IT Administrator	Client	Domain, DNS and email settings	Low	Medium	Keep satisfied: give early notice of access needs
S5	Finance Team	Client	Processes invoices	Low	Medium	Monitor: send invoices with sign-off proof
S6	Delivery Head	Our company	Internal sponsor; approves budget changes	High	High	Manage closely: fortnightly budget review
S7	Project Manager	Our company	Plans, coordinates, reports	High	High	Owner of this register
S8	UI/UX Designer	Our company	Design deliverables	High	Medium	Daily stand-up
S9	Developers (frontend, backend)	Our company	Build and deploy	High	Medium	Daily stand-up
S10	QA Tester and Content Writer	Our company	Testing and copy	Medium	Low	Daily stand-up
S11	Hosting provider	Vendor	Server and uptime	Low	Low	Monitor: support ticket when needed
S12	Website visitors	Public	End users of the site	Medium	Low	Represented through usability and UAT checks

2. Power-interest grid

Quadrant	Stakeholders	Approach
High influence, high interest	Head of Marketing, Delivery Head, Project Manager	Manage closely
High influence, lower interest	Managing Director, IT Administrator	Keep satisfied
Lower influence, high interest	Marketing Executive, project team	Keep informed
Lower influence, lower interest	Finance, hosting provider, visitors	Monitor

Note: The Managing Director has high influence but is not in weekly calls. Show the homepage design to the MD before the design sign-off so a late objection does not cause a third revision round.

WEB-2026-01/SR · v1.0 · Internal. Bracketed items such as [Client Name] are placeholders.