Track service-renewal conversations and decisions

Separate renewal date from response deadlines

Distinguish the renewal date, any notice deadline, the planned customer conversation and the internal review date. Verify them from each agreement rather than applying a universal thirty-day rule. Check whether renewal is automatic, requires confirmation or needs another document. The register coordinates work; it does not replace the authoritative agreement. When a condition is unclear, mark it for review instead of inferring a deadline from the previous customer’s arrangement.

Connect agreement references with customer intent

Keep contract ID, service, current period, agreement reference, review deadline, owner, customer intent, required action and completion evidence. In RN-112, a customer’s wish to continue may still leave a document or approval outstanding. Similarly, a request not to renew is not evidence that cancellation has been processed. Use distinct states for intent received, action pending and completion checked so the contact team and operational team can reconcile their work.

Review changes before asking for a decision

Review changes to price, scope, users, contact or billing details before requesting a decision. Do not reuse last year’s email without checking the current agreement and period. If nothing changes, record that someone reviewed it. Use only the customer information appropriate for this conversation and avoid putting unnecessary usage detail into an email. A renewal message should make the decision clear, not bury it under internal notes or imply terms that have not been approved.

Manage waiting cases by the next action

Separate contacted, awaiting response, clarification needed, processing and completed cases. Give waiting cases a next-review date rather than sending the same reminder every day. If the contact has left, update the approved route and obtain a new response. A customer with several services may answer about only one contract. Match the response to the relevant contract ID and period before using it to trigger any downstream action.

Escalate near-deadline work with evidence

Escalate cases nearing a real deadline with the agreement and communication history available. Lack of a reply is not a basis for guessing whether the customer wants continuation or cancellation. A failed reminder does not itself extend an agreed deadline. Before repeating a processing step, check whether the contract change already took effect. This separates recovery of an internal notification from repeating an externally consequential action.

Close only when intent and processing agree

Test continuation requested but unprocessed, cancellation requested but unprocessed, a response about the wrong period and a changed contact. Completion means the intended action is reflected for the correct agreement and period, not merely that an email was sent. Create a new cycle for the next review and preserve the earlier decision. This allows a later owner to explain what happened in each period without reconstructing a changing single-row history.

RN-112: follow the work remaining after a renewal reply

In RN-112, the customer wants to continue but a required confirmation document is outstanding. Record intent received while processing remains incomplete. State the relevant period and missing information, and set the next action before the real deadline. A document for another agreement does not complete this task. Close the cycle only after the intended action is reflected, then create a new review cycle. Keeping period-specific evidence avoids an annual overwrite that makes earlier renewal decisions impossible to explain.

Choose a tool and budget around the actual workload

A shared register with agreement references and review dates can work for a small portfolio. As access and document volume grow, choose tools that make ownership and history manageable. Budget for condition review and customer explanation, not just seats and reminder executions. Add communication automation after the register is dependable, and keep confirmation of the actual contract change under a responsible person’s control. The highest-value improvement is fewer missed obligations, not the largest reminder volume.

• Build an Airtable enquiry tracker: intake, owners and follow-up states
• Find unfinished work in Airtable views: filters, sorting and sharing checks
• Define business days and time zones for automation