Contract renewal watchlist

Purpose

Maintain a forward-looking register of contracts that may expire, renew automatically, or require notice. For each agreement, connect the contractual date and notice rule to owner, supplier or customer, committed spend, actual usage, service performance, and the recommended renewal action.

Scope

Review executed contracts and amendments together with the contract register, invoice or spend table, usage or seat report, supplier performance record, and renewal policy. Calculate the next action date from the initial term, renewal term, notice period, and governing date language. Separate contractual facts from a commercial recommendation.

Excluded: serving notice, renegotiating terms, deciding legal enforceability, and treating a missing contract date as an estimated deadline.

Data basis

• Contract register columns: contract_id, counterparty, owner, start_date, end_date, renewal_type, notice_days, status, and annual_value.
• Executed agreement and amendments, especially term, renewal, termination, price-adjustment, and notice clauses.
• Spend ledger, usage table, service-level reports, renewal policy, and owner mapping.

Result

Produce a persistent renewal watchlist with one row per contract: expiry date, notice deadline, days to action, renewal mechanism, annual spend, usage measure, performance signal, priority, owner, recommended action, and citations. Add a short portfolio summary of near-term exposure and data gaps.

Quality criteria

• Dates are calculated only from an identified clause or register field and show the date basis.
• Auto-renewal rows include renewal length and notice period or mark them unknown.
• Spend and usage figures state period, currency or unit, and source table.
• Priority follows the supplied policy; no priority is silently inferred from contract value.
• Every row is traceable to contract_id and a document section or table row.

Instructions

Use the amendment that is effective on the relevant date and retain superseded wording when it explains a discrepancy. Calculate notice_deadline as the contractual renewal or expiry date minus the stated notice period; do not subtract a default number of days. Flag deadlines already passed, dates within the policy lead-time window, missing owner, and conflicting register-versus-contract dates separately. Compare committed annual value with actual spend only when their periods and currencies are compatible. Mark recommendation as renew, renegotiate, review usage, terminate, or unknown only when the policy defines those labels.

Adapt before use

• Map contract, spend, usage, owner, and performance columns to the company tables.
• Add the renewal policy and the standard lead-time window.
• Define priority values, escalation roles, and treatment of past-due notice dates.
• Specify currency conversion and usage-period rules if portfolio totals are required.