One Household, One Plan: Why the Survivor Path Belongs in Your Software, Not a Spreadsheet

The projections are on the table, the rebalancing is approved, and the annual review is winding down when Elena — 61, the younger spouse — asks the question the whole meeting was actually about: "If something happens to Miguel first… am I okay?"

You have a spreadsheet for the household. It is a good spreadsheet — forty tabs, linked assumptions, a projection page you are honestly proud of. And the truthful answer to Elena's question, the one you don't say out loud, is: *"I'll have to get back to you."* Because the spreadsheet models the couple. It does not model the couple ending — and every number Elena needs lives on the other side of that event.

This is not a spreadsheet problem you patch with one more tab. It is an architecture problem: the survivor path either lives inside the planning model, or it does not exist.

Two Single Plans Are Not a Household

The workaround most practices reach for takes one of two shapes, and both quietly fail:

• Two separate single-person plans. One projection for Miguel, one for Elena. Now expenses are double-counted or arbitrarily split, joint filing is impossible to represent honestly, one spouse's Social Security claiming interacts with nothing, and there is no moment at which one plan hands its assets, income, and tax attributes to the other. The one event that most changes each plan — the other person's death — is exactly the event neither plan can see.
• One undifferentiated pot. A single projection with combined balances and combined spending. Cleaner, but now the model cannot answer whose benefit stops, whose account has which tax treatment, which pension has which survivor election, or what the survivor's filing status does to the same withdrawals. When one spouse dies, an undifferentiated pot just… keeps projecting, as if nothing happened.

A couple is neither of those things. A couple is one household with two lives, two benefit streams, two account structures, and one shared tax return that will someday become a single one. The model has to know all of that at once.

What Actually Changes on the Survivor Path

The survivor path is not a smaller version of the couple's plan. It is a structurally different plan, and it differs in ways a static model cannot fake:

• One Social Security check stops. The survivor generally keeps the larger of the two benefits; the smaller one ends. A household drawing two checks becomes a household drawing one — a permanent income step-down that arrives in the same season as everything else on this list.
• Filing status flips to Single. The year of death is generally the couple's last joint return; after that, the survivor typically files Single. The bracket breakpoints for a single filer sit at roughly half the married levels across most of the schedule, and the standard deduction roughly halves. Similar income, meaningfully higher effective tax.
• The account structures merge — with rules. A surviving spouse can generally roll the decedent's IRA into their own, after which RMDs run on the combined balance at single-filer rates. The Roth/traditional/taxable mix the couple built now belongs to one person, and its sequencing logic changes.
• IRMAA thresholds drop to the single schedule. Roughly half the married levels. The same portfolio income that never touched a Medicare surcharge for the couple can put the survivor into one.
• The pension either continues or it doesn't. Whatever survivor election was made — often years earlier, often irrevocably — now executes: 100%, 75%, 50%, or nothing.
• Withdrawal sequencing spans both spouses' account types. Which account funds year one of survivorship — his traditional IRA, her Roth, the joint taxable account — changes the tax bill materially. A sequence that was optimal for the couple can be exactly wrong for the survivor.

Every item on that list is conditional on who dies first and when — which is precisely the dimension a spreadsheet holds constant.

The Spreadsheet Was Never Built for This

To model the survivor path honestly, a tool has to do four things on demand:

• Re-project from the event. Recompute income, filing status, deductions, RMDs, and Medicare surcharges from the year of death forward — not apply a haircut to the couple's numbers.
• Run the event in both directions. "He dies first at 78" and "she dies first at 78" are different plans, with different survivors, different retained benefits, and different tax pictures. Both matter, because nobody knows the order.
• Move the event. A death at 70 and a death at 88 produce different survivor plans. The question is not one scenario; it is a family of scenarios.
• Stay current. Balances, law, and brackets move every year; the survivor projection has to move with them, not live as a one-time study from three years ago.

