<?xml version="1.0" encoding="utf-8"?>

<rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:admin="http://webns.net/mvcb/"
xmlns:cc="http://web.resource.org/cc/"
xmlns="http://purl.org/rss/1.0/">

<channel rdf:about="http://www.bostonerisalaw.com/">
<title>Boston ERISA Law Blog</title>
<link>http://www.bostonerisalaw.com/</link>
<description></description>
<dc:language>en-us</dc:language>
<dc:creator></dc:creator>
<dc:date>2008-05-14T11:52:41-05:00</dc:date>
<admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=3.34" />


<items>
<rdf:Seq><rdf:li rdf:resource="http://www.bostonerisalaw.com/archives/401k-plans-millions-for-defense-billions-for-damages-state-streets-exposure.html" />
<rdf:li rdf:resource="http://www.bostonerisalaw.com/archives/401k-plans-larue-auditing-and-401k-plans.html" />
<rdf:li rdf:resource="http://www.bostonerisalaw.com/archives/fiduciaries-big-questions-from-a-small-story-on-a-relatively-small-loss.html" />
<rdf:li rdf:resource="http://www.bostonerisalaw.com/archives/fiduciaries-excessive-fee-litigation-a-real-problem-or-an-imaginary-one.html" />
<rdf:li rdf:resource="http://www.bostonerisalaw.com/archives/conflicts-of-interest-why-structural-conflicts-of-interest-standing-alone-are-irrelevant.html" />
<rdf:li rdf:resource="http://www.bostonerisalaw.com/archives/exclusions-more-on-the-arthur-andersen-ruling.html" />
<rdf:li rdf:resource="http://www.bostonerisalaw.com/archives/conflicts-of-interest-some-thoughts-on-the-oral-argument-in-metlife-v-glenn.html" />
<rdf:li rdf:resource="http://www.bostonerisalaw.com/archives/electronic-discovery-a-few-words-on-the-practicalities-of-electronic-discovery.html" />
<rdf:li rdf:resource="http://www.bostonerisalaw.com/archives/conflicts-of-interest-metlife-v-glenn-in-a-nutshell.html" />
<rdf:li rdf:resource="http://www.bostonerisalaw.com/archives/benefit-litigation-on-discovery-problems-and-solutions.html" />
<rdf:li rdf:resource="http://www.bostonerisalaw.com/archives/pensions-pension-estimates-not-worth-the-computer-they-are-printed-on.html" />
<rdf:li rdf:resource="http://www.bostonerisalaw.com/archives/401k-plans-does-employer-stock-even-belong-in-retirement-plans.html" />
<rdf:li rdf:resource="http://www.bostonerisalaw.com/archives/401k-plans-passing-along-some-reading-on-excessive-fee-cases-and-other-timely-erisa-topics.html" />
<rdf:li rdf:resource="http://www.bostonerisalaw.com/archives/fiduciaries-what-happens-when-erisa-and-the-law-of-insurance-coverage-collide.html" />
<rdf:li rdf:resource="http://www.bostonerisalaw.com/archives/401k-plans-what-larue-wrought.html" />
</rdf:Seq>
</items>

</channel>

