The Stakeholder Alignment Map: Support, Conditions, Conflict, and Veto Risk

Who this worksheet is for

This worksheet is for B2B teams that have identified several people or functions but still cannot explain how their views interact. It is useful when technical, operational, financial, procurement, quality, legal, or executive concerns pull in different directions. BC-07 defines influence, authority, access, and veto power; this article maps current support and conflict. It does not prescribe persuasion tactics, contact cadence, or opportunity strategy.

Contents

1 Separate alignment from role and authority 2 Use bounded stakeholder position states 3 Attach conditions to every conditional position 4 Map conflict around decisions, not personalities 5 Identify veto risk with evidence 6 Complete and review the alignment worksheet 7 Illustrative example 8 Common mistakes 9 What this does not mean 10 Common questions 11 Sources and methodology

1. Separate alignment from role and authority

A functional role describes what a person or team does in a specific decision. Alignment describes their current, evidence-backed position toward a defined option or requirement. Authority describes what they may formally decide. Influence describes their ability to affect others. These fields can move independently. An Operational Evaluator may strongly support the desired outcome but oppose the proposed installation window. A Technical Evaluator may be neutral about the commercial choice while holding decisive influence over compatibility. A procurement professional may coordinate a mandatory process without personally supporting or opposing the purchase. Formal procurement offers useful evidence of role separation. FAR Part 7 describes integrated acquisition planning by personnel responsible for significant aspects of a purchase. FAR Part 15 distinguishes source-selection responsibilities, evaluation factors, proposal evaluation, and decision documentation. These federal rules do not define private-company alignment, but they demonstrate why participation, evaluation, and authority should remain separate. Start with a full decision scope: account or site, application, purchase situation, option being considered, relevant decision context, and evidence date. A person can support a pilot and oppose a full deployment without contradicting themselves. Without scope, the map will mislabel that conditional position as inconsistency.

2. Use bounded stakeholder position states

SellersGPT recommends six position states: Position state Definition Minimum evidence support Stakeholder favors the defined option without a known unmet material condition Direct bounded statement or confirmed action relevant to the decision conditional_support Stakeholder favors the option if specified conditions are satisfied Statement plus explicit conditions undecided Stakeholder is evaluating and has not taken a supported position Direct statement or documented open evaluation concern Stakeholder identifies material risk or deficiency without opposing the outcome Specific concern, requirement, or evidence gap opposition Stakeholder objects to the defined option or recommends an alternative Direct bounded statement or documented recommendation Position state Definition Minimum evidence unknown Available evidence does not establish position Missing, stale, ambiguous, or conflicting evidence Do not infer support from a meeting, reply, document request, or friendly tone. Do not infer opposition from a detailed review. Rigorous questions may indicate that a stakeholder is performing an evaluator role, not that they reject the purchase. Record evidence state beside position: confirmed, inferred, unknown, or contradicted. An inferred position must never be displayed with the same visual certainty as a confirmed one. Interest and access also remain separate. A highly engaged user can have little formal authority; a rarely visible validator can own a mandatory gate.

3. Attach conditions to every conditional position

"Supportive, with concerns" is not enough. Write the condition as a testable statement: Operational Evaluator supports the Plant A retrofit if installation can occur within the documented eight-hour maintenance window and the service plan covers restart support. Each condition needs:

• the stakeholder or function stating it;

• decision scope and evidence date;

• exact requirement or concern;

• acceptable evidence;

• whether it is a hard gate, compensating criterion, preference, or evidence contribution;

• owner of the underlying decision;

• state: pass, fail, unknown, or contradicted;

• review trigger. The U.S. GAO's 2025 Green Book emphasizes risk assessment, reliable information, preventive controls, documentation, and change assessment in federal internal control. SellersGPT adapts those principles by requiring a condition to be visible and reviewable rather than buried inside a sentiment label. Conditional support does not become full support merely because time passes. It changes only when credible evidence shows the condition was satisfied, changed, waived by an authorized party, or withdrawn by the stakeholder.

4. Map conflict around decisions, not personalities

Draw a conflict edge only when two positions cannot both govern the same decision as currently stated. Label the edge with the disputed object:

• required specification;

• acceptable risk threshold;

• implementation window;

• total-cost assumption;

• contract term;

• evidence sufficiency;

• site versus enterprise standard;

• short-term continuity versus long-term standardization. Some apparent conflicts disappear when scope is corrected. Engineering may discuss the product specification while maintenance discusses the installation method. Finance may compare three-year cost while procurement compares first-year cash exposure. BC-26 provides the claim-level method for resolving these differences. Do not store "engineering and procurement do not get along." That is a speculative personality label. Store the supported disagreement: "Engineering accepts specification X for Plant A; procurement says enterprise policy requires approved alternative Y unless an exception is documented." The second record preserves a condition and possible exception path. Conflict-of-interest rules are different from disagreement. FAR Part 3 addresses procurement integrity and actual or apparent conflicts in U.S. federal procurement. Canada's Contracting Policy Notice 2025-3 describes identifying, reporting, mitigating, documenting, and monitoring conflicts of interest in public procurement. Use those terms only for relevant integrity concerns; do not call ordinary stakeholder disagreement a legal conflict of interest.

5. Identify veto risk with evidence

Veto risk exists when a person, team, or process can formally stop the defined option by controlling a hard gate, non-delegable approval, mandatory acceptance, or authorized exception. It does not arise from seniority or strong opposition alone. Use three fields:

• Veto basis: the rule, authority, delegated responsibility, or process.

• Affected gate: the exact condition that can be stopped.

