Stakeholder Identification and Engagement

Introduction

Projects are undertaken to create change, but change is never experienced uniformly. A new information system may improve organizational control while disrupting established work practices. A transport project may improve regional connectivity while displacing households. A public-health programme may produce collective benefits while raising concerns about privacy or unequal access. In each case, project success depends not only on technical delivery but also on how affected and influential parties understand, support, resist, shape, and experience the project.

Stakeholder identification and engagement is therefore a core activity of project initiation and chartering. It converts a broad environment of interests into a structured understanding of people, groups, institutions, and communities that may affect or be affected by the project. The purpose is not simply to produce a contact list. It is to establish a defensible basis for governance, decision-making, communication, negotiation, risk management, benefit realization, and ethical conduct.

A stakeholder-centred approach also corrects a narrow conception of the project sponsor as the only important external party. Sponsors authorize and resource projects, but customers define value, users determine usability and adoption, regulators protect public interests, suppliers control capabilities, and affected communities may possess rights that cannot be reduced to their level of influence. Effective project leaders distinguish power from legitimacy, influence from formal authority, and consultation from genuine participation.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Define stakeholders and distinguish sponsors, customers, users, regulators, suppliers, partners, and affected communities.
2. Identify stakeholders systematically during project initiation and update the analysis as the project evolves.
3. Analyse stakeholder power, interest, influence, legitimacy, urgency, proximity, and attitude.
4. Develop stakeholder registers, maps, salience assessments, and engagement strategies.
5. Design inclusive communication, participation, negotiation, and conflict-management approaches.
6. Evaluate ethical, legal, cultural, accessibility, and governance implications of engagement decisions.
7. Apply stakeholder analysis to a complex project situation and defend strategic choices.

1. The Stakeholder Concept and the Project Environment

A stakeholder is an individual, group, organization, institution, or community that can affect, be affected by, or perceive itself to be affected by a project, its decisions, activities, outputs, outcomes, or closure. This broad definition deliberately includes parties with no formal contract and parties whose influence may be indirect.

Stakeholders may be internal or external, primary or secondary, supportive or opposed, visible or difficult to identify. A stakeholder may also occupy several roles. A government ministry may be both a regulator and a project sponsor. Employees may be users of a new system, affected by changes to their jobs, and representatives of a professional association. A local community may be a beneficiary, a rights-holder, and an objector to construction impacts.

Stakeholder analysis is different from stakeholder engagement. Analysis is the process of understanding stakeholders, their interests, capabilities, expectations, relationships, and likely responses. Engagement is the deliberate process of communicating and working with them to influence perceptions, decisions, behaviour, and outcomes. Analysis without engagement becomes a static document; engagement without analysis becomes uncoordinated activity.

1.1 Principal stakeholder categories

The categories are analytical rather than mutually exclusive. The project manager should record the specific relationship of each stakeholder to the project rather than assuming that category alone predicts behaviour.

1.2 Stakeholders, shareholders, and rights-holders

A shareholder owns an equity interest in an organization; a stakeholder has a broader interest in the project. A rights-holder is a party possessing recognized legal, customary, human, cultural, or procedural rights. Rights-holders require particular care because low power in a conventional organizational sense does not remove obligations toward them. For example, an indigenous community may have legally protected consultation or consent rights even if it has limited financial influence.

This distinction is central to ethical project initiation. A strategy that prioritizes only stakeholders with high managerial power can silence vulnerable groups and create legal, reputational, and social risks. Stakeholder prioritization must therefore consider legitimacy and rights, not only convenience or influence.

2. Stakeholder Identification During Initiation

Identification should begin before the charter is finalized. The project concept, business case, preliminary scope, assumptions, constraints, benefits, and delivery environment all provide clues about relevant stakeholders. The initial list should be treated as a hypothesis, not a complete truth. New stakeholders often emerge when design details, locations, procurement arrangements, data flows, or unintended effects become clearer.

2.1 A systematic identification process

A robust process commonly includes the following steps:

