13.3 Managing Disagreements & Constructive Resolution

13.3 Managing Disagreements & Constructive Resolution

Quick Answer: FAI 3.1.4 Manage Disagreements is broader than bid protests. It includes buyer–seller conflict management: early resolution, negotiation before formal claims, professional communications, documented positions, smart elevation, and a preview of FAR Part 33 Subpart 33.2 disputes. Prefer constructive problem-solving that still protects Government rights—not reflexive adversarial posture and not passive avoidance.

Sections 13.1 and 13.2 covered formal pre-award/award challenge forums. Day-to-day contracting generates a larger volume of disagreements that never become protests: interpretation fights, invoice disputes, schedule blame, inspection rejections, change-order scope debates, and personality friction between CORs and contractor project managers. How you manage those conflicts determines whether the acquisition produces mission results—or produces claims, bad past performance wars, and workforce burnout.

The competency frame: buyer and seller

Contracting is a relationship with rules. Both sides have interests:

Manage Disagreements means advancing legitimate Government interests without adopting illegitimate tactics—and without surrendering rights out of conflict avoidance.

Early resolution as risk control

Disagreements grow expensive with time:

Exam principle: Early engagement is not “giving in.” It is controlling risk while facts are fresh and positions are still flexible.

Scenario — Silent rejection. COR rejects deliverables for weeks without written reasons; contractor burns schedule. Later both sides claim the other breached. Better path: prompt written nonconformance notices, cure opportunities when appropriate, joint problem-solving on root cause, CO involvement when authority or interpretation is unclear.

Negotiation of disputes before formal claims

Before a matter becomes a claim, parties often can negotiate:

1. Identify the issue precisely — scope, clause, fact dispute, or pure business disagreement?
2. Gather the contract baseline — what does the contract actually require? (Spec, SOW/PWS, drawings, clauses, mods.)
3. Separate facts from positions — timeline, inspections, emails, Government-caused delays vs contractor performance failures.
4. Explore options — clarification mod, bilateral change with price adjustment, no-cost schedule adjustment, partial acceptance, re-performance, settlement of quantum.
5. Stay within authority — COs negotiate within warrant and approval thresholds; do not “settle” what you cannot approve.
6. Document the deal — bilateral modification or other proper instrument; do not rely on handshake peace.

REA vs claim awareness (preview): Contractors may submit requests for equitable adjustment or similar proposals seeking price/schedule relief. Negotiation is normal. A claim (especially a certified claim for money over applicable thresholds) triggers more formal Disputes procedures under Subpart 33.2 and the Contract Disputes Act framework—covered deeply in Post-Award chapters. For Manage Disagreements at Award competency level: try principled negotiation first; know when formality has begun.

Professional communications

How you write and speak changes outcomes.

Communication rules of thumb:

• Confirm oral direction in writing when it affects cost, schedule, or scope.
• Use the CO for interpretation disputes that bind the Government—CORs inspect and recommend; they generally do not freestyle change the contract.
• Listen first in meetings; many “disputes” are missing information.
• Do not promise what the contract forbids to keep peace (constructive change risk).
• Protect source selection and proprietary information even during angry debriefs or protest-adjacent talks.

Link to Guiding Principles: Communication and documentation (Chapter 5 themes) are the daily tools of disagreement management.

Documenting positions

When disagreement is material, each side should be able to answer from the file:

1. What is our position?
2. What facts support it?
3. What contract language supports it?
4. What relief or outcome do we seek?
5. What alternatives did we consider?
6. Who approved the Government position?

Documentation serves three futures:

Exam cue: “We verbally agreed to ignore the spec” with no mod is a documentation and authority failure waiting to become a claim and a quality failure.

When to elevate

Not every spat needs a flag officer. Elevation is a judgment skill.

Elevate / involve counsel or leadership when:

