SSA.tools

https://ssa.tools/

SSA.tools vs OpenSocialSecurity

If you have run both the ssa.tools/strategy filing optimizer and OpenSocialSecurity, you may have noticed that the two tools sometimes recommend different optimal filing dates. This guide explains why that happens, and why, in almost every realistic case, the practical impact of choosing either tool's answer is small.

Both tools are well-built implementations of the same SSA rules. The differences come from defensible choices about uncertain inputs (how long you will live, whether the trust fund runs short) and from a handful of small implementation details. There is no single "right" set of those choices.

The Optimum Is a Neighborhood, Not a Point

The most important thing to know about filing-date optimization is that the expected-value curve is very flat near its peak. Filing a few months on either side of the "optimal" date barely changes your expected lifetime benefit. Here is the strategy grid for a typical single filer:

ssa.tools/strategy grid showing expected lifetime benefit for each filing month from age 62 to 70. The optimal filing month is 68 years 3 months at $103,341. Most cells within a year of the optimum are colored dark green, indicating they are within 99% of optimal.
Each cell shows the expected lifetime benefit if you file in that month, relative to the optimum.

The optimal filing month here is 68 years and 3 months, with an expected lifetime benefit of $103,341. Look at what happens around that peak:

  • Filing six months earlier (67y9m): about $171 less, or 99.8% of optimal.
  • Filing twelve months earlier (67y3m): about $300 less, or 99.7% of optimal.
  • Filing twelve months later (69y3m): about $637 less, or 99.4% of optimal.
  • Filing two full years early (66y3m): about $490 less, or 99.5% of optimal.

Over an entire lifetime of benefits, the difference between the absolute best month and any month within a year of it is a few hundred dollars. That is the key context to keep in mind: if two tools recommend filing dates that differ by a few months, the lifetime dollar gap between their answers is small, often smaller than the uncertainty in your own life expectancy or in next year's COLA.

Where the Two Tools Differ

With the flat-optimum context in mind, here are the differences that actually move recommendations between the two tools, in rough order of impact.

Mortality model

ssa.tools/strategy uses cohort life tables. These project expected mortality improvements forward through your lifetime, so a person born in 1960 gets mortality rates that reflect anticipated medical advances over the coming decades. OpenSocialSecurity uses period life tables, which apply a single year's observed mortality rates to all future ages. Period tables generally overstate mortality for younger cohorts. The practical effect: ssa.tools/strategy tends to recommend slightly later filing dates. See our mortality tables guide for more on the difference between cohort and period tables.

Trust-fund benefit cut

OpenSocialSecurity offers an option to model a future benefit cut at trust-fund exhaustion (default 23% in 2033). When that option is on, the optimizer values dollars before the cut more highly than dollars after, pushing recommended filing earlier. ssa.tools/strategy does not model a benefit cut. If you turn the cut option off in OpenSocialSecurity, the two tools will agree more closely on this dimension. (Whether to model a cut is a personal judgment about Congressional behavior; see our guide on whether Social Security will run out.)

Partial-year delayed retirement credits

SSA has a specific rule about delayed retirement credits: credits earned in a given calendar year do not actually apply to your benefit until January of the following year, except in the month you turn 70, when all accumulated credits apply immediately. ssa.tools/strategy implements this rule. OpenSocialSecurity instead applies all accumulated credits at the filing month, which makes filing late in a year (for example, age 69 and 11 months) look slightly more attractive than it really is in practice.

Rounding and discounting precision

The Social Security Administration rounds monthly benefits down to a whole dollar. ssa.tools/strategy follows that rule. OpenSocialSecurity does not, which produces a marginally higher annual figure, at most a few dollars per month.

ssa.tools/strategy also discounts future cash flows at monthly precision, while OpenSocialSecurity discounts at annual precision. Both differences are cosmetic and never meaningfully change which filing date the optimizer prefers.

What each tool models that the other does not

Beyond the differences above, the two tools have somewhat different feature sets. OpenSocialSecurity models several scenarios that ssa.tools/strategy does not, including the earnings test for people who keep working, benefit suspension after filing, divorced-spouse benefits, child benefits, the family maximum, and disability (for people currently on SSDI who will transition to retirement benefits at full retirement age).

The two tools also approach mortality flexibility differently. OpenSocialSecurity offers a menu of alternative life tables: period tables from several years, plus Society of Actuaries smoker and nonsmoker tables for users with specific actuarial preferences. ssa.tools/strategy combines a single cohort table with a continuous health-multiplier slider and an optional blended-gender mode. They are different shapes of the same underlying flexibility.

Bottom Line

The choice between filing at, say, 68 years and 0 months versus 68 years and 6 months is not the kind of decision worth agonizing over. The flat shape of the expected-value curve means that any date in the neighborhood the two tools agree on is a good answer. Pick the tool whose interface and inputs you prefer, file within a few months of its suggested date, and turn your attention to the bigger questions in your retirement plan.

Related Guides