Planned
Increase scheduling precision
In order to increase accuracy, I’d recommend PL allow specific date-based entries (start/end points), as opposed to the far more general year-based entries. For example, PL may know I’m retiring in 2028, but there’s a huge different in January and December of 2028. The latter date would include 11 more months of salary in the math, not to mention the 11-month deferment of drawdowns from investments. It also affects eventual Social Security, although not to a huge degree. Ultimately, this level of precision would help set PL apart from OnTrajectory which also unfortunately limits to entire years–a very imprecise way to plan.