Might as well throw in quarterly while at it :)

quarterly definitely! Monthly would be nice as well. It’s really hard to mentally look at an entire year and see where my “retirement” falls.

Yes… quarterly, monthly (which is really a year at a glance).

Discord thread with some good back-and-forth on this topic: https://discord.com/channels/869222901054857216/1078050976142987305

I think this is needed to allow modeling changes in income or major expenses mid year with at least quarterly, ideally monthly. E.g retiring mid year with partial year of regular income and partial year of retirement income. Thanks

I think I would like to see this one - month granularity would probably be enough

My birthday is in October and notionally I can say I would like to retire at 60

But my company pays yearly bonus in February so I would be really dumb to retire before that’s in the bank.

On the other hand I don’t want to go on working until 61 - ideally I would retire exactly at the end of the UK tax year April 5th so as not to find myself over paying tax and having to claim it back and not be able to prise the overpayment from the taxman grasp until the following year.

One unfortunate consequence of a yearly granularity is your milestones get kicked out for a full year depending on what happens. For example, if I am to retire at 62 but I try to model buying a new car at 55, it’ll say I’ll retire at 63. In actuality, if I use https://engaging-data.com/fire-calculator and try to model as closely as I can to PL, it says it’ll take an extra 2.4 months.

Monthly granularity would be so useful.

I plan most things by monthly basis so I would like this a lot.

I’d like to be able to use the projections for monthly budget planning, not just yearly milestones.

I would like monthly. I check my accounts monthly and having the month of retirement or starting SS would improve accuracy of projections.

Agree, monthly adds a much better resolution to the plan and can make significant difference. Most people don’t collect a full 12 months when they first start collecting a pension or begin drawing down their assets.

Final year of employment would likely be a full year as well.

I would like monthly, too.

Per my comment in discord https://discord.com/channels/869222901054857216/1230176992263934003

Agreeing with earlier comments – there are lots of things that happen during a year that could affect plans, e.g. bonuses for employed people, tax payments, big purchases on certain dates. And for people approaching retirement, the ability to know the value of “just another month” (or six) is also important. One more important date for retirement/tax reasons – a birthday! E.g. when someone turns 55 while working with a 401K or when someone turns 59 1/2… or when someone turns 70 and wants to plug in Social Security right away…

Very interested in monthly granularity in order to see how smaller changes to current income could affect my retirement date by less than a year.

Monthly changes would be incredibly helpful

this is exactly my use case and why I am asking for this feature.

It’s not clear from the description, but this granularity must include specifying Retirement Date for “myself” and “spouse” to the same level of granulatiry (ideally monthly).

IMO adding this granularity for the retirement date is most important. Granularity can be added incrementally to different functions/values.

It would be great to be able to plan in a finer granularity like weekly or per fortnight (like a cashflow management system).

I acknowledge that there might be certain aspects that might require some thought as there are some assumptions of annual period (e.g. Tax event) that needs to make them work with a weekly/monthly granularity. However, having a projection graph that works with short-term financial planning would greatly enhance this app.

strongly agree with this.

I can’t agree with anything finer than monthly. You’re kidding yourself if you think you can accurately predict anything to a daily or weekly level. Even the monthly level makes little sense more than a few years in the future.

I find value in granular projections not because I expect perfect accuracy, but because they help illustrate the impact of small decisions. Seeing how an extra $100/month might move my retirement date by X weeks gives me better insight than monthly estimates alone. It’s not about following an exact timeline - it just helps me understand how small changes add up over time.

Monthly granularity is really important and I can’t develop an accurate plan without it because I expect to retire around 6 month between birthdays.

Can this Feature be simplified to just all month granularity for all events? That would provide the biggest bang for the buck. After using it, if people still want quarterly or more granular events they can make a new case for those changes.

To my mind the importance is convenience – I start SS on my birthday, or I retire in August – if PL can simulate mid-year changes, then I don’t have to do what I do now – add single-year expenses/income to account for the partial year. It’s a quality of life thing so far as I can see, nothing more (but an important one).

The developer/mathematician in me wonders if Kyle could preserve the annual nature of the simulation, and simply add a layer that automates adding partial-year events on the ends of our streams. So if I tell the PL frontend that I’m starting SS in April of 2025, you convert that to a stream of annual SS income from 2026 forward, plus a single year at the beginning earning 2/3 of the annual total.

The monthly breakdown could be nice for modeling, but honestly part of my challenge is the way the data is displayed. I’m < 5 years from retirement, so when i look at the plans its honestly hard to tell what year it is, with how the plans from current date are done. If I know I’m going to retire in June (just not sure which year) - then planning in december is confusing in the app.