What Can a Chief Retirement Officer Do for You?
This is so simple, its brilliant, and so brilliant, its simple – or something like that. The “this” I am talking about is the idea of appointing a Chief Retirement Officer, or CRO, as is discussed – and proposed – in Steff Chalk’s article, “The Advent of the Chief Retirement Officer,” in the latest issue of NAPANet. Essentially, he proposes that companies appoint a senior officer with overall responsibility for retirement plans, whether they be pensions, 401(k)s or what not. CROs would have responsibility for the types of issues that bedevil plans in the courtroom, such as overseeing revenue sharing and fees, as well as for the type of operational issues that often invoke fiduciary liability and equitable relief risks, such as the communication errors in Osberg. The brilliance and the simplicity of the idea stem from the exact same data point: it is the lack of knowledge, lack of interest, lack of time and lack of concern by company officials appointed to committees overseeing retirement plans, and who are just moonlighting in that role from what they consider their real jobs (like CFO, etc.) that are the cause of an awful lot of operational failures, litigation exposures, fiduciary liability risks and large settlements in the world of retirement plans.
I spoke and blogged recently about the nature of fiduciary liabilities in plan governance operations, and the theme of both my speaking and writing was the fact that officers overseeing plans are often shoehorning that work into the cracks in their otherwise busy schedules. By this, I don’t mean to suggest anything malevolent, or even intentional. Rather, it is just a fact of life. Counsel to plans are not loathe to note that they have to make a call as to how much of a governance committee’s limited time to tie up with a particular issue. Moreover, court decisions reflect that fiduciary breaches are often based on actions taken with limited discussion, limited knowledge and with a limited investment of time. When I say this, bear in mind that I am talking about cases that are litigated to at least the summary judgment stage, providing a factual basis for a court to find such facts; as a result, the cases I am describing are outliers, rather than a representative sample. Nonetheless, they still reflect the fact that it is the lack of expertise and the insufficient investment of human capital at the highest level of a plan sponsor that is often at the heart of fiduciary liabilities. Indeed, it is hard not to think of a major decision that ran in favor of participants in this area that did not have, among its factual bases, at least some evidence that those making the challenged decisions were ignorant about a key fact or important element of the investment world: think, for instance, of the key role in Tibble of the lack of knowledge about the nature of retail and investment fund choices.
And that’s the beauty of the CRO idea: the assignment of duties related to retirement plans to one individual who not only has the expertise to do the job well, but also has that as his or her only assigned job duties. If the nature of a fiduciary breach is found in an imprudent process – and it is – the assignment of such duties to a properly selected and qualified CRO with the time to do the work is a walking, talking barrel of evidence that a prudent process existed.