When Stakeholders Give Conflicting Answers: How to Preserve and Resolve Disagreement

Who this methodology guide is for

This guide is for teams that hear materially different answers about requirements, authority, timing, budget, technical fit, acceptable evidence, or process. It is useful when several stakeholders speak accurately about their own scope but the account record incorrectly forces one answer. It governs evidence reconciliation, not negotiation tactics, contact sequences, or pipeline escalation.

Contents

1 Capture the claims before resolving them 2 Test for scope and definition differences 3 Assess evidence reliability and authority 4 Classify the type of disagreement 5 Use neutral clarification and approved channels 6 Maintain the disagreement-resolution record 7 Illustrative example 8 Common mistakes 9 What this does not mean 10 Common questions 11 Sources and methodology

1. Capture the claims before resolving them

Do not edit a shared field repeatedly as new answers arrive. Create a claim record for each material statement:

• claim ID and exact statement;

• speaker or source;

• functional-role hypothesis;

• account/site, application, purchase situation, and relevant decision context;

• observation date and period covered;

• evidence object or supporting reference;

• evidence state and confidence;

• formal authority, if known;

• confidentiality or attribution boundary;

• relationship to competing claim IDs. Direct quotation is not always necessary and should stay within appropriate privacy and confidentiality limits. The goal is to preserve meaning, not every conversational detail. A bounded paraphrase such as "Plant A maintenance window is eight hours during the October shutdown, according to the maintenance planner on August 20" is more useful than "maintenance says October works." Government records rules illustrate why decisions and supporting information should be preserved. FAR Part 4 addresses administrative matters, contract files, distribution, identifiers, and retention in federal acquisition. It does not dictate a private CRM, but it supports keeping decision records rather than overwriting the history that explains them.

2. Test for scope and definition differences

Before labeling two claims contradictory, normalize eight dimensions: Dimension Clarifying question Entity Are both speakers discussing the same legal entity or business unit? Site Are they discussing the same plant, facility, or region? Dimension Clarifying question Application Is the same product use or operational problem in scope? Purchase situation Is one discussing replacement while another discusses expansion or new build? Period Do the claims cover the same date, fiscal period, project window, or version? Unit Are cost, volume, capacity, response time, and quantities expressed on the same basis? Definition Do terms such as approved, budgeted, qualified, or standard mean the same thing? Option Are both claims about the same configuration, supplier, contract, or implementation approach? Many conflicts disappear after normalization. "Budget is approved" may mean the business case has program approval, while "budget is not available" may mean a purchase order has not received current-period funding. Both statements can be accurate. If a difference comes from scope, do not merge the claims. Narrow each to its valid scope. If it comes from time, supersede the older current-state field while preserving its history. If it comes from definition, document the buyer's controlling definition or keep both until one is established.

3. Assess evidence reliability and authority

The U.S. GAO describes data reliability through accuracy, completeness, and applicability for its intended purpose and recommends a risk-based assessment. GAO, Assessing Data Reliability Apply these questions to stakeholder claims:

• Is the statement accurately captured?

• Is necessary context missing?

• Is it applicable to this decision scope?

• Is supporting evidence current and authentic?

• Does the speaker have direct knowledge?

• Does the speaker have authority to establish the matter, or are they contributing evidence? Authority depends on the claim. Engineering may establish technical compatibility but not contract-signing authority. Finance may confirm a budget control but not quality acceptance. Procurement may own solicitation communications without owning the operational requirement. FAR Part 15 distinguishes proposal evaluation, exchanges, source-selection responsibilities, decision, and documentation in negotiated U.S. federal procurement. That public framework shows why receipt of a statement and authority to decide it are separable. Do not use it to infer a private account's exact roles.

4. Classify the type of disagreement

Use one classification:

• scope_difference: claims apply to different entities, sites, applications, situations, or options;

• time_difference: a later event or version changed the answer;

• definition_difference: speakers use the same term differently;

• evidence_gap: one or both claims lack sufficient support;

• authority_difference: speakers address different decision rights;

• preference_conflict: stakeholders favor different trade-offs without stating a factual contradiction;

• material_contradiction: credible claims remain incompatible after normalization;

• integrity_or_process_concern: the conflict may involve protected information, fairness, or an actual/apparent conflict of interest and requires the appropriate control. Do not use the last category casually. Treasury Board of Canada Contracting Policy Notice 2025-3 describes identifying, reporting, mitigating, documenting, and monitoring conflicts of interest in Canadian public procurement. Ordinary disagreement about cost or risk is not automatically a legal conflict of interest. When a conflict is material, set the affected field to contradicted. Do not average numerical claims unless the values are measurements on a compatible basis and an approved method supports aggregation.

5. Use neutral clarification and approved channels

Ask questions that expose scope and authority without taking sides:

• "Does this requirement apply to Plant A, the whole division, or both?"

• "When you say approved, which decision has been completed?"

• "Which version and period does this figure cover?"

• "Which function records the final acceptance of this criterion?"

• "Is there an authorized exception path, and what evidence would it require?" Do not tell Stakeholder B that Stakeholder A privately disagreed unless attribution is permitted and necessary. Instead, present the neutral conflict: "We have two different documented service-window requirements and want to confirm the controlling scope." Public procurement sometimes formalizes equal clarification. The CanadaBuys phased offer compliance process describes defined assessments, notices, timeframes, equal treatment, and documented justification in its specific federal context. A private seller does not control that process, but the source illustrates why clarification rules should be explicit rather than improvised for the preferred answer.