• The issue exceeds your warrant / approval authority.
• There are integrity, fraud, or conflict-of-interest indicators.
• A protest, size challenge, or claim is filed or imminently threatened with legal process.
• Positions are locked after good-faith negotiation (impasse) and mission impact is material.
• Safety, classified, or statutory compliance issues arise.
• The contractor alleges bad faith or constitutional/procurement integrity violations.
• Multiple Government voices are creating inconsistent direction.

Do not elevate only to:

• Avoid making a hard but clear in-scope call.
• Punish a contractor personally.
• Shop for a “yes” after counsel already identified illegality.

Team dynamics: Use the acquisition team (PM, technical, legal, finance, small business) early—elevation works better as structured decision support than as last-minute crisis dumping.

Constructive disagreement management vs adversarial posture

Constructive is not capitulation. You can be constructive and still:

• Reject out-of-scope work without a proper mod and funding.
• Issue cure notices / show-cause when performance fails.
• Deny unsupported claims.
• Defend a sound award against a weak protest.

Adversarial is not always wrong. Fraud referrals, default terminations, and litigation may require a firm adversarial litigation posture. The skill is matching posture to stakes and facts.

Relationship to later claims and disputes (Part 33 Subpart 33.2 preview)

FAR Part 33 has two major worlds:

Subpart 33.2 themes you should recognize now (details deepen in Post-Award):

• Disputes clause procedures in the contract.
• Contractor claims (and Government claims).
• Certification requirements for certain claims.
• Contracting Officer’s final decision.
• Appeal paths (agency boards / Court of Federal Claims concepts).
• Interest and formality once a claim is in the disputes system.

Why preview here: Award-phase professionals who mismanage early disagreements create the claims that Subpart 33.2 must later adjudicate. Prevention and early negotiation are part of Manage Disagreements even when the formal disputes machinery is “later.”

Memory chain:

1. Spot disagreement early.
2. Clarify facts + contract baseline.
3. Negotiate within authority; document.
4. Elevate when needed.
5. If unresolved money/rights disputes mature → claims/disputes path (33.2).
6. Parallel: competition integrity fights → protests (33.1) / size (SBA).

Practical playbooks (exam scenarios)

Playbook A — Interpretation dispute. Contractor reads the PWS one way; COR another. Do: CO issues written interpretation based on the contract as a whole; consider clarification mod if ambiguity is genuine Government drafting failure; assess entitlement if Government direction changed the work.

Playbook B — Invoice / acceptance dispute. Do: Tie rejection to inspection/acceptance clauses and documented nonconformance; pay what is undisputed when rules require; avoid holding entire invoices hostage over minor issues without clause support.

Playbook C — Change / scope creep. Technical office orally asks for “just one more report.” Do: Stop oral out-of-scope direction; process a mod if needed; document constructive change risk if work already performed under Government direction.

Playbook D — Protest threat during discussions. Offeror says “award to anyone else and we’ll protest.” Do: Continue fair process; do not award based on fear alone; ensure the file can withstand review; never trade unequal treatment for “no protest” promises.

Playbook E — Relationship meltdown. Personal conflict between COR and contractor PM. Do: Reset communications norms; escalate to CO/PM leadership; replace personnel interfaces if needed; keep performance facts separate from personalities.

Connecting Manage Disagreements across the lifecycle

North-star for CON 3990V: The same professional—fair, documented, within authority, mission-focused—handles all of it.

CON 3990V closed-book anchors

• 3.1.4 = protests + size/status awareness + constructive buyer–seller conflict management.
• Early resolution and negotiation beat late formal warfare when facts allow.
• Professional communication + documented positions = transferable file power.
• Elevate for authority, integrity, legal process, and true impasse—not for avoidance.
• Constructive ≠ weak; adversarial ≠ default.
• Part 33.1 protests vs 33.2 disputes—know which world you are in.

---

Bottom line: Managing disagreements is core contracting professionalism. Resolve early, communicate cleanly, document positions, elevate wisely, and keep formal protest/claims tools ready without leading with hostility. On CON 3990V, choose the answer that protects mission, fairness, and the record simultaneously.