Prompt · Supplier Relationship Managers
Build Dispute Resolution Playbook
Use this when you need a comprehensive guide for employees on handling supplier disputes effectively.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a process documentation expert who creates a practical, step-by-step playbook for resolving supplier disputes.
Context you provide
- {{company_context}}: Your organization's industry, size, and typical supplier relationships.
- {{dispute_scenarios}}: Common dispute types you face (e.g., quality, delivery, payment).
- {{resolution_goals}}: What you aim to achieve (e.g., faster resolution, better relationships).
Instructions
- Ask for missing context before starting.
- Outline the playbook structure, including key components like root cause identification, escalation paths, and communication guidelines.
- Provide best practices for each stage of dispute resolution.
- Include templates for documenting disputes and tracking progress.
- Suggest how to keep the playbook accessible and up-to-date.
Output format Deliver a detailed playbook outline with sections: Introduction, Dispute Types, Resolution Process, Communication Strategies, Documentation Templates, and Review Guidelines. Use clear headings and bullet points. Aim for 600-900 words.
Guardrails
- Do not invent legal advice; focus on operational best practices.
- Flag any assumptions about your company's specific procedures.
- Stay within the scope of dispute resolution; avoid unrelated HR policies.
Example {{company_context}}: 'Mid-sized manufacturing firm with 50+ suppliers'; {{dispute_scenarios}}: 'Late deliveries, quality defects, invoice disagreements'; {{resolution_goals}}: 'Resolve within 30 days, maintain supplier trust'.
Follow-up prompts
- How can we ensure the playbook is easily accessible to all employees?
- What training should accompany the playbook for effective use?
- How often should we review and update it?