6. Maintain the disagreement-resolution record

For each conflict, store: Field Required record Conflict ID Stable identifier linking every claim Material question The exact decision affected Claim set Original statements, sources, scopes, and dates Classification Scope, time, definition, evidence, authority, preference, contradiction, or process concern Clarification method Question, evidence request, review, or authorized process Resolving authority Person, team, policy, or process with evidence of authority Resolution Narrowed scopes, current answer, accepted trade-off, or unresolved state Effective date and scope Where and when the resolution applies Superseded records Prior current-state records retained in history Field Required record Review trigger Event requiring new assessment The 2025 GAO Green Book emphasizes reliable information, documented risk assessment, responsibility, preventive controls, and change assessment in federal internal control. SellersGPT adapts those concepts by requiring the resolution and its basis to remain inspectable. Use a status of resolved, partially_resolved, or unresolved. A partial resolution can establish one site while leaving another unknown. Never widen it beyond the evidence.

7. Illustrative example

Illustrative example - fictional. A fictional manufacturer, HarborDrive, records five disagreements during evaluation of a fictional motor replacement: 1 Engineering says the voltage requirement is 460 V; the maintenance record says 480 V. 2 Finance says funds are approved; procurement says no purchase authority exists. 3 Operations says installation can take 12 hours; production says six hours. 4 Quality says Certificate A is acceptable; the tender appendix requires Certificate B. 5 The plant manager says the supplier is preferred; corporate sourcing says no preference has been recorded. Normalization produces:

• Claim 1: definition_difference; 460 V nominal and 480 V system descriptions refer to the same documented system.

• Claim 2: authority_difference; program budget is approved, but purchase authority remains unresolved.

• Claim 3: material_contradiction; both refer to the same shutdown window.

• Claim 4: time_difference; a newer appendix superseded the earlier quality note.

• Claim 5: scope_difference; plant preference does not equal corporate sourcing decision. Three of five are resolved by definition, time, or scope. One is partially resolved, and one remains contradicted. Resolution coverage = fully resolved disagreements / material disagreements x 100 Resolution coverage = 3 / 5 x 100 = 60%. The team does not call the account 60% aligned. It holds the installation-window claim as contradicted and purchase authority as partially unresolved. Both have named clarification owners. The example is fictional. The percentage measures claim-resolution status, not purchase probability, intent, pipeline stage, qualified lead status, or forecast.

8. Common mistakes

• Updating one CRM field repeatedly and losing the original statements.

• Choosing the claim from the most senior or most supportive stakeholder.

• Calling different sites or periods a contradiction.

• Averaging incompatible numbers.

• Revealing private stakeholder remarks to create pressure.

• Asking for confidential source-selection or evaluation information.

• Treating ordinary disagreement as a legal conflict of interest.

• Expanding a narrow resolution into an account-wide fact.

9. What this does not mean

This methodology does not require consensus on every preference. It does not give a seller authority to adjudicate the buyer's internal governance. It does not justify bypassing procurement or seeking restricted information. It simply preserves what was said, tests whether the claims truly conflict, and records the appropriate authority's bounded resolution or the fact that no resolution exists. This article is not legal, procurement, conflict-of-interest, or records-management advice.

10. Common questions

Which stakeholder should we believe first? Do not begin with belief. Begin with scope, direct knowledge, evidence quality, and relevant authority. Different stakeholders may each be correct within different boundaries. Can we use the newest answer automatically? Only if it covers the same scope and a credible source establishes that it supersedes the older state. Preserve both and record the change. What if no one will resolve the conflict? Keep the affected field contradicted or unknown, attach the consequence, and pause only decisions that depend on it. Do not manufacture consensus. Should we tell stakeholders that their answers conflict? Ask neutral clarification about the requirement or scope. Avoid attributing private remarks unless permission, necessity, and the buyer's process support it. Does conflict mean the account is a poor fit? Not necessarily. It may show that the decision is distributed or still being defined. Account fit belongs to Module 02; this method addresses buying-group evidence.

11. Sources and methodology

This article uses official U.S. and Canadian data-reliability, procurement, integrity, records, and internal-control sources. Their formal requirements apply within stated public-sector scopes. The claim schema, normalization dimensions, conflict classes, resolution record, and formula are SellersGPT editorial tools. 1 U.S. Government Accountability Office, Assessing Data Reliability (GAO-20-283G). https://www.gao.gov/products/gao-20-283g. Accessed August 24, 2026. 2 U.S. General Services Administration, Federal Acquisition Regulation Part 15 - Contracting by Negotiation. https://www.acquisition.gov/far/part-15. Accessed August 24, 2026. 3 U.S. General Services Administration, Federal Acquisition Regulation Part 4 - Administrative and Information Matters. https://www.acquisition.gov/far/part-4. Accessed August 24, 2026. 4 Public Services and Procurement Canada, Apply the Phased Offer Compliance Process. https://can adabuys.canada.ca/en/buyer-s-portal/buyer-s-guide/receive-and-evaluate/offer-evaluation/apply-phase d-offer-compliance-process. Accessed August 24, 2026. 5 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. 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.