A simple schedule + what to inventory + how to communicate maintenance windows.
Make patching predictable and low‑risk: small, regular updates instead of big, scary, overdue changes.
| Cadence | What | Examples | Notes |
|---|---|---|---|
| Weekly (optional) | Critical security fixes | Browser zero-days, emergency vendor advisories | Only when needed; keep it rare. |
| Monthly | Endpoints + apps | Windows/macOS, Office apps, browsers, PDF reader | Pick a “Patch Tuesday + 1 week” window. |
| Quarterly | Edge/infrastructure firmware | Firewalls, routers, Wi‑Fi controllers/APs, NAS, switches | Planned after-hours or low-traffic window. |
| Annually | Lifecycle review | End-of-life devices, OS upgrades | Align to budgeting. |
| Asset | Type | Model | OS/FW | Owner | EOL/Warranty | Notes |
|---|---|---|---|---|---|---|
| __________ | Endpoint/Firewall/Wi‑Fi/Switch/Server | __________ | __________ | __________ | __________ | __________ |
| __________ | ||||||
| __________ |
Copy/paste into email or Teams:
Scheduled maintenance: [Date] between [Time].
Expected impact: [brief] (e.g., short internet interruption / Wi‑Fi restart).
Purpose: security and reliability updates.
If you notice issues after the window, report them to: [contact].
No hard sell - just clarity and practical next steps.
hello@virtusgroup.biz