> ## Documentation Index
> Fetch the complete documentation index at: https://hc.pillargtm.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Renewals

> Renewal tracking with risk scoring and disposition lifecycle

# Renewals

Renewals track upcoming and historical contract renewals. Each renewal carries a multi-variable risk score and follows a structured disposition lifecycle.

## Core Information

| Field        | Description                           |
| ------------ | ------------------------------------- |
| Account      | Parent account                        |
| ARR          | Annual Recurring Revenue at stake     |
| Renewal Date | Contract renewal date                 |
| Disposition  | Current renewal lifecycle state       |
| Risk Score   | 0-100 renewal risk (higher = riskier) |
| Risk Level   | Low, medium, high, or critical        |
| Owner        | Renewal owner (CSM or AE)             |
| Auto-Renew   | Whether the contract auto-renews      |
| Save Play    | Active save play if risk is elevated  |

## Risk Scoring

Renewal risk is computed from 8 weighted variables covering engagement trends, stakeholder stability, support health, contracting activity, executive sponsorship, customer satisfaction, payment patterns, and market context. See [Renewal Risk](/scoring/renewal-risk) for details.

## Disposition Lifecycle

```
NOT_YET_DUE → APPROACHING → URGENT → SAVE_IN_PROGRESS → RESOLVED/RENEWED/CHURNED
```

| Disposition        | Description                         |
| ------------------ | ----------------------------------- |
| NOT\_YET\_DUE      | Renewal is far out                  |
| APPROACHING        | Renewal is approaching (30-90 days) |
| URGENT             | Renewal is imminent (under 30 days) |
| SAVE\_IN\_PROGRESS | Active save play running            |
| RESOLVED           | Risk mitigated, renewal expected    |
| RENEWED            | Contract renewed (terminal)         |
| CHURNED            | Customer lost (terminal)            |