The Retirement Navigator Called a Drawdown Account a Pension
One arrives no matter what happens next. One is a decision made every month. The Navigator filed both under the same word.
I ran an internal retirement profile through the Navigator I’d been building — full accounts, claimed benefits, foreign pension history, and a retirement date close enough to expose planning errors. I’ve rounded the financial figures here and removed identifying details. The account types, the classification failure, the planning consequence, and the fix are unchanged.
This wasn’t the Medicare case again. That failure was a missing document — the context wasn’t in the room. This time the context was in the room. The number came out right. The plan was still wrong.
The profile included two pieces of foreign retirement income: a state pension with a fixed monthly benefit, and a second account whose provider called it a pension but whose behavior was something else. I entered both. The Navigator put both in the pension bucket.
One of them wasn’t.
The Friction
The second account was a SIPP — a UK self-invested personal pension held in flexi-access drawdown. The name has “pension” in it. The behavior does not. The pot was worth a mid-six-figure sum, fully crystallised, with nothing currently being drawn. Withdrawals are discretionary: amount, timing, and continuation all remain choices, not obligations. The planned drawdown — roughly $3,000 a month once retirement starts — is a target that can be revised, not a payment that’s owed.
Compare that to the state pension in the same profile: a little over $1,000 a month, starting on a fixed date, guaranteed, no discretion involved. Same country of origin. Same shape on a spreadsheet — a number, a start date. Structurally, they have nothing in common.
The Navigator’s income-floor calculation depends on that distinction. A guaranteed source can count toward the floor because it arrives without a later decision. A self-managed drawdown account cannot. It is exposed to sequence risk, withdrawal discipline, and market performance. Treat the drawdown account as a pension and the income floor is overstated — not by a rounding error, but by a category. The number would have been right. The kind of promise behind the number would have been wrong.
The source document didn’t make this easier. The SIPP illustration was a scanned “Print to PDF” — image-only, no extractable text layer. It took a manual conversion pass before a single figure could be read out of it. By the time the data reached the Navigator, it had passed through a format that actively resisted structured entry — the kind of friction that makes “just call it a pension, it’s close enough” an understandable shortcut, not a careless one.
The Build
The fix wasn’t a bug patch. It was a change to the onboarding classification path itself: a flexi-access drawdown account can no longer enter the pension bucket by default. The routing logic — not just a written policy note — now sends this account type to “no pension,” with the drawdown figure entered separately under retirement accounts, a bucket already built into the schema for exactly this kind of self-managed source. An override exists for the rare case where a foreign account genuinely pays a fixed sum, but it requires an explicit flag, not a default assumption.
The same session exposed a second category error. The profile’s Social Security benefit had two figures at once: a gross benefit around $2,000, and a net deposit meaningfully lower. The gap wasn’t a Navigator error — it was two real, temporary billing distortions stacked on top of each other: an income-related surcharge under appeal (the wrong tier had been applied), and a credit from a coverage transition that hadn’t yet been applied. The net figure was accurate, in the narrow sense that it’s what actually deposits today. It was also not the number retirement planning should use, because it was temporarily wrong for reasons that had nothing to do with the actual long-term benefit.
The fix here is narrower than “always use gross.” The policy: treat the gross figure as the canonical benefit value for long-term planning, and track durable deductions — Medicare premiums, tax withholding, anything that reliably recurs — separately, rather than letting a temporarily distorted net deposit stand in for the benefit itself. Don’t revise the canonical figure until the appeal resolves and the correction is confirmed, not just expected. Gross benefit and spendable floor are not the same object; the Navigator has to preserve both rather than letting a temporary net deposit overwrite either one.
A third piece of the same session closed a related gap. A single flag — whether Social Security has already been claimed — now controls every place in the Navigator where advice depends on claim status. Once true, the “you could delay claiming for a larger benefit” tip disappears from the results screen. It’s not just unhelpful once someone has claimed — it’s wrong, and leaving it visible would have been actively misleading. In its place, an earnings-test awareness card appears: the $24,480-a-year limit the SSA applies to anyone drawing Social Security before full retirement age while still earning income, with the specific date that constraint lifts.
The Insight
The same discipline sat underneath both corrections.
The rule isn’t “check the label.” It’s: before an income source enters the floor, ask two questions. First — is this obligated or discretionary? A pension, a state benefit, an annuity payment is legally or contractually bound to arrive, on a schedule, regardless of what happens next. A drawdown account, an investment balance, a business’s future income depends on decisions that haven’t been finished, or markets nobody controls. Second — is the figure in front of you the stable promise, or a distorted instance of it? A benefit can be genuinely guaranteed and still show up, in a given month, as the wrong number — because of a billing dispute, a transition credit, an administrative delay that has nothing to do with the underlying entitlement. The first branch classifies the source. The second protects the canonical value once the source has been classified.
I logged this as the Guarantee Test. The drawdown account failed the first question: no fixed payment, no schedule, no obligation — only the provider label. The Social Security figure passed the first question and failed the second: the benefit is genuinely guaranteed, but the net deposit on the statement, that month, was not the number the guarantee actually promises.
Both failures produce the same downstream damage. A retirement Navigator that can’t apply the Guarantee Test — both branches of it — to every income source a profile names will silently distort the one number the whole plan depends on: the floor. Sometimes by counting a choice as a guarantee. Sometimes by counting a temporary distortion as the guarantee’s true value.
The Honest Part
The Navigator didn’t catch either misclassification. A person did — reviewing the profile and recognizing that “pension” had been applied to an account that doesn’t behave like one, and that a net deposit looked suspiciously low against a known gross benefit. There’s no structural check yet that flags a mismatch between an account’s stated behavior (no fixed payment, discretionary withdrawal) and the bucket a session assigns it to. The correction is now encoded as a routing rule for this specific account type. It is not yet a general rule the system applies to the next profile with a different country’s version of the same structure — a Canadian RRIF, an Australian superannuation drawdown, a 401(k) in payout phase. Those would need their own pass through the same test, and nothing in the current build runs that pass automatically.
The next build requirement isn’t a longer list of foreign account names. It’s an uncertainty gate: if an account has no fixed payment obligation and no guaranteed schedule, the Navigator should refuse the pension bucket by default until the source’s promise type is explicitly resolved — rather than defaulting to whichever label sounds closest. The durable version asks behavior questions before accepting provider labels: fixed payment, fixed schedule, contractual obligation, user discretion, market exposure.
The Social Security fix has a similar gap. Recognizing that a net figure looked suspiciously distorted relative to the known gross benefit was a judgment call made by a person, not detected by the system. And the sample size here is one profile, corrected in a single extended session. It demonstrates that the failure mode is real and that the fix is buildable. It does not demonstrate that the fix generalizes cleanly to income structures this test didn’t hit, or that someone without domain-specific pension knowledge would catch a misclassification like this themselves rather than trusting the Navigator’s first pass.
What This Is Actually About
This is the same argument the Medicare Navigator made, aimed at a harder failure. There, the risk was a generic model answering from a range because the actual document wasn’t in the room. Here, the document was in the room, the number was extracted correctly, and the plan was still wrong — because the number landed in the wrong category, and a wrong category looks exactly like a right one on a results screen. $3,000 a month reads the same whether it’s guaranteed or chosen.
That’s a harder failure to catch than a missing document, because nothing about it looks broken. The Navigator didn’t hedge, didn’t flag low confidence, didn’t ask a clarifying question. It took a clear answer and filed it under the nearest familiar label — pension — because that’s the word people use for “money that shows up every month,” even when the account behind it works nothing like a pension.
This generalizes only where a system is calculating a floor. A floor is not a forecast. It’s the part of a plan that’s supposed to survive bad conditions. If discretionary, reversible, or temporarily distorted numbers enter that layer as guarantees, the system hasn’t made the plan safer — it’s made the overstatement harder to see.
Case Study Insight: A number, a category, and a promise are different claims. A retirement Navigator can extract the right figure and still overstate the floor if it mistakes a choice for a guarantee, or a distorted deposit for the benefit itself.
Robert Ford builds products, writes stories and essays, and publishes The Intelligence Engine — a practitioner research publication about AI systems that compound. His other writing lives at Brittle Views.