Renewal and notice risk, on one sample contract

Static sample you can explore in one sitting — no signup. In a live workspace, contracts run through extraction and human verification first; how fast you see renewals and spend depends on processing and your review queue.

Sample values are in USD for easy comparison. In your workspace, portfolio views normalize to your organization base currency.

Static example — not live API data. Numbers and timelines come from checked-in JSON for this page only. They are not your tenant, not the upload → worker → verify queue, and not a substitute for signed-in renewal math.

PDF

Example contract (anonymized structure).

Renewal risk (sample callout)

The 60-day notice window closed on Dec 31, 2025. This pattern often means the term rolls forward before finance acts.

Financial exposure

$120,000

Committed spend

Locked due to missed notice window.

Extracted terms

Click a row to highlight text in the PDF. This demo uses curated fields; live contracts start as suggestions until you verify.

Notice deadline

Dec 31, 2025

Notice status

Missed

Impact

Auto-renewal likely triggered

Timeline

  • Dec 31, 2025Notice deadline
  • Mar 1, 2026Renewal date

What this sample shows

  • Curated fieldsStructured values aligned to this PDF — not a live extraction pipeline
  • TraceableClick a field to jump to the matching place in the sample agreement
  • Verify in productIn LedgerGuard you confirm fields against the PDF (Needs review) before relying on renewals and spend
In a live workspace: upload → processing → verify important fields → renewals and dashboards read deterministic data from the API. Timing varies by queue and review. How it works · FAQ