## TL;DR
Renewal dates flow from contracts into the CRM through integrations and human hands, and each path can move them: a sync reading signature date instead of term end, an amendment overwriting the original, a timezone-shifted import. Compare the CRM date against the signed contract for a sample of accounts; the pattern of errors names the path.

```text
renewal date wrong in CRM: forecast data corrupted
```

## Use this when
- Forecast shows renewals in the wrong quarter or month
- CSMs plan outreach too late or too early for accounts
- An integration, import, or amendment process recently ran

## Not for this skill when
- One CSM entered one date wrong, a coaching matter
- The contract itself was amended and the CRM is actually right

## Steps
1. Sample 15 accounts and compare CRM renewal dates to signed contract term-end dates. Verify: the error rate and direction (early, late, shifted) are measured
2. Group the errors by how each date entered the CRM: integration, import, amendment, or manual. Verify: the faulty path accounts for most errors
3. Read that path's field mapping or process for the date it actually writes. Verify: the wrong source field or step is identified
4. Fix the mapping or process, then bulk-correct dates from the contract system of record. Verify: CRM dates match contracts across the sample on re-check
5. Add a monthly contract-versus-CRM date audit with a variance report to RevOps. Verify: date corruption cannot silently rebuild

## Variant phrasings
### renewal date wrong in CRM
A related phrasing for the same underlying problem.
### forecast quarter wrong from dates
A related phrasing for the same underlying problem.
### sync writing wrong renewal date
A related phrasing for the same underlying problem.

Compatibility: Compatibility: CRM renewal fields (Salesforce, HubSpot) synced with contract systems (Ironclad, DocuSign CLM, billing), current versions.

## Why it happens
Dates are the forecast's skeleton; a systematic date error moves revenue across quarters and mistimes every playbook. Sampling against signed contracts converts suspicion into an error pattern, and error patterns point at exactly one ingestion path.

## Edge cases / pitfalls
- Amendments legitimately change dates. The contract system, not the original agreement, is the comparison source.
- Partial corrections are worse than none: a half-fixed book makes every remaining date suspect. Correct from the system of record in one pass.
- Renewal outreach timing depends on these dates, so notify CSMs which accounts' dates moved and by how much.

## Provenance

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