|
DC Plans Underperformed DB FundsBy Chris Flynn, Manager Defined Contribution Investment Benchmarking, and Hubert Lum, Research Director, CEM Benchmarking Inc. at www.cembenchmarking.com. Defined Contribution plans underperformed Defined Benefit funds by a wide margin over a long period-by 1.8% per year over the eight-year period ending in December 2005. On an annual basis, DC plans underperformed DB funds for seven consecutive years, through up and down markets, to 2005. The findings were based on the CEM investment performance databases, which comprised 616 DC plans with total assets of $500 billion and 1,323 DB funds with total assets of $2 trillion. Table 1 shows the performance difference between DC plans and DB funds.
What is the effect of this 1.8% difference on the DC participant's future account value? At the end of 25 years, the effect is a reduction in that participant's future account value by 34%. The stakes are high so an understanding of the reasons for this underperformance is valuable. The key driver for the under performance of DC plans was differences in asset mix. Large holdings of under performing GICs, company stock and cash reduced the return of DC participants. This group of assets accounted for 41% of DC plan assets but only 1% of DB fund assets. These assets crowded out better performing asset classes such as foreign stock, real estate and alternative investments. These better performing asset categories made up only 4% of DC plan assets compared with 24% of DB fund assets. Table 2 shows the asset mix differences. The largest negative impact on DC plan returns was produced by company stock. From 1998 to 2005, the average compound return on company stock was 1.7% compared with 4.8% for the S&P 500 or 6.0% for the Lehman Aggregate Bond Index. Further, the increase in risk through holdings of company stock was noteworthy. Over the eight-year period, the standard deviation in returns for company stock was 38%. This volatility was twice that of the S&P 500.
While DC plan sponsors do not invest participant assets, they have several levers to influence participant asset mix. The place with perhaps the greatest potential to influence participant asset mix is the default option. Behavioral finance suggests that participants are likely to leave their contributions in the default option because of inertia. CEM research has shown that assets in an investment option, when designated as the default, were 2.3 times higher than assets in the same option when it was not the default.
Therefore, if a DC plan sponsor wants the asset mix of its participants to resemble the asset mix of a DB fund, then the DC plan sponsor should use a balanced fund option as the default option. However, Table 3 shows that the most common default options for most funds in the CEM database were GICs, stable value and cash.
Another important driver of the DC participant asset mix is the matching option. Again, if the intention is make the DC plan look more like a DB plan, then the DC sponsor should match with a balanced fund option or with cash and a balanced fund default. However, Table 4 shows that 31% of plans still match employee contributions with company stock.
The final key driver of the DC participant asset mix is the investment options offered. This influences the DC plan participant asset mix in two ways. First, if an asset class is not offered, participants cannot invest in it. Table 5 shows that a large proportion of funds in the CEM database failed to offer several important asset classes.
Second, investment options influence asset mix based on the "1/n" behavioral finance rule. This rule describes naïve diversification whereby a participant allocates contributions evenly among the n investment options offered by the DC plan . This may partly explain the low bond holdings of the average DC plan asset mix relative to the average DB asset mix. Table 6 shows that, in 2005, the average DC plan had 15 investment options but, typically, only one of these was a bond option. It is not surprising then that investments in this important DB asset class were relatively small. |