# Renewal Management — Standard Operating Procedure > Source: https://b2bprocess.com/renewal-management > Last updated: 2026-08-03. Adapt owners, tools, and thresholds to your organization. ## 1. Purpose Renewal management is the process of carrying a customer from an active contract into the next one: maintaining an accurate forward calendar of renewal and notice dates, assessing each account's risk and value realization far enough ahead to act on it, running the commercial conversation about price and term, and closing the paperwork before the current contract lapses. It is the operational spine of recurring revenue — the point where every earlier post-sale process either pays off or doesn't. ## 2. Scope & prerequisites Applies to any business with fixed-term recurring contracts. Worth formalizing beyond a spreadsheet once renewal volume exceeds what one person can hold in their head — roughly 20+ renewals per quarter, or any book where contracts carry notice periods, auto-renew clauses, or negotiated uplift terms. Prerequisites: accurate contract data in the CRM (start date, end date, notice deadline, term, current ARR), a defined owner per renewal, and a health or adoption signal to prioritize against. ## 3. Roles & responsibilities | Role | Responsibility | | --- | --- | | Customer Success Manager | Owns account readiness: risk assessment, value case, sponsor engagement, and the save plan for at-risk renewals. | | Renewal Manager | Owns the commercial motion where the role exists — pricing, uplift, term negotiation, and close of the renewal itself. | | Account Executive | Owns the commercial negotiation where there is no dedicated renewal role, and leads any expansion attached to the renewal. | | CS leadership | Sets tiering and touchpoint standards, inspects the renewal pipeline, and owns the retention number. | | RevOps | Owns contract data accuracy, renewal triggers and automation, and renewal forecasting infrastructure. | | Deal Desk | Approves non-standard pricing and terms, and generates renewal quotes and order forms. | | Finance | Books renewed contracts, manages billing continuity, and flags overdue invoices ahead of the renewal. | | Legal | Handles redlines and term changes on renewal agreements. | ## 4. Procedure ### Step 1: Build and maintain the forward renewal calendar **Owner:** RevOps Create a single rolling 12-month view of every contract coming up for renewal, with the fields the process actually runs on. This is the foundation — every downstream step depends on the dates being right, and contract data entered once at booking and never audited is the most common point of failure. - [ ] Capture contract start, end, and notice/termination deadline per account - [ ] Record current ARR, term length, auto-renew status, and any contracted uplift - [ ] Assign a named owner to every renewal in the window - [ ] Audit the data quarterly against source contracts, not just CRM records ### Step 2: Segment renewals by motion **Owner:** CS leadership + Sales leadership Not every renewal deserves the same effort. Split the book into tiers — auto-renew/tech-touch for small and low-risk accounts, managed for the mid-market majority, and strategic for high-ARR or high-risk accounts requiring an executive-level plan — and define the required touchpoints for each so effort concentrates where it changes the outcome. - [ ] Tier by ARR, strategic importance, and current health band - [ ] Define the mandatory touchpoints and lead time for each tier - [ ] Route low-touch renewals to automated notice and self-serve confirmation ### Step 3: Trigger the renewal timeline at fixed lead times **Owner:** CS Operations / RevOps Set automated triggers at defined intervals before the contract end date — commonly T-120 for strategic accounts, T-90 for managed, T-60 for standard, and T-30 as an escalation backstop — with the notice deadline treated as the true deadline where one exists. Working back from the notice date rather than the end date is what prevents the classic surprise cancellation. - [ ] Set the first trigger before the notice deadline, not before the end date - [ ] Fire tasks to the assigned owner automatically from the CRM or CS platform - [ ] Escalate to leadership if a renewal is untouched at the T-30 checkpoint ### Step 4: Assess renewal risk and readiness **Owner:** Customer Success Manager At the first trigger, run a structured assessment rather than an informal gut check: current health score and its trajectory, adoption against the goals set at onboarding, open support escalations, sponsor and champion status, and any billing or invoice disputes. The output is a risk rating and, for anything not clearly green, a written plan with owners and dates. - [ ] Review health score trend, not just the current band - [ ] Confirm the executive sponsor and champion are still in role and engaged - [ ] Check open escalations, overdue invoices, and unresolved commercial disputes - [ ] Produce a risk rating and a save plan for at-risk accounts ### Step 5: Build and document the value case **Owner:** Customer Success Manager Assemble evidence of value delivered against the outcomes the customer bought for — adoption metrics, business results attributable to the product, support responsiveness, milestones hit. A renewal conversation opened without this is negotiated purely on price, because value is the only counterweight to a procurement-led discount request. - [ ] Pull usage and outcome data against the goals set at onboarding - [ ] Reuse and update the value narrative established in prior QBRs - [ ] Quantify results in the customer's own terms where the data supports it ### Step 6: Open the renewal conversation **Owner:** Customer Success Manager + Renewal Manager / AE Raise the renewal explicitly with the economic buyer well ahead of the deadline, confirm budget and any procurement process on the customer's side, and surface changes in their requirements. Enterprise procurement cycles routinely take longer than the notice period allows, so discovering a mandatory RFP at T-30 is a self-inflicted loss. - [ ] Confirm who signs and what their approval process requires - [ ] Surface changed requirements, seat counts, or usage patterns - [ ] Identify expansion or consolidation opportunities to fold into the renewal ### Step 7: Negotiate commercial terms **Owner:** Renewal Manager / AE + Deal Desk Work the price, term length, and contract terms: contracted uplift or a proposed increase, multi-year commitments in exchange for rate protection, seat or usage true-ups, and any redlines. Anchor on the value case and the contracted uplift rather than opening from the customer's discount request, and route non-standard terms through the standard approval path rather than around it. - [ ] Apply contracted uplift where the agreement provides for it - [ ] Trade concessions for term length, payment terms, or references — never give them free - [ ] Route non-standard discounts and terms through deal desk approval - [ ] Escalate legal redlines early rather than at signature ### Step 8: Execute paperwork and book the renewal **Owner:** Deal Desk + Finance Generate the order form or renewal agreement, route for signature, and book the renewed contract with correct dates, ARR, and terms — closing the loop by writing the new contract data back into the renewal calendar for the next cycle. Renewals that close commercially but sit unbooked distort both revenue reporting and the next renewal cycle. - [ ] Generate quote and order form from approved terms - [ ] Route for e-signature with a deadline ahead of the contract end date - [ ] Book the renewal and update contract dates, ARR, and term in the CRM ### Step 9: Forecast and inspect the renewal pipeline **Owner:** CS leadership + RevOps Run a recurring inspection of the renewal book by expected close, risk rating, and forecast value, in the same disciplined way new-business pipeline is inspected. Renewal forecasts built on CSM optimism rather than health and engagement data are the reason retention misses arrive without warning. - [ ] Forecast by risk category with a documented basis per at-risk renewal - [ ] Compare forecast to actual by band each quarter to calibrate - [ ] Inspect untouched renewals inside the trigger window as a standing agenda item ### Step 10: Debrief outcomes and feed the model **Owner:** CS Operations / RevOps After each cycle, review what closed, what churned, what downgraded, and why — then push the findings back into health scoring weights, onboarding, and the risk assessment criteria. A renewal loss that produces no change to an upstream process will recur. - [ ] Categorize losses by root cause, not by the reason the customer stated first - [ ] Feed churn causes back into health scoring inputs and onboarding milestones - [ ] Route lost accounts into the win-back motion with the documented reason ## 5. Metrics to monitor | Metric | Definition | Formula | Target | | --- | --- | --- | --- | | Gross Revenue Retention (GRR) | Share of starting recurring revenue retained, excluding any expansion — the cleanest measure of renewal performance. | (Starting ARR − churned ARR − downgrade ARR) ÷ Starting ARR | 85–95%, higher in enterprise segments | | Net Revenue Retention (NRR) | Starting revenue retained including expansion from the existing base, capturing renewal and growth together. | (Starting ARR − churned ARR − downgrade ARR + expansion ARR) ÷ Starting ARR | 100–120% | | Logo retention rate | Share of customers due for renewal that renewed, regardless of contract value. | Customers renewed ÷ customers up for renewal | 85–95% | | On-time renewal rate | Share of renewals signed on or before the contract end date, measuring process discipline rather than outcome. | Renewals signed by contract end date ÷ total renewals due | above 90% | | Renewal forecast accuracy | How closely the forecast renewal value matched actual renewed value in the period. | |Forecast renewal ARR − actual renewal ARR| ÷ actual renewal ARR | within 5% | | Renewal cycle time | Days from first renewal outreach to signed agreement, indicating whether lead times are sufficient. | Signature date − first renewal touch date | comfortably inside the tier's defined lead time | | At-risk lead time | Days between a renewal being flagged at risk and its contract end date — the window available to save it. | Contract end date − risk flag date | 60+ days | | Average renewal uplift | Weighted average price increase achieved across renewed contracts. | (Renewed ARR − prior ARR of renewed accounts) ÷ prior ARR of renewed accounts | 3–7%, subject to contracted terms | ## 6. Known failure modes | Failure | Symptom | Corrective action | | --- | --- | --- | | Renewal treated as a 30-day administrative task | Risk surfaces too late to fix; the only remaining lever is discounting. | Trigger the process at T-90 or T-120 by tier, and work back from the notice deadline rather than the contract end date. | | Notice and auto-renew dates not tracked | A customer gives notice inside the window and the renewal is lost before anyone has spoken to them. | Capture notice deadlines as a required field at booking and audit them against source contracts quarterly. | | Ownership undefined between CSM and AE | Renewals fall between roles, or both parties approach the customer with different messages. | Assign one named owner per renewal with a written split of relationship versus commercial responsibility. | | Reliance on auto-renewal in place of engagement | Silent renewals accumulate on disengaged accounts that churn a term later, or cancel at the first notice window. | Require a value and adoption check on auto-renew accounts too, even where no signature is needed. | | No documented value case | The conversation opens on price, procurement leads with a discount demand, and the seller has no counterweight. | Build the value case from adoption and outcome data before the first renewal conversation, reusing the QBR narrative. | | Price increase introduced without warning | An uplift lands as a surprise at quote stage and triggers escalation, delay, or an RFP. | Signal any increase at the first renewal conversation, and tie it to contracted terms and delivered value. | | Forecast based on CSM sentiment | Retention misses arrive without warning because confident renewals churn. | Require a documented basis per at-risk renewal and calibrate forecast bands against actual outcomes each quarter. | | Champion departure not detected | The renewal stalls because the person who bought the product left months earlier and was never replaced. | Track sponsor and champion status as an explicit renewal-readiness check, not an informal observation. | | Losses produce no upstream change | The same churn reasons recur cycle after cycle. | Run a structured debrief and feed root causes into health scoring weights and onboarding milestones. | --- This SOP is maintained as part of the B2B process encyclopedia at https://b2bprocess.com. Check the source page for the latest revision.