<item rdf:about="http://www.bostonerisalaw.com/archives/401k-plans-millions-for-defense-billions-for-damages-state-streets-exposure.html">
<title>Millions for Defense, Billions for Damages: State Street&apos;s Exposure</title>
<link>http://www.bostonerisalaw.com/archives/401k-plans-millions-for-defense-billions-for-damages-state-streets-exposure.html</link>
<description><![CDATA[<p>Backdating. It&rsquo;s a scandal. No, not that <a href="http://en.wikipedia.org/wiki/Options_backdating">backdating</a>. I mean when bloggers can&rsquo;t get to something when it first comes up, and then go back in time to talk about it. That&rsquo;s what I mean by backdating, and that&rsquo;s what I am going to do today. Last week, I read, but didn&rsquo;t have a chance to discuss here, <a href="http://www.bloomberg.com/apps/news?pid=20601103&amp;sid=aM5fuE5pY2.g&amp;refer=news">this article</a> from Bloomberg on the State Street Bank subprime losses and potential ERISA related exposure. The article was particularly interesting because it takes a tack someone different than most articles that, like this one, rely on lawyers to evaluate the litigation against State Street arising out of those events; most such articles focus on liability issues, the procedural defenses available to State Street under ERISA, and the defensive position that the company can assert. This article, though, asks and attempts to answer the million dollar - or in this case, more like the billion dollar - question of how much losing these cases will cost State Street. The numbers bandied about by well informed lawyers are staggering, even to the jaded eye. </p>
<p>The article rounds up the usual band of worthies to comment, including the <a href="http://lawprofessors.typepad.com/laborprof_blog/">Workplace Prof&rsquo;s</a> <a href="http://en.wikipedia.org/wiki/Clark_Kent">mild mannered alter ego</a>, Paul Secunda, who tacks the eye popping number of &ldquo;hundreds of millions to the billions&rdquo; on State Street&rsquo;s potential liability, and Boston ERISA lawyer Marcia Wagner, who noted that the plan administrators filing suit against State Street may have had no other options but to sue. To quote the article:</p>
<blockquote><p>Wagner said fund managers hurt by the drop may have an obligation to sue as the existing plaintiffs have. &ldquo;To the extent plans were misled into purchasing something they were not authorized to purchase, they may have a fiduciary obligation to sue,'' said the lawyer, who isn't representing the investment manager or plaintiffs. ``It's sue or be sued,'' she said. ``They allowed bad investments, so they should be attempting to make the plans whole.&rdquo;</p></blockquote>
<p>This echoes something I said in my last <a href="http://www.bostonerisalaw.com/archives/fiduciaries-big-questions-from-a-small-story-on-a-relatively-small-loss.html">post</a> on the State Street mess, in which I raised concerns about the fact that pension fund managers invested in the State Street products without properly understanding what they were buying. As I suggested in that post, administrators fall down on their own fiduciary obligations in such circumstances. As Wagner&rsquo;s comment suggests, it may well be that the administrators&rsquo; fiduciary duties under those circumstances require them to then try to remedy their initial mistakes by suing to recover the losses, rather than compounding their own fiduciary&nbsp;breaches by simply absorbing the loss; that latter course of action would likely just make the administrators themselves targets for breach of fiduciary duty lawsuits based on their own mistakes in investing in the State Street funds.</p>]]></description>
<dc:subject>401(k) Plans</dc:subject>
<dc:creator>Stephen D. Rosenberg</dc:creator>
<dc:date>2008-05-14T11:52:41-05:00</dc:date>
</item>
<item rdf:about="http://www.bostonerisalaw.com/archives/401k-plans-larue-auditing-and-401k-plans.html">
<title>LaRue, Auditing, and 401(k) Plans</title>
<link>http://www.bostonerisalaw.com/archives/401k-plans-larue-auditing-and-401k-plans.html</link>
<description><![CDATA[<p>On various occasions on this blog I have tried to turn away from its understandable focus on legal issues and onto the real world consequences of the legal rulings that govern ERISA plans. In particular, I have a particular interest, because of the manner in which it impacts my clients, on what practices companies should follow to best protect themselves from potential exposure in the current - and in the ERISA world these days, ever changing - legal environment. </p>
<p>As a result, I took particular interest in this <a href="http://www.law.com/jsp/ihc/PubArticleIHC.jsp?id=1202421325081">piece</a> out of Legal Times today by an experienced accountant and employee benefit plan auditor on the practical auditing steps that should be taken to ensure proper operation of a 401(k) plan and to limit potential liability in the operation of such a plan. The author&rsquo;s hook into this topic? The Supreme Court&rsquo;s decision in <em>LaRue</em>, and the manner in which the opening of liability, at least in theory, by the case is best met by that hoary chestnut, best practices. More than that, though, the author details exactly what, on an operations level, should be part of those best practices.</p>]]></description>
<dc:subject>401(k) Plans</dc:subject>
<dc:creator>Stephen D. Rosenberg</dc:creator>
<dc:date>2008-05-13T15:20:34-05:00</dc:date>
</item>
<item rdf:about="http://www.bostonerisalaw.com/archives/fiduciaries-big-questions-from-a-small-story-on-a-relatively-small-loss.html">
<title>Big Questions From A Small Story on a (Relatively) Small Loss</title>
<link>http://www.bostonerisalaw.com/archives/fiduciaries-big-questions-from-a-small-story-on-a-relatively-small-loss.html</link>
<description><![CDATA[<p>Here&rsquo;s a short newspaper <a href="http://www.newstimes.com/ci_9167824">story </a>of a local municipal pension plan that suffered a $2.4 million loss to its pension fund, which is only about a $53 million fund, as a result of investments in subprime mortgage backed assets made either by State Street or in State Street funds (the article isn&rsquo;t clear on the relationship between the pension plan and State Street, the current poster boy for breaching fiduciary duty by subprime investments). As the article points out, the pension plan has retained counsel to pursue State Street over the loss, on the theory that State Street did not adequately disclose the nature of the investments and the risk; this is pretty much par for the course for the various <a href="http://www.dandodiary.com/2008/01/articles/subprime-litigation/subprime-litigation-wave-hits-state-street/">State Street subprime lawsuits</a> being brought by pension and 401(k) plans, which essentially allege that volatile subprime related exposures were not disclosed but were instead contained within investment products sold as safe, conservative bond investments. Although dressed up to suit ERISA and breach of fiduciary duty issues, they can essentially be understand as highly gussied up bait and switch claims, in which retirement plan administrators and fiduciaries allege that they thought they were buying one thing from State Street - a conservative investment vehicle to balance out riskier investment allocations - but instead were sold something else, namely a highly volatile and risky exposure. State Street, of course, as the article reflects, views the cases otherwise, as instances in which the proper disclosure was made, but market downturns harmed the investments. </p>
<p>This whole scenario raises an interesting question, aside from whether it is the plaintiff administrators or instead State Street that is right, because no matter which one is correct in their interpretation of the events at issue, you still end up in the same place, which is that the plans signing off on these investments just plain didn&rsquo;t know what they were buying. This is certainly the case if, as the plaintiff fund fiduciaries claim, they weren&rsquo;t told the truth, but it is likely also the case if, as State Street claims, plan sponsors were told the truth and are now simply complaining about market outcomes; if it&rsquo;s the later case, one can only assume that the sponsors didn&rsquo;t understand the risk being taken when they signed up for the investment. </p>
<p>And this goes right back to the most important question of all here, which is what were the plan sponsors and fiduciaries doing when they were offering these investment options or making these investments themselves? This scenario speaks of poor investigation and over reliance on the investment provider, namely State Street, and suggests the plans themselves did not have proper processes, including independent administrators with the sophistication to analyze the investment choices and risks, in place for choosing investment options, prior to offering them to plan participants or investing the plans' funds directly. In this day and age, I think we are moving past the point of debating whether those types of processes are part of the fiduciary obligations of those running retirement plans. </p>
<p>And by the way, for the record, I am not buying the article&rsquo;s spin that the loss was not that damaging to the pension plan discussed in the article, because it was only about $2.4 million. Against total plan assets of approximately $53 million, and with the taxpayers on the hook to fund the pensions because it is a municipal plan, that&rsquo;s an important hit, both financially and to the public pocketbook.</p>]]></description>
<dc:subject>Fiduciaries</dc:subject>
<dc:creator>Stephen D. Rosenberg</dc:creator>
<dc:date>2008-05-08T11:48:24-05:00</dc:date>
</item>
<item rdf:about="http://www.bostonerisalaw.com/archives/fiduciaries-excessive-fee-litigation-a-real-problem-or-an-imaginary-one.html">
<title>Excessive Fee Litigation: A Real Problem or An Imaginary One?</title>
<link>http://www.bostonerisalaw.com/archives/fiduciaries-excessive-fee-litigation-a-real-problem-or-an-imaginary-one.html</link>
<description><![CDATA[<p>Here's a piece passed along by the <a href="http://lawprofessors.typepad.com/laborprof_blog/2008/05/hidden-401k-fee.html">Workplace Prof</a>, noting the rise in excessive fee litigation under ERISA. I have noted <a href="http://www.bostonerisalaw.com/archives/401k-plans-what-larue-wrought.html">before</a> that the combination of demographic and economic factors with the ruling in <em>LaRue</em> is going to create more of these types of actions over the years, not less, and thus I share the skepticism the Prof expresses over whether, as a defense lawyer quoted in the piece suggests, these cases don't pose a significant problem for plan administrators. Moreover, I don't necessarily buy the sentiment suggested by defense counsel quoted in the article, to the effect that these cases are about a battle of the experts over whether any particular plan's fees were too high relative to the market or not. I think of them more as due diligence and best practices cases, as really revolving around whether the administrator followed a proper process to pick providers and funds, and to make sure the fees involved remained appropriate as measured against appropriate benchmarks.</p>]]></description>
<dc:subject>Fiduciaries</dc:subject>
<dc:creator>Stephen D. Rosenberg</dc:creator>
<dc:date>2008-05-07T10:14:54-05:00</dc:date>
</item>
<item rdf:about="http://www.bostonerisalaw.com/archives/conflicts-of-interest-why-structural-conflicts-of-interest-standing-alone-are-irrelevant.html">
<title>Why Structural Conflicts of Interest, Standing Alone, Are Irrelevant</title>
<link>http://www.bostonerisalaw.com/archives/conflicts-of-interest-why-structural-conflicts-of-interest-standing-alone-are-irrelevant.html</link>
<description><![CDATA[<p><a href="http://lawprofessors.typepad.com/laborprof_blog/2008/04/hey-did-easterb.html">Workplace Prof</a> passes along today this <a href="http://lawprofessors.typepad.com/laborprof_blog/files/CW137TF8.pdf">opinion</a> out of the Seventh Circuit by Judge Easterbrook addressing the question of structural conflicts of interest and their effect on the standard of review in ERISA governed benefit cases. Anyone who has read the bulk of my past posts on this subject knows that I do not buy the idea that the mere existence of the structural conflict standing alone - without more, such as an inference of distorted decision making that can be drawn from the administrative record itself - should affect the standard of review. There are a number of reasons for this, many of which I have explored in past posts on the question.&nbsp; One of the most persuasive of which, however,&nbsp;has always been that the assumption that the structural arrangement by definition is affecting the decision making is frequently belied by close observation of the evidence concerning the processing of particular individual claims in situations where the administrator was also the payor; the evidence simply does not support the view that outcomes are typically varying simply because the administrator is also the payor of the benefits at issue. </p>
<p>Judge Easterbrook presents a very interesting take on this idea, focusing on the actual decision making by the administrator in any particular case, and suggesting why the mere fact that the same organization will also pay any covered benefits does not logically lead under those circumstances to improper claims processing. As the judge writes, in a section discussed by the Workplace Prof:</p>
<blockquote><p>[O]ne must not anthropomorphize &ldquo;the administrator.&rdquo; Rarely is a pension or welfare plan&rsquo;s administrator a person whose own welfare is at stake. Administrators commonly are large organizations, and the real people who make decisions on its behalf are no more interested in the outcome than federal judges are &ldquo;interested&rdquo; in the resolution of a tax case. True, judges&rsquo; salaries won&rsquo;t be paid if taxes can&rsquo;t be collected, but the effect of any one case on federal finances is so small that the judge does not care who prevails. Just so with the people who act on requests for pension or welfare benefits. Corporations often find it hard to align employees&rsquo; incentives with stockholders&rsquo; interests; they use stock options, bonuses, piece rates, and other devices. Administrators usually don&rsquo;t try. There would be a real conflict of interest if a given administrator put in place a method of linking decisionmakers&rsquo; income to the substance of their decisions. A quota system (&ldquo;grant no more than 50% of all applications&rdquo;) or some other means of tying the wages or promotion of staff to its disposition of claims could call for non-deferential judicial review. But [the claimant here] has not argued that anyone who handled his claim had any personal interest in the outcome.</p></blockquote>
<p>To which I would say, exactly. Note as well that the judge emphasizes one important distinction that I fear often gets overlooked when critics get their back up when anyone, myself included, suggests that structural conflicts of interest should not affect the standard of review. He is not saying that it can never affect the standard of review and that an administrator who also pays the benefits may not be acting under a conflict, but is instead recognizing that, given the realities of claim administration, it is inappropriate (perhaps more accurately, illogical) to assume that this alone is corrupting the claim determination process. Rather, as the judge points out, something more is needed in this situation to justify such an inference, something such as, in the judge&rsquo;s example, evidence of a quota system or other activity that would suggest that the process was corrupted and not impartial. </p>
<p>The case is <em><a href="http://lawprofessors.typepad.com/laborprof_blog/files/CW137TF8.pdf">Williams v. Interpublic Severance Pay Plan</a></em>.</p>]]></description>
<dc:subject>Conflicts of Interest</dc:subject>
<dc:creator>Stephen D. Rosenberg</dc:creator>
<dc:date>2008-05-01T10:38:33-05:00</dc:date>
</item>
<item rdf:about="http://www.bostonerisalaw.com/archives/exclusions-more-on-the-arthur-andersen-ruling.html">
<title>More on the Arthur Andersen Ruling</title>
<link>http://www.bostonerisalaw.com/archives/exclusions-more-on-the-arthur-andersen-ruling.html</link>
<description><![CDATA[<p>I like the legal issues raised by it; bigger media outlets like the big numbers involved. Either way, the story gets big play. Here&rsquo;s the National Law Journal&rsquo;s <a href="http://www.law.com/jsp/ihc/PubArticleIHC.jsp?id=1209373541208">article</a> on the Seventh Circuit&rsquo;s ruling on the lack of coverage for Arthur Andersen&rsquo;s pension obligations, a ruling I discussed in detail in this post <a href="http://www.bostonerisalaw.com/archives/fiduciaries-what-happens-when-erisa-and-the-law-of-insurance-coverage-collide.html">here</a>.</p>]]></description>
<dc:subject>Exclusions</dc:subject>
<dc:creator>Stephen D. Rosenberg</dc:creator>
<dc:date>2008-04-29T09:42:43-05:00</dc:date>
</item>
<item rdf:about="http://www.bostonerisalaw.com/archives/conflicts-of-interest-some-thoughts-on-the-oral-argument-in-metlife-v-glenn.html">
<title>Some Thoughts on the Oral Argument in MetLife v. Glenn</title>
<link>http://www.bostonerisalaw.com/archives/conflicts-of-interest-some-thoughts-on-the-oral-argument-in-metlife-v-glenn.html</link>
<description><![CDATA[<p>I had a chance over the weekend after a busy few days to ruminate on the oral argument in <em>MetLife v. Glenn</em>, a transcript of which you can find <a href="http://www.supremecourtus.gov/oral_arguments/argument_transcripts/06-923.pdf">here</a>; you can find Workplace Prof&rsquo;s review of the argument <a href="http://lawprofessors.typepad.com/laborprof_blog/2008/04/erisa-glenn-cas.html">here</a>&nbsp;and a thorough recap of the argument <a href="http://www.scotusblog.com/wp/oral-argument-recap-metlife-v-glenn/">here</a>, at SCOTUS blog. My take? There will be some sort of rule announced governing the standard of review that a court is to apply when presented with an appeal from a decision by an administrator functioning under a so-called structural conflict of interest - how&rsquo;s that for going out on a limb, since that&rsquo;s what the Court accepted cert to address? Moreover, there can&rsquo;t help but be a rule of general applicability of some type set forth by the Court for these situations, since, as I discussed in detail <a href="http://www.bostonerisalaw.com/archives/conflicts-of-interest-a-survey-of-all-the-circuits-on-the-effect-on-the-standard-of-review-of-structural-conflicts-of-interest.html">here</a> for instance, there is wide divergence among the circuit courts of appeals in the decision making rules they apply when confronted with that situation; given the <a href="http://www.bartleby.com/61/94/I0019400.html">idee fixe</a> that ERISA is supposed to give rise to uniform rules governing employee benefits across the country (an idea that in practice, tends to be honored more in the breach, something particularly illustrated at the district court level where you can often find two judges in the same circuit reaching opposite conclusions on the same open issue), this is not a situation that can be allowed to continue. That said, however, those hoping this case would lead to a wholesale reinterpretation of the standards of review that apply to ERISA cases, and more particularly to an overall rejection of both the &ldquo;arbitrary and capricious&rdquo; standard of review and of the existing formulations as to when that standard of review applies, are going to be soundly disappointed; I read the argument as telegraphing a fixation on determining, and creating (and then announcing), exactly what the technical rule should be when arbitrary and capricious review is applied by a supposedly conflicted administrator, and as telegraphing a lack of interest in changing the overall structure of the case law governing the standard of review question.</p>]]></description>
<dc:subject>Conflicts of Interest</dc:subject>
<dc:creator>Stephen D. Rosenberg</dc:creator>
<dc:date>2008-04-28T10:18:16-05:00</dc:date>
</item>
<item rdf:about="http://www.bostonerisalaw.com/archives/electronic-discovery-a-few-words-on-the-practicalities-of-electronic-discovery.html">
<title>A Few Words on the Practicalities of Electronic Discovery</title>
<link>http://www.bostonerisalaw.com/archives/electronic-discovery-a-few-words-on-the-practicalities-of-electronic-discovery.html</link>
<description><![CDATA[<p>I have written a lot on the blog about electronic discovery, most recently in this <a href="http://www.bostonerisalaw.com/archives/benefit-litigation-on-discovery-problems-and-solutions.html">post</a>, and much of it relates to the legal issues revolving around whether and when to allow such discovery. Before it vanishes off their website, I thought I would pass along this <a href="http://www.masslawyersweekly.com/042308.cfm">piece</a> out of the Massachusetts Lawyers Weekly that looks at electronic discovery from a more prosaic but equally important perspective, the practicalities of actually engaging in it.</p>]]></description>
<dc:subject>Electronic Discovery</dc:subject>
<dc:creator>Stephen D. Rosenberg</dc:creator>
<dc:date>2008-04-23T15:49:35-05:00</dc:date>
</item>
<item rdf:about="http://www.bostonerisalaw.com/archives/conflicts-of-interest-metlife-v-glenn-in-a-nutshell.html">
<title>MetLife v Glenn in a Nutshell</title>
<link>http://www.bostonerisalaw.com/archives/conflicts-of-interest-metlife-v-glenn-in-a-nutshell.html</link>
<description><![CDATA[<p>On Wednesday, the Supreme Court is holding oral argument in <em><a href="http://www.scotusblog.com/wp/the-week-ahead-35/">MetLife v. Glenn</a></em>, the case that will supposedly tell us once and for all what the effect is on ERISA litigation when the party who has to pay ERISA governed benefits is also the one who decides whether to pay those benefits. Given the Court&rsquo;s history when it comes to addressing issues related to litigating ERISA cases, starting with <em>Sereboff</em> (at a minimum) and running up through the recent ruling in <em>LaRue</em>,&nbsp;you can predict&nbsp;that the Court&rsquo;s ruling will add as many questions and issues to litigating such cases as it will resolve. I have discussed before here on this blog&nbsp;my view&nbsp;that the actual evidence in a particular case should be the basis for deciding how to handle any particular instance in which one party is both the administrator and the payor, and that it is specious to instead impose and enforce blanket assumptions that a meaningful conflict&nbsp;always exists in such situations. But I can tell from the responses to my prior posts to this effect how many people simply don't agree with me on that, and this case offers the Court the opportunity to make the call on that one. In any event, now that I have whet your whistle for all things <em>Glenn</em>, you can find all things <em>Glenn</em>, including everything you need to know in advance of the oral argument if this is something of interest to you, right <a href="http://www.scotuswiki.com/index.php?title=MetLife_v._Glenn">here</a>.</p>]]></description>
<dc:subject>Conflicts of Interest</dc:subject>
<dc:creator>Stephen D. Rosenberg</dc:creator>
<dc:date>2008-04-22T12:25:10-05:00</dc:date>
</item>
<item rdf:about="http://www.bostonerisalaw.com/archives/benefit-litigation-on-discovery-problems-and-solutions.html">
<title>On Discovery Problems and Solutions</title>
<link>http://www.bostonerisalaw.com/archives/benefit-litigation-on-discovery-problems-and-solutions.html</link>
<description><![CDATA[<p>Here&rsquo;s an interesting <a href="http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1120921">law review article</a>, passed along in detail by the <a href="http://lawprofessors.typepad.com/laborprof_blog/2008/04/postponing-disc.html">Workplace Prof</a>, on problems, and potential solutions, in managing discovery. Discovery, to beat what must now be a dead horse, has become infinitely more complicated and expensive - with far more <a href="http://soundevidence.discoveryresources.org/cases-168-broadcom-qualcomm-sanctions-blistering-show-cause-order-issued-for-14-attorneys-on-ediscovery-behavior.html">consequences</a> for mistakes - in any type of complex litigation with the adoption of the federal rules governing electronic discovery (and in fact with the rise of computerized data itself). Regular readers know that I have argued before in this space that the courts need to develop a jurisprudence that analyzes the need for and cost of electronic discovery - which can often involve massive amounts of computer generated and/or stored data - in much greater depth than the more superficial analysis of discovery disputes that has historically been the norm: in essence, courts should engage in a more searching inquiry into disputes over electronic discovery, given their costs and how much of such data is likely to be irrelevant in any given case, before granting extensive discovery into electronically stored data. At a minimum, there should be a degree of inquiry that, even if it won&rsquo;t allow conclusive enough findings to decide to outright not allow such discovery, will still allow an intelligent, reasoned limitation on exactly what the scope of that discovery should be. I would argue that, in cases that warrant it, it would even be appropriate to hold a mini-trial type proceeding, maybe of two or three witnesses, and then to rule on to what extent such discovery is warranted. This approach would be a far cry from how courts have traditionally addressed discovery disputes, but, as the article suggests, it is past time for the courts to begin applying a more systemic and in-depth approach to controlling discovery. </p>
<p>This is particularly important in the areas covered by this blog, ERISA litigation and insurance coverage litigation, where computerized data, communications and information processing, is almost literally the coin of the realm. Electronic discovery is therefore truly a major cost-driver and risk factor in these areas of the law. The development, at the boots on the ground level of magistrate judges (to whom discovery disputes are often assigned), special discovery masters and trial judges, of the law of electronic discovery provides an opening for courts to really address these issues, in the manner suggested by the article and with fresh eyes, and its an opportunity that should be taken advantage of, one that calls for curiosity, innovation and reasoned experimentation. I will give you one example, to make my point. One of my partners was recently handling a massive, multi-party litigation, in which there were numerous interrelated legal and factual issues, some of which may be outcome determinative. Rather than engage in the traditional approach of years of discovery with only minimal court oversight, followed by summary judgment motions, the court instead ordered some discovery, followed by summary judgment motions on the key potentially outcome determinative legal issues, followed by, if any party believed further discovery was needed to resolve those issues, the filing of Rule 56(f) affidavits to justify such discovery; the court would then decide what further discovery would be allowed before it would rule on the legal issues. The end result was order out of what otherwise could have been chaos, and a case that stayed on track towards resolution. It&rsquo;s a good example of a court proactively using existing procedural tools to narrow the issues, and decide on what issues further and potentially expensive discovery is actually needed.&nbsp; This appears to be exactly the type of use of existing procedural tools and focus on the timing of discovery that the article's author is advocating as the means to improve discovery.</p>]]></description>
<dc:subject>Benefit Litigation</dc:subject>
<dc:creator>Stephen D. Rosenberg</dc:creator>
<dc:date>2008-04-21T12:06:56-05:00</dc:date>
</item>
<item rdf:about="http://www.bostonerisalaw.com/archives/pensions-pension-estimates-not-worth-the-computer-they-are-printed-on.html">
<title>Pension Estimates: Not Worth The Computer They Are Printed On</title>
<link>http://www.bostonerisalaw.com/archives/pensions-pension-estimates-not-worth-the-computer-they-are-printed-on.html</link>
<description><![CDATA[<p>Here&rsquo;s an interesting decision out of the First Circuit yesterday, concerning errors in providing estimates of pension amounts to participants and whether a participant can hold the sponsor to the erroneous estimate, rather than receive only the correct amount under the actual terms of the retirement plan in question. Short answer? A participant only gets what the plan, by its express terms, grants, and not the larger erroneously estimated amount. Although it is fair to say that the actual outcome of any such dispute will depend on the actual facts of a given circumstance and the particular theories under which a particular participant elects to proceed, this case reflects that enforcing the estimate, rather than simply receiving the lower actual amount due under the plan, is an uphill battle, at best. In this particular case, <em><a href="http://www.ca1.uscourts.gov/cgi-bin/getopn.pl?OPINION=07-2108.01A">Livick v Gillette</a></em>, the employee struck out both on attempts to obtain the higher amount by arguing that the erroneous estimate was an actionable breach of fiduciary duty, and on an estoppel theory. The court&rsquo;s analysis of the estoppel theory is particularly noteworthy, as it provides great fodder for any sponsor or fiduciary defending against an estoppel claim related to an ERISA governed plan. If you are litigating a case in the First Circuit concerning an estoppel claim related to the benefits available under a particular ERISA governed plan, this case would be the place to start.</p>]]></description>
<dc:subject>Pensions</dc:subject>
<dc:creator>Stephen D. Rosenberg</dc:creator>
<dc:date>2008-04-17T15:16:49-05:00</dc:date>
</item>
<item rdf:about="http://www.bostonerisalaw.com/archives/401k-plans-does-employer-stock-even-belong-in-retirement-plans.html">
<title>Does Employer Stock Even Belong In Retirement Plans?</title>
<link>http://www.bostonerisalaw.com/archives/401k-plans-does-employer-stock-even-belong-in-retirement-plans.html</link>
<description><![CDATA[<p>Should there even be employer securities in a 401(k) plan or other retirement vehicle? That&rsquo;s the million dollar question (or more like the hundred million dollar question) that cases like those arising out of the Bear Stearns collapse raise. Moreover, it goes right to the underlying tension between ERISA and the securities laws that plays out in the concept of fiduciary duty: namely, the extent to which it is appropriate for a fiduciary to continue to allow employer stock holdings in a retirement vehicle when the company is simultaneously facing market pressure on its stock price and an obligation to comply with the securities laws in dealing with the marketplace as a whole. The legal and philosophical issues of this inquiry go on and on, spinning on like a fall into the <a href="http://en.wikipedia.org/wiki/Alice's_Adventures_in_Wonderland">rabbit hole</a>; this is manifest in cases such as the Seventh Circuit&rsquo;s ruling in <em>Baxter</em>, discussed <a href="http://www.bostonerisalaw.com/archives/401k-plans-what-larue-wrought.html">here</a>, in which these types of issues are merely raised, but not resolved. It&rsquo;s a good topic for a law review article, but since blog posts traditionally don&rsquo;t run to the hundreds of pages, I am not going to get very far into answering those issues here, but rather want only to raise the topic, which I think will be played out in a fundamental manner in the case law as the subprime mess lurches its way through the legal system. And on a practical level, what raised this thought this morning was this <a href="http://www.nytimes.com/2008/04/17/business/17pension.html?_r=1&amp;ref=business&amp;oref=slogin">story here</a> in the New York Times about pension funds moving out of equities, because, while there is a certain apples and oranges aspect to any comparison between that issue and employee holdings of employer stock in defined contribution plans (in that pension funds are moving in this direction because of future liabilities related to pension plan payouts and not necessarily for the same reasons that an employee might not want to be invested in his or her own employer&rsquo;s equities), that fact does raise an interesting question. Simply put, if the professionals who run pension funds are moving out of the stock market for, in part, volatility reasons, should comparatively unsophisticated 401(k) investors be allowed to, even in some instances encouraged to, overload with one particular company&rsquo;s equities?</p>]]></description>
<dc:subject>401(k) Plans</dc:subject>
<dc:creator>Stephen D. Rosenberg</dc:creator>
<dc:date>2008-04-17T11:13:38-05:00</dc:date>
</item>
<item rdf:about="http://www.bostonerisalaw.com/archives/401k-plans-passing-along-some-reading-on-excessive-fee-cases-and-other-timely-erisa-topics.html">
<title>Passing Along Some Reading on Excessive Fee Cases and Other Timely ERISA Topics</title>
<link>http://www.bostonerisalaw.com/archives/401k-plans-passing-along-some-reading-on-excessive-fee-cases-and-other-timely-erisa-topics.html</link>
<description><![CDATA[<p>What would this blog be if it was done as a newsletter instead? Well, probably something like this new <a href="http://www.proskauer.com/news_publications/newsletters/erisa/2008_03_31/_res/id=sa_PDF/16030-040008-ERISA%20Litigation%20Newsletter.pdf">ERISA newsletter</a> out of Proskauer Rose, with its detailed but readable length discussions of current events in the field, such as the Supreme Court&rsquo;s recent decision in <em>LaRue </em>and the Supreme Court&rsquo;s consideration of whether to hear a case that will allow it to return again to the problem of defining the available scope of equitable relief under ERISA. For me personally, I particularly liked the discussion of the latest trends at the trial level in the federal court system with regard to lawsuits filed over allegedly excessive fees charged on mutual fund investment options, as it takes an approach that I like to pursue whenever possible in my own posts here on this blog: it discusses the early decisions on the issue at the motions stage in the trial courts, and looks ahead to what this may mean for the industry as a whole and service providers. Its worth a read, and if you enjoy this blog, you will almost certainly enjoy this newsletter as well.</p>]]></description>
<dc:subject>401(k) Plans</dc:subject>
<dc:creator>Stephen D. Rosenberg</dc:creator>
<dc:date>2008-04-16T09:54:41-05:00</dc:date>
</item>
<item rdf:about="http://www.bostonerisalaw.com/archives/fiduciaries-what-happens-when-erisa-and-the-law-of-insurance-coverage-collide.html">
<title>What Happens When ERISA and the Law of Insurance Coverage Collide?</title>
<link>http://www.bostonerisalaw.com/archives/fiduciaries-what-happens-when-erisa-and-the-law-of-insurance-coverage-collide.html</link>
<description><![CDATA[<p>Wow, I guess this is really Seventh Circuit week here, with, I guess, a particular focus on the jurisprudence of Judge Easterbrook, whose opinion in <em>Baxter</em> I discussed in my last post. This time, I turn to his decision from Wednesday in <em><a href="http://www.bostonerisalaw.com/Federal Ins v. Arthur Anderson.pdf">Federal Insurance Co. v. Arthur Andersen</a></em>, which strikes right at the intersection of the two subject areas in the title of this blog, insurance and ERISA. The <em>Arthur Andersen</em> opinion concerns the extent of coverage, if any, for Arthur Andersen&rsquo;s massive settlement of lawsuits related to its retirement liabilities upon its well publicized, post-Enron collapse, under a policy covering breaches of fiduciary duty. The court found that there was no coverage, for a number of reasons, the most salient of which being that, first, the losses in question were the actual pension amounts, which the policy does not cover (it instead covers only other losses related to a pension plan, separate from the actual amount of the pension benefits in question), and second, that although the claims in question related to pension plans, they were not actually for breaches of fiduciary duty related to such plans, which is all that the policy actually responds to. There are some interesting lessons for plan sponsors and plan administrators in these findings: first, that it is important to remember that, in buying fiduciary liability coverage, this is not the same thing as insuring the benefits owed to pensioners themselves, and, second, that the exact scope of the coverage is narrow and limited by its exact terms, which may not extend coverage to the specific allegations of any particular lawsuit arising from the pension plan. What&rsquo;s the take away? A close look by an expert is needed when selecting insurance coverage for pension plans and the people who run them, if for no other reason than to have an accurate understanding of the extent to which potential problems with the plans may actually be covered. </p>
<p>Beyond these lessons in the case for people on the ERISA side of this blog&rsquo;s title, the decision provides a fascinating run through a number of complicated insurance coverage topics for those of you who are interested in the insurance coverage half of this blog&rsquo;s title. The judge - or perhaps his clerk, I don&rsquo;t know the practices in that particular court - writes fluidly on the law of estoppel, waiver, the duty to defend, and the respective rights of the insurer and the insured when it comes to control of the defense and settlement of a covered lawsuit.</p>]]></description>
<dc:subject>Fiduciaries</dc:subject>
<dc:creator>Stephen D. Rosenberg</dc:creator>
<dc:date>2008-04-11T12:57:28-05:00</dc:date>
</item>
<item rdf:about="http://www.bostonerisalaw.com/archives/401k-plans-what-larue-wrought.html">
<title>What LaRue Wrought</title>
<link>http://www.bostonerisalaw.com/archives/401k-plans-what-larue-wrought.html</link>
<description><![CDATA[<p>Suzanne Wynn has the story of the day when it comes to ERISA litigation, as she <a href="http://qualifiedpensionconsulting.com/ppablog/2008/04/07/7th-circuit-applies-supreme-courts-decision-in-larue-to-defined-contribution-overvalued-stock-lawsuit/">posts</a> on the Seventh Circuit&rsquo;s application of <em>LaRue</em> to exactly the type of case that, had the Supreme Court ruled otherwise, would have gone away without any potential liability on the part of the fiduciaries or, for that matter, recovery by the plan participant. The case, as Suzanne explains, concerns a single plan participant who charges plan fiduciaries with breaches of fiduciary duty related to the amount of company stock held in that particular participant&rsquo;s account; the plaintiff&rsquo;s theory holds that the fiduciaries breached their duties because they &ldquo;allowed participants to invest in [company] stock despite knowing that the stock was overpriced and therefore was a &lsquo;bad deal&rsquo;.&rdquo; The Seventh Circuit recognized that, after <em>LaRue</em>, a plan participant can move forward with such a claim, at least in terms of having standing to pursue relief that is not plan wide. </p>
<p>The Seventh Circuit&rsquo;s decision touches on a number of themes that are not fully addressed in the opinion, but which really rest at the crossroads that the law of ERISA finds itself at today. The first has to do with the extent to which <em>LaRue</em> will or will not increase litigation. I have previously discussed that, in my view, the real impact of <em>LaRue</em> is that the types of cases, such as stock drop cases of the kind considered by the Seventh Circuit in this case, that in the past would only be brought if the scale was sufficient to attract the interest of the organized plaintiffs&rsquo; class action bar, will now be brought in many instances even if the scale is insufficient to give rise to class or plan wide litigation. Rather, as this case illustrates perfectly, these types of theories will be pressed now if even only one participant has enough loss to warrant the action, as <em>LaRue</em> expressly authorizes and as occurred in this case. This is where you will see the impact of <em>LaRue</em> with regard to expanding litigation, not necessarily in terms of a massive increase in numbers of suits, but rather in an incremental increase in the types and natures of suits brought against fiduciaries. And don&rsquo;t kid yourself - as the baby boomer generation moves towards retirement, there are going to be a huge number of plan participants in 401(k) and ESOP plans and the like who have large enough accounts and holdings (for instance of company stock) for it to be worth their while to bring these types of suits if their accounts take a significant hit. </p>
<p>The second that I wanted to mention relates to something that is certainly not going to be news to any long time reader of this blog, and its certainly not an idea unique to me, namely, the fact that, in the aftermath of judicial and political responses to the growth - and some would say overuse - of class action securities litigation, the plaintiffs&rsquo; bar has begun using ERISA to prosecute what are in essence securities fraud claims of the kind that, in the past, would have been simply litigated under the securities laws. The plaintiffs&rsquo; bar has found that, given the evolution of the securities laws and of ERISA, ERISA may well be the better theory to prosecute in stock drop type cases. The swarm of litigation already being filed over the collapse of the Bear Stearns stock is a perfect example of the type of event that we have long been conditioned to expect to be litigated under the securities laws, but which is instead generating putative class actions under ERISA related to the company&rsquo;s ESOP and other retirement vehicles. Among the many issues that this evolution in securities related litigation raises is how to integrate the securities laws and ERISA under these types of scenarios, to prevent ERISA from being distorted from its original purpose and transformed instead into simply some type of alternative securities law regime; Judge Easterbrook, writing for the Seventh Circuit, raises exactly these points, but doesn&rsquo;t resolve them, noting instead that they will have to be developed in the future. </p>
<p>The case is <em><a href="http://www.bostonerisalaw.com/Rodgers v Baxter 7th.pdf">Rogers v. Baxter International</a></em>, and thanks to Suzanne for bringing it to my attention.</p>]]></description>
<dc:subject>401(k) Plans</dc:subject>
<dc:creator>Stephen D. Rosenberg</dc:creator>
<dc:date>2008-04-08T10:48:44-05:00</dc:date>
</item>


</rdf:RDF>