Risk Update

Risk Roundup (Disasters, Ethics Rules & Engagement Letters)

Posted on

Okay, let’s get on with the business. I’ve had my eye on some interesting developments over the past few months and thought a broad summary of key developments would be interesting. Just in case folks haven’t tracked all the in’s and out’s of what’s been going on out there.

ABA releases new ethics guidance on dealing with disasters

  • “Recent large-scale disasters like Hurricane Florence and wildfires on the West Coast have reinforced the need for the ABA to address the myriad rules that lawyers must consider under these challenging circumstances. ABA Formal Ethics Opinion 482, released on Wednesday by the Standing Committee on Ethics and Professional Responsibility, clarifies the variety of ethical obligations attorneys face when disaster strikes.”
  • “Following a disaster, a lawyer must evaluate available methods to maintain communication with clients… Lawyers should also remember that the duty of competency, Rule 1.1 includes a technology clause that requires lawyers to consider the benefits and risks of relevant technology. Because a disaster can destroy lawyers’ paper files, lawyers “must evaluate in advance storing files electronically” so that they can access those files after a disaster. Storing client files through cloud technology requires lawyers to consider confidentially obligations.”

And on the broader topic of evolving ethics rules: “Crafting Legal Ethics Rules For The 21st Century: How can the profession’s rules of conduct keep pace with the rapidly evolving technological landscape?

  • “Anecdotally, at least, there is a significant disconnect between the rules of professional conduct and the day-to-day reality of practicing lawyers. There is an apparent sea change happening in the world of legal ethics as attorneys confront previously uncontemplated ethical issues. Can you reference facts about a case when responding to a negative or false online review? Is it ethical for a lawyer to Facebook “friend” a judge before whom she appears? Can you allow your firm’s web consultant to view the names of your potential clients through your website contact form?”
  • “Above the Law and the Data-Driven Ethics Initiative are partnering on an unprecedented research effort to explore attorney perceptions of the rules of professional conduct, particularly as they intersect with emerging digital technologies. Our ultimate goal is to create an open source legal ethics resource. We hope this resource will serve to deliver actionable intelligence to the legal community by synthesizing data from actual practicing lawyers.”

Another topic that continues to continue is engagement letters. Here’s a fresh take on that topic by consultant Mike Quartararo: “Is It Time To Upgrade Your Engagement Letters?

  • “Wouldn’t legal services as a whole and the client relationship in particular benefit from more expansive, specific, individualized engagement letters?”
  • “So, how is it that legal engagement letters became such a perfunctory process? Well, at least in New York, it’s because 20 years ago the court system asked lawyers to begin using them to outline the scope of their legal services, the fees to be charged, and the right to arbitration of any disputes. To be sure, anyone who hires a lawyer wants to know at least these three things. But is that enough?”
  • “Here’s a challenge to GCs and corporate legal operations people: Dig out the engagement letters your organization has signed with outside counsel in the last few years. Go back as far as you like. Lay them out on a table (or across your computer monitor) and see if they aren’t just the same recycled letter with changed dates and increased billing rates.”
  • “If I were a corporate attorney charged with engaging outside counsel, engagement letters that I sign would include a lot more. And I’m sure that some of these things are discussed between client and counsel, but in today’s market, it just makes sense for engagement letters to contain some of these things. Here’s my list of what should be included in an engagement letter: [read more]”
If you liked this post, please share it:
Risk Update

Judicial Smears (Alleged), Disqualifications and Hacked Firms (Hypothetical)

Posted on

Okay, let’s get on with the business. I’ve had my eye on some interesting developments over the past few months and thought a broad summary of key developments would be interesting. Just in case folks haven’t tracked all the in’s and out’s of what’s been going on out there. I’ll be sharing a mix of what’s caught my eyes of the past few months, over the next few weeks.

Let’s start with some drama: “Squire Patton Atty Says Judge Smeared Him In Arbitration DQ” —

  • “A Squire Patton Boggs partner disqualified from arbitrating a fee dispute between a Chesapeake Energy subsidiary and the U.S. arm of a Chinese state-owned oil company wants in on the case now before the Fifth Circuit on appeal, claiming the lower court wrongly and unfairly tarred his reputation.”

  • “Dallas-based Squire Patton Boggs LLP partner Patrick Long told the Fifth Circuit Monday that he wasn’t even aware of the fight between Chesapeake and OOGC America LLC over fees for development in the Eagle Ford Shale until he was given a copy of U.S. District Judge Lynn N. Hughes’ Dec. 5 order partially invalidating an arbitration award after determining that Long spent nearly a year hiding his own business ties to Chesapeake while serving on the arbitration panel. In that ruling, Judge Hughes called Long “corrupt” and a “liar,” finding Long had hid his relationship to people and investments associated with Chesapeake.

  • “But Long told the Fifth Circuit that Judge Hughes’ “accusations were based on a flawed, incomplete understanding of the relevant facts.” He said he’s never represented Chesapeake, nor had any financial or social relationships with any officers or directors of the company or OOGC, as well as any witnesses called in the underlying arbitration.”

Next, an interesting read: “The Lawyer’s Duty When Client Confidential Information is Hacked From the Law Firm” —

  • “Imagine it’s a usual Tuesday morning, and coffee in hand you stroll into your office. Right inside the door, you see a handwritten notice on a big whiteboard which says: All network services are down, DO NOT turn on your computers! Please remove all laptops from docking stations & keep turned off. ‘No exceptions'”
  • “This really happened. In 2017, DLA Piper was hacked by the NotPetya malware, and until the breach was resolved, the 4,400-attorney law firm was reduced to conducting business by text message and cell phone.”

The article goes on to explore relevant opinions and rules, outlining three key duties:

  1. Monitor for Electronic Data Breaches
  2. Stopping the Breach, Restoring Systems, and Determining What Occurred
  3. Providing Notice to the Client
If you liked this post, please share it:
Risk Update

The Risk Blog Returns (No, It’s Not April Fool’s Day)

Posted on

I’m delighted to announce the launch of the Bressler RIsk Blog (BRB). Some of you may remember that from 2009-2017 I published a law firm risk blog, whilst wearing a different hat.

Having changed lanes professionally and re-emerged in 2018 with hands well full, I’ve still felt an itch unscratched. (And appreciate the many who have reached out over the hiatus with blogging encouragement — always nice to know that folks out there are real and reading!)

This new blog is a fresh start and a new experiment — and I’m looking forward to seeing how the story continues to play out. 

I’d like to encourage everyone who isn’t receiving email updates to sign up for them. And to send word to your friends and colleagues to do the same. Tweets, LinkedIn posts, emails forwards to colleagues are all welcome!

Finally, I’d like to encourage anyone with tips, stories and resources to share to get in touch. I’m always grateful for the articles, decisions, and even snarky comments readers have been known to send in from time to time. 

And, as they say, away we go!




If you liked this post, please share it:
Risk Update

Subscribe for email updates

Posted on

* indicates required

If you liked this post, please share it: