A critical document or piece of evidence that is overlooked or hidden never comes into legal consideration. For all practical purposes, it might as well not exist.
Large corporate defendants arrive at the Rule 26 meet and confer table with a structural advantage built over decades. Their records are held across sophisticated enterprise systems — ERP platforms, document management systems, communication archives, operational databases, and proprietary tools that have evolved across years or decades of business operations. The people who built and manage those systems understand them in intimate detail. Defense counsel is advised by them.
Plaintiff's counsel typically is not.
The asymmetry is twofold. The first gap is unfamiliarity with where and how business records are created and maintained in the normal course of corporate operations. The second is unfamiliarity with the computing systems and technical environments that hold them. Together, these gaps create a dangerous condition — one in which uninformed counsel is taken advantage of and their clients' interests are compromised before a single deposition is taken or a single motion is filed.
Under Rule 26(f), parties must meet and confer and develop a written discovery plan. Under Rule 26(b)(1), the scope of discovery is bounded by relevance and proportionality. Both provisions are routinely and skillfully used by well-advised defense counsel to narrow what enters the case. Agreements that appear reasonable on their face can silently eliminate entire categories of critical evidence — and what is excluded at this stage rarely surfaces later.
"What is not surfaced at this stage rarely surfaces later. Critical documents that are missed, overlooked, or deliberately kept out of scope do not re-enter the case. They are simply gone."
The Rule 26 Framework
Rule 26(f) — Conference of the Parties; Planning for Discovery. Requires parties to meet and confer as soon as practicable and develop a written discovery plan governing scope, form, and sequence of production.
Rule 26(b)(1) — Scope of Discovery. Limits discoverable material to what is relevant to a party's claim or defense and proportional to the needs of the case — the proportionality standard routinely invoked to narrow production obligations.
We bring to the plaintiff's side exactly what the defense brings to theirs: expert-level knowledge of how major enterprises build, maintain, and manage their records — and how those practices have evolved over time. We know which systems hold what. We know which custodians matter. We know which technical arguments are designed to narrow scope rather than reflect reality. We know what is being withheld and how. And we use our proprietary technology to find it, document it, and enforce against it.
Before negotiations begin, we build a complete picture of the opposing party's data environment — custodians, enterprise systems, databases, third-party platforms, communication archives, and legacy environments that may hold responsive materials. Counsel walks into the Rule 26(f) conference knowing what should be in scope before the other side has the opportunity to define it.
Individual custodian productions tell only part of the story. We identify the non-custodial locations — shared systems, operational databases, collaborative platforms, and enterprise repositories — that hold responsive materials no single custodian would surface, and that adversaries have no incentive to volunteer.
We assess whether documents and data are being destroyed, migrated, or moved in ways designed to place them beyond the reach of discovery. Evidence that disappears before it is identified never comes into play. We identify the indicators — technical, operational, and behavioral — that signal a problem before it becomes irreversible.
Every industry and every large organization has its own internal language — terminology, abbreviations, code words, and operational shorthand that employees use in the normal course of business to describe conditions, processes, and decisions. We analyze that language before search terms and culling agreements are negotiated, ensuring that neutral-sounding limitations do not silently exclude categories of critical evidence.
Proportionality arguments under Rule 26(b)(1) are a standard and sophisticated tool for narrowing production obligations. Applied without technical scrutiny, they create the conditions under which critical documents are excluded by agreement before anyone realizes what was lost. We ensure that every scope reduction is made with full visibility into what is actually at stake — and that burden-reduction agreements do not function as evidence-exclusion agreements.
We map the relationships between people and processes within the opposing organization and advise on the optimal order in which custodians and non-custodial sources should be produced — ensuring that each deposition is prepared against the fullest possible evidentiary record. After agreements are established, we use our technology to monitor production for gaps, inconsistencies, and patterns that indicate the terms of agreed obligations are not being honored.
Rule 30(b)(6) is one of the most powerful tools in complex litigation. It requires a corporation to designate a witness — or witnesses — to testify on behalf of the organization on specified topics. That testimony binds the corporation. Done well, a Rule 30(b)(6) deposition produces the corporate admissions that define the trajectory of the case.
Done poorly — or against a witness who has been carefully prepared by sophisticated defense counsel — it produces little of value and telegraphs the gaps in plaintiff's technical understanding.
When the matter demands it, Crivella goes beyond technical advisory. We conduct detailed analysis of the deposition topics, develop preparation notes for counsel, build the exhibit set, and attend the deposition in person — working hand-in-hand with litigation counsel at the table to establish the corporate admissions and testimony the case requires.
Our presence is not passive. We bring direct knowledge of the corporation's systems, records practices, and organizational structure into the room — giving counsel the real-time technical grounding to press on the answers that matter and recognize when a witness is being evasive about technical realities.
Topic Analysis & Scoping
We analyze the proposed Rule 30(b)(6) topics against our knowledge of the corporation's systems and records environment — identifying which topics are most likely to yield corporate admissions and where the technical pressure points are.
Preparation Notes for Counsel
Detailed technical preparation materials — translated into language counsel can use at the table — covering the systems, processes, and records practices at the center of each deposition topic.
Exhibit Development
We build and organize the exhibit set — selecting, sequencing, and annotating documents to support the examination and maximize the evidentiary value of the testimony.
In-Person Attendance & Real-Time Support
We attend the deposition and work directly alongside counsel — providing real-time technical guidance, identifying evasive or technically inaccurate testimony, and ensuring the examination presses on the corporate admissions the case requires.
The Rule 26 meet and confer is not a procedural formality. It is the moment at which the evidentiary landscape of the case is defined — often permanently. What is negotiated here determines what the lawyers will have to work with at every stage that follows: depositions, motions, expert testimony, trial.
Counsel who enters this process with full technical intelligence negotiates from strength. Counsel who enters without it negotiates from a position the other side has spent years preparing to exploit.
When clients trust Crivella at this stage — the earliest, most consequential stage — they find that the same expertise and technology that served them in discovery continues to serve them throughout the life of the matter. The relationship that begins here is built on demonstrated value when it mattered most.
The document that surfaces changes cases.
The document that doesn't might as well
never have existed.
Engagements typically begin with
Every engagement begins with a confidential conversation about the specific matter. Tell us where you are in the case, who you are up against, and what you know — or don't know — about the other side's data environment. We'll take it from there.