Employment Litigation Discovery: Why Your Client's HR File Always Shows Up Incomplete
Employment plaintiff work has a particular pain point: the documents you need most are sitting in the personnel file of the company that just fired your client. Or they're in your client's personal email, mixed in with two years of unrelated correspondence. Or they were on a work laptop that got returned.
Whether you're litigating wrongful termination, Title VII discrimination, FLSA wage-and-hour, or ADA accommodation cases, the discovery production from your client is rarely complete on the first pass.
Here's why — and how to fix it.
The Three Document Streams in Employment Discovery
Every employment plaintiff's production requires three streams of documents:
- Personnel and HR documents — performance reviews, disciplinary actions, complaints, leave requests, accommodation requests, offer letter, job description, employee handbook.
- Communications — emails between your client and management/HR, especially around the alleged discriminatory or retaliatory acts. Often spans personal and work email accounts.
- Pay and compensation records — paystubs, W-2s, commission statements, bonus schedules, timekeeping records (especially in FLSA cases).
Each stream has a different access pattern. Personnel docs your client may have copies of, but probably not all of them. Communications may exist on systems they no longer have access to. Pay records they technically have but rarely organized.
Why Generic Portals Fail in Employment Cases
The PM-platform client portals (Clio, MyCase) treat document upload as a single bucket. Your client uploads what they have, in the order they think of it. Your paralegal then has to manually sort which document answers which RFP. That's hours per case.
Worse, when something's missing, the lawyer sends a generic "we still need more documents" email. The client doesn't know which specific documents. They send the same five they already sent.
The Better Workflow
1. Itemize the RFP into specific document tasks
A request like "Produce all documents reflecting communications between plaintiff and defendant's HR department regarding the alleged accommodation request" becomes a single task with a precise plain-English description and three suggested sources: personal Gmail, work email archive (if exported at termination), text messages with HR director.
2. Capture custody and control as structured data
Half of the documents your client doesn't physically possess. They're on a work email account they no longer have access to. Or they're in a manager's notes. Your discovery production should distinguish:
- I have it and will upload
- Defendant has it and I do not
- Third party has it (insurance, prior employer, doctor)
- Document does not exist
When your client picks "Defendant has it," you have an instant trigger to draft your own RFP to the defense and to lay the groundwork for a motion to compel if it isn't produced.
3. Bridge personal and work-email evidence
The single biggest gap in employment discovery is communications. Most plaintiffs forwarded the smoking-gun email to themselves before they got fired. Some didn't. Building a structured task — "Upload any emails between you and [HR director name] from [date range], from any email account you used" — surfaces evidence your client forgot they had.
4. Build the production package incrementally
In employment cases, the production happens over several weeks. Documents trickle in. The lawyer needs to know, in real time, what's complete and what's still outstanding without a paralegal manually running an Excel checklist.
A modern collection tool tracks each task's status (open / uploaded / explained / accepted) and computes a completion percentage. When you hit 95%, you know you're ready to certify.
DocuPrompt for Employment Plaintiff Firms
We've designed DocuPrompt to fit the rhythm of employment plaintiff work:
- RFP parser handles the common patterns (numbered, "REQUEST FOR PRODUCTION NO.", "Request No.")
- Plain-English translation of each request — your client knows what's actually being asked
- Structured "I don't have it" reasons — defendant has it, third party has it, does not exist, etc. — feed directly into your motion-to-compel strategy
- AI-personalized reminders that name specific missing items, sent automatically until your client uploads or explains
- Markdown status export ready to attach to a discovery conference statement
We're not a Filevine competitor. We're not trying to replace your case management. We're the layer between you and the client that turns 6 hours of email reminders per case into 30 minutes of supervised review.
"The structured 'reason missing' field is what I didn't know I needed. I get four 'defendant has it' answers per case, which is exactly the motion to compel I was already going to file — but now with documentation."
— Plaintiff employment attorney, San Diego
Start your free 14-day trial → — no credit card.
See it in action — free for 14 days
No credit card. Setup in 5 minutes. Send your first client portal link the same day.
Start free trial →Why Your Family Law Clients Never Send Their Bank Statements (And How To Get Them To)
Divorce clients aren't lazy — they're overwhelmed. Here's why your discovery responses keep going out half-empty, and a 5-step framework to fix it.
The Personal Injury Discovery Tax: How Many Hours Are You Wasting Per Case Chasing Medical Records?
Personal injury attorneys lose 6–12 hours per case to medical record collection. Here's why the chase is broken — and what to do instead.