A spreadsheet does none of this natively. It answers the question it was built for, with the filing status hard-coded into its tax cells — and the research on error rates in complex spreadsheets is not flattering. Each "what if he dies first" becomes an afternoon of manual surgery, so it gets done once, goes stale, and the next time the question comes up in a meeting, the honest answer is again "I'll get back to you."

The Answer Elena Actually Needed

Run it the way a household model runs it, with round, illustrative numbers. Miguel is 68, Elena is 61. Between them: his $1.1 million traditional IRA, her $250,000 403(b), a $300,000 joint taxable account, and two Social Security benefits — his $3,000 a month, hers $1,700.

Say Miguel dies at 79. The model applies the transition in order:

• Elena keeps the $3,000 benefit; the $1,700 stops. Household Social Security income falls by roughly a third.
• She rolls his IRA into her own. Her RMDs now run on the combined balance — a balance that spent eleven more years compounding — through the Single schedule.
• Her standard deduction roughly halves, her bracket breakpoints sit at roughly half the married levels, and the same RMD dollars land a bracket higher.
• Her IRMAA thresholds drop to the single table, and the RMD alone can put her over one.

The spreadsheet shortcut — "assume the survivor needs 80% of the couple's income" — sees none of this. It scales the spending side and misses that the tax-and-premium side moves in the opposite direction. The household model returns the number Elena actually asked for: whether her plan still funds her life to 95, after taxes, in the world where she is the one at the table. Sometimes the answer is yes, and the meeting becomes a celebration. When it is no, you have just found the highest-value work in the relationship — years before it is urgent.

Then run it the other direction. If Elena dies first at 79, Miguel's picture is different: he keeps his own larger benefit, inherits a smaller account, and his shorter remaining horizon changes the conversion math entirely. Neither direction is "the" answer; the pair of them is. And because the model holds the whole household, the pair costs two clicks — not two afternoons.

One Household, One Model

The alternative is structural: model the couple as a single household with the survivor path built in — not as an add-on study, but as a first-class scenario the engine can produce at any time.

This is how WiseNest is built, and one design decision matters for your practice more than any feature list: the account structure is abstracted away from the plan. Under the hood, a household might be a single account with spouse data alongside it, or two full member accounts in a Familia household — but neither you nor the plan ever branches on that. You ask for the survivor projection; the engine knows the structure, applies the transition — benefit retention, the filing-status flip, the rollover, the resequencing — and hands back the answer. Both directions of "who goes first." Same question, one click, every review.

The practical consequence: the survivor scenario stops being a research project and becomes an artifact of the review meeting — as routine as the net-worth page.

The Survivor Scenario as a Deliverable

The process recommendation, concretely:

• Put one page in every married-couple annual review: the survivor projection, both directions. Not triggered by illness, not saved for "estate season." A standing page normalizes the topic — it is planning, not prophecy.
• Present it with both spouses in the room. The younger spouse — statistically, often the wife, and often the one who has quietly held Elena's question for years — watches the plan hold with her at the center of it. That single page answers the question she may never have asked out loud.
• Let it drive decisions while they are cheap. The survivor page is where Roth-conversion urgency, insurance sizing, and the pension election stop being abstractions — the companion piece to this post covers those levers in depth.
• Bilingual households get it in both languages. In many of the families we serve, the two spouses read numbers in different languages. A deliverable each can read is not a nicety; it is comprehension of the plan's most emotionally weighted page.

Monday Morning

• List your married-couple households. For each, answer honestly: could you produce the survivor projection, both directions, inside the meeting, today?
• Retire the spreadsheet from this job. Keep it for what it is good at; the survivor path is not that.
• Add the survivor page to your next three annual reviews and watch what it unlocks — it is reliably the page clients pull closer across the table.
• Answer Elena in the meeting. The question was never hypothetical to her.

The couples in your book are one household each — not two plans, not a pot. Software that models them that way, survivor path included, turns the hardest question in the review into the moment the client remembers you were ready for it.