Dispute Resolution Script

The difference between a dispute that resolves and one that escalates is almost always the quality of the first substantive response. Most people, under pressure, mix emotions with facts, defend positions instead of exploring interests, and make threats they later regret. This skill produces the response itself — the actual words to write or say — not generic advice about staying calm.

Every dispute gets diagnosed before a word is drafted. Surface issue (what they're complaining about) is usually different from the underlying interest (what they actually want). "The work is terrible" often means "this isn't what I pictured." "You keep changing requirements" often means "I can't hit the deadline if the target keeps moving." Power dynamics matter — who holds the money, who has the contract on their side, who can walk away easily, whose reputation is more exposed. Escalation level (1 to 4) determines whether you go straight to PACE or whether the response needs to de-escalate before anything productive can happen. Level 3 or above triggers a cooling-off advisory: draft now, send tomorrow.

The PACE framework — Position acknowledgement, Area of agreement, Constructive proposal, Escalation path if needed — runs through every output. Acknowledge before advocating: if the other side doesn't feel heard, they can't hear you. Find what you genuinely agree on, even in bitter disputes (both want resolution, both value the relationship, both want the project finished). Make a specific, actionable proposal — "I propose X" beats "I won't accept Y" every time. And outline the next step calmly if the proposal is rejected, framed as transparency about the process rather than as a threat.

Outputs are channel-matched. Email disputes get a complete drafted email. Verbal disputes get a talk track with anticipated pivots ("if they push back, say…"). Scenario-specific adjustments cover the common patterns: client won't pay, client says work is bad, scope-creep dispute, bad review, partnership disagreement, multi-party chain disputes where you're caught in the middle and need separate scripts for upstream and downstream parties. Every output ships with what to save and record — because every response should still read well if a judge sees it later.

This produces drafts and scripts, not legal advice. Dispute resolution can shade into legal territory fast — refund claims, breach of contract, defamation exposure when bad-review responses go public. Have a qualified solicitor review before sending anything that might end up in front of a court. The skill is a starting point for professional review, not a substitute for one.