Smash Technology v. Smash Solutions

CourtDistrict Court, D. Utah
DecidedJune 30, 2020
Docket2:19-cv-00105
StatusUnknown

This text of Smash Technology v. Smash Solutions (Smash Technology v. Smash Solutions) is published on Counsel Stack Legal Research, covering District Court, D. Utah primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Smash Technology v. Smash Solutions, (D. Utah 2020).

Opinion

IN THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF UTAH

SMASH TECHNOLOGY, LLC, et al., MEMORANDUM DECISION AND ORDER Plaintiffs,

v. Case No. 2:19-cv-00105-TC-JCB

SMASH SOLUTIONS, LLC, et al., District Judge Tena Campbell Defendants. Magistrate Judge Jared C. Bennett

The court issues the following Memorandum Decision and Order regarding Defendants’ three short-form discovery motions, all of which were filed on March 2, 2020.1 For the reasons discussed below, Defendants’ motions are GRANTED. INTRODUCTION

The opening scene in the musical Fiddler on the Roof has a silhouetted figure playing a violin on a rooftop during which the protagonist, Tevye, directs a lengthy aside to the audience. In this aside, Tevye states that everyone in his small village of Anatevka is “a fiddler on the roof” because each person “is trying to scratch out a pleasant, simple tune without breaking his neck.” After acknowledging the difficulty and danger of such a precarious situation, Tevye anticipates what the audience is thinking and asks, “And how do we keep our balance?” He then answers that question in one word: “Tradition!”

1 ECF Nos. 77, 78, 79. In many ways, civil litigators live in Anatevka. With ominous warnings in the Federal Rules of Civil Procedure such as “any ground not stated in an objection is waived,”2 civil discovery litigation is difficult and, like fiddling on a roof, can even feel dangerous. In this environment, civil litigators do their best to scratch out a living without breaking their necks. Given the precarious nature of civil discovery practice, many attorneys—like the Anatevkans— rely on “tradition” for stability. Some of these civil discovery traditions include: (1) a page or two of “general objections” wherein the responding civil litigator objects “to the extent that” any of the interrogatories, document requests, or requests for admission violate some rule; (2) objecting in every discovery response that the request was vague, ambiguous, overbroad, and unduly burdensome, among many other things; but (3) providing a response “without waiving

and subject to” all of the foregoing objections. The party that receives these tradition-laden responses is then left to wonder whether these objections had any actual consequence regarding whether documents were withheld or other responses were left incomplete. Although incredibly inefficient, the civil litigator who provides this traditional “response” feels secure because he/she cannot fall off the metaphorical roof after having played “any and all” available objections. However, many of the aforementioned civil discovery traditions have come under attack over the years. In fact, the United States Supreme Court has doggedly sought to eradicate these traditions to “secure the just, speedy, and inexpensive determination of every action and proceeding.”3

2 Fed. R. Civ. P. 34(b)(4). 3 Fed. R. Civ. P. 1. Several amendments to the Federal Rules of Civil Procedure from 1983 to 2015 amply demonstrate this tradition-breaking effort.4 One of the objectives of these amendments was to end the tradition of the “boilerplate objection.”5 As one commentator described this tradition, The hallmark of a boilerplate objection is its generality. The word “boilerplate” refers to “trite, hackneyed writing”—an appropriate definition in light of how boilerplate objections are used. An objection to a discovery request is boilerplate when it merely states the legal grounds for the objection without (1) specifying how the discovery request is deficient and (2) specifying how the objecting party would be harmed if it were forced to respond to the request. For example, a boilerplate objection might state that a discovery request is “irrelevant” or “overly broad” without taking the next step to explain why. These objections are taglines, completely “devoid of any individualized factual analysis.” Often times they are used repetitively in response to multiple discovery requests. Their repeated use as a method of effecting highly uncooperative, scorched-earth discovery battles has earned them the nicknames “shotgun”—and “Rambo”—style objections. The nicknames are indicative of the federal courts’ extreme disfavor of these objections.6

