WorkflowInvestigations & White Collar

Civil Investigative Demand Response

Civil investigative demand response that keeps each specification worked as currently agreed, letter by letter, through rolling productions to the sworn certificate of compliance.

Watch it work Book a walkthrough

Open the lanes, the letters and the productions ↓

Watch with transcript →

The problem

A narrowing agreed in a letter reaches the review team a week later

The demand arrives with dozens of numbered specifications, pages of definitions and a return date. Over the following weeks the partner negotiates it down in calls and letters: a shorter date range, fewer custodians, a set of call recordings in place of all of them. After each letter, what the team should collect, review and produce is different.

The tracker is a spreadsheet the associate rebuilds at the weekly status call from the letters and the vendor's production log. Until then, the team collects and reviews for a scope that no longer exists.

At the end, an officer of the client swears that everything required was produced. If one production went out under an old scope, or a narrowed specification was never fully answered, that certificate is wrong under oath. A missed return date can cost the cooperation credit too.

Built forEnforcement partnersInvestigations associateseDiscovery managersCompliance officers

The Problem Today

Each meet-and-confer letter changes the scope, while the team keeps working the demand as it was served.

$2.92B: recovered in false-claims cases in fiscal year 2024 published
979: whistleblower suits filed in fiscal year 2024, a record published

Rebuilt from these each week

Letters
Custodians
Bates log
Answers

Narrowings land a week lateThe tracker catches up at the weekly status call
Cover letters typed from Bates rangesAssociate hours each week go on the tracker and the letters

The Solution

Demand split into lanesDocuments, written questions, data and testimony, each cited to its page
Letters tied to their lanesEach agreed narrowing updates the scope, custodians and dates it touches
Productions checked to scopeBates ranges mapped; documents outside the agreed period held back
Certificate, swornEach specification listed as agreed, for an officer to swear

Built-in controls

Only agreed letters change a lane
A narrowing leaves each legal hold in place
The partner signs each letter to the government

What You Get

Each specification is answered as agreed, so the sworn certificate matches what actually went out.

≈1 h: a week of associate time on tracker and letters, from about 6 our estimate

A Bates map for each productionEach range tied to the specification it answers
A source behind each answerWritten answers ready for the client's officer to swear
Review spent only on live scopeReleased custodians and old dates drop out the same day

Nine screens, nine jobs

How a civil investigative demand is worked lane by lane, as agreed

Nine screens, set out as a response unfolds: what each handles, how, and which role it serves.

