The 90-60-30 Renewal Rule: Reminder Windows for SaaS and Client Assets

The direct rule: send renewal reminders at 90, 60, 30, 14, and 7 days before renewal, plus overdue, missing-owner, and missing-date alerts. Good saas renewal reminder rules are not random calendar events. They define what each reminder means and who should act.

Use the SaaS renewal tracking template to capture renewal dates and owners, then use reminders to turn those dates into operations. For the wider client-domain view, run the free 10-domain agency audit. For the broader renewal operating model, use Renewal Ledger for Agencies, and review the CertPilot methodology for public domain, DNS, certificate, and email-authentication checks.

Why renewal reminders need rules, not random calendar events

Random reminders create noise. Rules create expectations.

A useful reminder should answer:

• Why is this alert firing?
• Who owns the next step?
• What decision is needed?
• What happens if it is ignored?
• Should this appear in a report or digest?

Without rules, reminders become calendar clutter. With rules, they become a renewal-risk workflow.

Reminder windows table

| Alert window | Trigger | Owner | Decision needed | Risk if ignored | |---|---|---|---|---| | 90 days | Renewal within 90 days | Business owner | Budget/review planning | Review starts too late | | 60 days | Renewal within 60 days | Service owner | Usage/need confirmation | Unneeded renewal continues | | 30 days | Renewal within 30 days | Decision owner | Renew, cancel, downgrade, or escalate | Notice window may close | | 14 days | Renewal within 14 days | Operational owner | Final operational check | Surprise charge or expiry | | 7 days | Renewal within 7 days | Assigned owner | Final confirmation | No time to fix ownership gaps | | 0 / overdue | Date passed | Escalation owner | Urgent action | Service, client, or budget risk | | Missing owner | Owner blank | Operations lead | Assign owner | No accountability | | Missing date | Renewal date blank | Data owner | Fix data | No reliable reminders |

The windows are a starting point. Adjust them for contracts with longer notice periods.

The 90-day review reminder

The 90-day reminder is for planning. It should not ask the team to make a final decision unless the contract requires it. It should ask whether the renewal needs budget review, client discussion, vendor review, or internal confirmation.

Good 90-day questions:

• Is this asset still needed?
• Who owns the decision?
• Does the client need approval?
• Is the cost known?
• Is auto-renewal enabled?
• Is the notice deadline earlier than expected?

For agencies, the 90-day reminder can also identify client conversation topics for upcoming account reviews.

The 60-day usage and need check

The 60-day reminder should confirm whether the asset is still needed. CertPilot does not collect usage analytics or optimize licenses, so the owner must verify usage through the appropriate vendor or internal process.

The reminder should prompt:

• Confirm active use.
• Confirm owner.
• Confirm client or department.
• Confirm cost.
• Confirm renewal path.
• Confirm cancel or downgrade requirements.

This is where many wasteful renewals are prevented, but the process should stay honest. Renewal Ledger can flag the work; it does not replace the business decision.

The 30-day renew/cancel decision

The 30-day reminder is the decision window. By this point, the owner should know whether the asset will renew, cancel, downgrade, or escalate.

Useful statuses:

• Renew.
• Cancel.
• Downgrade.
• Waiting for client.
• Waiting for owner.
• Unknown.

If the status is unknown at 30 days, treat it as risk. Unknown status is not neutral.

The 14-day operational warning

The 14-day reminder is an operational warning. It is for items where the decision may be made but the execution is not complete.

Examples:

• Client approved renewal but payment owner has not confirmed.
• Owner decided to cancel but vendor cancellation is not complete.
• Domain or hosting renewal needs registrar access.
• Plugin license needs client billing confirmation.

At 14 days, the team should remove ambiguity.

The 7-day final reminder

The 7-day reminder is the final warning. It should be reserved for items that still need action or confirmation.

Do not send a loud 7-day alert for every healthy renewal if that creates noise. Send it when:

• Owner is missing.
• Status is unknown.
• Auto-renewal is true and review is incomplete.
• Payment owner is missing.
• Client approval is pending.
• Renewal date is tied to a critical asset.

The closer the date, the more specific the reminder should be.

Overdue alerts

Overdue means the renewal date passed. The item may have renewed successfully, expired, or become inaccurate. In all cases, it needs review.

Overdue alert actions:

• Confirm whether service renewed.
• Confirm whether cost changed.
• Update renewal date.
• Update status.
• Record any client-facing risk.
• Escalate if service was interrupted.

Overdue alerts should not sit in the same queue as normal reminders. They represent either operational risk or stale data.

Missing owner alerts

Missing owner is process risk. A renewal without an owner can still appear healthy until the decision date arrives.

Trigger missing-owner alerts when:

• Owner field is blank.
• Owner is a former employee.
• Owner is a generic inbox no one monitors.
• Client-owned asset has no internal agency owner.

The fix is not only filling a cell. The fix is assigning accountability.