These “boilerplate objections” violate the rule that “[t]he grounds for objecting” be “stated with specificity” as to interrogatories and that objections to document requests be “state[d] with specificity . . . including the reasons.”7 In other words, “merely assert[ing] boilerplate objections that the discovery sought is vague, ambiguous, overbroad, unduly burdensome, etc. . . . without specifying how each [interrogatory or] request for production is deficient and without articulating the particular harm that would accrue if [the responding

4 Paul W. Grimm, Are We Insane? The Quest for Proportionality in the Discovery Rules of the Federal Rules of Civil Procedure, 36 THE REV. OF LITIG. 117, 123-34 (Winter 2017) (addressing 30 years of amendments to the Federal Rules of Civil Procedure and the discovery practices that all of the amendments sought to change). 5 Fed. R. Civ. P. 26 advisory committee’s note to the 2015 Amendments. 6 Matthew L. Jarvey, Boilerplate Discovery Objections: How They are Used, Why They are Wrong, and What We Can Do About Them, 61 DRAKE L. REV. 913, 914–16 (2013) (footnotes omitted). 7 Fed. R. Civ. P. 33(b)(4); 34(b)(2)(B). party] were required to respond to [the] discovery requests” simply is not enough.8

The amendments to the Federal Rules of Civil Procedure themselves along with cases too numerous to cite here have all declared an ignominious end to the tradition of boilerplate objections.9 Nevertheless, this odious tradition continues because it provides a sense of security— albeit false—on the high-pitched roof of civil litigation. Most civil litigators believe that if they simply play all objections, then they cannot be found to have waived any. But this traditional reliance on boilerplate objections is misplaced for two reasons. First, there is no provision in the Federal Rules of Civil Procedure that allows a party to assert objections simply to preserve them.10 Instead, as stated above, the Federal Rules require that objections be specific.11 Second,

8 Liguria Foods, Inc. v. Griffith Labs., Inc., 320 F.R.D. 168, 185 (N.D. Iowa 2017) (citation omitted). 9 Although the cases are too numerous to cite, here are just a few over the past 40 years: Id.; Fischer v. Forrest, No. 14-CV-1304-PAE-AJP, 2017 WL 773694, *1, *3 (S.D.N.Y. Feb. 28, 2017) (issuing “a discovery wake-up call” that general objections violate the rules especially after 2015 amendments to Federal Rules of Civil Procedure); Precision Timber v. United States, No. 98-720 C, 2001 WL 1819224, *6 (Fed. Cl.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Morissette v. United States
342 U.S. 246 (Supreme Court, 1952)
Northcross v. Memphis Board of Education
412 U.S. 427 (Supreme Court, 1973)
Pierce v. Underwood
487 U.S. 552 (Supreme Court, 1988)
Hutchinson v. Pfeil
105 F.3d 562 (Tenth Circuit, 1997)
United States v. Zapata
546 F.3d 1179 (Tenth Circuit, 2008)
Sabol v. Brooks
469 F. Supp. 2d 324 (D. Maryland, 2006)
Lawson v. FMR LLC
134 S. Ct. 1158 (Supreme Court, 2014)
Peabody Twentymile Mining v. Secretary of Labor
931 F.3d 992 (Tenth Circuit, 2019)
Swackhammer v. Sprint Corp. PCS
225 F.R.D. 658 (D. Kansas, 2004)
Mills v. East Gulf Coal Preparation Co., LLC
259 F.R.D. 118 (S.D. West Virginia, 2009)
Rogers v. Giurbino
288 F.R.D. 469 (S.D. California, 2012)
In re Folding Carton Antitrust Litigation
83 F.R.D. 260 (N.D. Illinois, 1979)
Mulvaney v. Rivair Flying Service, Inc.
744 F.2d 1438 (Tenth Circuit, 1984)
In Re Convergent Technologies Securities Litigation
108 F.R.D. 328 (N.D. California, 1985)
B. Braun Medical Inc. v. Abbott Laboratories
155 F.R.D. 525 (E.D. Pennsylvania, 1994)
Momah v. Albert Einstein Medical Center
164 F.R.D. 412 (E.D. Pennsylvania, 1996)
Everett v. USAir Group, Inc.
165 F.R.D. 1 (District of Columbia, 1995)

Cite This Page — Counsel Stack

Bluebook (online)
Smash Technology v. Smash Solutions, Counsel Stack Legal Research, https://law.counselstack.com/opinion/smash-technology-v-smash-solutions-utd-2020.