1. Examine project documents. Review the problem statement, business case, strategic objectives, preliminary requirements, benefits map, risk assumptions, site information, legal obligations, and lessons from comparable projects.

2. Analyse the project system. Identify who provides inputs, approves decisions, performs work, receives outputs, operates the result, bears costs, experiences risks, or can block progress.

3. Consult knowledgeable informants. Interview the sponsor, customer representatives, functional managers, community liaison officers, legal advisers, operational staff, and subject-matter experts. Snowball questioning—asking each person who else should be involved—often reveals hidden stakeholders.

4. Map relationships and dependencies. Consider ownership, authority, funding, supply chains, professional networks, political relationships, community structures, and informal influencers.

5. Test for absent or marginalized voices. Ask who is unable to attend meetings, who may be digitally excluded, who bears impacts without receiving benefits, and whose interests are represented indirectly.

6. Validate and record. Confirm names, roles, interests, preferred communication channels, data restrictions, and assumptions. Record uncertainty rather than inventing precision.

2.2 Stakeholder register

The stakeholder register is a controlled working record that supports planning and governance. Typical fields include:

• stakeholder name, category, and organizational affiliation;
• role, relationship to the project, and geographical location;
• interests, needs, expected benefits, and concerns;
• formal authority, informal influence, and dependencies;
• current attitude and desired future attitude;
• likely impact of the project on the stakeholder;
• preferred language, channel, format, frequency, and accessibility requirements;
• engagement owner and planned actions;
• risks, opportunities, commitments, and unresolved issues;
• confidentiality classification and date of latest review.

The register should not become a repository of personal speculation. Descriptions should be evidence-based, respectful, proportionate, and relevant to project decisions. Sensitive personal data should be collected only when necessary, lawfully, securely, and with appropriate access controls.

3. Analysing Stakeholder Power, Interest, Influence, Legitimacy, and Attitude

No single matrix is sufficient for all projects. The familiar power–interest grid is useful for prioritizing management attention, but it can mislead if it treats low-power groups as unimportant. A more comprehensive analysis combines several dimensions.

3.1 Power and formal authority

Power is the capacity to enable, constrain, delay, alter, or terminate project activity. It may arise from:

• formal decision rights or regulatory authority;
• control of funding, resources, assets, data, or access;
• contractual rights;
• technical expertise or scarce knowledge;
• social networks, reputation, or political connections;
• ability to mobilize public opinion, legal action, labour action, or media attention.

Formal authority is only one form of power. A community organization may lack approval authority but possess strong mobilization power. A systems architect may have no executive title but control knowledge essential to safe implementation.

3.2 Interest and impact

Interest refers to the degree to which a stakeholder cares about project decisions or outcomes. Impact refers to the extent to which the project changes the stakeholder’s welfare, rights, resources, work, environment, or identity. A stakeholder may have low visible interest but high impact, especially when information is inaccessible or consequences are delayed. High-impact stakeholders warrant proactive engagement even when they do not demand attention.

3.3 Influence and dependency

Influence is the ability to shape perceptions, decisions, behaviour, or implementation. It may be direct or indirect. Dependency asks how much the project relies on the stakeholder for approvals, information, resources, adoption, legitimacy, or access. A stakeholder with moderate power but high project dependency may deserve priority comparable to a powerful sponsor.

3.4 Legitimacy and urgency

Legitimacy concerns whether a stakeholder’s claims are viewed as appropriate, valid, or grounded in recognized rights, duties, contracts, expertise, or social expectations. Urgency concerns the time sensitivity and criticality of the claim. A useful conceptual classification is:

• Definitive stakeholders: possess power, legitimacy, and urgent claims.
• Expectant stakeholders: possess two of these attributes.
• Latent stakeholders: possess one attribute but may become more salient as circumstances change.

This salience perspective is not a mechanical ranking system. It is a prompt to examine whose claims require attention and why. A regulator’s urgent safety directive and a community’s legally protected land claim cannot be dismissed because neither controls the project budget.

3.5 Attitude and readiness

