Lookback questions sound simple until someone says "thirty days prior" and three people pick three different Mondays. Finance wants the invoice window. Legal wants the notice period. Support wants to know whether a ticket is inside a refund window. The form above is the unglamorous fix: reference date, days backward, one earlier date you can drop into a log line.
The start field is your anchor—not always today. A filing might count backward from the due date. An audit might count from the incident. A warranty email might count from delivery while you are reading it on a Tuesday. Put the date the rule actually names in the box, then run the count. Using "today" because it is convenient is how teams discover their spreadsheet was fine and their anchor was wrong.
This page moves in calendar days. Saturdays and Sundays count unless the policy says business days. If you need the gap between two dates you already have on paper, switch to the April 9 to May 9, 2026 day span instead of stepping backward from one end.
Retention windows and "about a month ago"
People round. Systems do not. Thirty days before an anchor is a popular policy shape—trial lookbacks, prior-statement requests, "changes in the last 30 days" tickets. Thirty days before May 9, 2026 is a good default to compare against a wall calendar; "about a month" might be 28 or 31 depending on where you land.
Longer lookbacks show up in compliance language more than chat. Ninety days before the same anchor is the kind of phrase everyone repeats until someone needs the actual date for a export filter. Whole-week wording is common too—the four weeks before May 9 check saves mental division when the memo speaks in weeks.
Forward counts belong on the sibling page. If the question is when a period ends, not when it started, forty-five days forward from May 9 is the habit that matches how deadlines are usually phrased.
Before you paste the date into a ticket
Double-check the detail line under the result—it restates how many days you stepped back from which anchor. Copy that anchor beside the answer so the thread does not re-litigate it Friday. If you estimated first ("roughly three weeks ago"), run the real count afterward; month boundaries and February still surprise people who skip the calculator.
- Anchor matches the document (due date, incident, delivery—not an arbitrary today).
- You know calendar days vs business days for this rule.
- Timezone midnight issues will not matter for your use (this is date-only).
Investigation and log work often pairs day lookbacks with time-of-day questions; the audit trail time-ago note is worth a skim when friendly "2 days ago" labels need to match exported timestamps.
Ordinary reference math, not legal advice. When the date matters, keep the anchor and the day count with the answer so Future You does not reverse the window from memory.