-
Discord thread with some good back-and-forth on this topic: https://discord.com/channels/869222901054857216/1078050976142987305
-
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.
-
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…
-
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.