Attitude describes a stakeholder’s current orientation toward the project, such as leading, supportive, neutral, resistant, or unaware. Desired attitude should be defined realistically. A project does not always need enthusiastic support; in some cases, informed acceptance, lawful compliance, or constructive challenge is the appropriate goal.

Readiness also matters. Users may support the project in principle but lack skills or capacity to adopt it. A regulator may be neutral but require substantial evidence before granting approval. Engagement strategies should address the reason behind an attitude rather than labelling a stakeholder as simply “difficult.”

3.6 Combining dimensions without false precision

Numerical scoring can help compare attention requirements, but scores are judgments, not objective measurements. If a team uses a scale from 1 to 5, it should define anchors—for example, power score 1 means no practical ability to affect the project, whereas 5 means authority to stop or materially redirect it. Scores should be accompanied by evidence and reviewed for bias.

A simple priority index might be used internally as a screening aid:

Here, P is a stakeholder-priority screening score; Pₛ, Iₛ, Lₛ, Uₛ, and Mₛ are normalized scores for power, interest or impact, legitimacy, urgency, and project dependency respectively; and the w terms are explicit weights whose sum is 1. The score has no universal unit and should not be interpreted as a probability or a legally valid ranking. It is applicable only when the organization has defined scoring anchors, uses the same scale consistently, documents evidence, and retains a separate rights-and-compliance review. A high score should trigger analysis, not automatic exclusion of lower-scoring stakeholders.

4. Engagement Strategy as a Design Problem

Engagement should be planned according to the decision, the stakeholder, and the context. Generic newsletters are inadequate when stakeholders must negotiate land access, validate requirements, or consent to data use. The project team should specify what each engagement activity is intended to achieve.

4.1 Engagement purposes

Common purposes include:

• informing stakeholders about facts, constraints, decisions, and changes;
• consulting stakeholders to obtain evidence, preferences, and concerns;
• involving stakeholders in defining requirements or evaluating options;
• collaborating through joint problem-solving and shared governance;
• empowering stakeholders to make or approve decisions within a defined mandate;
• negotiating trade-offs, compensation, responsibilities, access, or acceptance;
• monitoring impacts and learning from implementation experience.

The distinction between informing and involving is important. Calling an information session a consultation can create false expectations and undermine trust.

4.2 Matching strategy to stakeholder conditions

A practical engagement plan answers six questions:

1. What decision, uncertainty, or relationship requires attention?
2. Which stakeholders need to participate, and why?
3. What information will be shared, by whom, and in what form?
4. What response or decision is being requested?
5. How will feedback influence the project, and how will the team demonstrate this?
6. What will happen if agreement is not reached?

These categories are starting points, not substitutes for judgement. Cultural context, history, language, trauma, power imbalance, and confidentiality may require adaptation.

4.3 Inclusive communication

Inclusive engagement removes avoidable barriers to participation. Planning should consider language translation, literacy, disability access, digital exclusion, meeting timing, transport, childcare, safety, cultural protocols, and the ability to participate without retaliation. A meeting held online may be efficient for executives but inaccessible to communities with poor connectivity. A technically accurate environmental report may be unusable without plain-language summaries and visual explanations.

Participation should also be representative. The loudest individual is not necessarily the legitimate voice of a community. The project team should identify how representatives are selected, what mandate they hold, and how dissenting views will be recorded. Inclusion does not mean that every request must be accepted; it means that affected parties have a fair opportunity to understand, contribute, challenge, and receive reasons for decisions.

5. Communication, Negotiation, and Conflict Management

5.1 Communication architecture

The communication plan should connect stakeholder needs with project governance. It normally identifies message ownership, audience, purpose, channel, timing, security classification, feedback mechanism, and record-retention requirement. Decision communications should state what was decided, the rationale, assumptions, consequences, responsible owner, and route for challenge or appeal.

Communication is not complete when a message is sent. The team should verify receipt, comprehension, and implications. For high-risk issues, use multiple channels and maintain an auditable record. Do not promise confidentiality that cannot legally or operationally be maintained.

