Purpose of This Template
You've been ordered to meet and confer on ESI protocols. Your team has hired a litigation support specialist. You've run some AI searches. You think you're done.
You're not.
A recent federal court decision clarifies what "meet and confer to develop ESI protocols" actually means. It's not a single meeting followed by unilateral decisions. This template provides a structured framework for running a compliant ESI protocol development process when a court orders collaboration with opposing counsel and expert involvement.
Use this when you're under a court order to develop protocols for searching, extracting, and producing ESI from complex databases. It's built around the requirements courts actually enforce, not what vendors promise their tools can handle.
Prerequisites
Before you start this process, confirm you have:
- Court order language in hand. Read what the judge actually ordered. If it says "develop protocols," that means iterative collaboration, not a take-it-or-leave-it proposal.
- Access to your litigation support specialist. Not just for the kickoff meeting. Budget for ongoing involvement through protocol finalization.
- Technical access to the data systems in question. Your specialist needs to examine what can actually be extracted, not just what the system vendor claims.
- Authority to negotiate. The people at the table must be able to make decisions about methodology, not just report back for approval.
- Transparency mandate from leadership. You'll need to disclose technical limitations and workarounds. Get buy-in for that approach before you start.
The Protocol Development Framework
Phase 1: Initial Joint Session (Week 1)
Attendees: Both parties' counsel, both litigation support specialists
Agenda:
- Review court order requirements together
- Identify all data systems in scope
- Document known technical constraints
- Agree on next steps and timeline
Deliverable: Joint memo to the court confirming the process and participants
Phase 2: Technical Assessment (Weeks 2-3)
Your specialist's tasks:
- Access each database system
- Test what fields can be reliably searched
- Identify records that can't be processed by proposed tools
- Document file size limitations, format issues, and error rates
- Quantify any gaps (e.g., "8,140 records could not be reliably searched")
Critical: Share findings with opposing counsel before developing workarounds. Don't engineer solutions in isolation.
Phase 3: Methodology Development (Weeks 3-4)
Joint session with specialists present:
- Review technical assessment findings together
- Discuss each limitation identified
- Propose solutions collaboratively
- Document agreed methodology for each data source
- Address AI tool limitations explicitly
If your AI search tool fails on certain file types or sizes, you need a plan for those records. That plan requires input from opposing counsel, not just your vendor.
Phase 4: Protocol Documentation (Week 5)
Draft ESI protocol must include:
- Search methodology for each database
- Handling procedures for files that can't be processed by AI tools
- Quality control steps
- Production format specifications
- Timeline for extraction and production
- Role of specialists in ongoing issues
Both specialists review and sign off. Both parties' counsel approve.
Phase 5: Court Submission (Week 6)
Joint filing that includes:
- Agreed ESI protocol
- Technical assessment summary
- Explanation of any unresolved issues
- Proposed timeline for production
Customizing the Framework
If you're dealing with legacy systems: Add a Phase 1.5 for specialist-led system documentation. Your specialist may need to reverse-engineer how data is stored before you can propose search methods.
If AI tools are part of your approach: Build in explicit checkpoints. When the AI tool fails on a subset of records, stop and reconvene. Don't just exclude those records and move on.
If you're the producing party: Add transparency steps. Before each joint session, prepare a written summary of what you've learned, what worked, and what didn't. Share it 48 hours before the meeting.
If you're the requesting party: Bring your own technical questions. Don't just accept the producing party's assessment of what's "searchable." Your specialist should verify claims about technical limitations.
If the court ordered a neutral third-party expert: Modify Phase 1 to include expert selection. The neutral should be present for all subsequent phases and should have independent access to the data systems.
Validation Steps
Before you submit your protocol to the court, verify:
Specialist involvement is documented. Can you show that specialists participated in developing the methodology, not just the initial meeting? Do you have meeting notes, email threads, or technical memos that prove ongoing engagement?
Technical limitations are addressed, not hidden. If 8,140 records can't be searched reliably, does your protocol explain how those records will be handled? Have you agreed on that approach with opposing counsel?
AI is positioned as a tool, not a solution. Does your protocol explain what happens when AI fails? Is there a manual review process for records the AI can't handle?
Modifications are transparent. If you adjusted your approach after the initial meeting, did you document why and get input from the other side?
The court's specific language is covered. Go back to the order. Did the judge ask you to "develop protocols for downloading the information into usable formats"? Does your protocol actually address that?
Run this checklist with your litigation support specialist present. If they can't explain how a particular requirement was met, you're not done.
What this framework prevents: Unilateral protocol development. Ad-hoc modifications without consultation. Relying solely on AI when the court ordered collaborative methodology development. Limiting your specialist to a single meeting when ongoing technical issues require ongoing expertise.
What it requires: Time. Transparency. Willingness to share technical limitations before you've solved them. Budget for specialist involvement through completion, not just kickoff.
Courts are making clear that "meet and confer" means exactly that. Your AI tool can assist the process. It can't replace the collaboration the court ordered.
