Seven Signals Before a Workspace Lapses
A workspace does not lapse suddenly. Seven distinct conditions are evaluated against five named thresholds, and one of them fires without any payment ever having failed — which is the one worth knowing about.
The worst version of a billing failure is the one nobody saw coming, and almost none of them are that. The signals are there for weeks.
Whether a workspace is at risk of losing access is not one flag. It is seven separate conditions, each with its own threshold, its own severity and its own suggested action, evaluated together and reported as a list.
The seven
| Signal | When it fires | Severity |
|---|---|---|
| The subscription period has ended | Immediately after the end date passes | Critical |
| A free plan is ending | Within fourteen days of the end | Warning |
| Auto-renew is off on a paid plan | Within thirty days of the renewal | Warning |
| Billing status is not active | Any status other than active | Critical when past due, cancelled or expired; a warning otherwise |
| Renewal payments have failed | Any failed attempt on record | Warning |
| No payment method on file | A paid plan with nothing chargeable saved | Critical within seven days of renewal, otherwise a warning |
| The grace period is ending | Within seven days, or already past | Warning, or critical once it has passed |
Alongside those sits an eighth signal at a lower level — a watch rather than a warning — for a paid workspace whose billing data has not been reconciled with the provider in a fortnight, or ever. That one is not about the customer at all; it is about whether the picture being shown is current.
The one that fires without a failure
A paid workspace with no saved payment method is the signal worth understanding, because it is reachable without a single payment ever going wrong. Paying through a channel that leaves no reusable authorisation behind produces exactly this state, as does a subscription that failed to be created in the first place — which leaves auto-renew off and no card saved. Everything looks paid, everything works, and the renewal has nothing to charge. It is caught before the date rather than at it, which is the entire value of evaluating this as a condition rather than waiting for a failure.
Why thresholds rather than a single date
Each signal gets a window sized to how long it takes to fix. That is the design decision underneath the five numbers, and it is worth stating because a single "renewal is coming" warning would be either too early to act on or too late to act at all.
-
Fourteen days for a free plan ending
Choosing a paid plan is a decision that may need somebody else's approval. Two weeks is enough for a conversation and not so long that the warning becomes background noise.
-
Thirty days for auto-renew being off
The longest window in the set, because the fix is a deliberate act somebody has to remember, and because a month of visibility means the renewal date is never the first time it is discussed.
-
Seven days for a grace period ending
The shortest, because by this point the situation is already known and what remains is urgency rather than notice.
-
Fourteen days for a stale reconciliation
Not about the customer at all — it is the system saying its own view of the subscription may be out of date, which is exactly the thing that would make every other signal unreliable.
Every warning is sized to how long the fix takes, not to how bad the outcome is.
Deduplicated on the fact, not the rule
Several of these can be true at once and several of them can point at the same underlying date. A subscription that has ended, a grace period that has passed and a billing status that is no longer active are frequently one situation described three times.
The list is therefore reduced by the combination of what the signal is called and what date it concerns, so two rules landing on the same fact on the same day report once. That keeps a genuinely bad situation from producing a wall of alerts, which is how people learn to skim them.
Where these show up
Three places, on three schedules, and it is worth knowing which is which because they serve different people.
- A daily reminder to the workspace, at twenty-five to ten in the morning, so the organisation that has to act hears about it.
- A daily digest to whoever runs the platform, earlier, so a pattern across many workspaces is visible before individual ones lapse.
- A nightly reconciliation with the payment provider, at ten past three, which is what keeps the underlying data current — and whose absence is what the stale-sync watch is reporting.
A separate nightly job charges add-on renewals. That is worth mentioning here only because a failed add-on charge presents as the same billing-status and failed-attempt signals as a plan renewal, and the distinction matters when working out what actually needs fixing.
What to do with the list
A critical signal appears
Treat the date as the deadline, not the notice
Critical means the situation has already occurred — a period that ended, a grace window that closed, a renewal within a week with nothing to charge.
Auto-renew is off and nobody turned it off
Check whether a subscription was ever created
A subscription that failed to be created leaves auto-renew off with no card saved, and both signals fire together. That pairing is diagnostic.
Everything looks fine and the sync is stale
Reconcile before believing the picture
A watch on a stale sync is the system telling you its own view may be a fortnight old. Every other signal is computed from that view.
You are on a free plan
Note the fourteen-day window
It is the only warning you will get, and choosing a plan is usually not a decision one person makes alone.
Five questions to ask about billing warnings
How much notice do we get?
A good answer sounds like
Named windows per condition.
What ours actually is
Fourteen days for a free plan ending, thirty for auto-renew off, seven for a grace period, and immediate for a period that has ended.
Does a warning mean a payment failed?
A good answer sounds like
Not necessarily.
What ours actually is
Not necessarily. A paid workspace with no saved card is reachable without any payment ever failing, and it is reported as its own condition.
Do overlapping problems produce overlapping alerts?
A good answer sounds like
No.
What ours actually is
No. The list is reduced by what the signal is and what date it concerns, so one situation described three ways reports once.
Who is told?
A good answer sounds like
Both sides.
What ours actually is
A daily reminder to the workspace and a daily digest to whoever runs the platform, on separate schedules.
How do you know the billing data is current?
A good answer sounds like
A freshness signal.
What ours actually is
A nightly reconciliation with the provider, and a watch-level signal when a paid workspace has not been reconciled in a fortnight.
What AWRA OpsHub does today
- Seven distinct billing risk conditions evaluated per workspace, each with its own threshold, severity, description and suggested action.
- A separate watch-level signal for a paid workspace whose billing data has not been reconciled with the provider in a fortnight or ever.
- Named windows sized to how long each fix takes — fourteen days for a free plan ending, thirty for auto-renew off, seven for a grace period closing.
- Detection of a paid workspace with no chargeable payment method on file, which is reachable without any payment having failed.
- Escalation from warning to critical as a date approaches, rather than one severity per condition.
- A list deduplicated on the signal and the date it concerns, so one situation described by three rules reports once.
- A daily reminder to the workspace and a separate daily digest to whoever runs the platform.
- A nightly reconciliation with the payment provider, and a separate nightly charge for add-on renewals.
- A summary reducing a list of risks to a single label, severity and count.
More we can add to your workspace
- A history of when each signal first appeared, so a workspace that has carried a warning for two months is distinguishable from one that raised it yesterday.
- An escalation to a second contact when a critical signal goes unactioned, rather than repeating to the same recipient.
- A projected date of restriction on the workspace itself, stated plainly rather than inferred from the signals.
- A distinction between a plan renewal failure and an add-on charge failure, which present through the same status and attempt signals today.
- A self-service way to confirm the payment method will work, before the renewal rather than at it.
- A per-signal mute, for the workspace that has deliberately disabled auto-renew because it pays by invoice.
Where we point you to a specialist
- We will not restrict a workspace without having warned it. Every condition here carries a window sized to the fix, and the point of evaluating seven separate signals rather than one is that an organisation losing access should have heard about it several times through several routes first.
- How you pay, and whether you keep a card on file, is your commercial arrangement. The signal about a payment method not yet on file describes a consequence — that an automatic renewal has nothing to charge — rather than instructing you to save a card.
- We will not act on a stale picture as though it were current. Where reconciliation with the provider has not happened, that is reported as its own signal rather than allowing every other signal to be computed silently from data a fortnight old.
A history of when each signal first appeared is the contained piece here, and it is the one that separates a workspace drifting towards a problem from one that has been carrying the same warning since March.
From signals to a lapse that never happens
The conditions and the thresholds are right. What would close the remaining distance is memory and escalation — knowing how long a warning has stood, and reaching somebody else when it does not move.
When each signal started
A first-seen date per condition, so a two-month-old warning reads differently from a new one.
Escalation to a second contact
A critical signal that has gone unactioned reaching somebody other than the person already ignoring it.
A stated restriction date
The date access would be restricted, said plainly on the workspace, rather than inferred from the signals around it.
We publish scope, not dates.
Scope billing visibilityCheck whether a card is actually on file
It is the one signal that fires without anything having gone wrong, and it is the one most often discovered on the renewal date. Confirming it takes a minute.
Talk through billingFrequently asked questions
How much warning does a workspace get before losing access?
It depends on the condition, and that is deliberate. A free plan ending is flagged fourteen days out, auto-renew being off is flagged thirty days before the renewal, and a grace period closing is flagged seven days ahead. Each window is sized to how long the fix takes rather than to how serious the outcome is.
We have never had a payment fail. Why are we being warned?
Most likely the missing payment method signal, which is reachable without any failure. Paying through a channel that leaves no reusable authorisation behind produces it, as does a subscription that failed to be created — which leaves auto-renew off and no card saved. Everything works until the renewal, which has nothing to charge.
Why do several warnings sometimes describe the same thing?
They should not, and the list is reduced on the combination of the signal and the date it concerns to prevent it. A subscription that has ended, a grace period that has passed and a status that is no longer active are frequently one situation, and reporting it three times is how people learn to skim alerts.
What is the stale sync warning about?
It is the only signal that is not about your billing at all. It reports that the picture being used to compute every other signal has not been refreshed against the payment provider in a fortnight. Reconciliation runs nightly, so this appearing means the reconciliation itself has stopped — which makes it the first thing to resolve rather than the last.
Who gets told when a workspace is at risk?
Two audiences on two schedules. The workspace receives a daily reminder in the morning so the people who can act hear about it, and whoever runs the platform receives a separate daily digest so a pattern across many workspaces is visible before individual ones lapse.
We pay by invoice and keep auto-renew off deliberately. Can we stop the warning?
Not per signal today — a muted condition for a workspace with a deliberate arrangement is named on the list above. It is the most reasonable request against this feature, because a warning that describes an intentional arrangement teaches its recipient to ignore the whole class.