5.2 Principled negotiation

Negotiation is appropriate when stakeholders have partly competing interests but can benefit from an agreed arrangement. A principled approach separates people from problems, focuses on underlying interests rather than stated positions, generates options for mutual gain, and uses objective criteria where possible.

For example, a community may oppose night construction. Its stated position is “no night work,” but the underlying interests may include sleep, safety, cultural practices, and trust. The project’s interest may be maintaining a fixed completion date. Options could include restricted hours, noise controls, compensation for verified disruption, or a revised sequence. Agreement should be documented with responsibilities, review points, and remedies for non-performance.

Negotiation is not appropriate where a stakeholder’s legal right requires consent, where coercion invalidates participation, or where a safety-critical minimum cannot be traded away. In such cases, the project must comply with law and professional duty rather than treating rights as bargaining variables.

5.3 Managing conflict

Conflict may concern facts, interests, values, relationships, processes, or scarce resources. Early diagnosis prevents a technical disagreement from being mismanaged as a personal dispute. Useful responses include joint fact-finding, facilitated dialogue, independent review, design change, escalation to governance bodies, and formal dispute resolution.

Project leaders should distinguish constructive dissent from obstruction. Critical questioning can reveal hazards and improve decisions. Suppressing dissent may produce apparent harmony while increasing latent risk. Escalation should be transparent, proportionate, and free from retaliation.

6. Governance, Ethics, and Regulatory Responsibility

Stakeholder engagement has governance consequences because it affects who can influence decisions, what evidence is considered, and how accountability is distributed. The project charter should clarify stakeholder-related authority: who approves scope, who accepts deliverables, who grants access, who owns operational decisions, and who receives escalations.

Important ethical principles include:

• Respect: treat stakeholders as persons and communities with dignity, not merely as obstacles or resources.
• Fairness: apply consistent procedures while recognizing unequal burdens and accessibility needs.
• Transparency: explain material assumptions, limitations, trade-offs, and decision rationales.
• Do no avoidable harm: identify and mitigate physical, economic, social, environmental, and psychological harms.
• Accountability: assign owners for commitments and provide mechanisms for complaint and remedy.
• Privacy and confidentiality: collect, use, store, and disclose personal or sensitive information lawfully and minimally.
• Integrity: avoid manipulation, tokenistic consultation, conflicts of interest, bribery, and selective disclosure.

Regulatory requirements vary by jurisdiction and sector. They may include environmental assessment, planning permission, occupational health and safety, data protection, procurement rules, accessibility standards, labour law, financial controls, and consultation duties. The project team should involve qualified legal and compliance advisers when requirements are uncertain. Compliance is a baseline, not a complete definition of responsible engagement.

7. Technology and AI in Stakeholder Engagement

Digital platforms can support stakeholder registers, issue tracking, surveys, multilingual communication, meeting records, sentiment analysis, and visualization of stakeholder networks. Artificial intelligence may help classify large volumes of feedback, identify recurring themes, summarize meetings, or flag unanswered questions. These uses can improve scale and consistency, but they do not replace human judgement.

Risks include biased training data, misclassification of minority views, surveillance, privacy breaches, fabricated summaries, automated exclusion, and the false appearance of objectivity. AI-generated analysis should be treated as decision support. The project team should disclose material automated processing where appropriate, validate outputs against source evidence, preserve dissenting views, protect personal data, and ensure that consequential decisions remain reviewable by accountable people.

8. Worked Application: Riverside Integrated Transport Project

The following is an illustrative case.

Background

A metropolitan authority proposes a bus rapid transit corridor connecting a low-income outer suburb to the central business district. The project promises shorter travel times, improved access to employment, lower emissions, and safer public transport. It requires road reallocation, removal of some parking, temporary construction disruption, and acquisition of a small number of properties.

Problem

