# screening agent auto-advanced internal referrals from a stale spreadsheet - the list had 2-year-old names

## TL;DR

The referral list lived in a spreadsheet nobody updated for two years, and the agent auto-advanced everyone on it. Source referrals from the live HRIS or referral system, expire entries, and require re-verification. A spreadsheet is not a system of record.

```text
screening agent auto-advanced internal referrals from stale spreadsheet - 2-year-old names
```

## Steps

1. Confirm the staleness: check the spreadsheet's last-modified date and sample the names against the current employee roster.
   Expected: Most names are gone.

2. Switch the source to the live referral system or HRIS with an API.
   Expected: Referrals reflect current employees.

3. Expire referral entries: a referral older than the policy window (e.g. 12 months) needs re-confirmation.
   Expected: Stale referrals lapse.

4. Review the auto-advanced candidates from the bad window; some may not be real referrals.
   Expected: The damage is assessed.

5. Delete the spreadsheet as a source and redirect its users to the live system.
   Expected: The stale source cannot be used again.

## When to use

- referral auto-advance uses a spreadsheet
- referred candidates are not current employees' referrals
- the list has no owner

## When not to use

- the list is current and owned (then it is a fine source)
- referrals are verified per candidate already (the staleness does not matter)
- the spreadsheet is the system of record by policy (give it an owner and a refresh cadence)

## Tool compatibility

- any referral workflow
- HRIS APIs

## Variant phrasings

- "stale spreadsheet referrals auto-advance"
- "referral list 2 years old"
- "outdated referral list screening"

## Why it happens

Spreadsheets are where data goes to fossilize: no owner, no refresh, no expiry, but the agent treated it as current truth. Employee referrals are valuable signal, which is exactly why acting on a fossilized list is harmful: it advances strangers while real referrals wait.

## Edge cases

- even live systems need expiry; employees leave and referrals go stale there too
- the migration needs a cutover date; dual-sourcing creates its own confusion
- audit who was advanced from the stale list for fairness review

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_7bWA2wZ8y_p5XK8F-jfJiA
