GoalsMapper calculates age using Age Last Birthday based on the current date, and performs some of the projections on a monthly basis (CPF). 

This means your age increases immediately when your birthday passes — and your entire financial timeline updates accordingly.

What happens when your birthday passes?

Example:

• You created a goal at age 45

• Goal set to happen at age 50

• At the time of creation → 5 years away

After your birthday:

• You turn 46

• The system recalculates from your new current age

• The same goal at age 50 is now 4 years away

If a goal was set very close to your current age (e.g. age 46), once you turn 46, it may appear as happening “this year” or slightly in the past depending on the projection month.

The goal itself has not been removed or altered — the timeline has simply updated to reflect your real age progression.

Why doesn’t GoalsMapper lock age for the whole calendar year?

Some systems keep a user at the same age for the entire year (e.g. 45 from January to December).

However, GoalsMapper uses exact-date progression because:

• CPF modelling (55 Retirement Account, 65 CPF LIFE) must align accurately

• Retirement timing depends on exact birthday dates

• Locking age by calendar year may overstate time available

We prioritise financial accuracy over calendar simplification.

Recommended Solution

If a goal or scenario was created very close to your upcoming birthday, you may:

✔ Adjust the goal age forward by 1 year

Example:

• Goal created at age 45

• Birthday is in 1–2 months

• Instead of targeting age 50, revise to age 51

This preserves your intended time horizon and prevents the goal from appearing too close or in the past after your birthday passes.