Use the Retirement goal's What If tab to compare a temporary scenario with the saved plan. Running the scenario does not save its assumptions to the household.

You can also search for Retirement What If in the command bar to open this tab directly.

Selecting another goal tab or leaving the goal clears What If inputs and results. Saved changes to inputs What If reads also reset it. Record assumptions and results before leaving.

Check the saved retirement assumptions and assigned accounts first, because the scenario starts from that household's existing plan. A change to an input does not refresh an already displayed result until you run again. For explanations of the underlying inputs and outputs, see Retirement Goal: Assumptions and Projection.

What If lets you test retirement ages, returns, withdrawal order, the plan's ending year, legacy amount, base spending, and a Social Security reduction. The available rows depend on the saved plan.

Each adult with a retirement age has a [Name] retires at row. The other controls include Investment return, Withdrawal order, Plan end year, Legacy amount, and Base annual spending. Retirement return and Return glide duration appear when the saved plan has a retirement return configured. Social Security cut appears when the household has Social Security income.

Select a starting point, review changed rows, and run the plan. Each starting point replaces the draft inputs instead of stacking on another preset; edit individual rows afterward for a combined comparison. A starting point that would change nothing for this household is hidden.

In Retirement What If, Starting points fills scenario inputs; select Run plan afterward to calculate a comparison. Returns 1% lower lowers Investment return by one percentage point and also lowers Retirement return when the saved plan has one.

Spending +$12k/yr adds $12,000 to Base annual spending. Retire 5 years earlier and Retire 5 years later shift each adult's saved retirement age by five years. Earlier retirement is limited to next year; review any adjustment note. Social Security pays 77% applies a 23% reduction to saved Social Security amounts.

Only starting points that change this household appear. Both retirement buttons are absent if no adult has a retirement age. Record an existing scenario before selecting another starting point, because the new preset replaces its inputs.

Change Base annual spending in What If to test a different ongoing spending level. This changes the base amount while retaining saved spending items that start or end at particular times.

For example, compare a saved $120,000 base with a $108,000 alternative. A saved future care allowance remains in both scenarios; reducing the base does not delete that allowance.

Spending that ends rows are subtracted from the base and added back on their own schedules. Lowering the base reduces only its ongoing remainder.

If the base falls below the sum of those rows, the remainder stops at $0; each ending row still counts in full until it ends.

What If does not provide a separate editor for each dated spending row. Record the scenario before leaving What If, which clears it. To change dated rows, use the saved Plan's Adjust spending editor, following Retirement Goal: Assumptions and Projection, and restore any temporary edits afterward.

In What If, Find earliest retirement age searches for the first date where required monthly savings is covered by current monthly savings into the goal's assigned accounts, including applicable employer match, within a $1 tolerance. It does not increase savings to make an earlier date work.

In What If, first set any non-age assumptions you want to hold fixed, such as spending or returns. Then select Find earliest retirement age.

The search replaces the draft retirement-age values while keeping those other scenario edits, and displays Earliest workable retirement when it finds a result. It runs the comparison automatically; a separate Run plan click is unnecessary.

If the found date produces no change from the saved plan, no separate Scenario result is shown.

The search shifts the adults' saved retirement ages together. For future retirees, its earliest dates are limited to next year; it searches up to 15 years later than the saved retirement ages. Read the returned ages and any adjustment note, especially when the adults have different retirement dates.

“No date found — Not funded within 15 years at current savings” means no workable date was found within the search, not that retirement is impossible under every set of assumptions. Missing adult retirement ages also prevent a useful search.

Review spending, assets, savings, and timing before drawing a conclusion. The returned scenario is temporary and does not update Household retirement ages.

Yes, when its timing is tied to retirement. At plan retirement moves with the year the first adult retires; At [Name]'s retirement moves with that adult's retirement year. A specific year and At a person's age stay anchored to that year or age.

Before creating a scenario, open the Retirement goal's Plan → Adjust spending. For new spending check Starts and Ends; for spending that ends, check Ends.

Leaving What If to do this clears any existing scenario, so record it first. Use the timing that matches the intended assumption.

Changing that row edits the saved plan, so record the original setting if the change is temporary.

