# offer-letter agent sent the wrong salary band - it read the comp grid from last quarter's cached file

## TL;DR

The agent read a cached comp file instead of the live grid, so the offer carried stale bands. Point the agent at the live compensation source, version-stamp every lookup, and require the band's effective date on the offer. Stale comp data is a legal and trust problem, not just a data problem.

```text
offer-letter agent sent the wrong salary band - cached comp grid from last quarter
```

## Steps

1. Confirm the staleness: compare the band in the sent offer against the current comp grid and the cached file's timestamp.
   Expected: The file predates the current quarter.

2. Switch the agent to the live comp source (API or current file) and remove the cached path.
   Expected: Lookups hit current data.

3. Add version stamping: every offer records the comp version and effective date it used.
   Expected: Each offer is auditable to a comp version.

4. Require a human approval step for offers where the band changed since the candidate's first touch.
   Expected: Changed bands get eyes before they go out.

5. Alert on comp-source staleness: if the source has not refreshed on schedule, page before offers go out.
   Expected: Stale data never silently feeds offers.

## When to use

- an offer carried outdated salary bands
- the agent reads comp from a cached file
- comp grids update quarterly

## When not to use

- the band was correct but the candidate disputes it (negotiation, not a bug)
- comp is pulled live already (check the offer approval flow instead)
- the error is in equity or bonus math (different calculation)

## Tool compatibility

- any offer-generation agent
- comp grid API or file

## Variant phrasings

- "offer letter wrong salary band stale"
- "agent used cached comp grid"
- "outdated compensation band offer"

## Why it happens

Compensation grids update on a cycle, and agents cache aggressively to avoid slow lookups. A cached file from last quarter is silently wrong the day the new grid publishes. The offer is a commitment; generating it from stale data creates renegotiations and erodes candidate trust.

## Edge cases

- the live source needs its own freshness check; a broken refresh looks like current data
- version-stamp the candidate-facing letter too, so disputes resolve to a specific grid
- mid-cycle off-band exceptions need a human path; the agent should escalate, not improvise

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_581hN4Sm3PGtZzU4UlrNSg
