Stakeholder register and map

List every role the work touches, what the law or guidance gives or asks of each, and how much each can shape the outcome.

In the first week, with the brief. Revisit it at each baseline. Feeds: the RACI, the risk register and the choice of reviewers.

• List roles, never people.
• For each role, write what it needs from the process and what it can do to the process.
• Cite the rule that puts the role here, or tag the role MINE and name the decision that created it.
• Place each role on the influence and interest grid, and write why it sits there.
• Say how you will involve each role.

1. Who is affected but has no say? Answered in STK-01 and STK-02: high interest, low influence.
2. Who can overturn a decision? Answered in STK-04 on a complaint (BR-53) and STK-09 on review (BR-51, BR-52).
3. Which roles are your own assumptions? Answered in The rows tagged MINE: STK-06 to STK-15, except STK-09; DEC-06.
4. Where is each placement on the map explained? Answered in Column "Why here"; the sheet "Map" lists the same placements by quadrant.
5. Who can break a deadline without knowing it? Answered in STK-05, because a request is received when it reaches anyone (BR-22).

• Names instead of roles. You can spot it when the register needs editing every time someone changes job.
• One row called "IT": nobody can say which role owns the mailboxes and which owns the system.
• A grid placement with no reason: two reviewers would place the same role differently, and nothing settles it.
• Forgetting the external body that can overrule you: every role in the register sits inside the organisation.
• Treating a group of people as one role without listing the variants the rules treat differently. A rule then applies to some members of a role, and the register cannot say which.

• Roles, never job titles or names. The sources name duties, not posts, so the internal roles other than STK-05 and STK-09 are the author's design (DEC-06). Rejected: job titles borrowed from a real council, which would point at a real organisation.
• STK-01 is one row with its variants listed in the Role column. Each variant is still "any person" under section 1(1), and what differs is handled by rules (BR-10, BR-14, BR-15, BR-35), not by a separate role. Rejected: four applicant rows repeating the same needs and rights.
• STK-05 sits high on influence although it has no say in the design. A request is received when it reaches anyone (BR-22), so any member of staff can start the clock without knowing it. Rejected: placing it low, which would drop it from the briefing plan.
• STK-04 is outside, with high influence and low interest. It can decide a complaint about any request (BR-53), but it has no part in how the council designs its process. Rejected: leaving the regulator off the register because it never attends a meeting.