For example, healthcare that starts at retirement and ends at age 65 can span more years in an earlier-retirement scenario. An expense set to start in a particular calendar year does not move just because retirement moves. An end set a number of years after the start follows the resolved start date.

What If recalculates the saved spending schedules using the scenario's ages. Check the timing settings themselves when an expense appears not to move; renaming the row “retirement healthcare” does not link its dates.

What If can move Social Security claiming timing through a retirement-age change when the benefit starts at that person's retirement. It has no separate claiming-age control that leaves all other retirement-linked items unchanged.

Check the saved benefit's timing and entry mode first; Entering Social Security in Kerdora explains those inputs. In What If, change the recipient's [Name] retires at, select Run plan, and compare the result. Repeat for another age after recording the first comparison.

With PIA entry, Kerdora adjusts the benefit using the claiming age implied by the start timing, within its 62–70 window. With Manual entry, moving the start does not automatically replace the entered benefit with an age-adjusted amount.

This is a combined retirement-date comparison. It can also move wages, spending, contributions with retirement-linked dates, and other income. A benefit tied to a fixed age, fixed year, or Full Retirement Age does not move merely because a retirement age changes.

For a claiming-only test, record the original Profile income settings, change only that benefit's Starts, and review retirement results. PIA adjusts the amount; Manual needs the appropriate benefit amount. These are saved edits: restore the original timing, mode, and amount unless adopting the change.

Social Security pays 77% is a What If starting point that reduces the household's Social Security amounts by 23% for that scenario. It is an assumption to test, not a statement that a benefit cut will occur.

Select Social Security pays 77%, review Social Security cut, and select Run plan. You can enter a different reduction percentage instead.

The reduction applies to all Social Security income records in the household. It does not choose a claiming age or move a fixed start date.

For a PIA record, the reduction is applied to PIA before the claiming adjustment. For Manual entry, it scales the entered amount while preserving its frequency. Each run starts from the saved amounts, so repeated runs do not repeatedly reduce the previous scenario's already-reduced benefit.

The field and starting point are absent when there is no Social Security income to reduce. To add or correct the source benefit, see Entering Social Security in Kerdora. Select Reset when finished testing the reduction.

Retirement What If compares the saved Current plan with the last-run Scenario; Change shows the difference. Select Table for every result row. Chart retains only Spending supported in the table and adds a chart.

Spending supported compares supported spending with each plan's spending pattern. Reducing requested spending can raise its percentage; check the dollar amounts too. When essential coverage is available for both plans, Table includes Essentials supported, capped at 100%.

Needed monthly savings or Needed yearly savings is the full requirement, not the increase above current savings, and always uses today's dollars. Target at retirement is the required starting balance; Projected at retirement is what current funding reaches. First-year spending supported shows the first retirement year's supported amount.

Use Monthly / Yearly and Today's $ / Future $ to choose presentation. Pre-tax / After-tax changes Spending supported and First-year spending supported; it doesn't alter saved assumptions. Needed savings retains today's-dollar basis regardless of that display choice.

Use Show current plan to clear the displayed comparison without clearing the draft inputs. Use Reset to clear the scenario edits and results.

After editing any assumption, select Run plan again; the previous result can remain visible while new inputs are waiting to run. Read warnings or adjustment notes before presenting the comparison.

What If has no Apply or Save-to-plan action. Record the agreed assumptions and results before switching tabs: leaving What If clears its inputs and results. Then make those changes in the saved Retirement Plan or the relevant Profile records.

For retirement ages, spending, returns, withdrawal order, horizon, or legacy, use the corresponding controls in the Retirement goal's Plan. An age change there updates Household.

A claiming-only Social Security change belongs in the income record described in Entering Social Security in Kerdora. Review the saved result after the changes.

Temporary What If results are not a stored library of named alternatives and do not become client Guide content just because you ran them. Review the saved retirement content and explanation you intend to share through the normal Guide workflow.

Use What If for discussion before editing the saved plan. If a run fails, check the displayed error, reset the draft, and retry one change. If the problem persists, contact Kerdora Support with the goal, exact assumptions, and error text. Do not treat a result left from an earlier run as the failed scenario's result.