Initiating

Stakeholder Register

The stakeholder register is used to identify those people and organizations impacted by the project and to document relevant information about each stakeholder. Relevant information can include:

  • Name
  • Position in the organization
  • Role in the project
  • Contact information
  • List of stakeholder’s major requirements
  • List of stakeholder’s expectations
  • Classification of each stakeholder

Initially you will not have enough information to complete the stakeholder register. As the project gets underway you will gain additional information and understanding about each stakeholder’s requirements, expectations, and classification and the stakeholder register will become more robust.

The stakeholder register receives information from:

  • Project charter
  • Procurement documents

It is related to:

  • Stakeholder analysis matrix It provides information to:
  • Requirements documentation
  • Quality management plan
  • Communications management plan
  • Risk management plan
  • Risk register
  • Stakeholder engagement plan

The stakeholder register is an output from the process 13.1 Identify Stakeholders in the PMBOK® Guide – Sixth Edition. The stakeholder register is a dynamic project document. The stakeholders, their level of influence, requirements, and classification are likely to change throughout the project.

Tailoring tips

Consider the following tips to help you tailor the stakeholder register to meet your needs:

  • Combine the position in the organization with the role on the project, especially if it is a smaller project and everyone knows everyone else’s position.
  • Combine the stakeholder analysis matrix information with the stakeholder register.
  • Eliminate position, role, and contact information for small internal projects.

Alignment

The stakeholder register should be aligned and consistent with the following documents:

  • Project charter
  • Stakeholder analysis matrix
  • Stakeholder engagement plan
Document element  Description
Name Stakeholder’s name. If you don’t have a name you can substitute a position or organization until you have more information
Position/Role The position and/or role the stakeholder holds in the organization. Examples of positions include programmer, human resources analyst, or quality assurance specialist. Roles indicate the function the stakeholder performs on the project team, such as testing lead, Scrum Master, or scheduler
Contact information How to communicate with the stakeholder, such as their phone number, email address, or physical address
Requirements High-level needs for the project and/or product Expectations
Expectations Main expectations of the project and/or product
Classification Some projects may categorize stakeholders as friend, foe, or neutral; others may classify them as high, medium, or low impact