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

# Renewal review

> Keep your renewal book current and run the weekly renewal call — the biggest lever on your forecast.

Renewals is where you keep your renewal book current and run your weekly renewal call. The calls you make here are the single biggest lever on your forecast — they flow straight into the projection — so this is where most of your forward number gets shaped.

## What Renewals shows

Your renewal book, grouped by when each contract comes up: expired, next 30 days, 31–60, 61–90, and beyond 90. A running **total at risk** sums the [ARR](/get-started/glossary) coming up in the next 90 days, so you can see your near-term exposure at a glance. Each row carries the contract's terms — ARR, whether it auto-renews, notice period — so you have what you need to make the call without leaving the screen.

## Setting your judgment

For each renewal you set three things:

* **Likelihood** — Likely, Maybe, At-risk, or Churn. Each carries a weight that decides how much of the contract's ARR carries into your base forecast: Likely counts 90%, Maybe 60%, At-risk 30%, Churn 0%. A renewal you haven't judged yet counts at 70% until you make the call.
* **Expected change** — the percentage you expect the ARR to move at renewal: positive for an [expansion](/get-started/glossary), negative for a [contraction](/get-started/glossary).
* **Notes** — context for the call, or for whoever reads the book later. You can also set a grace period — how long past a contract's end date to wait before treating it as [churned](/get-started/glossary) rather than a pending renewal.

This is the judgment the forecast runs on — see [the weekly forecast](/workflows/weekly-forecast) for how the three scenarios use it.

## The weekly call

The **Call Sheet** is a dense, screen-shareable grid built for the live renewal call — one row per contract, grouped by customer. During the call, you record the outcome, the new ARR, and notes inline as each customer comes up, so the book is updated in real time rather than written up afterward. When you're done, **Lock Snapshot** saves the book exactly as it stands to [Portolan](/concepts/portolan) — a record of where renewals stood that week.

## Closing the loop

When a renewal is signed, link the new contract as the successor to the one it replaces. That link is what connects the two terms in the [lifecycle](/concepts/lifecycle-model) and lets HarborOS tell a renewal from new business, and an expansion from a contraction. HarborOS auto-links the obvious matches; you confirm or link the rest.

## Why it matters

Because renewal judgment drives so much of the forward number, running this weekly keeps the forecast honest — it reflects what you actually believe about each account, not a stale guess. And every call is yours: nothing here moves a number until you set it. (See [Judgment is the gate](/concepts/judgment-is-the-gate).)