At initiation, the sponsor identifies the transport authority, finance department, contractor, and planning regulator. Early public meetings attract strong opposition from shop owners and residents. The project team initially labels opponents as “low cooperation.” A review reveals that several affected groups have not been properly identified: mobility-impaired users, informal traders, school communities, tenants who may be displaced, emergency services, bus drivers, and residents who speak languages other than the official language.

Analysis

The sponsor has high formal power and high interest. The planning and environmental regulators have high authority and legitimacy, with urgent approval conditions. The transport authority is both customer and future operator. Bus drivers and maintenance staff have high operational knowledge but limited formal decision power. Small businesses have moderate collective influence and high potential impact because construction may reduce access and trading income. Tenants and informal traders have limited formal power but high impact and potentially strong legitimacy regarding livelihood disruption. Persons with disabilities have high legitimacy regarding accessibility requirements even if they do not control the budget.

The team distinguishes three issues that had been conflated:

1. Technical: whether the corridor can meet capacity and safety requirements.
2. Distributional: who receives benefits and who bears construction or access costs.
3. Procedural: whether affected groups have a meaningful opportunity to influence design and receive reasons for decisions.

Approach and solution

The revised engagement strategy includes:

• accessible neighbourhood workshops at different times and locations;
• translation and plain-language materials;
• walk-through accessibility audits with users of wheelchairs and mobility aids;
• separate confidential discussions with potentially displaced tenants and traders;
• a business-access plan covering signage, delivery windows, temporary routes, and compensation processes where legally applicable;
• driver and maintenance workshops to test operational assumptions;
• regulator briefings supported by traceable evidence;
• an online and paper feedback process with a published response log;
• an independent community liaison function reporting unresolved issues to the project board.

The team does not promise that every requested design change will be adopted. Instead, it publishes decision criteria: safety, accessibility, legal compliance, lifecycle cost, travel-time benefits, environmental effects, and distributional consequences. Where suggestions are rejected, the project explains why and records mitigation measures.

Outcome

The final concept retains the main corridor but changes several station locations, adds safer pedestrian crossings, modifies construction sequencing near schools, and establishes a business-access protocol. Some opposition remains, but meetings become more substantive. The project secures approvals with clearer conditions, reduces redesign risk, and improves the legitimacy of unavoidable property impacts.

Learning points

First, stakeholders are discovered through impacts and dependencies, not only organizational charts. Second, low formal power does not mean low importance. Third, engagement quality includes both the opportunity to contribute and the transparency of the response. Fourth, separating technical, distributional, and procedural questions makes negotiation more productive. Finally, a stakeholder strategy should be linked to design and governance decisions rather than treated as public relations.

9. Challenges and Limitations

Stakeholder analysis is inherently provisional. Interests change as project information, leadership, markets, regulations, and public attention change. A stakeholder who is neutral during initiation may become highly influential after an incident or election. Registers should therefore be reviewed at stage gates, major scope changes, risk reviews, and after significant feedback.

Power maps can reproduce managerial bias. Teams may overvalue formal authority, underestimate collective action, or describe dissent as irrational. Scoring systems create an illusion of precision and can conceal ethical choices behind arithmetic. Consultation can also become tokenistic when decisions are predetermined, participation is inaccessible, or feedback is collected without response.

Other challenges include stakeholder fatigue, conflicting representative mandates, misinformation, confidential negotiations, polarized communities, consultation capture by organized groups, and the tension between transparency and commercial or personal privacy. These cannot be eliminated by a single template. They require contextual judgement, independent challenge, clear governance, and willingness to revise the project.

Best-Practice Checklist

Before approving the project charter, the initiating team should be able to answer yes to most of the following questions:

• Have all parties affected by benefits, costs, risks, and decisions been considered?
• Have rights-holders and marginalized groups been identified separately from powerful institutions?
• Are sponsor, customer, user, regulator, supplier, and community roles clear?
• Is every important stakeholder assessment supported by evidence or an explicit assumption?
• Does the engagement plan specify purpose, owner, timing, channel, accessibility, and feedback method?
• Are negotiation boundaries and non-negotiable legal or safety requirements clear?
• Are commitments recorded, assigned, monitored, and escalated?
• Are privacy, confidentiality, conflicts of interest, and data governance addressed?
• Are communication methods appropriate for language, disability, culture, literacy, and digital access?
• Is the register scheduled for review as the project changes?
• Can the project explain how stakeholder input affected decisions?

