How Do You Know If You're Still On Track Once Life Changes?

A plan doesn't go wrong. It goes stale.

When you first run a retirement plan, every number in it is correct for that moment: your balance, your spending, your target retirement age, the market conditions baked into the projection. None of that is a mistake. The problem is that not one of those inputs holds still. The market moves — up, down, sideways — every single day. Your spending shifts as your life does: a kid moves out, a health issue shows up, a hobby gets more expensive or less. You get a raise, or you don't get the raise you expected. Your target retirement age drifts, sometimes without you consciously deciding it should.

None of that invalidates the original calculation. It just means the calculation needs to be run again, with the current numbers, to still mean anything. A plan built eighteen months ago isn't wrong today — it's answering a question about eighteen months ago. The honest version of "am I on track" has to be asked in the present tense, repeatedly, not answered once and filed away.

And almost nobody does this with any real cadence. Most people build a plan once — for a mortgage application, a conversation with a parent, a New Year's resolution — and then don't open it again until something forces them to: a scary headline, a birthday that feels significant, a job loss. The plan sits there, technically correct and practically useless, because the world underneath it has moved on without it.

Why "check back in a year" isn't specific enough

Even people who accept the idea of periodic check-ins often stop at the vaguest possible version of it: glance at the number, feel reassured or alarmed, move on. That's better than nothing, but it throws away the part that's actually useful.

A single success-rate number, on its own, can't tell you why it changed. If your plan showed 91% six months ago and shows 85% today, that six-point drop could come from a dozen different places, and they don't call for the same response:

• The market had a rough stretch, and your portfolio balance is genuinely lower than projected. This is largely outside your control — the honest response is usually to keep the plan running and see how the next few check-ins look, not to overreact to one bad quarter.
• You increased your spending — a new car payment, more travel, a renovation — and the plan is correctly reflecting a real decision you made. This one you can act on directly, because you're the one who moved the input.
• You pulled your target retirement age closer, or reduced how much you're contributing. Same story: a decision you made, showing up honestly in the math.

The number alone doesn't distinguish these. What does is comparing the inputs behind each check-in, not just the headline rate — which numbers actually moved between one snapshot and the next. That's the difference between "something changed, no idea what" and "my spending is up 12% and that's the entire story; the market barely moved." The second version tells you exactly where to look if you want to do something about it. The first is just anxiety with a percentage sign on it.

A success rate that dropped tells you something happened. Only the inputs behind it tell you whether it was something you did, or something the market did.

Why one snapshot in isolation misleads you

There's a second failure mode, and it catches people who do revisit their plan periodically: looking at the current reading in isolation, with no memory of what came before it. A single check-in, on its own, can't tell you whether it's an anomaly or the continuation of a pattern — and that distinction changes what, if anything, you should do about it.

Picture two people who both see a success rate of 84% at their latest check-in:

• The first person's last check-in, three months ago, also read 84%. Before that, 85%. The number is essentially flat — noise around a stable plan. There's nothing here that calls for a reaction.
• The second person's last three check-ins read 93%, 89%, 84% — a steady, consistent slide over the same stretch of time. Same number today, completely different story. This isn't noise. It's a trend, and a trend usually has a cause worth finding, because it's more likely to keep going than to reverse on its own.

Without the history, both people see the identical snapshot and have no way to tell which situation they're in. With the trajectory, the second person has a real signal to act on — and the first person can reasonably ignore a number that would otherwise look concerning in isolation. This is the actual value of tracking a plan over time: not the current reading, but the shape of the readings that led to it.

A worked example

Consider someone who checks in on their plan every few months over about a year and a half. Their success rate looks like this:

Looked at as a single number, "80%, down from 92%" reads like a plan quietly falling apart. Looked at as a trajectory with the inputs attached, a different story emerges: the market's contribution to the decline was small and partly temporary — it recovered, then stayed roughly flat. Nearly the entire twelve-point drop tracks two specific spending increases, both real decisions, both things this person can see clearly and choose to address. The most recent check-in, where spending held steady and the rate barely moved, is actually a good sign — it suggests the decline has stopped, not that it's accelerating. None of that is visible in the headline number alone. It only shows up when the check-ins are compared to each other, not read one at a time.

What Progress and check-ins actually do

This is what the free Progress feature in the app is built around. Save a snapshot whenever something changes — a market move you noticed, a spending shift, a raise, a different target age — and the app keeps a record of your success rate and the inputs behind it at each point. Months later, you see the trajectory: where the plan held steady, where it drifted, and which specific decisions actually carried the load. Instead of comparing snapshots in your head — or not comparing them at all, because that's tedious and easy to skip — the AI Advisor reads the trajectory and tells you what's driving it.

That's a materially different question than "what's my success rate right now." It's closer to "what's actually been happening to my plan, and is it something I caused or something that happened to me" — which is the version of the question that tells you what to do next, if anything.

The honest limitation

None of this works if it isn't used. A check-in system is a tool for the discipline of revisiting a plan — it removes the friction of comparing numbers by hand and makes the trajectory visible instead of buried in memory, but it can't make anyone open the app. If the plan only gets checked once, there's no trajectory to read, and this is no better than the single-glance version it's meant to replace. The value compounds with use, the same way the underlying plan itself does. A snapshot saved sporadically, whenever you happen to remember, still beats never checking at all — but it's a weaker signal than a plan checked with real consistency, because gaps in the record are gaps in the story.

It's also worth saying plainly: a rising or falling success rate over time is still a projection, not a verdict. It reflects the inputs you gave it and the assumptions behind the simulation, tested against a range of plausible market outcomes — not a guarantee about what will actually happen. The trajectory is real information. It isn't a countdown clock.

Common questions