Stakeholder Register vs. Custom Fields

[Brigid33770]

Hi everyone!

We implemented Demand before the other SPM modules and made several customizations.

Four custom fields were added to the Demand Details to identify the IT Sponsor, IT Executive Sponsor, Executive Sponsor, and Business Sponsor. We've used this for some reporting. 

The Stakeholder Register has the same "users", so we are duplicating documentation, which is not optimal. 

I'd like to understand best practice for using the Stakeholder Register for the roles as described above. How is the Stakeholder Register used in reporting, i.e. Projects by <NAME> or <FUNCTION>

[Dhiren Aghera · Accepted solution]

Hi @Brigid33770  Stakeholder register is used primarily to understand the level of influence that person has on the particular portfolio to make certain decision for Demand prioritization. Fields like Assessment recipient and Approver when set to Yes can help trigger assessment records and approvals for the said stakeholder. In your case as you have already created fields as they are also key stakeholders, would recommend you to use OOTB stakeholder table and add custom fields to identify the nature of stakeholders. This is based on my experience working on stakeholder register

[Dhiren Aghera · Accepted solution]

Hi @Brigid33770  Stakeholder register is used primarily to understand the level of influence that person has on the particular portfolio to make certain decision for Demand prioritization. Fields like Assessment recipient and Approver when set to Yes can help trigger assessment records and approvals for the said stakeholder. In your case as you have already created fields as they are also key stakeholders, would recommend you to use OOTB stakeholder table and add custom fields to identify the nature of stakeholders. This is based on my experience working on stakeholder register

[Brigid33770 · Accepted solution]

Thank you kindly. I will share with my team. Appreciate your feedback!

Brigid