Managed cadence, named: RMM, patch rhythm, and device lifecycle.
Managed cadence has been the vaguest lane on this site — tool-driven checks, an exception queue, a review. Here is what actually runs underneath those words: RMM-driven monitoring, a defined patch rhythm, and the enroll, retire, and replace steps that carry a device through its working life.
What runs inside managed cadence.
Useful when a practice wants to evaluate this lane by its actual mechanics, the way the rest of the catalog can already be evaluated.
RMM alert triage against agreed thresholds — disk space, failed backups, stopped services — patch-rhythm execution for OS and named third-party applications on a defined cycle with reboot coordination, device enrollment (baseline configuration before a device reaches its user), device retirement (deprovisioning, access removal, and data handling per the client's instruction), and replacement coordination staging a new device against the retiring one's profile.
A patch cycle completes and is verified — not just pushed — against the agreed device population, with exceptions listed by device and reason.
The approved RMM/MDM platform, an agreed patch cadence and maintenance window, a device inventory of record, an enroll/retire checklist, and clarity on who procures the hardware itself.
Patch rhythm, defined precisely.
A vague version of these terms is how "we patch regularly" quietly becomes an unmet expectation. A precise version is how the lane definition can actually be tested.
- Ring or wave
- Which devices patch first, so a bad update is caught before it reaches every machine at once.
- Maintenance window
- The agreed hours a reboot is allowed to interrupt someone's work.
- Deferral and exception
- What happens to a device that cannot patch on schedule, and who is told about it.
- Verification
- Confirming a patch actually applied — not just that it was sent — before the cycle is marked complete.
Who owns what in the device lifecycle.
| RMM/MDM platform licensing | Confirmed at intake — practice or client, never assumed by delivery. |
|---|---|
| Patch-cycle definition and maintenance window | Selling practice approves; delivery proposes from experience. |
| Emergency or zero-day patch decision | Named owner via the escalation matrix, not a standing default. |
| Hardware procurement and warranty | Practice or client, confirmed separately from the administration lane. |
Ask these before assuming a fleet is covered.
- Does the lane name the actual device population, or just "endpoints"?A device that is not on the list is not in the lane, whatever it looks like.
- Is a completed patch cycle verified, or only reported as sent?The two are not the same claim.
- What happens to a device that repeatedly fails to enroll or patch?Recurring failure should trigger a review, not repeated silent retries.
- Who decides an out-of-cycle emergency patch gets pushed early?Name the owner before the next zero-day, not during it.
See where this sits in the catalog and the rate.
The managed-cadence entry in the service catalog is what Plus adds on top of Essential; the review cadence is where its exceptions and patterns get discussed.