01Lanes
Every specification on its own lane, on one timeline of the response
How it works
- 34 specifications in four bands: documents, written questions, data and testimony
- Each lane shows its agreed scope, custodians, review and production marker
- A tag on the lane names each letter that changed it
- Today's line at day 64 of 90, with the four productions drawn as vertical lines
Senior associateReplaces the tracker rebuilt every week from six letters and a vendor spreadsheet, so each day's work starts from the scope as it stands.
02Specifications
The demand read into specifications, definitions and instructions
How it works
- Splits the 14-page demand into 34 specifications, 11 definitions and 9 instructions
- Cites each specification to its page, served text struck through where a letter changed it
- Flags definitions that read two ways and keeps them open until answered
- Lists the instructions that bind: format, privilege log timing, certificate and petition window
Senior associateEnds the first week spent building a specification chart by hand, and keeps each unclear definition on the record until the government answers it.
03Negotiation
Each meet-and-confer letter read clause by clause and tied to its lanes
How it works
- Letters from both sides in order, each marked agreed or proposed by the firm
- Agreed clauses highlighted in the letter, each linked to the lane it changes
- Each change shown before and after, cited to its paragraph
- A proposal of the firm's own stays visible and moves no lane
Enforcement partnerGets what she agreed on the call into the team's hands the day the government's letter confirms it, without waiting for the status meeting.
04Approve a narrowing
A narrowing waits for the associate's approval before any lane moves
How it works
- Each change shown as it stands and as agreed, with its source paragraph
- Review population falls from 41,800 to 23,600 documents; custodians from 6 to 4
- 312 documents already coded responsive fall out of period and are held back
- Approve, reject with a reason for the partner, or leave it for now
Senior associateApplies the letter the day after it arrives, seeing exactly what moves before anything does.
05Lane 7, narrowed
An approved narrowing redraws the lane's scope, custodians and production
How it works
- Lane 7's scope bar shrinks to the period the letter agreed
- Two custodians whose roles on that work ended drop off the lane
- The production marker moves from Production 4 to Production 3
- The count of narrowings applied now reads 3 of 3
eDiscovery project managerKnows which custodians and which dates are live as of today, so collection and review stop for a scope that has gone.
06Custodians
A custodian grid that shows who each narrowing releases, with holds kept
How it works
- 22 custodians against 34 specifications, with hold date, sources and data gathered
- 21 of 22 holds acknowledged, with a reminder ready for the one outstanding
- The two released from request 7 stay grayed on that lane, holds kept
eDiscovery project managerSees who is in scope for what without a second spreadsheet, and can show that no narrowing quietly dropped a legal hold.
07Productions
Each rolling production checked document by document against the agreed scope
How it works
- 19,800 documents compared with each specification as agreed
- 312 documents from outside the agreed period held back and logged, not deleted
- 3,076 documents for request 12 go as served, since the firm's proposal was not agreed
- Consumer numbers masked in 37 documents
eDiscovery project managerReleases a production knowing nothing outside the agreed scope is in it, with the Bates map already built for the cover letter.
08Written answers
Written answers to interrogatories with a source on each sentence
How it works
- Interrogatories 15–26 in one list: 9 of 12 drafted, 3 waiting on data
- Each answer opens with its objection, then numbered sentences, each cited
- An answer still waiting on data stays empty until the data arrives
- The sources counted: 19 produced documents and 6 privileged interview memos
Chief compliance officerSwears to answers she can trace sentence by sentence, instead of taking the drafting team's word for where each one came from.
09Certificate
A certificate of compliance built from the lanes, one specification a line
How it works
- Each specification shows the letter that modified it and how it was satisfied
- 11 of 34 satisfied today; the rest carry their dates
- Attaches the Bates map, the privilege log of 412 and the letters
- Drafted now, sworn only when all 34 are satisfied
Enforcement partnerSends the certificate with the final production knowing each line was answered under the scope in force.

Three letters from the government, and one proposal it never answered

The narrowings behind the lanes in this response, and the one change that stays off them.

Letter	What it agreed	Lanes it changes
N1, after the first call	Dialer records limited to a set window; 400 call recordings chosen from a list; four rolling productions in place of one return date	28, 29 and the dates
N2	Contracts with the 10 largest debt owners only; complaints limited to those logged; custodians fixed at 22 where the government proposed 31	5, 10 and the custodians
N3	Item 7 of the demand limited to a shorter document period, and moved up a week into Production 3	7
The firm's own proposal	Item 12 of the demand limited to later pay plans; no answer yet	None: Lane 12 stays as served

Around the response

Letters, oath and audit trail around one civil investigative demand

What the partner signs, the officer swears and the team checks between productions.

Lane 7 card: served text struck through, agreed text cited to its letter, review population 23,600 and two custodians released with holds kept — **One lane, opened**The served text struck through, the agreed text in its place with its paragraph cited, and a review population of 23,600 with 6,900 expected to produce.

Confirming letter drafted from the government's letter and the lane changes, with a button to send it to the enforcement partner to sign — **A confirming letter, drafted**Drafted from the government's letter and the lane changes, pressing the open proposal and an unclear definition, for the partner to sign.

Production 3 cover letter with its confidential-treatment request, beside the Bates ranges by specification and the completed scope check — **Cover letter for Production 3**Bates range, specifications as modified and the confidential-treatment request in one draft. The project manager releases the production; the partner signs the letter.

Send for verification: the drafted answers and the oath the client's chief compliance officer reads before she swears them — **Sent for the officer's oath**The associate sends the drafted answers to the client's officer, who alone can verify them. Answers waiting on data follow once drafted.

Audit record of the response: the parser's re-read, letters received, the narrowing approved and applied, the scope check and the certificate drafted — **Agents and people on one audit record**Each letter received, each narrowing approved and applied, each check run and each production released, by agent or by person.

