Lookback questions often arrive in weeks. A clinic letter says follow-up was six weeks ago. A manager asks what shipped three weeks back. Someone in a thread writes "about eight weeks prior" and the spreadsheet filter needs an actual date. The fields above are the dull fix: anchor date, weeks backward, one earlier day you can paste into a ticket or query.
The start field is the reference—not always today. Retention rules count backward from a filing date. Warranty language counts from delivery while you are reading the email on a Tuesday. Incident reviews count from the report date. Convenience "today" is a common mistake; the math can be perfect while the anchor was wrong.
Each week here is seven calendar days, weekends included. Policies that mean business days or instructional weeks without holidays are a different question. If both endpoints are already on paper, the weeks from mid-March through May 9, 2026 may be clearer than stepping back from one end alone.
"About a month ago" vs a week count
People round; exports do not. Four weeks before an anchor is a shape people say out loud before anyone writes the Monday. Four weeks before May 9, 2026 is a quick sanity check against a wall calendar—"roughly a month" might be 28 or 31 depending where you land.
When the memo switches to days—"thirty days prior"—thirty days before the same anchor keeps units honest without multiplying by seven in the meeting. Shorter windows show up in support and finance: two weeks before May 9 is the kind of refund or trial lookback people estimate first, then verify once.
Long lookbacks and the forward habit
The default thirty in the form is deliberately long—quarterly reviews, long treatment intervals, "when did this program start if we are week thirty now" kinds of questions. Thirty weeks before May 9, 2026 crosses enough months that mental subtraction drifts. Deadlines that point ahead, not back, belong on the sibling page—six weeks forward from that date matches how due dates are usually phrased.
Before you paste the date into Slack or a SQL filter, read the detail line under the result. Plenty of people run it twice after realizing they anchored on received instead of postmarked. Copy the reference date beside the answer so Friday's thread does not rebuild the window from memory.
- Whole weeks only; odd day counts belong on the days-ago form.
- Calendar days unless your policy explicitly says otherwise.
- Date-only here—midnight timezone edge cases are outside this form.
Log and audit work sometimes mixes week lookbacks with time-of-day labels; the audit trail time-ago note helps when friendly "two days ago" copy has to match exported timestamps.
Ordinary reference math, not legal advice. When the date matters, keep the anchor and the week count with the answer.