A key custodian’s mailbox is collected, processed, reviewed, and ready to produce. Another custodian’s phone data is still being preserved, and a third-party subpoena response will not arrive for weeks. What is rolling production in that situation? It is the controlled delivery of discovery materials in successive batches rather than one complete, final production.
For litigation teams, rolling production is often the practical answer to compressed schedules, large data volumes, expanding custodian lists, and continuing collections. It can move a matter forward without waiting for every source, but only when the production process is documented, quality-controlled, and aligned with the governing discovery agreement or court order.
What Is Rolling Production in Discovery?
Rolling production, also called a rolling document production, is the staged release of responsive documents and electronically stored information over an agreed period. Instead of producing all responsive materials on a single date, a party produces defined batches as review and quality control are completed.
A rolling production may be organized by custodian, data source, date range, issue, document family, or collection phase. For example, a party may first produce reviewed email from priority custodians, followed by shared-drive documents, mobile-device data, and later-acquired third-party records. Each delivery should be traceable as a separate production volume while remaining consistent with the broader discovery protocol.
The concept sounds straightforward. The execution is not. Each batch can affect deposition preparation, motion practice, expert work, privilege analysis, and the opposing party’s review schedule. A rolling approach does not lower the standard for completeness or production quality. It changes the timing and sequencing of the work.
Why Legal Teams Use Rolling Productions
The primary benefit is speed. Waiting for every collection, processing job, and review decision to finish can delay the exchange of material that is already ready for production. In a matter with active depositions or a near-term case management deadline, that delay can create avoidable risk.
Rolling productions also allow counsel to prioritize the evidence most likely to matter early. Senior decision-maker communications, key contract files, board materials, incident-related messages, or documents tied to a dispositive issue may be moved through collection and review ahead of lower-priority sources.
This approach is particularly useful when data collection is ongoing. A forensic collection from iPhones, cloud accounts, email systems, or departed employees may require different preservation, extraction, and processing timelines. A phased production plan lets the producing party meet obligations on the material already under control while continuing to collect from more complex sources.
For receiving parties, rolling production can provide earlier visibility into the factual record. Counsel can begin issue coding, witness preparation, and deposition planning before the entire universe is available. That advantage is real, though it comes with a qualification: early documents may change the significance of later productions.
A Rolling Production Needs a Clear Protocol
The most effective rolling productions begin with an agreement about what will be produced, in what format, and on what schedule. The relevant requirements may appear in an ESI protocol, Rule 26(f) discussions, a stipulated order, written discovery responses, or correspondence between counsel.
At a minimum, the parties should address the production format, including image files or native files, searchable text, metadata fields, load files, attachments, and document-level confidentiality designations. They should also establish how Bates numbering will be applied. Every production batch must receive a unique, consecutive Bates range that avoids overlap and allows documents to be cited accurately later.
Timing deserves equal attention. A statement that documents will be produced “on a rolling basis” is often too vague by itself. A more workable arrangement identifies an initial production date, anticipated intervals for subsequent batches, and the categories of information expected in each phase. The schedule should be realistic enough to withstand collection complications, privilege review, and quality-control work.
Counsel should also define how corrections will be handled. If an image is incomplete, a document family is split, metadata is missing, or privileged material is inadvertently produced, the team needs a documented path for replacement, clawback, and notice. These are ordinary production issues, but they become harder to manage when multiple batches are moving at once.
The Operational Workflow Behind Each Batch
A defensible rolling production is not simply a folder of documents delivered every Friday. It is a repeatable workflow with consistent controls from collection through delivery.
First, the team identifies the batch scope. That may include particular custodians, repositories, date ranges, or prioritized search terms. Collection should preserve source data and chain-of-custody information, especially for mobile devices, email, and other sources where authenticity may later be contested.
Next, the collected data is processed and loaded for attorney review. Processing typically includes deduplication, text extraction, metadata normalization, file-type handling, and identification of potentially problematic items such as encrypted files, corrupt documents, or unsupported formats. In a RelativityOne-based review workflow, the review team can track batch status, coding progress, privilege decisions, and production sets in one controlled environment.
After responsiveness and privilege review, the documents require production quality control. That review should confirm that required fields are present, confidentiality markings are correct, family relationships are preserved, redactions are properly applied, and Bates labels are legible and consistent. Native-file productions require particular care because a native file, placeholder image, and metadata record must correspond correctly.
Finally, the production is exported, validated, and delivered with a transmittal that identifies the Bates range, volume name, document count, and any exceptions or technical notes. The producing party should retain a complete record of what was produced, when it was produced, and the specifications used to create it.
Common Risks and How to Control Them
The risk in rolling production is not that it occurs in batches. The risk is that batches become inconsistent, poorly tracked, or disconnected from the case schedule.
One recurring issue is duplication. The same document may appear in more than one batch when collections overlap or deduplication settings change. Sometimes duplicates are unavoidable, but the team should understand why they occurred and communicate material exceptions where appropriate.
Another issue is incomplete document families. Producing an email without its attachment, or a spreadsheet without the associated native file, can generate disputes and force costly rework. Family integrity should be tested before release, not after opposing counsel identifies the omission.
Privilege is a third pressure point. Fast-moving batches can create production risk if the privilege workflow is not calibrated for the volume and document types involved. Privilege logs, redaction standards, clawback provisions, and escalation procedures should be established before the first batch is due.
The fourth issue is case management. Depositions scheduled before later batches arrive may create fairness arguments or requests to reopen testimony. When possible, parties should align production phases with key litigation events and notify one another promptly if a material source will not meet the expected timetable.
When a Single Production May Be Better
Rolling production is not automatically the best approach. A single, complete production can be more efficient when the data set is limited, the review population is stable, and the case schedule allows adequate time for a full review. It reduces the administrative burden of multiple exports, transmittals, Bates ranges, and production logs.
A consolidated production may also be preferable where context is especially important. Producing an entire transactional file, investigation record, or defined custodian set together can make review easier for both sides. The decision depends on the volume, urgency, discovery obligations, available review resources, and the consequences of delaying high-value evidence.
Preparing Your Team for Rolling Production
Before committing to a schedule, legal teams should test whether their workflow can support it. That means confirming that collections are defensible, review capacity is available, production specifications are understood, and quality-control ownership is clear.
A practical readiness check includes four questions:
- Which custodians and sources must be produced first?
- What production format and metadata fields have the parties agreed to?
- Who approves responsiveness, privilege, redactions, and final quality control?
- How will each batch be logged, delivered, and reconciled against the overall production obligation?
For high-stakes matters, experienced litigation support can make the difference between a manageable rolling schedule and a series of preventable corrections. Concord Document Technologies supports end-to-end legal document and ESI workflows, from forensic data collection and scanning through attorney review, Bates labeling, and trial exhibit production.
A rolling production should give the case momentum without sacrificing accuracy. When the scope, timing, and controls are established early, each batch becomes more than a deadline response – it becomes a reliable part of the litigation record.
