The Comprehensive Guide to Second Requests
Veterans of the Hart-Scott-Rodino (HSR) Act Second Request practice know the demands well. Parties to a pending merger often have hundreds of millions or billions of dollars at stake and a closing schedule that drives every decision. The government files a broad request for additional information to complete its antitrust analysis. The parties race the calendar while simultaneously negotiating scope and compliance dates with the reviewing agency.
Top antitrust lawyers understand – patiently or otherwise – that ediscovery takes time. But as data volumes grow, government requests broaden, and deal value accumulates by the day, those same lawyers have every right to ask: is there a better way? The answer, increasingly, is yes.
Modern technology has fundamentally changed what is operationally possible in a Second Request response – compressing timelines that once took weeks into days and giving legal teams analytical capabilities that simply did not exist a decade ago.
Hold, Collection, Uploading, and Processing
Gone are the days of sequencing a response to a Second Request as a linear series of steps – hold, then collect, then process, then review. That waterfall model was a product of legacy technology constraints, not of legal necessity, and it cost responding parties weeks they could not easily afford to lose.
Modern cloud-to-cloud connectors into Microsoft 365 and Google Workspace can ingest, process, index, and make data available for review at volumes of many terabytes per day. Collection can include hyperlinked content from M365 and Google email stores, collaboration tools, and file storage. Critically, a legal hold can be placed on an entire collection simultaneously, and the team can begin analysis and review of priority custodians – and negotiate scope – while additional data continues to upload and process in parallel.
The result is a compression of the early-stage timeline that prior-generation workflows could not achieve. While data continues to flow into the platform, the review team is already working. While negotiations of scope are ongoing, the ediscovery team is modeling the data. The old constraint of having to wait for loading and processing before being able to do anything is over.
Issue Spotting
Document discovery and AI-powered analysis tools like EverlawAI Deep Dive allow counsel to ask questions of the data in natural language and surface responsive documents, themes, and narratives without waiting for a full linear review pass. A reviewer can prompt the system with a specific antitrust issue – pricing coordination, market allocation, competitive response strategy – and receive a ranked set of documents and synthesized context within seconds.
This capability is particularly valuable for short-form communications, which are among the most consequential and most difficult document types in Second Request practice. Slack messages, Teams chats, and text threads are frequently informal, context-dependent, and stripped of the structural cues that make email easier to classify. AI tools trained to find meaning in short messages – identifying the competitive significance of a brief exchange that a first-pass reviewer might miss – directly address one of the most persistent landmines in antitrust document review.
Analysis and Negotiation of Scope
Negotiation of scope in a Second Request has historically been an exercise in estimation fraught with risk. Counsel would propose custodian lists and date ranges based on organizational knowledge and experience, and both sides would negotiate largely in the dark about the actual data burden implications of their positions. Modern ediscovery platforms have changed this dynamic fundamentally.
Data visualizations and search term reports (STRs) allow counsel to model scope changes and see the resulting impact on review burden in real time – within seconds of adjusting a parameter. The practical consequence is a shift in how scope conversations happen. Rather than an exchange of proposals followed by a days-long wait for the ediscovery team to run searches and estimates, counsel can respond to a government ask in the room: “You want to add these eight custodians for all five years and limit these twenty to email and chat for the same period? Give me sixty seconds.” That capability reshapes the negotiating dynamic in favor of the party that has built the infrastructure to use it.
Granular STRs showing document hit counts, exclusive hits, and family hits by custodian and date range allow parties to make evidence-based tiering proposals rather than position-based ones – and to counter government scope expansion requests with concrete burden data rather than generalized objection. Data visualizations surface communication patterns and relationship clusters that inform both custodian identification and privilege review strategy.
Speed to Production
Modern ediscovery platforms have eliminated several of the most time-consuming steps in the production workflow. There is no longer a need to separately download, encrypt, and physically ship production media. Productions can be transmitted directly through the platform using the same secure infrastructure that regulators already use, delivering the production set instantly and generating a verified transmission log at the moment of delivery. The government has the production; the party has an auditable record of exactly what was sent and when.
This shift is not merely a matter of convenience. Rolling productions are a standard feature of Second Request practice, and each production cycle under a legacy workflow consumes time that accumulated across a multi-week response. Eliminating the manual steps from each cycle compresses the overall timeline meaningfully.
Transparency
As AI-assisted review becomes standard practice in Second Request responses, the defensibility of that review – and the legal team’s ability to explain and document it – has become both an internal quality imperative and a potential subject of regulatory inquiry. The question of how good an AI first-pass review is should have a precise, documented answer, not an approximation.
Running EverlawAI Coding Suggestions alongside a simultaneous predictive coding (TAR) model for each coding category gives legal teams exactly that level of transparency. A separate PC-TAR model running in the background for each issue tracks precision and recall in real time, every day, giving counsel a current and specific view of where the review stands – not just overall, but on each substantive coding category. Selecting to the left of the F1 score surfaces a statistically valid sample for defensibility documentation. If the government inquires about the quality of the AI-assisted review process, the answer is not an estimate; it is a number with documentation to support it.
Speed of Review
Everlaw has been deployed on some of the largest ediscovery matters in history, including on major antitrust matters. Platform performance at scale is a material operational variable, and Everlaw’s cloud-native architecture is built to maintain speed and stability as data volumes grow – not to degrade.
“Everlaw is able to navigate the changes and demands of a Second Request seamlessly due to its unique admin tools,” Anna-Maria Licata Coombs, Regional Director at Beacon Hill Legal, said. “It allows for quick reassessment and workflow strategies that can be adjusted multiple times a day, which is a feat other tools are not able to easily handle. Everlaw offers the ability to quickly shift teams and meet the ever-changing needs of a Second Request matter.”
The compounding effect of AI-assisted first pass Coding Suggestions and platform speed across a multi-week, multi-custodian, rolling production response is significant. Every hour saved multiplied across a distributed review team over a four- to six-week production cycle produces a measurable compression of the overall response timeline and a corresponding reduction in review cost.
Compliance Standards
Certification of substantial compliance is not the end of the government’s engagement with the production. Once the agency has what was promised, it routinely surfaces follow-up questions – inquiries about specific documents, custodians, or gaps in the record that require a prompt and well-documented response.
Everlaw’s AI tools allow counsel to respond to these inquiries using the same natural language prompting capability applied during initial review – surfacing responsive documents and synthesized context quickly without requiring a separate review workflow. For more complex follow-up inquiries involving multiple documents, custodians, or themes, Everlaw’s Storybuilder allows the team to assemble dossiers organized by hot topic, pulling together the relevant record into a coherent narrative that supports both the response to the government and the ongoing internal case assessment. The infrastructure built to respond to the Second Request continues to deliver value through the certification and follow-up phase – and, if the matter proceeds to litigation, beyond it.
When the Federal Trade Commission (FTC) or Department of Justice (DOJ) issues a Second Request in connection with a pending merger, the transaction’s waiting period is tolled. Compliance is not optional, and delay carries real cost: strained deal financing, signals of unreadiness to regulators, and the prospect of a collapsed transaction worth hundreds of millions or billions of dollars make speed and precision the defining imperatives. HSR Second Requests sit at the intersection of antitrust law, corporate strategy, and ediscovery operations, demanding a level of coordination, rigor, and technical capability that exceeds nearly any other document production context. This guide addresses the legal framework, operational challenges, technology infrastructure, and best practices that legal teams must command to respond effectively.
What Is the HSR Act?
The HSR Antitrust Improvements Act of 1976 requires parties to a proposed transaction to file premerger notifications when the deal exceeds certain size thresholds established by the FTC. The FTC’s Bureau of Competition and the DOJ’s Antitrust Division share jurisdiction over HSR filings, with one agency taking the investigative lead on each matter based on industry expertise and internal clearance protocols. Their review is designed to determine whether the proposed transaction would substantially lessen competition or tend to create a monopoly under Section 7 of the Clayton Act.
Most filings are cleared within the initial 30-day waiting period. When an agency determines that a transaction warrants closer scrutiny, it issues a Second Request – a formal demand for documents, data, and written narrative responses that tolls the waiting period until the parties certify substantial compliance. The filing parties cannot close until the agency either clears the deal or files suit to block it.
Over the past two decades, the FTC and DOJ have together issued between 30 and 70 Second Requests annually, representing roughly 2 to 5 percent of all qualifying large transactions. While these figures represent only a fraction of the estimated 15,000 to 20,000 mergers occurring in the United States each year, the operational significance is considerable. At an average cadence of roughly one Second Request every one to two weeks, and with the implicated transactions routinely carrying deal values in the hundreds of millions to billions of dollars, Am Law firms, economic consulting practices, and ediscovery service providers must maintain standing capacity to mobilize quickly and at scale when a Second Request arrives.
What Is the Role of Ediscovery in a Second Request?
A Second Request is, at its core, a massive and time-pressured document production that unfolds in an adversarial but negotiated environment. The responding parties must identify custodians, preserve ESI under legal hold, collect and process data across multiple platforms and geographies, review for responsiveness and privilege, and produce to the government on a rolling basis – often while simultaneously negotiating the scope of what must be produced. These requests routinely implicate terabytes of data spanning email, enterprise messaging platforms, financial models, board and investor presentations, strategic planning documents, and marketing materials.
The legal and practical dynamics are distinctive. The government has an interest in receiving sufficient information to make a sound antitrust determination within a defensible timeline; once the parties certify substantial compliance, the agency has thirty days either to challenge the deal or to allow it to proceed. The merging parties have an interest in limiting scope, controlling cost, and moving toward closing as quickly as possible. These competing interests are reconciled through ongoing negotiation over custodians, date ranges, search parameters, and data types – often while production is already underway. Parties routinely begin review and rolling productions before scope is fully settled, accepting some uncertainty to demonstrate good-faith progress toward compliance.
Efficient, defensible ediscovery is not merely a compliance function in this context – it is a strategic asset. The quality of a party’s ediscovery infrastructure directly affects its ability to negotiate scope credibly, meet rolling production deadlines, and certify substantial compliance on a timeline that protects deal value and keeps financing in place.
What Are the Challenges of Second Requests?
Responding to a Second Request demands simultaneous performance across three dimensions that are each difficult to manage independently: speed, accuracy, and negotiating agility.
Legal teams must identify custodians, issue and track legal holds, collect and process data across distributed environments, and produce responsive documents – all while maintaining a defensible record and managing an ongoing dialogue with the reviewing agency about scope. Delays or deficiencies do not merely slow compliance; they signal bad faith to regulators and, in serious cases, can provide grounds for a legal challenge to the proposed merger.
The merging parties accordingly begin review and rolling productions even while scope negotiations remain open, accepting operational complexity in exchange for demonstrable forward progress.
Large Data Volumes and Moving Targets
The volume of data implicated by a Second Request is rarely static. Initial estimates expand as custodian lists grow, date ranges shift, and the government requests additional categories of information. Second Request responses routinely involve millions of documents spanning enterprise email, collaboration platforms such as Slack and Microsoft Teams, spreadsheets and financial models, board and investor presentations, competitive intelligence files, and audio or video recordings of internal meetings. Each data type presents distinct collection, processing, and review challenges that must be anticipated in the project plan.
Scope negotiation runs in parallel with production throughout the Second Request process. The government and the responding parties negotiate custodian tiers, search term parameters, and date ranges on a near-continuous basis until the government signals it has received what it needs and the parties affirm substantial compliance. Effective ediscovery teams treat scope as a dynamic variable and build workflows that can absorb changes – including the addition of custodians or the expansion of date ranges – without requiring a full restart of review or processing.
Tiers of Custodians Generate Complexity
Second Requests typically arrive as broad subject-matter categories rather than precise custodian lists. The parties must negotiate the specifics: which individuals are covered, what date ranges apply, and which data types are in scope. This process routinely produces a tiered structure – for example, full communications and business files for a core group of senior executives, and communications only within a specified date range for a second tier of operational custodians. Each tier requires its own volume assessment, collection strategy, and review protocol, placing a premium on ediscovery teams that can rapidly model data burden and adjust workflows accordingly.
Identifying the relevant custodians is itself a significant undertaking, particularly when a request spans multiple years of communications and involves individuals across departments, business units, and locations. Executives, product managers, pricing analysts, sales leaders, and competitive intelligence personnel may each hold material data stored across enterprise email, collaboration platforms, shared network drives, local devices, and third-party cloud services. Each environment requires a distinct forensic collection approach. Scalable, cloud-based ediscovery infrastructure is not optional in this context; it is a baseline operational requirement for any team expecting to meet the government’s production timeline.
Regulatory Scrutiny
Every document produced in response to a Second Request enters an environment of close regulatory scrutiny. Routine internal communications – pricing discussions, competitive assessments, product roadmaps, and executive correspondence – are examined for evidence of market intent, deal rationale, and competitive strategy. The agencies frequently request not just final documents but drafts, versions, and associated metadata, meaning that the completeness and consistency of a production can itself become a point of regulatory contention.
The privilege implications are equally significant. Second Request productions typically generate large volumes of documents requiring attorney-client privilege and work product review, and the parties must produce privilege logs that withstand regulatory challenge. Counsel should consider securing a Federal Rules of Evidence 502(d) order early in the process to limit the risk of subject-matter waiver arising from inadvertent disclosure on a fast-moving, high-volume production. Privilege review workflows must be both thorough and scalable – a combination that requires deliberate protocol design and capable review technology from the outset.
Recent Changes to the Second Request Process
The legal and operational framework governing Second Requests has changed substantially over the past several years, driven by statutory updates, new agency rulemaking, and a sustained shift toward more expansive antitrust enforcement. Legal teams and ediscovery practitioners who relied on playbooks built five or ten years ago will find that both the scope of what must be produced and the administrative burden of certifying compliance have materially increased.
Amendments to the HSR Act
Two significant legislative developments have reshaped HSR compliance in recent years. The Merger Filing Fee Modernization Act of 2022 overhauled the filing fee structure, substantially increasing fees for larger transactions, reducing them for smaller ones, and expanding the categories of transactions subject to HSR reporting obligations. The intent was to direct greater agency resources toward high-value transactions – those most likely to draw Second Requests.
Separately, the FTC’s comprehensively revised HSR rules, finalized in October 2024 and effective February 10, 2025, impose new substantive reporting obligations that directly affect the scope and complexity of what a compliant response must contain.
FTC Guidelines
The FTC’s enforcement posture has shifted considerably since 2021. In August of that year, the agency withdrew its 2020 Vertical Merger Guidelines, signaling an intent to apply a broader view of competitive harm in transactions involving supply chain and distribution relationships. In December 2023, the FTC and DOJ jointly issued new Merger Guidelines that replaced both agencies’ prior horizontal and vertical guidance, articulating an expanded analytical framework for evaluating competitive effects.
The agency has also broadened the thematic scope of its Second Request inquiries to include algorithmic pricing practices, AI-driven product and platform strategies, and labor market competitive effects. The practical result – particularly in technology, healthcare, and consumer products sectors – is that Second Requests have grown broader in both custodian scope and subject-matter reach, requiring responding parties to identify and collect categories of ESI that were rarely implicated under prior enforcement frameworks.
DOJ Guidelines
The DOJ’s Antitrust Division co-authored the 2023 Merger Guidelines and has applied their expanded framework across Second Requests in digital markets, healthcare, financial services, and defense. Requests from the Division now routinely seek technical data, product roadmaps, internal innovation strategy documents, and competitive assessments – categories of ESI that were less commonly targeted under prior enforcement norms and that require specialized review protocols to handle at volume.
Parties responding to a DOJ Second Request should also anticipate requests for structured data alongside traditional ESI, including customer transaction databases, pricing models, and market share analyses. These data sets often require processing outside standard document review workflows and benefit from early coordination between antitrust economists, outside counsel, and the ediscovery team.
Changes in 2024
The FTC’s revised HSR rules represent the most substantive overhaul of the premerger notification process since the HSR Act’s original implementing regulations. Running to approximately 460 pages, the final rules do not alter the underlying legal standards for antitrust review but significantly expand what a compliant submission must contain.
Parties are now required to submit documents and written narratives addressing overlapping products and services, supplier and distribution relationships, the rationale for the transaction, and the anticipated market impact of the combination – obligations that practitioners across the M&A bar have widely characterized as meaningfully broader and more burdensome than the prior framework.
The operational implications for ediscovery are direct. The new narrative requirements necessitate early coordination between antitrust counsel and the ediscovery team, because the custodians and document categories relevant to overlapping products or supply relationships may differ from those historically identified under prior Second Request practice. Teams that treat the 2024 rules as a simple extension of prior playbooks risk under-collecting on newly required categories and exposing the parties to compliance deficiencies that could delay or jeopardize the transaction.
Are Second Requests Urgent?
Yes – and urgency operates on multiple dimensions simultaneously. Issuance of a Second Request tolls the HSR waiting period, meaning the parties cannot close the transaction until the government either clears the deal or files suit to block it.
That pause is not passive. Acquisition financing commitments carry expiration dates. Stock prices and market conditions move. Deal fatigue accumulates on both sides of the table. Every additional week of delay carries direct, measurable cost to the merging parties and their stakeholders.
The certification deadline is also a hard constraint. Once the parties certify substantial compliance, the government has thirty days to challenge the deal or allow it to proceed. The parties’ ability to control the timeline depends entirely on how quickly and completely they can demonstrate that compliance. Teams that underestimate scope, mismanage custodian collection, or produce inconsistently risk the government concluding that certification was premature – which reopens the compliance window and resets the clock. Speed and accuracy are not competing priorities in a Second Request response; both are non-negotiable from the moment the request arrives.
How Should a Second Request Be Handled?
Effective Second Request management requires a structured response framework activated within hours of receiving the request – not days. The following components represent the operational foundation of a defensible, efficient response.
DOJ vs. FTC
While both agencies apply the HSR framework, their Second Request processes differ in operationally significant ways. The FTC’s model Second Request contains 29 specifications and tends to focus on competitive effects in terms of customers, facilities, pricing, and sales – reflecting its traditional product-market analytical approach. The DOJ’s model contains 39 specifications and more commonly seeks technical data, product architecture documents, forward-looking business plans, and internal competitive assessments, reflecting their emphasis on innovation competition and dynamic market effects. Both model requests are publicly available at the FTC and DOJ websites, respectively, and should be reviewed immediately upon receipt to begin mapping specifications to custodians and data sources.
The agencies also differ procedurally. The FTC typically conducts its review through its Bureau of Competition staff and communicates with outside counsel through a liaison process. The DOJ Antitrust Division tends toward more direct staff-level negotiation on scope and timing. Understanding these procedural differences – and working with antitrust counsel who has agency-specific experience – materially affects how a response strategy is structured from the outset.
Key Documents to Gather
Early identification and preservation of key document categories is critical. Priority categories typically include executive and board-level communications regarding the transaction, competitive analyses and market assessments, pricing data and models, product roadmaps and technical specifications, financial projections and due diligence materials, and any internal communications involving competitors, customers, or market strategy. The scope should be mapped against each specification in the Second Request rather than approached generically.
A data map – documenting the systems, custodians, data types, and locations implicated by each specification – is an essential early deliverable. It serves as both an internal planning tool and a defensible record of the collection effort. Data maps should be developed collaboratively with the client’s IT and records management teams as early as possible, as gaps discovered late in the process are costly and difficult to remediate under time pressure.
Team Organization
A dedicated project manager should be assigned at the moment a Second Request is received, with clear authority over logistics, timelines, and cross-team communication.
The core response team typically includes antitrust counsel (lead and supporting), an ediscovery project manager or litigation support director, the client’s internal IT and records management contacts, economic experts if the transaction involves market share analysis, and the ediscovery platform vendor or service provider. Each team member’s role, decision-making authority, and escalation path should be defined in writing within the first 24 to 48 hours. Ambiguity at the organizational level compounds at the operational level as the matter progresses.
Legal Holds
Legal holds must be issued to all relevant custodians immediately – within hours, not days, of receiving the Second Request. The hold notice should be specific enough to communicate what is being preserved and broad enough to capture the full scope of the agency’s likely interest, including relevant data types across all devices and platforms. Acknowledgment tracking is not optional: a defensible record of who received the hold, when, and whether they acknowledged it is essential both for internal compliance and for demonstrating good faith to the reviewing agency if questions arise.
Automated legal hold platforms significantly reduce administrative overhead while strengthening the defensibility record. They also support iterative hold management – expanding the custodian list as scope negotiations produce new tiers – which is a predictable feature of most Second Request responses rather than an exception.
Templates
Pre-approved templates accelerate every stage of the response and reduce the risk of inconsistency under time pressure. Essential templates include privilege log formats calibrated to the applicable agency’s expectations, custodian interview questionnaires adapted for antitrust scope, correspondence templates for agency liaison communications, and a production cover letter framework. Teams should also have a standing Federal Rules of Evidence 502(d) order template ready for immediate submission to protect against subject-matter waiver arising from inadvertent disclosure on high-volume productions.
Standardized review protocols tailored for antitrust matters are equally important. A generic relevance coding protocol is insufficient for a Second Request, where reviewers must apply specification-by-specification responsiveness determinations, understand competitive sensitivity designations, and flag documents that may be responsive to the government’s request but also implicate confidentiality or privilege in ways specific to the antitrust context.
ESI Management
ESI management is the operational core of any Second Request response. The ediscovery platform must support high-volume data ingestion, advanced search and filtering, rolling productions, and real-time reporting on review progress – all at the scale and speed the Second Request timeline demands. Deduplication and near-duplicate detection are baseline requirements; they reduce review volume without sacrificing completeness and are expected features of any credible production workflow.
Technology-assisted review (TAR) and continuous active learning (CAL) workflows have become standard practice in Second Request responses due to the volume of data involved and the time constraints on review. These approaches use iterative machine learning models trained on attorney coding decisions to prioritize the most relevant documents for human review, substantially reducing both time and cost relative to linear review.
AI-assisted coding and classification tools further accelerate first-pass review and support consistent application of specification-by-specification responsiveness determinations across large and distributed review teams. Platforms that combine robust TAR/CAL capabilities with transparent model performance reporting give counsel the visibility they need to manage quality and certify compliance with confidence.
How Does Everlaw Handle Second Requests?
Everlaw is built around the demands that define Second Request response: high-volume data ingestion, rapid TAR model deployment, precision search and analytics, and AI-assisted review that accelerates coding without compromising defensibility. The platform’s cloud-native architecture is designed to scale with the unpredictable scope expansions that characterize Second Request practice, allowing legal teams to maintain production momentum even as custodian lists grow and data volumes shift mid-response.
Data Ingestion
Rapid, reliable data ingestion is the entry point for every Second Request workflow, and delays at this stage compound throughout the production timeline. Everlaw’s cloud-native ingestion pipeline supports a broad range of structured and unstructured data types and is engineered to process large data sets at the speed Second Request timelines require.
Once data is ingested, Everlaw’s TAR models can be deployed immediately and updated by review managers directly, without requiring vendor intervention or extended turnaround time. This self-service model gives legal teams the agility to recalibrate their predictive coding approach as scope negotiations produce new custodian tiers or expanded date ranges – maintaining review momentum rather than waiting on the platform to respond.
Redaction Tools
Second Request productions routinely require redaction of third-party confidential information, personally identifiable information, and competitively sensitive data that falls outside the scope of the government’s request. Managing these redactions accurately and at scale is a significant operational burden, particularly on rolling productions where documents are being reviewed and produced under continuous time pressure. Everlaw’s automated redaction tools allow teams to withhold or remove confidential content at the document level and the metadata level, and to apply redactions across individual files or large document sets in a single workflow.
The ability to redact metadata alongside document content is particularly important in the Second Request context. Reviewing agencies routinely request metadata in addition to document content, and inconsistencies between redacted document text and unredacted metadata can create compliance vulnerabilities that are difficult to remediate after the fact. Everlaw’s metadata redaction capability addresses this risk directly, supporting a production that is complete and consistent across both dimensions.
Search Term Reports
STRs are among Everlaw’s most operationally significant features in the Second Request context. The ability to run the government’s specified search terms – or counsel’s proposed alternatives – against the entire dataset and immediately see document hit counts, exclusive hits, and family hits gives legal teams the data they need to negotiate scope with the agency intelligently and in real time. High hit counts on a particular term may indicate a concentrated area of responsive material warranting focused review; unexpectedly low counts may signal collection gaps that require remediation before they become compliance deficiencies.
This visibility also supports custodian tiering. By running term reports against individual custodians’ data sets, counsel can assess relative data density by subject matter and date range, building an evidence-based tiering proposal for agency negotiations rather than relying on organizational charts or job titles alone. The result is a more defensible scope negotiation position and a more efficiently structured review workflow.
Generative AI
Generative AI has become a meaningful accelerant in Second Request document review, and Everlaw’s generative AI tools deliver that capability through purpose-built application. EverlawAI Coding Suggestions allows legal teams to define highly specific, specification-level code criteria – for example, documents discussing pricing strategies for a particular product line, competitive communications involving a named counterpart within a defined date range, or internal analyses referencing market share – and then receive AI-generated coding suggestions across the full dataset at speed.
The system produces graduated recommendations – Yes, Soft Yes, Soft No, and No – allowing reviewers to concentrate their attention on validating high-confidence suggestions and scrutinizing the soft-call documents where nuanced judgment is required. The result is a material reduction in the manual effort required to identify responsive materials, with consistent application of code criteria across distributed review teams operating under the time pressure that defines Second Request practice. Quality control protocols and a defensible validation methodology remain essential components of any AI-assisted workflow; Everlaw’s transparency into model performance supports the oversight and documentation that counsel need to certify a production with confidence.
The Continued Importance of Second Requests
The regulatory trajectory is clear: Second Requests are becoming broader, more technically demanding, and more burdensome to satisfy. The 2024 FTC rule changes, the expanded analytical framework of the 2023 joint Merger Guidelines, and the agencies’ growing focus on digital markets, algorithmic behavior, and labor market effects have collectively shifted the Second Request from a document-intensive compliance exercise into a multidisciplinary undertaking that tests the full depth of a legal team’s ediscovery infrastructure, antitrust expertise, and project management capability.
The cadence of Second Requests – roughly one every one to two weeks across the U.S. antitrust enforcement system – means that large-cap M&A counsel and their clients cannot treat Second Request readiness as a reactive proposition. The teams that respond most effectively are those that have built their playbook before the request arrives: standing legal hold protocols, current data maps, pre-approved review templates calibrated for antitrust matters, and ediscovery platform relationships tested at the scale and speed the Second Request environment demands.
Technology is now a decisive variable in Second Request outcomes. TAR and CAL workflows, AI-assisted coding, real-time search term analytics, and scalable cloud infrastructure are not enhancements to a capable review workflow – they are the workflow. Platforms like Everlaw, purpose-built for the speed and precision demands of high-stakes regulatory productions, give legal teams the tools to negotiate scope credibly, produce on a rolling basis efficiently, and certify compliance with the confidence that protects deal value and serves their clients’ strategic interests.
The ability to respond to a Second Request efficiently is not merely a measure of legal competence. It is a competitive differentiator for the firms and service providers that handle these matters – and, for the companies whose transactions depend on timely regulatory clearance, a direct driver of business outcomes.
