# Agents need the business clock in the answer instead of an optional tool

Fiscal years and as-of dates belong in every response the agent reads.

By Ki Moon · 2026-10-28 · technique · current
Canonical: https://kihmoon.com/bench-notes/p/business-clock-in-the-answer/

**Symptom:** Answers about "this quarter" use calendar quarters for a company whose fiscal year starts in another month, and date windows drift from the data.

Many companies run a fiscal year that doesn't start in January, and some datasets are pinned to an as-of date rather than today. An agent doing date math from the wall clock and calendar quarters gets both wrong.

A fiscal calendar kept in free-text instructions reaches only the interface that reads them.

Agents don't reliably call an optional tool, and a separate tool helps only when the agent thinks to ask. Putting the values in tool responses, or on the records themselves, works better.

The wall clock is also the wrong anchor for an organization whose data is frozen at a past date, because windows measured from today slide past the data and recent history drops out of answers.

In a synthetic test set of 1,000 activities pinned to a past as-of date, windows anchored on today's date returned no rows for "last 90 days" or "this quarter"; windows anchored on the as-of date and the fiscal calendar returned 118 and 11. The set shows the mechanism, not how common it is.

## Check your setup (read-only)

Find the last 5 agent answers in your transcripts that name a quarter, a week or "today". For each answer, compare the dates it used with the CRM's fiscal calendar. Read the transcript before the answer for a read of the fiscal calendar and of the data's as-of date. Any date mismatch is a gap. An answer given without reading both dates is also a gap.

**Passes if:** In all 5 sampled answers the dates match the fiscal calendar, and each transcript shows both reads before the answer.

**Access needed:** agent-transcripts, crm-read

## If it fails (changes to make later, not part of the check)

1. Return timezone, as-of date and fiscal-year bounds in the tool responses the agent already reads.
2. Tell agents to read those values from the tool responses before any date math.
3. Anchor every relative window on the organization's as-of date, not the server clock. Relative windows include "last 30 days" and "this quarter".
4. Store the fiscal calendar as structured fields, never only in free-text instructions.

**Applies if:** Your agents or digests answer this-quarter or last-week questions, and your CRM's fiscal year starts outside January or data is pinned to a past date.

**Skip if:** Your CRM's fiscal calendar uses calendar quarters, its data is live, and all users share one timezone.

Tags: time, agents
