About This Blog
Summaries, news and resources relating to eDiscovery in Delaware and beyond.
Showing 6 posts in Statutes/Rules.
Earlier this year, proposed amendments to the Federal Rules of Civil Procedure were submitted to the United States Supreme Court for review following a years long process that began in 2010. The proposed amendments will become effective on December 1, 2015 barring any action by either the Supreme Court or Congress to modify them.
Circuit splits and a lack of uniform standards have plagued eDiscovery for some time. The proposed amendments attempt to bring uniformity to the body of eDiscovery law that has been developing since the early 2000s. The proposed amendments also seek to address litigants’ concerns that eDiscovery has in the past been used as a weapon to force settlement upon those who cannot afford to engage in the process. To that end the proposed amendments address proportionality and the scope of discovery.
These amendments will most likely eventually be adopted by various States as well. For a full discussion by the Advisory Committee on Federal Rules of Civil Procedure and a list of all of the Committee’s proposed amendments, see the March 2014 and September 2014 Reports of the Judicial Conference Committee on Rules of Practice and Procedure, available here [http://www.uscourts.gov/rules-policies/records-and-archives-rules-committees/committee-reports]. More ›
This summer one current and one former United States District Court Judge took to the interview circuit on the topic of eDiscovery. The most common theme was that lawyers have the obligation to understand both the law and technology. More ›
As many of you are likely aware, the Delaware District Court revised its Default Standard for Discovery back in December. Several sources walked readers through the new provisions and speculated about the practical impacts of the new Default Standard. I opted to wait until working under the new Default Standard before offering commentary. Now that I have had the opportunity to use the new Standard in real cases, I'm ready to offer a practical critique.
The new Default Standard is a real leap forward from its predecessor and an excellent guide for litigants. Whereas the old Default Standard was basic, a bit scattershot, and meant to be a punishment to parties who failed to cooperate, the new Default Standard is a gift wrapped eDiscovery plan. (It's my understanding that DuPont's Global eDiscovery Director, Vince Catanzaro, was a driving force behind development of these new guidelines. Well done Vince!) To date, I have used the new Standard in several cases as the basis for agreements for conducting eDiscovery. Among it's best features are:
- A focus on early party Meet & Confers regarding eDiscovery, including early consideration of Proportionality;
- Schedule A of the new Standard lists data types and sources that are excluded from preservation absent a good cause showing;
- A list of metadata fields that parties must exchange, no other fields are required;
- During search term discussions, receiving parties may request no more than 10 additional search terms;
- Seeks enforcement of the FRCP 26(f) Meet & Confer requirement to discuss eDiscovery and the timing of the same;
- Protection of litigation holds and other preservation efforts from discovery; and
- On-site inspection of the producing party's information systems is barred absent a good cause showing.
However, the new Standard is not without it's flaws. Although none of it's flaws are major, there are a few items that I think are unclear in the new Standard. I will address them in the order in which they appear in the new Standard, citing the section, so you can play along at home.
The first oddity, while not an actual flaw per se, merits mentioning because of its irony: the document appears to be scanned paper. Odd.
To Preserve or Not To Preserve
The first possible flaw is that the language of section 1.c.(i) seems to contradict or at least conflict with Schedule A #5. I'll explain.
Schedule A of the new Standard lists data types and sources that are excluded from preservation absent a good cause showing. Schedule A #5 identifies "Back-up data that are substantially duplicative of data that are more accessible elsewhere." The inclusion of the word "substantially" here means to me that the Court recognizes and accepts that *some* relatively small amount of non-duplicative data may be lost. So good cause to preserve a backup source would require showing that a backup has a unacceptably large amount of non-duplicative data. Just showing one document, or even a few, would likely not be good cause to force preservation. This is pragmatic and enlightened, and I like it (and I'm sure the Court is relieved to know that I approve).
However Section 1.c.(i) concerns the scope of discoverable information and says:
Absent a showing of good cause by the requesting party, the parties shall not be required to modify, on a going-forward basis, the procedures used by them in the ordinary course of business to back up and archive data; provided, however, that the parties shall preserve the non-duplicative discoverable information currently in their possession, custody or control.
To me, the first phrase in this section says that parties don't need to change their regular backup routines, including the regular destruction of backups. In other words, just like Schedule A #5, there's no need to preserve backups. Good.
Not so fast. The second phrase in section 1.c.(i) says that parties may only continue executing their regular backup routines, including the regular destruction of backups, if there is no unique data in a backup. There's unique data in most backups, so reading the second phrase literally seems to negate the first part of section 1.c.(i).
That is, section 1.c.(i) really says that parties may continue executing their regular backup routines, including the regular destruction of backups, if, and only if, the backups they intend to destroy have no unique data. None. Zero. This could cause parties to keep all backups for fear that any of them contain even one unique item. Not only is that a bad rule, it directly contradicts Schedule A #5's exclusion of backups from preservation.
I have no doubt that causing parties to keep all backups was not the Court's intention, and this is merely a drafting error. Nevertheless, it's potentially problematic, and I hope it will be corrected. I offer the following language as a possible alternative:
Neither party shall be required to modify, on a going-forward basis, the procedures used by them in the ordinary course of business to back up and archive data, unless those procedures may be reasonably expected to destroy potentially relevant data that does not also exist on a more readily accessible source.
This isn't a flaw so much an issue with style. Section 1.d.(iii) says:
Activities undertaken in compliance with the duty to preserve information are protected from disclosure and discovery.
While this is certainly a clear and welcome statement that preservation activities are protected, there are times when disclosing some of those activities is helpful. If a party discloses their preservation efforts and the opposing party will agree (in writing) that those efforts are reasonable, the disclosed preservation effort then become highly defensible.
Section 1.d.(iii) doesn't preclude such disclosure and discussion, but it doesn't encourage it either. I would have preferred the section said something like:
Although activities undertaken in compliance with the duty to preserve information are protected from disclosure and discovery, parties are encouraged to share this information in reasonable detail when appropriate in the interest of cooperation.
I'm not married to that language, but you get the idea. Like I said, this isn't a flaw, just a style preference.
Section 5.b. does a lot of good things, but I believe it could use some clarification. Specifically, it says:
Absent a showing of good cause, a requesting party may request no more than 10 additional terms to be used in connection with the electronic search.
What counts as a search term? Quite often, we use search strings (e.g. "too much" w/3 noise) of varying complexity, because they yield more tailored results and smaller data sets than individual terms (e.g. "noise"). So, I may have several search strings like:
- Smith AND [misappropriat* OR stole OR steal* OR (customer w/3 list) OR (client w/3 list) OR fire OR terminat* OR discipline* OR suspend* OR resign* OR unemploy*] between 1/1/08-1/1/10
- (Kennedy OR Jones OR Adams) AND (fire OR terminat* OR discipline* OR suspend*) between 9/15/09-10/15/09
- Smith AND [perform! OR theft! OR (client w/7 contact)] between 10/1/08-11/1/10
What exactly can the receiving party request? It seems clear to me they can request that individual words be added to a string with each word counting against the 10. That is, using the above strings, the receiving party can request the addition of "account" to the final string so it reads:
Smith AND [account OR perform! OR theft! OR (client w/7 contact)] between 10/1/08-11/1/10.
The requesting party can do that 9 more times.
But what if the receiving party requests the addition of "account manager" instead? Is that one term or two? What if, in addition to the strings above, they requested we also run: "(Williams OR Martin OR Wilson) AND (captur* OR escap* OR dwindl*) between 6/15/09-8/15/09?" Is that 6 terms? I think so, but, to avoid party confusion and unnecessary court intervention, this could be clarified.
Section 5.d. says:
The only files that should be produced in native format are files not easily converted to image format, such as Excel and Access files.
I see two problems here. The first is a minor drafting error. For accuracy, "Excel" should be changed to "spreadsheets" (I would even add "and similar files like those with a .csv extension"). Certainly, Excel spreadsheets are the most common spreadsheets--and perhaps Excel has become synonymous with spreadsheets the way Qtips now means all cotton swabs--but there are many of us who use non-Excel spreadsheets. This is an easy fix.
The other problem is two-fold. First, like the Excel issue, "Access" should be changed to "databases." Again, there are many other types of databases besides Access. In fact, I would wager SQL (pronounced sequel) databases are the most common right now. This is also and easy fix, but there's a much bigger problem here.
The second problem is that production of entire databases is not a very good way to handle databases in eDiscovery. In fact, it's a bad way to handle them.
The Sedona Conference® Database Principles Addressing the Preservation and Production of Databases and Database Information in Civil Litigation (April 2011) explains that the best way to handle databases in eDiscovery is to generate relevant reports for production. This requires the producing party to determine the fields available in a given database, disclose the fields to the receiving party, and negotiate relevant reports.
There's more to it than that, but that's the basic idea: database production is based on reports not exchanging entire databases. This process is very similar to search term negotiation and development, except the discussion is about database fields. I would hope this portion of the new Standard can be revised quickly, because I think it could prove problematic.
Metadata, I Knew You Well
Section 5.e. lists the metadata fields parties must provide. Among the fields listed are Conversation Index, Control Number Begin, and Control Number End.
Conversation Index. As I understand it, this is a field created by eDiscovery software that identifies and groups email threads, which is useful during review. Not all software does this, so not everyone will have a Conversation Index field to produce. Even when a party does have this field, it exists for their own use during review and is not something typically produced, if ever. Moreover, even if a party were to produce this field of information, most, if not all, review software would be unable to utilize the information. This field should be removed from the list.
Control Numbers. These are typically numbers assigned to documents for internal use and are never disclosed. I think what was intended here was Bates Begin and Bates End. These are arguably the two most important fields parties must exchange, but they do not currently appear on the list.
Title. This is a commonly exchanged field indicating the title given to an office document. I would have included it on the list.
Missing in Action
As terrific as the exclusions in Schedule A are, they do not address custodians' personal data, SMS text messages, or social media. Maybe the Court doesn't want these categories of data excluded by default, but they seem to fit in nicely with the other categories on that list. Either way, some guidance on handling these types of data would have been appreciated, especially considering how frightened some people seem to be about social media.
If you like the new Default Standard as much as I do, you will want to use it as the basis for a form eDiscovery agreement for use in Delaware District Court and any other court. After all, why reinvent the wheel? But, as pointed out above, the new Standard is not perfect. The workaround for that is to pull the text of the new Standard into a form agreement and correcting the errors discussed above. After that, all you will need to do is make changes warranted by the specific circumstances of a case and you're done. Pre-cooked eDiscovery Plan.
Apparently I am the only one who seems to be concerned with the Court of Chancery's unqualified allowance for parties to agree to forgo discovery of ESI. Here are the other blog posts I found that have reported on the new guidelines, not a single one raises any concern:
Last week, the Delaware Court of Chancery—one of the nation's premier business Courts—unexpectedly issued a one and a half page "Guidelines for Preservation of Electronically Stored Information." Surprisingly, the Guidelines seem to allow parties to opt-out of document discovery entirely (see the last item below). In summary, the Guidelines are as follows:
- There is a common law duty to preserve potentially relevant electronically stored information (ESI) within a party's possession, custody, or control once litigation is commenced or when litigation is "reasonably anticipated."
- Parties must take reasonable steps in good faith to meet their duty to preserve ESI.
- Parties and their counsel should confer early in the litigation regarding the preservation of ESI.
- Parties and their counsel must develop, oversee, and document a preservation process in collaboration with the appropriate client information technology personnel.
- Parties and their counsel should discuss the need to identify how custodians store their information, including document retention policies and procedures as well as the processes used to create, edit, send, receive, store, and destroy information for the custodians.
- Counsel should take reasonable steps to verify information they receive about how ESI is created, modified, stored, or destroyed.
- The preservation process should include a written litigation hold notice to individual custodians instructing them to take reasonable steps, act in good faith, and with a sense of urgency in preserving potentially relevant information.
- Parties and their counsel may face "serious consequences" for failing to take reasonable steps to preserve ESI.
- The reasonableness of a party's preservation process is judged on a case-by-case basis.
- Counsel for all parties should confer about the scope and timing of discovery of ESI and may agree to limit or forgo the discovery of ESI.
I am very interested to hear comments on this development.
As explained by Ed McNally (one of the most renowned corporate litigators in the known universe), the Delaware Superior Court has created a commercial litigation division. This is exciting for many reasons, not the least of which is the new division has rules regarding eDiscovery. Morris James had the honor of providing input on the formation of those rules, and we are very pleased with the final results. A brief summary of the rules:
The new rules require parties to meet and confer to discuss:
- any issues relating to preservation of ESI;
- the form in which each type of ESI will be produced and any problems relating thereto;
- the scope of production, including the custodians, time period, file types and search protocol to be used to identify which ESI will be produced;
- the method for asserting or preserving claims of privilege or of protection of ESI as trial-preparation materials, including whether such claims may be asserted after production;
- the method for asserting or preserving confidentiality and proprietary status of ESI relating to a party or a person not a party to the proceeding;
- whether allocation among the parties of the expense of preservation and production is appropriate; and,
- any other issue relating to the discovery of ESI.
From those discussions, the parties are required to develop an eDiscovery plan for submission to the Court for entry as a order. The rules then provide a safe harbor for destruction of documents outside the scope of the order. The rules also provide a process for handling not reasonably accessible data, and they explicitly preserve privilege for inadvertently produced documents.
In a recent Court of Chancery letter opinion in Dawson v. Pittco Capital Partners, CA No. 3148-CC, at page 2 in footnote 3, Chancellor Chandler wrote:
Federal Court decisions are “of great persuasive weight in the construction of parallel Delaware rules” due to the analogous nature of the Court of Chancery Rules and the Federal Rules of Civil Procedure. Cede & Co. v. Technicolor, Inc., 542 A.2d 1182, 1191 n.11 (Del. 1988).
Interesting. Or, as Jimmy Stewart would say, "Well, that's very in'resting."