Missing renewal date alerts

Missing renewal date is data quality risk. If the renewal date is unknown, the system cannot remind anyone at the right time.

Actions:

• Ask the vendor owner to confirm the date.
• Check contract or account billing page.
• Ask the client if the asset is client-owned.
• Mark the asset as unknown until fixed.

Do not hide missing dates. A clean-looking tracker with missing dates is less safe than a tracker that exposes the gaps.

Auto-renewal risk alerts

Auto-renewal needs a rule because it can be both helpful and risky.

Trigger auto-renewal review when:

• Auto-renew is true and renewal is within 60 days.
• Auto-renew is true and owner is missing.
• Auto-renew is true and cost is high.
• Auto-renew is unknown and renewal is within 30 days.
• Auto-renew is true and client approval is required.

The goal is not to turn off every auto-renewal. The goal is to avoid unmanaged renewals.

Escalation rules for agencies

Agencies should escalate based on client impact.

Escalate when:

• A client website, domain, hosting plan, plugin, or email tool may be affected.
• Client approval is missing inside the notice window.
• The owner is missing and the renewal is within 30 days.
• The asset may appear in a monthly proof report.

For agency context, pair reminder rules with agency care plan renewal tracking and monthly proof report for agencies.

Escalation rules for IT teams

IT teams should escalate based on business impact and operational ownership.

Escalate when:

• Department owner is missing.
• Renewal supports identity, email, website, monitoring, or customer operations.
• Cost is material and approval is unclear.
• Renewal is overdue.
• Date is missing for a critical service.

For internal inventory structure, see digital asset tracking for IT teams.

Digest vs immediate alerts

Not every reminder needs to interrupt someone immediately.

Use digest alerts for:

• 90-day planning.
• 60-day review.
• Low-risk renewals.
• Data cleanup summaries.

Use immediate alerts for:

• Overdue renewals.
• Critical assets due soon.
• Missing owner inside 30 days.
• Auto-renewal risk inside 14 days.
• Client-impacting renewal with pending approval.

Alert design should reduce noise, not create another inbox problem.

Alert noise: what not to send

Do not alert on everything with the same urgency.

Avoid:

• Daily reminders for low-risk renewals months away.
• Repeated alerts to people who do not own the asset.
• Alerts with no next action.
• Alerts for resolved items.
• Alerts that ignore missing data.

The reminder should make the next step clearer.

How reminder rules feed renewal risk reports

Reminder rules become report signals:

• Missing owner becomes process risk.
• Missing date becomes data quality risk.
• Due soon becomes upcoming renewal risk.
• Overdue becomes urgent risk.
• Auto-renewal review becomes decision risk.

CertPilot Renewal Ledger can use these signals for renewal-risk visibility and proof-report content. The value is not another reminder. The value is a renewal-risk workflow that can be reviewed and reported.

For a report-oriented workflow, see client renewal risk report and renewal risk audit template.

Related Renewal Ledger Resources

• SaaS renewal tracking template
• Client renewal risk report
• Renewal risk audit template
• Agency care plan renewal tracking
• Domain and hosting renewal checklist for agencies

Frequently Asked Questions

What are good SaaS renewal reminder rules?

Good SaaS renewal reminder rules trigger at 90, 60, 30, 14, and 7 days before renewal, plus overdue, missing-owner, and missing-date alerts. Each reminder should have a purpose. The 90-day window supports planning, 60 days supports need review, 30 days supports a decision, and the final windows support execution.

Is the 90-60-30 rule enough for every renewal?

No. The 90-60-30 rule is a baseline. Some contracts require longer notice periods, and some low-risk monthly subscriptions may not need heavy review. Adjust reminder windows based on cost, client impact, notice terms, and operational importance. Critical assets deserve earlier and clearer escalation.

Should reminders go to the whole team?

Usually no. Reminders should go to the owner or responsible group. Team-wide reminders create noise and reduce accountability. Use digests for broad visibility and immediate alerts for urgent risk. If the owner is missing, send that alert to the operations lead or the person responsible for data quality.

How should overdue renewals be handled?

Overdue renewals should be treated as urgent review items. Confirm whether the asset renewed, expired, changed cost, or simply has stale data. Then update the renewal date, owner, status, and notes. If the asset affects a client website, email, domain, or hosting plan, escalate quickly.

Are auto-renewal reminders always necessary?

Auto-renewal reminders are necessary when the renewal is unmanaged, high cost, client-facing, or close to the notice deadline. Auto-renewal itself is not always bad. It can prevent interruption. The risk is letting it happen without owner review, client approval, or accurate cost context.

How does CertPilot use renewal reminder rules?

CertPilot Renewal Ledger uses renewal dates, owners, and risk status to support alerts, renewal-risk summaries, client grouping, and proof-report content. It does not cancel services, approve purchases, parse invoices, or optimize licenses. The reminder rules help turn renewal data into an operational workflow.