There's a specific kind of quiet dread in a small PI office: the discovery stack. Interrogatories on the Hendricks file due Friday. Requests for production on two others, one already on its second extension. Your own outgoing discovery that should have been served a month ago on the case that needs it most. Each item is routine; the stack is the problem — because a solo attorney's discovery obligations scale with the caseload, and (as the caseload ceiling post in this series laid out) attorney hours don't.
Offices handle the stack one of two ways. Reactively: whatever is due next gets done next, extensions paper over the rest, and the practice lives in a permanent low-grade discovery emergency. Or systematically: with a triage discipline that decides — before the week starts — what gets answered first, what gets delegated, and what genuinely needs the attorney's hand. Here's the system I run when an office hands me its stack.
Step 1: Inventory before urgency
The reactive office's real problem isn't speed; it's visibility. Items surface when they're nearly due, which makes everything an emergency by definition. So triage starts with the unglamorous move: one inventory of every open discovery obligation across every file — incoming items with response dates, outgoing discovery owed, extensions in play and their history, and the depositions each item feeds.
This usually takes a few hours of file-by-file review, and it routinely surfaces two or three items nobody was tracking. That alone justifies the exercise: the most expensive discovery item is the one you learn about from a motion to compel. (This inventory is also, candidly, an ideal first engagement for contract support — it's systematic, self-contained, and produces immediate relief.)
Step 2: Sort by deadline and exposure
Pure deadline-sorting feels rigorous but misleads, because discovery items carry wildly different stakes. The sort that works runs two axes:
Deadline pressure — due date, minus realistic drafting time, minus your review time. An item due in ten days that needs client input is tighter than one due in five that doesn't.
Case exposure — what the item costs if handled badly. Interrogatory answers in the case headed for trial carry impeachment risk for years (more on that below). Boilerplate requests in the case that will settle at the demand stage carry almost none. The extension history matters here too: a second extension on the same item starts costing credibility with opposing counsel and, eventually, the court.
High-pressure/high-exposure items get the attorney's calendar this week. High-pressure/low-exposure items get drafted for fast review. Low-pressure/high-exposure items get scheduled — which is the step reactive offices skip, and the reason high-stakes answers end up drafted at midnight.
Step 3: Split every item into its two layers
Almost every discovery item is two jobs wearing one deadline.The operational insight that makes the system work
The assembly layer — 60–80% of the hours, fully delegable
Gathering the client's documents, pulling facts from the file, organizing records responsive to each request, building the draft response structure, tracking what's been produced before.
The judgment layer — yours, non-negotiably
Objections, privilege calls, strategic phrasing, the decision about what a verified answer commits your client to. That's the ethics line from the first post — discovery responses sit close to it precisely because answers bind clients.
The triage system makes the split explicit: every item arrives on your desk assembled — facts gathered, documents organized, draft structured, open questions flagged — so your hours go to the judgment layer only. The midnight problem isn't that attorneys answer discovery; it's that they spend midnight on the assembly layer.
One flag deserving its own mention: consistency checking. In a PI case, the client's story exists in many places — intake notes, recorded statements, deposition testimony, prior discovery, the medical chronology. Answers that drift across documents become impeachment material later (a cautionary tale that gets its own post in this series). Part of the assembly layer, done right, is reading the new draft against everything the client has already said and flagging every divergence for the attorney's attention. This is tedious, document-heavy, cross-referencing work — which is to say, exactly the work that slips when the attorney does everything personally, and exactly where support earns its rate.
Step 4: Keep the system fed
Triage that happens once is a cleanup; triage that happens weekly is a system. The maintenance rhythm is light: new items enter the inventory the day they're served (a two-minute habit), the two-axis sort gets refreshed weekly, and outgoing discovery gets calendared to case strategy — not to guilt. Offices that run this rhythm stop living in discovery emergencies not because the volume dropped, but because nothing surprises them anymore.
And that's the honest pitch for the whole discipline: discovery volume is a fact of PI practice, but discovery chaos is a choice of workflow. The stack doesn't need your weekends. It needs an inventory, a sort, a split — and someone to carry the assembly layer.
Discovery support
The inventory is an ideal first engagement: systematic, self-contained, immediate relief.
Contact →Educational content for legal professionals — not legal advice. All case examples fictional.