Chapter Summary

Stakeholder identification and engagement is a central discipline of project initiation. Stakeholders include anyone who can affect, be affected by, or perceive themselves to be affected by the project. Sponsors, customers, users, regulators, suppliers, partners, affected communities, rights-holders, and civil-society groups may occupy overlapping roles and require different forms of engagement.

A sound process begins with systematic identification, validation, and maintenance of a stakeholder register. Analysis should consider power, formal authority, interest, impact, influence, dependency, legitimacy, urgency, rights, and attitude. Power–interest grids are useful but incomplete; low-power stakeholders may have high impact or legitimate claims. Numerical scoring can support screening only when assumptions, evidence, and limitations are explicit.

Engagement must be designed around a purpose: informing, consulting, involving, collaborating, empowering, negotiating, or monitoring. Inclusive practice addresses language, disability, culture, digital access, representation, safety, and unequal power. Effective communication is two-way and decision-linked. Principled negotiation focuses on interests, objective criteria, and workable commitments, while ethical governance protects rights, privacy, fairness, accountability, and procedural integrity.

Technology and AI can support large-scale analysis but require human oversight, privacy safeguards, bias controls, and accountability. The Riverside case demonstrates that meaningful engagement can improve design, reduce risk, support regulatory approval, and strengthen legitimacy. Ultimately, stakeholder engagement is not a public-relations activity added after technical planning; it is part of defining project value and governing change responsibly.

Key Terms

Stakeholder: An individual, group, organization, or community that can affect, be affected by, or perceive itself to be affected by a project.

Sponsor: The person or body that authorizes, supports, and provides strategic direction for a project.

Customer: The party that commissions, funds, specifies, or accepts project outputs.

User: A person or group that operates, experiences, or relies on the project’s product, service, or result.

Regulator: A public or authorized body that establishes and enforces requirements affecting the project.

Affected community: A geographically, socially, culturally, or economically connected population experiencing project effects.

Rights-holder: A stakeholder possessing recognized legal, customary, cultural, human, or procedural rights.

Stakeholder register: A controlled record of stakeholder identities, interests, influence, attitudes, needs, risks, and engagement actions.

Power: The capacity to enable, constrain, delay, redirect, or terminate project activity.

Interest: The degree to which a stakeholder cares about project decisions or outcomes.

Influence: The capacity to shape perceptions, decisions, behaviour, or implementation.

Legitimacy: The perceived or recognized validity and appropriateness of a stakeholder’s claim.

Urgency: The time sensitivity and criticality of a stakeholder claim.

Attitude: A stakeholder’s orientation toward the project, such as support, neutrality, resistance, or unawareness.

Engagement: Deliberate interaction intended to inform, involve, influence, collaborate with, or negotiate among stakeholders.

Social licence: Informal continuing acceptance of a project by affected or interested communities.

Principled negotiation: Negotiation focused on interests, objective criteria, options, and relationships rather than positional demands.

Tokenism: The appearance of participation without meaningful opportunity to influence decisions.

Stakeholder salience: The relative prominence of a stakeholder claim based on attributes such as power, legitimacy, and urgency.

Procedural fairness: The quality, accessibility, transparency, and impartiality of the process through which decisions are made.

Review Questions

5 Short Answer Questions

1. Define a stakeholder and explain why the definition should include parties without formal contracts.
2. Distinguish a customer, a user, a sponsor, and a regulator.
3. What information should normally be recorded in a stakeholder register?
4. Explain why power and legitimacy are different stakeholder attributes.
5. Give two examples of barriers that inclusive engagement should address.

5 Long Answer Questions

