Viewpoints

February 25th, 2020 | by

Using Factors to Rebalance a Client’s Portfolio

We normally think about investment risk factors—such as value or momentum—at the individual security level. We decided to test whether the same factor logic works at the asset-class level. Specifically, we studied whether applying the momentum factor is a useful tool to manage quantitative, tactical asset allocation and its byproduct—portfolio rebalancing—in an effective way.

Momentum is the well-researched tendency for security winners to keep winning (for a period of time) and losers to keep losing. We measured momentum at the asset class level over 12 months, and used absolute and relative scores to determine what asset classes in particular to tactically over- and underweight in a 60/40 portfolio. In this scenario, large-cap growth stocks compete against large-cap value, for example; small caps against large caps; international fixed income vs. U.S. fixed income; stocks vs. bonds vs. alternatives. We then compared the long-term investment results of this systematic asset allocation (from January 1976 to June 2019) with those of two other typical methods of rebalancing.

Strategy 1
In Strategy 1, we used a simple technique of rebalancing asset classes back to target allocation weights (e.g. 14.5% for large-cap growth, 12.5% for large value, 4% for global REITs, 31% for US bonds) each month. This method, which uses time rather than value as the trigger to rebalance, generated an annualized return of 9.3% for a 60/40 portfolio, 13.5% portfolio turnover, and an annual tax liability of 60 basis points for those investing in the presence of taxes.

Strategy 2
For Strategy 2, we set bands, or ranges, around asset classes, a very common rebalancing technique in the investment industry. Specifically, we set 10% bands, which implies that if an asset class with a target weight of 20% appreciates to a 22% weighting in the portfolio (or falls 10% to an 18% position), then rebalancing is triggered. Compared with Strategy 1, this rebalancing strategy generated a higher annualized return (9.5% vs. 9.3%), but a higher tax cost (90 instead of 60 basis points) and much higher (29%) portfolio turnover. When viewed through the lens of returns over various rolling-year periods, Strategy 2 boasted quite a high win-rate, beating Strategy 1 pretax in 74% of the 5-year periods, 88% of the 7-year time frames, and 93% of the 10-year rolling periods.

Strategy 3
For Strategy 3, we employed the momentum factor, allowing asset-class winners to drift higher with momentum and losers to drift lower than permitted by the target bands described in Strategy 2, and we permitted this allocation skew until the momentum signal reversed. For instance, by riding winners, the large-cap growth allocation (which had a benchmark allocation of 14.5%) had an average weighting of 15.7%, while in the second strategy it averaged 15.2%.

In our study, Strategy 3 generated the highest return (10.1% annualized), lower turnover (20%) than for Strategy 2, an 80 basis point tax cost, and the best risk-adjusted return (as measured by the Sharpe ratio*). In terms of batting average, Strategy 3 is a “slugger”, outperforming Strategy 1 in 97% of the 5-year rolling periods, and 100% of the 7- and 10-year periods.

*Sharpe Ratio is a measure used to help understand the return of an investment compared to its risk. Generally, the greater the value of the Sharpe ratio, the more attractive the risk-adjusted return.

Contact Us
[contact-form-7 id="6520" title="Sign Up For Our Mailing List"]
<div role="form" class="wpcf7" id="wpcf7-f6520-o2" lang="en-US" dir="ltr"> <div class="screen-reader-response" role="alert" aria-live="polite"></div> <form action="/viewpoints/using-factors-to-rebalance-a-clients-portfolio/#wpcf7-f6520-o2" method="post" class="wpcf7-form init" novalidate="novalidate"> <div style="display: none;"> <input type="hidden" name="_wpcf7" value="6520" /> <input type="hidden" name="_wpcf7_version" value="5.2.2" /> <input type="hidden" name="_wpcf7_locale" value="en_US" /> <input type="hidden" name="_wpcf7_unit_tag" value="wpcf7-f6520-o2" /> <input type="hidden" name="_wpcf7_container_post" value="0" /> <input type="hidden" name="_wpcf7_posted_data_hash" value="" /> <input type="hidden" name="_wpcf7_recaptcha_response" value="" /> </div> <div id="mb-form"> <p><span class="wpcf7-form-control-wrap FirstName"><input type="text" name="FirstName" value="" size="40" class="wpcf7-form-control wpcf7-text wpcf7-validates-as-required" id="FirstName" aria-required="true" aria-invalid="false" placeholder="First Name*" /></span> </p> <p><span class="wpcf7-form-control-wrap LastName"><input type="text" name="LastName" value="" size="40" class="wpcf7-form-control wpcf7-text wpcf7-validates-as-required" id="LastName" aria-required="true" aria-invalid="false" placeholder="Last Name*" /></span> </p> <p><span class="wpcf7-form-control-wrap Email"><input type="email" name="Email" value="" size="40" class="wpcf7-form-control wpcf7-text wpcf7-email wpcf7-validates-as-required wpcf7-validates-as-email" id="Email" aria-required="true" aria-invalid="false" placeholder="Email*" /></span> </p> <p><span class="wpcf7-form-control-wrap Phone"><input type="tel" name="Phone" value="" size="40" maxlength="10" minlength="10" class="wpcf7-form-control wpcf7-text wpcf7-tel wpcf7-validates-as-required wpcf7-validates-as-tel" id="Email" aria-required="true" aria-invalid="false" placeholder="Phone*" /></span> </p> <div class="hide"> <span class="wpcf7-form-control-wrap ctct-560"><span class="wpcf7-form-control wpcf7-ctct"><div><input type="hidden" value="1380445631" name="ctct-560[]" /> </div></span></span> </div> <p><span id="wpcf7-5f739b61e307f" class="wpcf7-form-control-wrap gf-hp-wrap" style="display:none !important; visibility:hidden !important;"><label class="hp-message">Please leave this field empty.</label><input class="wpcf7-form-control wpcf7-text" type="text" name="gf-hp" value="" size="40" tabindex="-1" autocomplete="nope" /></span></p> <div class="formcaptcha"> <div style="margin: 30px 0;"> </div> </div> <p><input type="submit" value="Submit" class="wpcf7-form-control wpcf7-submit" id="submit" /></p> </div> <div class="clear"></div> <div class="wpcf7-response-output" role="alert" aria-hidden="true"></div></form></div>