Stakeholder engagement resources

Welcome to the Stakeholder engagement resources page.

This is a rich source of helpful case studies, patterns, tools, books, papers, presentations, videos, webinars, podcasts and social media – all related to Stakeholder Engagement. 

NewSE Bites – August 2020

“NewSE Bites” is a regular update for project managers seeking information about stakeholder engagement. Inclusion of a link should not be taken to mean endorsement of a site or publication.

For archived Useful Links updates see below.

August 2020


Can you contribute?

There are lots of different ways to approach stakeholder engagement.

The purpose of these resources is to share potential solutions and other people’s experience rather than to provide the definitive answer.

If you have experience that could be of benefit to other project managers, then we would like to hear from you! 

Contact us

List of resources

Patterns & tools


Patterns document commonly observed, project-related behaviours that impede project delivery, including analysis, learning and solutions.


Tools include techniques, models, methods and applications for improving stakeholder engagement that have been applied, adapted and found helpful in practice.

For more information on the group or stakeholder engagement, click here.


The bibliography contains the details of suggested academic papers and business literature, relevant to Stakeholder Engagement.

Click here

NewSE Bites archive

Useful Links Update is a regular update produced by the Stakeholder Engagement Focus Group. The aim is to share links to tools, developments and forthcoming events that may be of interest or help to address your stakeholder engagement questions.

July 2020 June 2020 May 2020 April 2020 March 2020 February 2020 January 2020


November 2019 October 2019 September 2019 August 2019 July 2019

June 2019 May 2019 March 2019 January 2019


November 2018 October 2018 September 2018 August 2018 July 2018 May 2018

April 2018 March 2018 February 2018 January 2018

December 2017 November 2017 October 2017 September 2017 August 2017 July 2017

June 2017 May 2017 April 2017 March 2017 February 2017 January 2017



Why is stakeholder engagement important to project management? This white-paper by SEFG team member Benedict Pinches makes the case for making stakeholder engagement a higher priority.

Download now


1. How does a project manager identify the stakeholders?

   a. The ‘front line’ stakeholders will be readily identifiable from the outset.
   b. The real issue is identifying those stakeholders who are in the background but may have significant influence.  To aid in the identification of these ask the known stakeholders if they are aware/know of others who may have a vested interest in the project,        and then ask them the same question.

2. Having identified the stakeholders how can a project manager identify those stakeholders who hold the actual power?

   a. This really is an ‘ear to the ground’ requirement.  Ask around (discretely) amongst people connected with the project and see who has ‘the ear’ of the decision maker(s).
   b. The person(s) with the ‘power to influence’ are not necessarily those at the top.  Look for ‘advisors’ to those at the top.
   c. Ask senior stakeholders if there is anyone they would like you to discuss issues with prior to a meeting with them.

3. What initial method of communication (engagement) should take place?

   a. Ideally a face-to-face meeting should be held.
   b. Make sure you meet with all of the key stakeholders.
   c. Distributing a ‘point brief’ during the meetings helps keep the discussion on track and provides a written account of what was discussed.

4. Where is the best location for initial meetings? (Their location, project manager’s location, neutral location.)

   a. It is preferable to meet in a place where the stakeholder feels at ease/comfortable – often their own offices.

5. How often should the project manager communicate with the stakeholders?

   a. The easy answer is 'as often as is necessary'.
   b. Don’t wait until there is an ‘issue’ – regular communication generates trust and displays commitment.
   c. Agree a periodicity of communication, and content, with each of the key stakeholders and then stick to it.

6. What method of communication is best?

   a. Where possible the best method is face-to-face coupled with a brief outline of where the project is, including any potential issues on the horizon.

7. Should all stakeholders have full access to all project documentation?

   a. Not always. There may be commercial/financial/technical aspects that are considered restricted and can only be shown to nominated personnel.
   b. Agree early on who can see what.

8. How should the project manager deal with stakeholders that are in disagreement with each other over aspects of the project? Example: Internal stakeholder insists on a particular direction/process whilst the external stakeholder disagrees and insists on a different direction/process.

   a. This is a potential minefield.  Unless you can get the disagreeing parties to sit together then you will need to be the ‘go-between’ trying to find the path most suitable to the success of the project.
   b. Resist the urge to play one stakeholder off against the other.
   c. Try and establish the ‘why’ associated with the direction the various stakeholders want to follow.

9. How can the project manager change the attitude of a stakeholder who is a ‘blocker’ into one that at the very least is ‘neutral’?

   a. Regular meetings – face-to-face is always best.
   b. On a one-to-one basis try and establish what concerns this particular stakeholder has regarding the project.
   c. See if you can engage the assistance from other stakeholders (same level of influence) to discuss with the ‘blocker’.

10.  What methods are most appropriate in dealing with constant change requests (insistence) from stakeholders?

   a. Ensure that the scope documentation is definitive and clear on what is to be delivered against what timescale.
   b. Have a comprehensive document that clearly states the ‘dependencies/assumptions/exclusions’ of the project.  This needs to have been signed off by the project sponsor and senior member of the client base.
   c. Use a ‘change request’ log.  Have the stakeholder initial their request(s).

11. How honest should the project manager be with regards to reporting issues within the project (slippage, budget etc.) to external stakeholders (client/customer)?

Be honest; explain that something has come up (outline what this is) that has resulted in a ‘change’ (slippage to the baseline, increase in costs etc.) and what the impact will be.  Make sure you have a ‘recovery plan’ to discuss with the stakeholder(s).

Join APM

Sign up to the APM Newsletter.