Chief Justice Roberts commented that the newly amended Federal Rule of Civil Procedure, Rule 26 “crystalizes the concept of reasonable limits in discovery through increased reliance on the common-sense concept of proportionality.”  This common sense approach was recently embraced by a Special Master, and then approved by the District Court Judge, in the products liability case In re Takata Airbag Prods. Liab. Litig., MDL No. 2599 (S.D. Fla. Mar. 1, 2016).

In that case, the defendants proposed to withhold or redact non-relevant information from their production of documents.  The proposal included redacting non-relevant parent emails from responsive families (i.e., if the email was not relevant but it’s attachments were, defendants proposed to redact the email, but produce the entirety of attachments).  Specifically, defendants proposed to redact information pertaining to seven discrete categories of information in an effort to balance their desire to protect highly confidential trade secrets while complying with their discovery obligations.

The District Court concluded the defendants’ proposal was appropriate and, quoting Chief Justice Robert’s comments about the then proposed amendments, highlighted that “a party is not entitled to receive every piece of relevant information,” and therefore “it is only logical” that “a party is similarly not entitled to receive every piece of irrelevant information in responsive documents if the producing party has a persuasive reason for why such information should be withheld.”  This “common Sense” approach is a fair and balanced way to proceed with discovery, especially when responsive information is mixed with non-responsive information.

While not discussed in the In re Takata case, query whether a redaction log – comparable to a privilege log — is advisable when applying responsiveness redactions to one’s production.  Such a log may prevent against gamesmanship and over-designations.  I, myself, have had occasion to apply responsiveness redactions to productions and have made it my practice to create a redaction log, which articulates – in a summary fashion – the reason for the redaction (i.e., redaction of information relevant to a contract other than the one at issue in this litigation).