1. Explain a systematic process for identifying stakeholders during project initiation, including methods for discovering marginalized or indirect stakeholders.
2. Critically evaluate the usefulness and limitations of the power–interest grid.
3. Discuss how legitimacy, urgency, and rights should influence stakeholder prioritization.
4. Compare informing, consulting, involving, collaborating, and empowering as engagement purposes.
5. Explain how ethical principles and regulatory duties shape stakeholder communication and negotiation.

3 Analytical / Application Questions

1. A hospital is introducing an AI-supported patient scheduling system. Identify at least eight stakeholders, classify their interests and potential impacts, and propose an engagement strategy for each.
2. A construction project has strong executive support but opposition from residents who have little formal authority. Analyse the situation using power, interest, legitimacy, urgency, and impact. Recommend a response that avoids tokenistic consultation.
3. A regulator requires additional safety controls that increase cost and delay, while the sponsor demands the original completion date. Design a negotiation and escalation approach that protects legal and safety obligations while addressing the sponsor’s interests.

Multiple Choice Questions with Answers

Question 1

Which statement best defines a stakeholder?

A. Only a person who funds the project

B. Only a person employed on the project team

C. Any party that can affect, be affected by, or perceive itself affected by the project

D. Only a person with formal decision authority

Correct Answer: C. Any party that can affect, be affected by, or perceive itself affected by the project

Question 2

Which stakeholder attribute concerns the recognized validity of a claim?

A. Legitimacy

B. Urgency

C. Interest

D. Dependency

Correct Answer: A. Legitimacy

Question 3

What is the principal limitation of relying only on a power–interest grid?

A. It cannot display organizational names

B. It may undervalue low-power stakeholders with high impacts or legitimate rights

C. It prevents communication planning

D. It applies only to internal stakeholders

Correct Answer: B. It may undervalue low-power stakeholders with high impacts or legitimate rights

Question 4

Which activity is an example of consultation rather than simple information?

A. Publishing a final decision without responses

B. Sending a newsletter describing project milestones

C. Requesting stakeholder views and explaining how they will inform a decision

D. Archiving the project charter

Correct Answer: C. Requesting stakeholder views and explaining how they will inform a decision

Question 5

Which item is most appropriate for a stakeholder register?

A. Unverified personal rumours

B. Stakeholder interests, influence, attitude, needs, and planned engagement

C. The project team’s private social-media passwords

D. Only the stakeholder’s job title

Correct Answer: B. Stakeholder interests, influence, attitude, needs, and planned engagement

Question 6

In principled negotiation, the project team should primarily focus on:

A. Underlying interests and objective criteria

B. Defeating the other party

C. Avoiding written commitments

D. Treating every position as non-negotiable

Correct Answer: A. Underlying interests and objective criteria

Question 7

Why should a project identify rights-holders separately from powerful stakeholders?

A. Rights-holders are always project sponsors

B. Rights and legitimate claims may require attention even when formal power is limited

C. Rights-holders never need communication

D. Rights-holders can be excluded from risk analysis

Correct Answer: B. Rights and legitimate claims may require attention even when formal power is limited

Question 8

Which practice best supports inclusive engagement?

A. Using one digital meeting at a fixed time for everyone

B. Providing accessible formats, suitable language, and opportunities for two-way participation

C. Allowing only senior executives to speak

D. Collecting feedback without explaining its use

Correct Answer: B. Providing accessible formats, suitable language, and opportunities for two-way participation

Question 9

What is a major risk of using AI to analyse stakeholder feedback?

A. It always eliminates human bias

B. It may misclassify minority views or reproduce bias in the data

C. It makes privacy irrelevant

D. It guarantees legal compliance

Correct Answer: B. It may misclassify minority views or reproduce bias in the data

Question 10

In the illustrative transport case, why were tenants and informal traders important stakeholders?

A. They controlled the national transport budget

B. They had high potential impact and legitimate livelihood concerns despite limited formal power

C. They were automatically project sponsors

D. They were responsible for regulatory approval

Correct Answer: B. They had high potential impact and legitimate livelihood concerns despite limited formal power