Insights Articles

When a Second Request arrives, organizations often focus on the most visible challenge ahead: reviewing large volumes of data under tight deadlines.

But experienced response teams know that successful outcomes are rarely determined during review alone. The most consequential choices are often made before review begins.

Long before the first document is assessed for responsiveness, critical decisions are made around scope, custodians, data sources, collection requirements, and production obligations. These early choices shape every stage of the response, including timelines, costs, defensibility, and the organization’s ability to meet regulatory expectations.

When responding to a Second Request, success often depends on one thing: establishing a clear, defensible plan before collection and review begin.

Why Second Requests Are Different

Unlike many litigation matters, Second Requests come with expansive information demands, compressed timelines, and highly specific production requirements.

Organizations may need to identify and preserve information across numerous custodians, business units, systems, and communication channels while coordinating efforts among legal, IT, forensics, review teams, and outside counsel.

The challenge is not simply collecting more data. It is understanding what must be collected, where it resides, and how response decisions will affect downstream workflows.

Without a clear strategy, teams can quickly find themselves managing unnecessary data volumes, duplicative work, collection gaps, and avoidable production risks.

Start by Reading the Request Strategically

One of the most important early steps is thoroughly analyzing the request itself.

Beyond identifying key deadlines, response teams should carefully evaluate:

• Scope and definitions
• Custodian requirements
• Requested data sources
• Production specifications
• Assumptions that may affect collection or review workflows
• Areas that may require clarification or negotiation
  
  

A Second Request should not be viewed simply as a checklist of collection tasks. It is a roadmap that drives every subsequent workstream.

Understanding the request at the outset allows teams to identify potential challenges before they become costly operational problems.

Identify Areas for Early Negotiation

Not every requested requirement can or should be accepted without discussion.

Production specifications, data source availability, collection limitations, and technical constraints can all create practical challenges. The most effective response teams identify these issues early and raise them before significant work begins.

Waiting until processing, review, or production to address known obstacles often creates unnecessary delays, rework, and increased costs.

Early communication allows legal teams to document proposed modifications, seek clarification where needed, and reduce the likelihood of downstream disputes.

Custodian Strategy Is a Critical Early Decision

Few decisions have a greater impact on a Second Request than custodian selection.

Custodian choices directly affect:

• Collection volumes
• Processing costs
• Review scope
• Production timelines
• Overall defensibility

The goal is not simply to identify more custodians. It is to identify the right custodians based on their involvement, responsibilities, and likely possession of responsive information.  

This requires close collaboration between counsel, business stakeholders, and technical teams to understand organizational structure, decision-making processes, communication patterns, and data locations.

A thoughtful custodian strategy helps ensure collections remain targeted, defensible, and aligned with the objectives of the request.

Map the Data Before Collection Begins

Custodian identification is only part of the scoping exercise. Modern business communications may reside across email, network shares, cloud collaboration platforms, mobile devices, structured databases, and enterprise applications. Understanding where relevant information resides is often as important as identifying who possesses it.

An early data-mapping exercise can connect custodians and business processes to the systems that contain potentially responsive information. It can also help teams identify system owners, retention considerations, access limitations, overlapping repositories, and appropriate collection methods before those issues disrupt later work.

This broader view helps reduce collection gaps and duplication while giving review and production teams a more reliable understanding of the data they will receive.

Document the Decisions That Define Scope

Defensibility depends not only on the decisions a response team makes, but also on its ability to explain how and why those decisions were made. Teams should maintain a contemporaneous record of significant scoping choices, including custodian selections, data-source inclusions or exclusions, collection approaches, testing results, and negotiated protocol adjustments. 

That decision history provides continuity as personnel and priorities change. It also gives counsel a clear record to consult if questions later arise regarding the reasonableness, completeness, or consistency of the response.

Build a Response Plan Before You Build a Review Workflow

One of the most common mistakes in large regulatory matters is rushing into collection activity without first creating an operational framework.

Before significant collections begin, response teams should establish a centralized process for tracking:

• Custodians
• Data sources
• Collection status
• Key dates
• Search-term activity
• Follow-up actions
• Dependencies between workstreams

Maintaining a single source of truth helps teams stay aligned as the matter evolves and new information emerges.

As additional custodians, repositories, or responsive datasets are identified, the response plan can be updated without losing visibility into the overall process.

Treat Scope as a Controlled, Iterative Process

Second Request scope rarely remains static. Interviews, collections, search-term testing, and early review may reveal additional custodians, repositories, aliases, or business processes that warrant further investigation.

A defined governance process allows the team to evaluate those developments consistently. Each proposed change can be assessed for legal relevance, technical feasibility, cost, timing, and downstream impact, then documented and incorporated into the overall plan. The plan needs to remain flexible as changes to scope can change review strategy that may require re-negotiation with the regulatory bodies that issued the request. The objective is not to prevent scope from changing, but to ensure that it changes deliberately and transparently with enough time to pivot to an alternate plan if constraints demand it.  

The Most Important Work Often Happens Before Review

Technology-assisted review, quality control, and production management all play important roles in a successful Second Request response.

But those activities depend on the quality of decisions made much earlier.

A well-defined scope, informed custodian strategy, data map, documented decision history, and centralized response plan create the foundation for efficient collections, defensible review workflows, and successful productions.

Before collecting millions of documents, organizations should take the time to answer the following critical questions:

1. What exactly are we required to produce?
2. Where does the responsive information reside?
3.  How should we approach review, technology and production specifications as each of these may require negotiation and sign-off with the regulatory bodies?
4. How will we demonstrate that our response is reasonable, defensible, and complete?

Organizations that invest in scoping, data mapping, and response planning at the outset are better positioned to manage cost, maintain momentum, and support a defensible response. In many matters, the success of a Second Request is determined long before the first document reaches a reviewer.

Navigating a Second Request?

Array's experts help organizations manage complex Second Request and SIR responses, from early scoping and data identification through collection, review, quality control, and production. Contact our team to discuss your matter and explore strategies for building a more efficient, coordinated, and defensible response.