Video Reports

Embed this video

Copy Code

Link to this video

Get LinkEmbedLicenseRecommend (-)Print
Bookmark and Share

By Christine Benz | 09-27-2010 05:53 PM

Vanguard Ups International Exposure in Target Date Funds

Vanguard's decision to increase and broaden its exposure to international equities in its target date funds was to boost diversification, not expected returns, says John Ameriks

Christine Benz: Hi. I'm Christine Benz for Vanguard's target-date funds have always been very streamlined, but recent changes will make them even more so.

Here to discuss those changes is John Ameriks. He is Director of Investment Counseling and Research at Vanguard. John, thanks for being here.

John Ameriks: I'm glad to be here, Christine. Thank you.

Benz: So, a couple of changes announced over the past week that will actually make these funds even more minimalist than they were before. Can you talk about some of the changes that you're making?

Ameriks: Absolutely, and this is all about gaining efficiencies and broadening the diversification that's available in our target-date funds, and then more broadly in our Total International funds as well. But let me talk about target-date first.

As many folks know, in the Vanguard target-date funds, the international exposure historically had been derived from three funds that represented different markets, Emerging Pacific and Europe. The announcement we made today is going to involve exchanging the exposure that we are getting through those three funds and consolidating that in one fund, the Total International fund.

We think that we can make that change, and in that way give people a little bit more efficiency around how we get that exposure. For example, you've got one fund that tracks, now the MSCI Equity Ex-U.S. benchmark, which is a very broad-based benchmark. We won't have these issues with graduation in terms of when a country moves from an emerging category to either the Pacific or the European category. That won't happen now. So there are efficiencies that we're going to pick up that way.

We're also as part of this change, an earlier change we announced, change the benchmark to the MSCI Equity Ex-U.S. That means that the exposure in the international fund now includes a broader selection of countries; importantly, Canada and Israel are in that index, as well as we go deeper into the market capitalization. Basically, growth in global markets and efficiencies in terms of how we can operate these things is going to allow us to do that at what we expect to be the same expense ratios we currently have in the funds.

Benz: Okay. So, another change is that you are nudging up the international equity allocation within these portfolios. Can you discuss the thinking that went on behind that decision?

Ameriks: Sure. So this is something that actually we've been looking at and doing analysis on for many, many years now. In fact, if we go back to 2006, Vanguard had produced a paper on exactly how much international should someone hold, and the answer to that question was between 20% and 40% is what we thought was reasonable for an investor to hold.

We're moving to 30% of the equity allocation in the funds, which will be allocated non-U.S. So it was 20, we are going to go to 30; that's right in the middle of our range. And basically it reflects the growing size of the non-U.S. market, the transactional efficiencies that have basically increased over time in terms of investing outside of the United States, and a desire for broader diversification.

This is not about a difference in expected returns. We still take the view that over the very long horizons that someone who is in the target retirement fund needs to think about that U.S. versus a broadly diversified non-U.S. portfolio are going to generate roughly the same amount of return. It really is about diversification to make you sure you are getting exposure to as much of the global economy as you can.

Read Full Transcript
{0}-{1} of {2} Comments
{0}-{1} of {2} Comment
  • This post has been reported.
  • Comment removed for violation of Terms of Use ({0})
    Please create a username to comment on this article