Entered a duplicate here: https://changemap.co/projectifi/projectifi/task/9690-future-starting-amount-should-reflect-inflation-x/#comment-10735

Future “Starting amount” should reflect inflation +X%

Future amounts are currently not inflating using +X% to model expenses outpacing inflation (e.g. health care, college).

From forum: I think what might be a clean way to support a feature like that could be: a new third option in the starting amount type menu, e.g. “Actual Currency”, “Today’s Currency”, and “Actual Currency (Adjusted)”, or something like that.

Related: discord.com/channels/869222901054857216/1164698486554497034

A possible UI suggestion:

In the CHANGE OVER TIME section of an Expense, two check boxes, one of which must always be checked. (ie. if you uncheck the current checked box, the other one is automatically selected):

[X] Change Over Time starts now [ ] Change Over Time starts when Expense begins

As an aside, would it make any sense to have this option as well? I can’t personally think of a reason (and it might create some odd computation behaviors) but perhaps there’s a use case… [ ] Change Over Time starts at {Other Milestone}

Adding the CHANGE OVER TIME option to certain Income types might make a lot of sense as well (Inheritance, Custom Income, etc.)

Additionally, separating out the ‘Value Change Over Time’ portion of the DURING OWNERSHIP section of Real Assets into its own CHANGE OVER TIME subsection, might add UX consistency.

Or more simply, each Income / Expense / Asset item should have a CHANGE OVER TIME section with the checkboxes listed above.

Hopefully this is clear enough and is of some help.

Cheers.

I like the ideas above, but IMHO it doesn’t even need a UI change. Adjusting the future expense using the Yearly Change value should just be the default behavior.

d

Would love this feature! Great for things like college that are far away and price increases much higher than inflation

I agree having the options as suggested would be best, the default value should have always been over all time not just at start of the event.

I would like the ability for the CONTROL POINTS to be in milestones, or as an age vs. only a year counter.

Example #1 Control Point #1: @Before Current Year — $5000 Control Point #2: @Me Retirement — $15,000 Control Point #4: @Me in LTC – $0

Example #2 Control Point #1: @Now — $5000 Control Point #2: @Me age 65 — $15,000 Control Point #3: @Me age 72 – $25,000 Control Point #4: @Me age 90 – $50,000 Control Point #5: @Me age 105 – $50,000

This way I can set up the ADVANCED CHANGE OVER TIME table to represent values that shows $ change over time, and the first control point is not the year this item was triggered. The START & STOP date of the (Income/Expense/Asset/CFP) item is when this item gets triggered, and represents which ‘slice’ of this table to model out.

Easiest scenario is a Death Benefit that grows over time, so would be nice to enter the schedule into the ADVANCED EDITOR showing between ‘now’ and age ‘100’ what the benefit would be, and then configure the Income event to trigger Once@Me End-of-Life....and then PL would pick up the value from the table which corresponds to the death benefit of the age/year of my end-of-life milestone.

The other scenario is a table representing the yearly LTC Benefit over time (how much the LTC Insurance would pay during that year if I went into a LTC facility that year), and using the triggering event of start=move_to_LTC_facility, and stop=end_of_life, PL could dynamically model out the income during that (3yr) slice of time.

At the moment PL assumes that Year 1 (control point #1) starts when this item is triggered. I would like the ability to have PL dynamically determine which (triggering event start/stop defined) slice of time of this table is used when the triggering event hits.