Skip to content
Back to skills

Discovery Dispute Letter

ASecurity

Drafts discovery dispute resolution letters documenting meet-and-confer efforts and unresolved issues in U.S. litigation. Use when drafting meet-and-confer letters, discovery conference follow-ups, or pre-motion to compel correspondence during the discovery phase.

  • 41 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 12, 2026
documentationgo

Works with

  • cli

Security analysis

A100/100

Scanned September 12, 2026

npx -y skills add CaseMark/skills --skill discovery-dispute-letter --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Discovery Dispute Letter?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Discovery Dispute Letter
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/casemark-discovery-dispute-letter/badge)](https://www.skillsdirectory.com/skills/casemark-discovery-dispute-letter)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: discovery-dispute-letter
language: en
description: Drafts discovery dispute resolution letters documenting meet-and-confer efforts and unresolved issues in U.S. litigation. Use when drafting meet-and-confer letters, discovery conference follow-ups, or pre-motion to compel correspondence during the discovery phase.
tags:
  - drafting
  - letter
  - litigation
---

# Discovery Dispute Resolution Letter

Drafts a court-ready letter that documents meet-and-confer efforts, memorializes agreements, and builds the record for potential motions to compel.

## Required Inputs

1. **Case info** — caption, court, case number, judge, discovery deadline
2. **Conference details** — date, participants, outcomes (if conference held)
3. **Disputed requests** — exact request language, objections raised, compromises discussed
4. **Scheduling order** — discovery cut-off, motion deadlines

## Letter Structure

**Header:** Date, opposing counsel address, Re line with full caption, case number, client name, matter number, discovery cut-off date. Include "Via Email" with address.

**Body sections in order:**

1. **Opening** — Reference conference date/participants, acknowledge agreements, identify remaining disputes. Note motion practice may follow.
2. **Agreements Reached** — Numbered list of compromises with compliance deadlines. Request written confirmation.
3. **Outstanding Disputes** — Organized by discovery method (RFPs, interrogatories, depositions). Use the per-dispute format below.
4. **Deadlines** — Specific response date tied to court schedule. State motion to compel and sanctions consequences.
5. **Closing** — Invite further discussion, propose specific follow-up date/time. Include preservation reminder.
6. **Signature Block** — Name, title, contact info, cc list, attachments (original requests, conference notes, scheduling order).

## Per-Dispute Format

Each disputed item must include all four elements:

1. **Exact Request Language** — quote verbatim as served
2. **Opposing Objection** — quote verbatim
3. **Why Objection Lacks Merit** — cite applicable rules and authority
4. **Proposed Compromise** — narrowed alternative demonstrating reasonableness

## Letter Type Variations

- **Pre-conference agenda** — collaborative tone; outlines issues for conferral; sent before meet-and-confer
- **Post-conference follow-up** — precise, collaborative; memorializes agreements, narrows disputes; sent within 24–48 hours
- **Pre-motion to compel** — firm, formal; final attempt before court involvement; allow response time before filing deadline

## Guidelines

- **Write for the judge** — every sentence may become a motion exhibit; make the client look reasonable
- **Quote exactly** — requests and objections must be verbatim as served
- **Characterize fairly** — describe opposing responses accurately even when inadequate
- **Cite authority** — FRCP 26(b)(1) (proportionality), FRCP 30(a)(1) (depositions), FRCP 33(d) (interrogatories), plus local rules
- **Demonstrate good faith** — show willingness to compromise on scope, timing, or format
- **Pin down follow-up** — always propose a specific callback date/time to prevent indefinite delay
- **Preservation language** — remind of ongoing duty to preserve documents and ESI

## Court-Specific Notes

- **Federal** — Rule 26(f) meet-and-confer required; Rule 26(b)(1) proportionality; magistrate referral; CMO deadlines
- **State** — verify local meet-and-confer requirements; check objection standards and discovery cut-off calculations
- **Complex commercial** — address e-discovery protocols, protective orders, voluminous production, privilege log disputes

## Checklist

- Local meet-and-confer rules satisfied
- Reasonable response deadline provided
- All disputed items identified with exact request language
- Good faith compromise demonstrated for each dispute
- Legal authority cited for contested positions
- Firm but professional tone throughout
- Preservation language included
- Letter is court-exhibit ready

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.