WhenMathMilestone Birthday Planner
Enter a birth date and the milestone ages you care about (18th, 21st, 30th, and so on). See each milestone's exact date.
Want to learn more?
Worked example
Born June 15, 2017, the 10th birthday falls on June 15, 2027, a straightforward non-leap-day case. Born February 29, 2016, instead, the same 10th milestone falls in 2026, a non-leap year, so under the Feb 28 policy the plan reports February 28, 2026, while switching to the Mar 1 policy for that identical birth date instead reports March 1, 2026, the same milestone landing one day later purely because of which policy was selected.
Common mistakes
- Forgetting to set the Feb 29 policy for a leap-day birthday. Without an explicit choice, most milestones would fall on a date that does not exist in most calendar years.
- Assuming both leap-day policies produce the same eventual date. Feb 28 and Mar 1 genuinely disagree by one full day for every affected milestone.
Limitations
This plans up to 50 milestone ages at once. It does not send reminders or notifications on its own, so each resulting date needs to be saved elsewhere to be acted on later.
Frequently asked questions
- Do milestones need to be entered in order?
- No, the ages entered are sorted automatically before the plan is generated, so they can be typed in any order.
- What happens on a Feb 29 birthday when the leap-day policy is set to Mar 1?
- Every milestone that would otherwise fall on February 29 of a non-leap year is rolled forward to March 1 of that year instead, consistently applying the same rule across the entire plan.