Settings for roles and separation of duties, what counts as agreed, deadline alerts at 10, 5 and 2 business days, holds and retention — **Separation of duties, set once**Whoever agreed a narrowing cannot apply it, and whoever releases a production cannot sign its letter. Call notes count as no agreement at all.

Six agents prepare the drafts; people agree, release and swear

Each agent prepares one part of the work. Every change, release and signature stays with a named person.

Specification parser

Splits the demand into specifications, definitions and instructions, groups them into lanes and cites each to its page.

Never decides what is responsive
Never narrows a specification

Scope tracker

Reads each meet-and-confer letter and email, pulls out each agreed change and proposes it on the lane it changes, with the clause cited.

Never applies a change without the associate
Never treats the firm's own proposal as agreed

Custodian mapper

Keeps each lane's custodians, holds, sources and collection current, and shows who a narrowing releases.

Never releases a legal hold

Production mapper

Maps each Bates range to the specifications it answers, checks each document against the scope as agreed and holds back what falls outside.

Never produces anything: the project manager releases each production

Answer drafter

Drafts the written answers and objections from the produced documents and interview notes, with a citation on each sentence.

Never verifies an answer: a client officer swears it

Letter drafter

Drafts production cover letters, confidential-treatment requests, confirming letters and the certificate of compliance.

Never sends anything: the partner signs each letter

Four decisions on a civil investigative demand that no agent makes

Each sits with a named role, set in the settings and kept on the audit record.

Agreeing scope with the governmentThe enforcement partner agrees each narrowing and signs each letter. Agents never contact the government.

Applying a change to a laneThe senior associate approves it, and only from a letter or email that counts as agreed. Call notes never count.

Releasing a productionThe eDiscovery project manager releases each one, and cannot sign its own cover letter.

Swearing the answers and the certificateAn officer of the client verifies both under oath, after reading the sources behind each sentence.

Questions from counsel answering a government demand

What is civil investigative demand response?

Civil investigative demand response is answering a government demand for documents, written answers, data and testimony, under a scope negotiated down over weeks. This solution splits the demand into lanes, ties each agreed narrowing to the lanes it changes, checks each production against the agreed scope, and drafts the answers, cover letters and certificate for people to sign.

Can the scope of a CID be negotiated, and how does the team keep up?

Scope is usually narrowed in meet-and-confer calls and letters. The solution reads each letter, proposes each agreed change on its lane for the associate to approve, and keeps the firm's own proposals off the lanes until the government agrees in writing.

What happens to documents already reviewed when a period is narrowed?

Documents already coded responsive but dated outside the agreed period are held back from the next production and logged, never deleted. The scope check lists them before the project manager releases the production.

Does a narrowing release a custodian's legal hold?

No. A narrowing can take a custodian off a lane, and the custodian grid shows it, but the hold stays in place. Releasing a hold needs the partner and the client's general counsel.

How is the certificate of compliance built?

From the lanes. Each specification lists the letter that modified it and how it was satisfied: produced with its Bates range, answered under oath, or given as testimony. It can be drafted early, and it is sworn only when each specification is satisfied.

Does it work for a government subpoena as well as a CID?

Yes. The same lanes, letters and production checks apply, and settings decide which letters count as agreed and when deadline alerts fire.

How are client and consumer records protected?

Consumer account and identity numbers are masked in each output, and each production carries a confidential-treatment request. The response file stays inside the firm, no model learns from it, and the audit record logs each read, change and signature.

Investigations & White Collar

See your last demand's scope
as each letter changed it.

Send us a demand you have closed, with its meet-and-confer letters, and we will show each lane as it stood the day each letter arrived.

Book a walkthrough Browse solutions

Civil Investigative Demand Response

A narrowing agreed in a letter reaches the review team a week later

The Problem Today

The Solution

What You Get

How a civil investigative demand is worked lane by lane, as agreed

Every specification on its own lane, on one timeline of the response

The demand read into specifications, definitions and instructions

Each meet-and-confer letter read clause by clause and tied to its lanes

A narrowing waits for the associate's approval before any lane moves

An approved narrowing redraws the lane's scope, custodians and production

A custodian grid that shows who each narrowing releases, with holds kept

Each rolling production checked document by document against the agreed scope

Written answers to interrogatories with a source on each sentence

A certificate of compliance built from the lanes, one specification a line