Lookback questions often arrive as a year count. Compliance wants records for the last five years ending on a filing date. HR asks when a system went live if the contract was signed "about three years back." A family timeline says the move was four years before the wedding date on the invite. Everyone repeats the year number; exports and filters need the actual day. The fields above are the blunt fix: anchor, years backward, one date to paste.
This page steps back by calendar years, not by multiplying 365. May 9, 2026 minus one year lands on May 9, 2025; anchors on February 29th land on the last valid day in non-leap years—the same anniversary logic as moving forward, reversed. Policies that say "within eighteen months" are month-shaped—eighteen months before May 9, 2026—not a year count.
The start field should be the date the rule names: period end, incident, audit as-of—not "today" because the tab was handy. Subtracting 2026 minus 2023 in your head is a different habit than stepping three calendar years back from a real anchor.
Retention windows and chart year labels
Dashboards show 2023 through 2026 and people call it "three years" while the span is partial at both ends. Running the real anchor once beats arguing from labels. Three years before May 9, 2026 is a common audit shape worth checking on a wall calendar before anyone pulls data.
Longer holds show up in grants and insurance more than chat. Five years before the same anchor is the phrase people mix up with "1825 days" when the PDF never switched units. When both endpoints are already fixed, January 1, 2020 through January 1, 2026 in years answers span between dates, not step-back from one point.
Forward cliffs belong elsewhere
Vesting and renewal dates that point ahead—not back—live on the from-now page. Five years forward from May 9 is an easy swap to get wrong in a long email thread. The default thirty in the form is a stress test; most real questions are smaller and still worth running once after a mental estimate.
Before the date lands in a query or slide, read the detail line and watch February anchors. Plenty of people run it twice after using purchase date instead of activation.
- Whole years only; partial-year rules may need months or days.
- Contract "years" can mean anniversary dates—read the clause.
- Copy anchor plus year count beside the answer for next year's thread.
Multi-year lookbacks are where inclusive endpoints argue; the long-range year planning note helps when one day shifts the story.
Ordinary reference math, not legal advice. When the date matters, keep the reference event and the year count with the answer.