Here is an excellent and very educational post that I wanted to pass along from the Florida Insurance Blog on the statute of limitations applicable to denied benefit claims under ERISA. It is an issue that is often not as straightforward as it either appears or should be, as the Ninth Circuit case addressed in the post illustrates. If you are new to this issue, you could do worse than to start with a read of that post.
The Envelope, Please . . .
Funny that I referenced the Oscar Awards the other day in a post, as I just found out this blog has been nominated as a top insurance blog by LexisNexis. You know how all the Oscar nominees who don’t win always say its an honor just to be nominated? I never believe them – I am in this to win!
You can see the full list here, and thanks to my producer, the director, the guys at UTA, my agent, the academy . . .
Can the Deepwater Horizon Spill Sink the Fiduciaries of BP’s 401(k) Plan as Well?
Well, someone thinks so. You can count me, though, as monstrously skeptical that you could tag the fiduciaries of the BP 401(k) plan with breach of fiduciary duty for overexposure to company stock because they failed to expect the Deepwater Horizon explosion and account for it by greater diversification. On the other hand are two notes: (1) perhaps there is a circuit, somewhere out there, with fiduciary liability standards for company stock investment that are so loose that including BP stock ahead of such an event could be deemed an actionable breach; and (2) the decline in the value of the plan’s assets may be so large that, if a class gets certified, even a minor settlement to avoid a potential ruling against the fiduciaries could easily run into the tens of millions.
ERISA Preemption: Depends on What You Mean by the Word Relate
I really, really like this opinion, to paraphrase Sally Field’s perhaps most famous line (or perhaps not, since she never actually said it.) I like it because it deals really well, and out of a highly respected court, with a question that often bedevils not just courts, but also lawyers trying to determine the scope of preemption, which is how close does a state law claim have to come to impacting an ERISA governed benefit plan for it to be preempted on the thesis that the state law claim “relates” to the benefit plan. The trend in the case law is to recognize that the word relate is overbroad in this context, and to note that, in light of current Supreme Court jurisprudence, state law claims do not become preempted simply because they relate, in the common English language sense, in some general manner to an ERISA governed benefit plan. Rather, they only relate for these purposes, and are preempted, if the state law claim “interferes with the relationships among core ERISA entities [or] tends to control or supersede their functions,” thereby threatening to undermine “the uniformity of the administration of benefits that is ERISA’s key concern.” When, in contrast, the state law claims, if recovered upon, would not be paid by the plan itself and do not seek to impose peculiar, state by state, obligations on the plan’s administrators and fiduciaries, the state law claims do not relate to the ERISA governed plan for purposes of preemption analysis, and there is no preemption.
I suspect that one of the reasons this issue – of the scope of ERISA preemption – is difficult to handle at times is that there is a language barrier of sorts; as this case shows, relate has a specific meaning in the context of ERISA and ERISA preemption, and an entirely different and broader one when used as part of regular speech, including by lawyers. As a result, analyzing the scope of preemption under ERISA can become one of those areas of the law in which ERISA lawyers and other lawyers become “two peoples separated by a common language,” in the famous formulation.
The case, incidentally, is Stevenson v. Bank of New York, decided this week by the Second Circuit. You can find a copy of it here.
The Attorney-Client Privilege in Insurance Litigation
My in-box, like most of you I assume, is inundated on a day in, day out basis with offers of webinars, seminars, and the like on every topic under the sun that the sponsors think I might even conceivably have any interest in or professional connection to. Most I ignore without even opening, as not even close to being on point with my professional interests and concerns. Even of that remaining subset of ones that have something to do with my work, or my blogging interests, or my professional development, I seldom pass them along in a post because they often appear to simply be lawyers over-complicating and over-analyzing what should be, and normally is, a relatively simple point or area of law (what, lawyers making something more complicated than is necessary? Who’d have thunk it?). My favorite in this regard are the seminars that are routinely touted to me about the complexities of the tripartite relationship in the insurance context, an area of law in which there is, frankly, little complexity and most of the rules of which I summed up right here in this post some time ago.
A different species of educational opportunity, however, consists of those that actually provide a detailed level of analysis on a question that is in fact complicated, and that presents nuances that need to be dealt with in the day to day hurly-burly of practice. This webinar here, on the attorney-client privilege in the context of insurance coverage counseling and litigation, looks on its face to fall into that category. The privilege, in this context, is a lot of fun for a litigator, like me, who enjoys working with the rules of evidence, and exploiting – or conversely defending against – gaps in the protection provided by the privilege. Two issues that quickly jump to the forefront of my mind even as I write this post – both of which appear to be covered by the webinar – are the interrelationship of the privilege with bad faith litigation, including in particular the impact on whether and how to use an advice of counsel defense, and the possible risk of disclosure by means of discovery from an expert witness. There are many more, but they seem to fall within the broad categories listed in the webinar’s agenda, so rather than my reciting them, you may just want to take a listen.
On Named and Functional Fiduciaries
I have been a fan of Scott Simon’s Morningstar articles on the various fiduciary relationships among those who run plans and those who advise them. This one here is a good, practical, business oriented view of the different forms of fiduciaries – named and functional (or deemed) – in 401(k) and other plans. It is written more from the business perspective, of who are the different players and what fiduciary niches do they occupy, in the structuring and operation of a plan. This is somewhat different than how we lawyers, particularly litigators, tend to look at these issues, because it is forward facing and addresses the deliberate structuring of the plan and of these roles. We litigators in particular tend to look at things from a different vantage, more in hindsight, and say did this person or that entity, looking at what they actually did, acquire the status of a fiduciary for purposes of liability exposure, whether they were intended to be put in that position or not at the outset of the plan’s establishment. And from that perspective, one of the most useful comments in his most current article is his explanation of one type of functional fiduciary, namely the party that assumed control over plan assets to some extent unintentionally, but that nonetheless then became a fiduciary with fiduciary responsibility for any acts taken in that regard. As he points out, that party assumes fiduciary liability in that situation, even if it did not knowingly cross the line into that role. As Simon Says:
A more serious scenario is where a person unilaterally exercises discretionary control or authority over a plan without express authorization. Such a person can become a "functional" 3(21) limited scope/non-named fiduciary–without a written contract–through its mere conduct of providing unauthorized advice or exercising unauthorized control or discretion. Given that no contract is present in this situation, the entity obviously doesn’t intend to become a 3(21) limited scope/non-named fiduciary but becomes so anyway through its inadvertent conduct.
From a litigation perspective, this is a far more common circumstance than one might assume, and is a central point in much breach of fiduciary litigation, where a key question is often whether a particular defendant became a fiduciary by its actions concerning the plan and its assets, where it was not intended by the plan’s authors and founders to be a fiduciary.
The Future After Hardt
Well, everybody and their mother’s lawyer has an article, blog post or client advisory memo out on the Hardt case, and I suspect that is because, frankly, its about as easy a Supreme Court decision to understand as you can find. What’s it hold? Procedural victory requiring remand of an ERISA denied benefit claim is sufficient to justify an award of attorney’s fees to the claimant so long as there is some substantive achievement by the claimant in moving his or her case forward. The question left open? What more than just a simple order of remand is necessary to trigger an award of attorneys’ fees, since that alone isn’t enough. The answer? Frankly, on a practical level, it is hard to conceive of a remand that isn’t driven by the claimant showing some significant problem in the administrative record whose existence advances the claimant’s case sufficiently to justify an award under the Hardt ruling. That said, however, I am sure there are going to be factual scenarios in which the issue is arguably close, and one can predict that the development of the case law on that point going forward will be driven by how certain fact patterns intersect with the quality of the lawyering, the quality of the administrative record at issue (and thus of the administrator in question as well, since the caliber of the administrative record in a given case is, in essence, a stand in for the quality of the work done by the administrator and is its physical representation), and with the approach of the particular judge to which the case is assigned. How’s that for an easy and safe prediction? The great southern novelist Walker Percy once commented to the effect that a well written horoscope is one that many people can fit themselves into, and, similarly, this prediction is one into which you can shoe horn pretty much any future development of the case law on this issue. That doesn’t make it any less accurate, though.
This is all a preamble to this link, registration required, to a Lawyers USA story on the decision, in which yours truly is quoted:
Stephen D. Rosenberg, a partner at the McCormack Firm in Boston and author of the Boston ERISA and Insurance Litigation blog, said the relaxed standard could result in more cases being filed.
“I can see more cases being brought by plaintiffs’ lawyers because they can file a case with a procedural problem, knowing they don’t have to win the whole case at the end of the day to collect a fee,” he said.
But a remand order to a plan administrator might not be enough by itself to be considered success on the merits, Rosenberg noted. . . .
“The fight that is going to play out in these cases [involves] the question of how much beyond just a failure to dot an “I” on remand does [a claimant] need to have,” Rosenberg said.
I have a lot more thoughts on the case, some of which are actually more subtle than these broad brush thoughts, but an important one to pass along relates to the issue I am quoted on, of the possibility of Hardt opening the door to more cases being filed. Certainly, there is room and motivation now for participants’ lawyers to bring cases where a clear procedural problem is present, thus making recovery of attorneys’ fees more likely and making filing suit more feasible economically from their perspective, in cases where previously the relatively low dollar value of the benefits at issue combined with a reasonably high degree of difficulty in prevailing on the substantive claim to reverse the denial of the benefits itself would have argued against filing suit. But even that dynamic, in terms of its likelihood of producing more lawsuits, is tempered by a dynamic somewhat peculiar to ERISA litigation, namely the relative paucity of participant lawyers who can spot both a procedural error and a strategic path from it to remand; that is not something just any old plaintiff side lawyer or moonlighting personal injury attorney is going to be able to do. As a result, you may see more cases filed by the better ERISA focused participant lawyers on claims that they otherwise would not have seen as financially worth pursuing, but I doubt you are going to see a noticeable or measurably significant increase in the filing of such suits across the legal and participant population as a whole.
Hardt, A Unanimous Supreme Court, and the Perfect Example of Why Remand Is Enough of a Win to Support an Award of Attorneys’ Fees
I posted recently on the Supreme Court’s consideration in Hardt v. Reliance Standard Life Insurance of the question of just how much success on the merits is necessary to trigger a plan participant’s right to an award of attorneys’ fees, and discussed the fact that requiring an outright and complete win by the plan participant is likely too high of a standard for a fair and equitable system. In a case mostly remarkeable for its unanimaty, the Supreme Court ruled to this effect today, upholding, in essence, the approach to this issue taken by those courts that find some substantive success by the plan participant to be enough to trigger an award of attorneys’ fees.
A decision a week or so ago, Gelumbaukskas v. USG Corporation Retirement Plan Pension and Investment Committee, out of the United States District Court for the District of Maryland provides a perfect example of why this is the correct rule. As the case reflects, the plan participant in that case was never provided with a substantively and procedurally compliant internal appeal process, leaving a record in place from which the court could not pass on the question of whether, in fact, the decision denying benefits was arbitrary and thus should be overturned, which would have resulted in an award of benefits by the court to the plan participant. Rather, the court found that the matter had to be remanded to the plan administrator to redo the appeal process in a manner that would comply with its obligations under ERISA and would create the necessary record for the court to pass on the ultimate question of whether or not the plan participant was actually entitled to the benefits after application of the arbitrary and capricious standard.
Certainly, this is a significant enough win for the plan participant that it should allow an award of attorney’s fees, in that the remand is likely to either end in: (1) a settlement or an award of benefits to him, to avoid the court passing on the question again after having already found deficiencies in the record and having noted potential substantive problems with the record in its opinion; or (2) in the creation of a record that the plan participant can actually use to challenge the denial. In that first possible outcome, the remand order in essence becomes a victory for the plan participant, and it is hard to justify, other than as form over function, the idea that the plan participant should not be entitled to attorney’s fees for that result, when the outcome ends up substantively comparable to an actual outright victory at the courthouse. In the second potential outcome, it is clear that the procedural victory by the plan participant was, at a minimum, a necessary counterweight to the administrator’s control of the appeal process and, simultaneously, the necessary prerequisite to the court ever ruling on the substantive claim for recovery of the actual benefits in dispute; should the plan participant thereafter prevail in court, that initial procedural victory becomes a necessary prerequisite to overturning the substantive denial of benefits, thus warranting treating the remand decision as a necessary part of the court process in litigating the case and one that is therefore capable of supporting an award of fees.
Of course, one can point out the other possible outcome after the administrative appeal process is concluded after the remand by the court, which is that the benefits are still denied on remand, and the court eventually upholds that denial. But even then, the original win served the purpose of enforcing ERISA’s procedural regulations and mandates, which the court found were violated by the administrator. ERISA imposes those procedural obligations on plan administrators for a reason, which is to guarantee the type of fair process that is supposed to stand in for a quick trip to the courthouse clerk’s office; recall that ERISA is interpreted to disfavor litigation for the resolution of disputes, in favor of an administrative handling of disputes outside of the court system, so as to lower plan expenses, encourage the adoption of benefit plans, and make use of the administrator’s expertise in deciding claims for benefits. It is the plan participant in this third potential outcome who has vindicated those underlying principles, and thus has, in essence, scored a win, which should be the predicate for an award of attorney’s fees.
What’s a Good ERISA Lawyer Worth, Anyway?
That’s what this case here begins to answer, at least in the Boston market and in the context of the fees that should be awarded to a prevailing plaintiff. This case was intended to be the next in the series of recent Massachusetts/First Circuit centric decisions I started writing two weeks ago, and haven’t returned to since. It is interesting on two fronts, the first being, as intimated above, it’s survey of billing rates for ERISA counsel in the Boston market. The second is it provides a good explanation, as well as example, of applying a lodestar.
It seemed particularly timely to return to the series of recent decisions by bringing up this one, in light of the Supreme Court’s recent hearing of arguments on the question of the nature of attorney’s fee awards to prevailing plaintiffs in ERISA cases. That case, and the argument before the Court, revolved heavily around exactly what result adds up to a sufficient enough win by a plaintiff/plan participant to trigger an award of attorney’s fees, since an ERISA case involving denied benefits can end up with a result that falls anywhere across a broad continuum of possible outcomes that range from a win for the plan, to a remand back to the plan administrator to fix procedural errors and make a new decision, to an outright win for the plan participant. It is my view, even as predominately a defense lawyer, that those courts who use substantial success (under other names sometimes) by the plan participant in his or her suit as the proper trigger for awarding attorney’s fees under ERISA have it right. There are a lot of barriers to plan participants bringing suit over denied benefits that relate to the costs of doing so, including the fact that many cases simply don’t involve enough in benefit amounts to warrant the plan participant incurring the costs needed to prosecute a claim out of his or her own pocket; making attorney’s fees available so long as the participant proves some substantive problem in the handling of the claim, even if it only results in remand to the plan administrator, is both a necessary counterweight to this problem and consistent with the premise that a plan participant is entitled, even if not to benefits, than to the proper handling of his or her claim and a correct decision making process.
Indeed, if you think about it, the animating principle that makes arbitrary and capricious review morally appropriate is the idea that the decision must be based on a proper process; absent a proper process, the justification for allowing the plan administrator the leeway to make the decision, with only limited review by a court, is weak at best. One can only assume that the administrator’s decision making is appropriate, which is the essential assumption behind discretionary review, if in fact the process used to make that decision was correct; anything less, and there is no reason to assume a correct outcome by the administrator. From a practical perspective, as one who has represented various plan administrators over the years, there is nothing wrong with this approach and idea either, as it is my experience that most good companies strive for a proper process and a correct result (something that itself is dependent on a quality decision making process in the first instance).
For arbitrary and capricious review to exist in a fair legal system, there has to be a realistic opportunity for plan participants to test whether the process pursued was correct, and the opportunity to recover the legal costs incurred in proving that the process was flawed is a necessary part of that, as in its absence, participants will become, for financial reasons, even less likely than they are now to challenge the procedural underpinnings of decisions that go against them. This is simply logical, if you think about it. Why would any rational economic actor spend tens of thousands to prove a mere procedural error leading to remand to the administrator, in cases that often involve only five figures in benefits, absent a realistic opportunity to recoup those fees if correct in his or her belief that the process was flawed?
From this point of view, the exceptional (when compared to every other legal area I can think of at the moment) degree of latitude granted to the administrator by arbitrary and capricious review, something firmly shored up most recently by Chief Justice Roberts in Conkright v Frommert, must exist hand in hand with rules that create a realistic system under which participants can test the administrator’s process in reaching decisions, and the ability to recover legal fees by proving a procedural error and forcing a remand is a sensible part of that system.
What Conkright v. Frommert Means
Well, I guess this wouldn’t be much of an ERISA blog if I didn’t put up a post about the Supreme Court’s decision in Conkright v. Frommert, on the question of whether an administrator continues to be entitled to deferential review when it has already had one interpretation of the challenged plan terms rejected by the court under that standard. Interestingly, coming on the heels of Glenn, the simple fact that the Court had accepted cert in the case suggested some type of change was in the offing for the standard of review, even if it was only incrementally with regard to the application of that standard of review in this type of a fact pattern. Otherwise, frankly, one could see no reason for the Court’s particular interest in the case. The Court, though, found no change to be warranted, and simply reinforced the basic themes of its main cases over the years related to this issue: that deferential review is to be applied, that lower courts are not to deviate from it on ad hoc rationales, and that deferential review is a necessary element of the balancing act between employee rights on the one hand and the need to encourage employers to provide benefit plans on the other. Its not a bad ruling, in the sense that it does give lower courts and practitioners some much needed guidance after decisions such as Glenn, by the Supreme Court, and lower court decisions that played at the margins of the deferential review standards; the decision can, in many ways, be understood as a signal to stick to the basic rules that apply in this area, to not accept the many creative challenges to deferential review that participant lawyers come up with (and which, to their credit, seem to be limited only by the extent of their imagination and legal skills), and to not read cases like Glenn as suggesting any fundamental weakening of that standard outside of the specific factual circumstances presented by that case. And in that regard, the majority opinion can be read as sending that message loud and clear; in fact, the language of the opinion seems to have been selected to purposely drive that point home in as strong a tone as possible. That’s my take on it, anyway.
In fact, the majority opinion was written by Chief Justice Roberts, who, you will recall, authored a concurring opinion in LaRue that has been interpreted by some writers, myself included, as an attempt to prevent the ruling from significantly expanding the extent and scope of ERISA litigation, by placing the type of claim at issue in that case in the realm of denied benefit claims – where deferential review, limited discovery, limitation to the administrative record, and internal administrative appeals rule – rather than in the more free form realm of fiduciary duty litigation. His opinion in LaRue strikes the same tone of wanting to prevent an escalation in ERISA litigation that is at play in the opinion authored by him in Conkright, and this ruling may well have that exact effect; if nothing else, it should quickly become arrow number one in a defense lawyer’s quiver whenever a participant or a participant class seeks to deviate from a strict application of the arbitrary and capricious standard.