Renewal radar | Business Helper AI

Inputs and purpose

Use this workflow to prepare: Renewal priorities and preparation checklist.

Start with: Renewal/contract export, dates and supplied risk evidence.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

Procedure

Read contract dates, notice windows, renewal terms and accountable roles from the supplied records. Distinguish expiration from the last date to give notice.
Combine commercial deadlines with customer outcome, service and relationship evidence. Mark stale or missing records.
Prioritize preparation actions by the decision deadline and plausible risk. Do not assume an automatic renewal is commercially desirable.
Return a renewal calendar and preparation list. Check every priority can be traced to a term or observed concern.

Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Prepare consistent responses and identify renewal risks.

Possible success measures: Response preparation time, repeat contacts, retention. Choose the measure that fits the owner's actual goal; it is not a promised result.

Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the input guide, calculation reference or output template. For tool setup, use the shared instructions.

Plain-text instructions

---
name: renewal-radar
description: "Prepare renewal priorities and preparation checklist. Use for this workflow with supplied business information."
---

# Renewal radar

## Inputs and purpose

Use this workflow to prepare: Renewal priorities and preparation checklist.

Start with: Renewal/contract export, dates and supplied risk evidence.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

## Procedure

1. Read contract dates, notice windows, renewal terms and accountable roles from the supplied records. Distinguish expiration from the last date to give notice.

2. Combine commercial deadlines with customer outcome, service and relationship evidence. Mark stale or missing records.

3. Prioritize preparation actions by the decision deadline and plausible risk. Do not assume an automatic renewal is commercially desirable.

4. Return a renewal calendar and preparation list. Check every priority can be traced to a term or observed concern.

## Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Prepare consistent responses and identify renewal risks.

Possible success measures: Response preparation time, repeat contacts, retention. Choose the measure that fits the owner's actual goal; it is not a promised result.

## Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the [input guide](../../../references/INPUT_DATA_GUIDE.md), [calculation reference](../../../references/CALCULATIONS.md) or [output template](../../../references/WORKFLOW_OUTPUT_TEMPLATE.md). For tool setup, use the [shared instructions](../../../AGENTS.md).