Good grief, get to the point!

This week we discuss one of The Scribe’s pet peeves—written materials that show the reader that the writer has no qualms about wasting the reader’s time.  Please, get to the point … quickly!

Written materials should immediately get to the point.  This admonition not only applies to materials submitted to judges (who are especially cranky when you waste their time), but also to materials submitted to anyone else.  So although the rest of this tip is focused on written submissions to judges, it applies to any written materials.

Every motion submitted to a judge should begin with a summary that succinctly describes (1) the nature of the case (“This lawsuit concerns John Smith’s alleged exposure to asbestos supplied by TraneCo.”),  (2) the purpose of the submission (“TraneCo moves for summary judgment against Smith’s claims because there is no evidence that Smith worked around any TraneCo product.”), and (3) the reasons why the court should rule in your favor (“During his deposition, Smith testified that he couldn’t associate TraneCo with any product that he worked on during his career.  Therefore, no jury could conclude that Smith worked around any TraneCo product or was exposed to asbestos from that product.”).

Judges don’t read your filings because they are interested in your case and have nothing else to do; they read them because it’s their job.  And judges don’t want to work any harder (or longer) than necessary to figure out what you are asking them to do.  So please, don’t make their job more difficult by hiding—on page 10—the key issue that you want decided; the judge should understand the nature of the case and the issue presented after spending no more than 90 seconds with your brief.

Set out below is an example of how to do it. By the time you finish reading this introduction, you won’t have all the details, but you’ll know exactly the nature of the case, what the court is being asked to do, and why:

This lawsuit arose from the crash of one of defendant-appellant Reliable Helicopters, Inc.’s helicopters in August 2008.  As a result of that crash, nine people were injured.  Even More Reliable Helicopters, Inc.—along with many other companies, including Reliable—has been sued in lawsuits arising from that crash.  In its Fourth Claim for Relief, EMRH sought a declaration that Reliable has a duty to defend EMRH in those lawsuits.

Eighteen years earlier, EMRH and Reliable entered into a Repair/Overhaul Services Agreement that governs the services performed by EMRH on Reliable’s helicopters.  In that Agreement, Reliable agreed to defend future “claims made” against EMRH that exceed certain monetary thresholds ($1 million for any one individual claim or $2 million for all claims arising from any one occurrence) that are allegedly related to EMRH’s provision of services under the Agreement.  It is undisputed that the thresholds have been reached with respect to claims made against EMRH arising from the August 2008 crash, and that the claims are allegedly related to EMRH’s provision of services under the Agreement.

Based on Oregon’s contract-interpretation rules, the Agreement’s plain language, and the undisputed fact that the monetary thresholds have been reached, the district court ruled that Reliable has a duty to defend EMRH in the helicopter-crash lawsuits.  That ruling should be affirmed.

As you can see, this introduction explains, quickly, what the appeal is about (at least from EMRH’s perspective) and why the district court’s ruling should be affirmed.  In other words, it gets to the point . . . quickly.  And in doing so, it shows the reader that her time will not be wasted.

That is all for now …

Leave a comment

Filed under Judge Irritants, Style

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s