Meet-and-Confer Letter: Structure and Template
States the rules as of July 2026. This is a practical summary, not legal advice, and AsyncConfer is not a law firm. Rules, local rules and standing orders change — confirm against your court's current requirements before you rely on it.
A meet-and-confer letter has two audiences. The first is opposing counsel, who you are genuinely trying to get something from. The second is the judge who will read it as an exhibit if the first audience says no.
Most letters are written for the second and fail with both — they read as position-taking, they demand rather than propose, and they give the court no reason to think resolution was actually attempted. A letter that works on opposing counsel is also the one that reads best in an exhibit.
Structure
1. Identify the specific discovery at issue. By number. “Interrogatories 7, 9 and 14 and Requests for Production 22–31.” Not “your discovery responses.”
2. State the deficiency, concretely. What is missing, or what the objection fails to address. If the objection is boilerplate, say which part — an objection that a request is “overly broad and unduly burdensome” without explanation is worth naming as such.
3. Explain why you are entitled to it. Briefly. One or two sentences of relevance to a claim or defense and proportionality under Rule 26(b)(1). You are not briefing the motion here.
4. Propose something. This is the part that is usually missing, and it is the part courts look for. Offer the narrowing you would accept: a shorter date range, fewer custodians, a sample production first, search terms you would agree to, production in phases. A letter with a proposal in it is evidence of an effort to resolve. A letter with only a demand is evidence of a formality.
5. Give a real deadline. Long enough to be reasonable — a week is usually defensible, less if there is a genuine time constraint you can articulate.
6. Offer the conference. Propose two or three specific times. If your district requires a live conversation — and several do — this is not optional, and proposing times is what makes a later “they would not schedule it” credible.
7. Keep it civil. Judges read these. Contempt for opposing counsel reads badly on the page and never helps.
Template
Re: [Case name], No. [number] — Meet and Confer re [Plaintiff’s/Defendant’s] Responses to [Discovery Set]
Dear [Counsel],
I write regarding [Party]‘s responses, served [date], to [set]. This letter is sent pursuant to [Fed. R. Civ. P. 37(a)(1) / applicable local rule], and we hope to resolve these issues without involving the Court.
Requests for Production 22–31. [Party] objected that each request is “overly broad and unduly burdensome” and produced no documents. The objection does not identify what is burdensome, and the requests are limited to [subject], which goes directly to [claim/defense].
Proposal: We are prepared to limit these requests to the period [date] to [date] and to the following five custodians: [names]. We would also accept production in phases, beginning with [category].
Interrogatory 9. [Party] answered by reference to Rule 33(d) and identified [production] generally. The rule requires specification in sufficient detail to permit us to locate the responsive records. Please identify the documents by Bates range.
[Repeat for each item.]
Please let us know by [date] whether [Party] will supplement. I am available to confer by telephone on [date] at [time], [date] at [time], or [date] at [time], and will make other times work if none of these suit.
Regards, [Name]
Common mistakes
- One letter, thirty requests, no proposal. Reads as a prerequisite being checked off, and courts say so.
- Sending it after the motion is drafted. The timing is usually visible, and it undercuts the certification.
- Never descending to specifics. “Your responses are evasive and incomplete” is not a conferral.
- Treating silence as an impasse too quickly. Follow up once, in writing, before you file. It costs a week and it makes the certification substantially stronger.
- Losing the thread. Six letters, three calls and a chain of emails later, nobody can say cleanly which of the original items are still disputed — which is exactly what the certification has to state.
When the letter is the wrong instrument
A letter is a good tool for two or three items. It is a poor one for a conferral with twenty, because each round collapses everything into prose and the per-item state of play — proposed, countered, accepted, still open — has to be reconstructed by reading the whole chain in order.
That is the situation AsyncConfer is built for: the conferral runs item by item, each with its own proposal, response and timestamp, so what is agreed and what is deadlocked is always current rather than reconstructed. If it ends in a motion, the record exports as an attachment. If it doesn’t, you have a joint statement instead of a correspondence file.