• Evidence state: confirmed, inferred, unknown, or contradicted. If authority is inferred, label possible_veto rather than veto. If the owner is unknown, use BC-24's stop-condition method. An aggregate support score cannot offset a confirmed hard-gate failure. The Government of Canada's procurement-governance audit describes separate contracting-authority, business-owner, senior-official, and oversight responsibilities in that public system. It is useful evidence that decision rights can be distributed. It is not a template for assigning authority inside an unverified account.

6. Complete and review the alignment worksheet

Use one row per person or team for one decision scope: Stakehold er Functional role Position Conditions Influence Formal authority Veto basis Evidence state Review trigger Person/tea m Role hypothesis One controlled state Exact conditions or none known Low/mediu m/high with evidence Defined authority or unknown Gate and basis or none known Confirmed/i nferred/unk nown/contra dicted Date/event Add a separate conflict-edge list. Do not try to fit stakeholder-to-stakeholder relationships into a single row. Measure map quality with evidence coverage, not positive sentiment: Position evidence coverage = stakeholders with confirmed or explicitly unknown position records / material stakeholders mapped x 100 An explicitly unknown position counts as a controlled record because uncertainty remains visible. An inferred position without its inference label does not. Coverage says whether the map is honest and reviewable, not whether the account is supportive. Review after a requirement, option, evidence object, authority, stakeholder, or decision scope changes. BC-28 provides the full refresh playbook.

7. Illustrative example

Illustrative example - fictional. Fictional AlloySense maps six material stakeholder functions for a fictional mill-monitoring purchase: Function Position Condition Authority evidence Maintenance conditional_support Restart support within four hours Confirmed evaluator role, no formal veto Engineering support None known after interface review Confirmed technical recommendation role IT security concern Network segmentation evidence missing Confirmed hard-gate validator Finance undecided Three-year cost model under review Confirmed budget recommendation, final authority unknown Procurement unknown Process requirements not yet confirmed Process ownership inferred Plant manager support Subject to all mandatory reviews Priority influence confirmed; signing authority unknown Five of six rows have either a confirmed position or an explicit unknown supported by a current record. The procurement row is explicit unknown, so it counts as controlled. The finance row has a confirmed undecided position. Position evidence coverage = 6 / 6 x 100 = 100%. Yet the account is not approved. IT security controls an unresolved hard gate. There is also a conflict edge between maintenance's four-hour restart condition and the proposed eight-hour service response. Overall state remains Blocked on security evidence and unresolved on service condition. The example is fictional. The 100% value means all six mapped functions have honest current position records. It is not positive sentiment, intent, purchase probability, qualified lead status, or revenue forecast.

8. Common mistakes

• Equating a positive tone with support.

• Treating requests for evidence as opposition.

• Recording "supportive" without the attached condition.

• Averaging support and opposition into one score.

• Calling every opponent a veto holder.

• Using seniority as proof of authority.

• Turning a requirement conflict into a personality judgment.

• Hiding unknown positions to make the map look complete.

9. What this does not mean

This worksheet does not invite a seller to manipulate factions or expose one stakeholder's private comments to another. It does not guarantee that every material role is visible. It does not establish legal authority or replace a buyer's formal process. It provides a bounded, evidence-aware picture of alignment so the team can understand which decision, condition, or authority remains unclear. This article is not legal, procurement, or conflict-of-interest advice.

10. Common questions

Can a stakeholder be supportive and still block the purchase? Yes. A validator may support the goal but be required to reject insufficient evidence. Position and gate authority are separate. Should unknown positions count against alignment? Do not score them as negative. Keep them unknown and show their number or weight separately. They reduce certainty, not necessarily support. How do we record a stakeholder whose view changes? Create a new dated state, preserve the prior state, and record what evidence, scope, or condition changed. Do not overwrite history. Is disagreement always harmful? No. It may expose requirements or trade-offs early. The risk comes from hiding, personalizing, or falsely resolving it. Can the map determine the next outreach message? It can inform relevance and evidence needs, but BC-03 and Module 04 govern coordinated contact and execution. The map itself does not authorize contact.

11. Sources and methodology

This article uses official U.S. and Canadian procurement and internal-control sources to demonstrate distributed responsibilities, evaluation, integrity, and documentation. They do not define a universal private buying group. The position states, condition record, conflict edges, veto fields, worksheet, and formula are SellersGPT editorial tools. 1 U.S. General Services Administration, Federal Acquisition Regulation Part 3 - Improper Business Practices and Personal Conflicts of Interest. https://www.acquisition.gov/far/part-3. Accessed August 24, 2026. 2 U.S. General Services Administration, Federal Acquisition Regulation Part 7 - Acquisition Planning. https://www.acquisition.gov/far/part-7. Accessed August 24, 2026. 3 U.S. General Services Administration, Federal Acquisition Regulation Part 15 - Contracting by Negotiation. https://www.acquisition.gov/far/part-15. Accessed August 24, 2026. 4 Treasury Board of Canada Secretariat, Contracting Policy Notice 2025-3: New Guide to Mitigating Conflicts of Interest in Procurement. https://www.canada.ca/en/treasury-board-secretariat/services/policy-notice/2025-3.html. Accessed August 24, 2026. 5 Treasury Board of Canada Secretariat, Horizontal Internal Audit of Procurement Governance. ht tps://www.canada.ca/en/treasury-board-secretariat/services/audit-evaluation/horizontal-internal-audits/ horizontal-internal-audit-procurement-governance.html. Accessed August 24, 2026. 6 U.S. Government Accountability Office, Standards for Internal Control in the Federal Government (GAO-25-107721). https://www.gao.gov/products/gao-25-107721. Accessed August 24, 2026.