MSP renewal calendar template: decide before the notice deadline
An MSP renewal calendar should show the last date the client can make a useful decision, who owns it, and what happens if nobody answers.
An invoice date does not establish the action deadline. Waiting for the invoice can leave the client facing a renewed subscription, an overdue cancellation notice, or too little time for replacement work.
For a vCIO or account manager running client reviews out of Connectwise Manage, this is a planning job. The PSA agreement, distributor subscription, registrar account, and hardware warranty can each describe a different part of the same client commitment. Put those facts into one decision register without pretending they all share a renewal rule.
Copy the register, CSV header, and decision note below to prepare the next client conversation.
Keep three dates separate
A single "renewal date" column hides the decision you need to make.
| Date | What it means | What the account manager does with it |
|---|---|---|
| Expiry or term end | The current registration, coverage, or commitment reaches its end | Confirm the service or commercial consequence |
| Vendor action deadline | The last date to submit the required cancellation, quantity change, renewal, or other action under the applicable terms | Attach the source and the person who can execute it |
| Client decision deadline | Your earlier date for approving the budget and the next step | Schedule the conversation while alternatives are still practical |
An invoice date can be a fourth field. Keep it separate from the term end and the notice deadline.
If a vendor requires notice before the term ends, plan from that notice deadline. If replacing the service takes longer, plan from the replacement lead time. Use whichever requires the client to decide first.
"We will discuss it at the next QBR" only works when that QBR happens before the decision deadline.
Copy this renewal register
Start with the renewals that affect a client decision. Keep one row per subscription, asset group, domain, or contract with the same terms and action path. Split rows when dates, owners, or commercial terms differ.
| Field | What belongs in it |
|---|---|
| Client and account owner | The client record and the MSP person accountable for the decision |
| Item and identifier | Domain, subscription ID, warranty asset group, contract number, or other exact reference |
| Category | Domain, certificate, warranty, security subscription, Microsoft/CSP, other SaaS, or client agreement |
| Source record | Link to the portal, order, contract, or vendor terms that establish the dates |
| Expiry or term end | Exact date, with timezone where the action has a cutoff time |
| Auto-renew and notice terms | Current setting, notice requirement, submission method, and any relevant quantity-change rule |
| Vendor action deadline | The dated action required under those terms |
| Client decision deadline | The earlier approval date you will use to run the account |
| Business consequence | What stops, costs more, loses coverage, or becomes a new commitment |
| Cost and client price | Current vendor cost and client charge; next-term quote separately, with its validity date |
| Recommended action | Renew, resize, replace, retire, or investigate |
| Client approver and status | Named budget owner; awaiting facts, decision needed, approved, declined, or executed |
| Work and evidence | Related roadmap item or quote, execution owner, and proof the action completed |
Use this CSV header in a spreadsheet or another system that supports these fields:
client,account_owner,item,item_id,category,source_record,term_end,timezone,auto_renew,notice_terms,vendor_action_deadline,client_decision_deadline,business_consequence,current_vendor_cost,current_client_price,next_term_quote,quote_valid_until,recommended_action,client_approver,status,roadmap_or_quote,execution_owner,completion_evidence
An unknown term goes into awaiting facts, with an owner and a follow-up date. A blank notice field should never quietly mean "no notice required."
For client-owned accounts, record who controls the portal and billing method. An MSP can own the reminder while the client still owns the renewal action.
Set the deadline from the contract, then work backward
Here is an illustrative planning scenario, not a vendor policy or a customer result.
A client's service term ends January 31, 2027. Assume its contract requires cancellation notice 60 calendar days before that date. The vendor action deadline is December 2, 2026. Your MSP chooses a 14-day approval buffer, putting the client decision on November 18. Allowing another seven days to prepare the options puts the account review on November 11.
| Illustrative milestone | Date | Owner |
|---|---|---|
| Current term ends | January 31, 2027 | Vendor and contract parties |
| Cancellation notice due under the assumed terms | December 2, 2026 | Named execution owner |
| Client decision due under this MSP's chosen buffer | November 18, 2026 | Client budget approver |
| Options ready for the client review | November 11, 2026 | Account manager |
Those buffers are choices for the scenario. Your actual contract may use business days, a particular timezone, a prescribed notice channel, or a different effective date. Read those terms before calculating the deadline.
Now add replacement work. If the alternative needs discovery, procurement, configuration, migration, validation, and a client change window, determine when that work must start. Move the client decision earlier if the delivery plan requires it. A timely cancellation with no viable replacement plan is still a bad client outcome.
The MSP scope of work template is the next document when the renewal decision creates a project. Put the replacement work and its dependencies into scope before offering a price.
Different renewals need different evidence
Microsoft and CSP subscriptions
Track the subscription, quantity, commitment term, billing frequency, renewal setting, and allowed change path separately. Monthly billing does not establish a monthly commitment.
Microsoft's new commerce license-based overview distinguishes subscription terms from billing options and describes scheduled changes that take effect at the end of a term. Its NCE cancellation policy gives license-based purchases a seven-calendar-day prorated-refund window, with specific rules for partial upgrades and renewal into a new term. Other product types have different rules.
Build the decision around the actual subscription and the distributor's execution process. Do not turn a limited cancellation window into your normal budget-planning window.
Before approving the next quantity, check the client roster and assigned licenses. Use the Microsoft 365 license audit for that evidence. A renewal register tells you when to decide; the audit helps you decide what to buy.
Domains and certificates
For a domain, name the registrar account, registered-name contact, expiry date, renewal setting, payment owner, and execution owner. Confirm that notices reach someone who still works with the client.
ICANN's Expired Registration Recovery Policy requires registrars to send notices approximately one month and one week before gTLD registration expiry. That is a registrar notification requirement, not your client's approval workflow. Country-code domains can have different rules.
Treat certificates as separate items. Record the certificate expiry, issuing service, renewal method, deployment location, and evidence that the replacement is serving correctly. Renewing a domain does not establish that its certificate has been renewed and deployed.
Warranties, hardware, and security subscriptions
For warranties, record the covered asset group, coverage end, support terms, and replacement options. The client may choose renewal, replacement, or to accept a documented support gap. Make the consequence specific to the actual coverage.
For security subscriptions, verify what the applicable terms say changes at expiry. Do not copy another vendor's behavior into the row. Include the implementation work if replacing the service changes agents, configuration, policies, or support ownership.
A quote for the subscription alone can leave the migration work unpriced. The account manager owns getting both into the client decision.
Client agreements and MSP tool contracts
Keep client agreements distinct from the upstream services they fund. Compare the client commitment and notice terms with the vendor commitment before approving another term.
If those dates do not line up, put the mismatch in front of the owner. The choice may be to change the client agreement, choose a different upstream term, or knowingly carry the exposure. The calendar should make that choice visible.
MSP tool contracts belong in an internal view with the MSP's own budget approver. Do not mix the shop's software renewal with a client-owned approval merely because both invoices arrive in December.
Use the QBR to make the decision
A renewal row needs a recommendation the client can respond to. Use a short decision note:
Item: [subscription, domain, asset group, or agreement]
Current term or coverage ends: [date]
Required vendor action and deadline: [action, date, timezone]
Client decision needed by: [date]
Recommendation: [renew, resize, replace, retire, or investigate]
Reason: [current client facts and business consequence]
Commercial choice: [quantity, term, cost, client price, quote validity]
Related work: [scope, dependencies, lead time, responsible team]
Client approver: [name and role]
Decision: [approved, declined, or pending]
Execution owner and proof: [person and completion record]
A client talk track can be plain:
"This term ends on [date], but the action deadline is [earlier date]. We recommend [action] because [client fact]. The choice needs [budget or work]. Can [named approver] confirm the decision by [date]?"
Keep approved and executed as different statuses. A client saying yes does not change a vendor portal. Close the row when the named owner records the completed action and its evidence, then set the next applicable date.
If the client declines, record the decision and the consequence they acknowledged. If the client does not answer, escalate to the agreed approver before the deadline. Do not invent authorization from silence.
The MSP QBR template gives this decision a place in the meeting. Move it earlier when the renewal timeline cannot wait for the normal quarterly cadence.
Review the exceptions, then carry the work forward
A short weekly review can focus on four queues:
- Missing terms or unverified dates that prevent a recommendation.
- Client decisions approaching their deadline.
- Approved actions that still lack execution evidence.
- Renewals that need replacement scope, a quote, or a changed client agreement.
Keep the source register linked to the client record. If Connectwise Manage, a spreadsheet, and a vendor portal disagree, reconcile the source facts before sending the client a confident date.
Scopable's vCIO and QBR workflow connects client context, assessments, agreements, and roadmap decisions to reviewed client recommendations and follow-up work. Use the renewal register to supply the dates and commercial terms you have verified. The account manager still owns the recommendation, client approval, and vendor action.
Start Scopable for free to evaluate the QBR workflow with one real client whose next renewal needs a budget decision.
