Skip to main content
PGIM LogoPGIM Logo
  • About
    • Diversity, Equity and Inclusion
    • Contact Us
  • INSIGHTS
  • DC Themes

    • DC Plan Sponsor Survey
    • Financial Wellness
    • Retirement Income
    • Target Date Funds
  • Solutions
    • Target Date Funds
    • Advice Solutions
    • Retirement Spending Portfolios
  • Careers

    • Careers at PGIM
    • Job Opportunities
""
White Paper

Rebalancing 401(k) Core Menus to Make Them Retirement ReadyRebalancing401(k)CoreMenustoMakeThemRetirementReady

Jan 26, 2022

1 min

Download research paper

The role of the core menu in defined contribution (DC) plans has changed considerably over the last decade as default investments, target-date funds in particular, continue to capture participant attention and assets. This evolution requires plan sponsors and consultants to revisit key assumptions about optimal core menu design, especially as plan sponsors increasingly seek to retain retiree assets, which, in turn, necessitates that plans offer attractive solutions for older participants.

This paper uses data from 11,643 401(k) plans to better understand where asset class coverage gaps exist across core menus and quantifies the portfolio implications associated with the gaps. Two key potential improvements are noted.

First, core menus could potentially benefit from a “rebalance” to better accommodate the participants who are most likely to use them. Younger participants are much more likely to use default investments (e.g., target-date funds) while older participants, who tend to invest more conservatively, are much more likely to use the core menu. This is in direct contrast with common core menu design, where there are typically significantly more equity funds than fixed income funds (roughly three to one). The relatively high proportion of equity funds makes it not only difficult to build efficient conservative portfolios, but it may also lead to excess risk taking among participants (i.e., if the participant follows a naïve allocation strategy or chases returns).

Second, core menus are not currently designed to be “retirement ready.” Efficient retirement portfolios look different than efficient accumulation portfolios given the more focused objective of generating an income stream, and unfortunately the key building blocks for efficient retirement portfolios are generally missing from DC core menus. The portfolio efficiency costs of these gaps can be staggering, exceeding roughly 100 bps on alpha-equivalent basis. The most notable gaps in asset class coverage include inflation-linked bonds, high yield bonds, commodities, and real estate, although adding other asset classes, such as long-term bonds, may be worth considering.

While some plan sponsors may hesitate to expand core menus given past research on the topic (e.g., research noting negative relationship between core menu size and plan participation1) it’s important to realize that a lot of existing research may be less applicable today, given the fact it took place before the broad adoption of automatic enrollment and prepackaged asset allocation solutions, such as target-date funds. Core menus don’t necessarily need to be bigger, though, they just need to be smarter: it is possible to consolidate a few of the riskier (equity) options to make room for retirement-focused strategies.

Creating a truly optimal DC core menu requires a certain degree of art and science that will vary by plan. This research suggests, though, that most core menus today need to be revisited before they can truly be considered optimal for those most likely to use them.

Download research paper
  • INSIGHTS

    • The Accidental Plan Sponsor Podcast
  • DC THEMES

    • DC Plan Sponsor Survey
    • Financial Wellness
    • Retirement Income
    • Target Date Funds
  • SOLUTIONS

    • Target Date Funds
    • Advice Solutions
    • Retirement Spending Portfolios
  • OTHER RESOURCES

    • Careers at PGIM
    • Contact Us
    • Diversity, Equity & Inclusion
    • Form CRS
    • Job Opportunities
    • Request for Information
PGIM Logo
  • Terms & Conditions
  • Privacy Policy
  • Accessibility Help
  • Cookie Preference Center

All investments involve risk, including the possible loss of capital.

PGIM DC Solutions LLC ("PGIM DC Solutions") is an SEC-registered investment adviser, a Delaware limited liability company, and an indirect wholly-owned subsidiary of PGIM, Inc. ("PGIM"), the principal asset management business of Prudential Financial, Inc. ("PFI") of the United States of America. Registration with the SEC does not imply a certain level of skill or training. PFI of the United States is not affiliated in any manner with Prudential plc incorporated in the United Kingdom or with Prudential Assurance Company, a subsidiary of M&G plc, incorporated in the United Kingdom.

The content and materials presented here are for informational, illustrative and educational purposes only and should not be construed as investment advice or an offer or solicitation in respect of any products or services to any persons who are prohibited from receiving such information under the laws applicable to their place of citizenship, domicile or residence. The information presented is not a recommendation about managing or investing retirement savings and does not take into account individual investment objectives or financial situations.

PGIM DC Solutions aims to help participants achieve their retirement goals through their suite of “PGIM RetireWell™” solutions. These solutions may include a range of investment options including target date portfolios, retirement income strategies, and managed accounts that can be coupled with our proprietary advice engine. There is no guarantee that investment or retirement goals will be achieved.  Use of the term “RetireWell” and any related phrase is not intended to indicate that such- goals will be achieved.

PGIM, PGIM DC Solutions logo and the Rock design are service marks of PFI and its related entities, registered in many jurisdictions worldwide.

© 2025 PGIM DC Solutions. All Rights Reserved.

PGIM Logo
PGIM Logo

You are viewing this page in preview mode.

Edit Page