# Patch Management Procedure Template, Nine Steps

Canonical: https://patchmanagementpolicy.com/templates/patch-management-procedure/
Last reviewed: 19 Nov 2026

## Patch management procedure

A patch management procedure is the nine-step monthly routine that sits under the policy: it names who does each step and which record each leaves. On the November 2026 cycle, released on Patch Tuesday 10 November, the 14 day window closes on 24 November and the 30 day window on 10 December.

### What a procedure holds that a policy does not

A policy states what must be true: windows, scope, roles. A procedure states what people do, in what order, and what proof results. NIST SP 800-40 Rev. 4 describes enterprise patch management as the process of identifying, prioritizing, acquiring, installing and verifying patches, and breaks a risk response into four actions: plan it (which may include acquiring, validating and testing the patch, and coordinating with change management), implement it, verify it, and monitor it continuously. The nine steps below expand those actions into the order a team can run.

### The November 2026 cycle worked through

| Date | Event | Procedure step |
|---|---|---|
| Tue 10 Nov 2026 | Microsoft monthly security update released; clock starts for class 2 to 5 items from this release | Steps 2 and 3 |
| Thu 12 Nov | Canary set installs; two working days of observation begin | Step 4 |
| Fri 13 Nov | Class 1 internet-facing deadline (3 days) for any exploited item released 10 Nov | Steps 6 and 7 |
| Tue 24 Nov | Class 2 critical deadline (14 days) | Steps 6 and 7 |
| Thu 10 Dec | Class 3 high deadline (30 days); report due within 5 working days of the last deadline | Steps 7 and 8 |
| Mon 8 Feb 2027 | Class 4 medium deadline (90 days) | Step 7 |

Dates computed from the second-Tuesday rule on Microsoft Learn (release cycle page, read 19 Nov 2026) and the general policy's windows. Windows are the site's defaults.

Today is 19 November 2026, so the November cycle is mid-flight: critical items released on 10 November are five days from deadline. Microsoft also publishes an optional non-security preview in the fourth week and out-of-band updates as needed, so step 2 checks vendor channels on more than one day.

### Rollback and stop conditions

Step 6 requires stop conditions written before deployment. NIST's sample procurement questionnaire asks vendors whether they provide rollback capabilities for uninstalling patches and how often customers see significant issues; the answers decide how tight the stop conditions need to be. If the vendor offers no rollback, the procedure's fallback is restoration from a backup taken before the window, noted in the step 4 record.

### The template

```text
# Patch Management Procedure

Sits under: Patch Management Policy [version]. Owner: [Patch coordinator]. Cycle: monthly, starting on the second Tuesday.

## Step 1. Keep the inventory current
Who: Patch coordinator with system owners.
Do: Reconcile discovery output with the inventory; assign an owner to every unowned asset; confirm each asset's maintenance group.
Record: Inventory snapshot dated [date]; list of assets added, removed, unowned.

## Step 2. Watch for releases
Who: Patch coordinator.
Do: Check vendor advisories for every product in the inventory on the release day and again two working days later. Check the CISA Known Exploited Vulnerabilities catalog on each working day.
Record: Release log (product, advisory, release date, vendor label).

## Step 3. Assess and prioritize
Who: Patch coordinator; policy owner for disputes.
Do: Match each release to affected assets; assign the policy class; set the deadline = release date + window.
Record: Assessment sheet (advisory, assets affected, class, deadline).

## Step 4. Acquire and test
Who: Platform administrators.
Do: Download from the vendor's own channel; verify integrity; install on the canary set; observe for [2] working days (class 1: hours).
Record: Canary result and tester, rollback method.

## Step 5. Approve and schedule
Who: System owner.
Do: Approve the deployment and the maintenance window, or state the reason for refusal; refusals go to the exceptions clause.
Record: Approval (name, date), scheduled window.

## Step 6. Deploy
Who: Platform administrators.
Do: Install in the scheduled window in the order canary, then groups; force installation after the grace period; roll back if a stop condition is met: [list stop conditions].
Record: Deployment log per asset (installed, failed, pending, reboot required).

## Step 7. Verify
Who: Platform administrators, checked by the patch coordinator.
Do: Confirm the patch is installed and has taken effect (version, rescan or attestation); chase failed and pending assets.
Record: Verification result per asset; list of assets still open at the deadline.

## Step 8. Report
Who: Patch coordinator.
Do: Send the monthly report defined in policy section 8 to the executive sponsor within [5] working days of the cycle's last deadline.
Record: Report and the data export behind it.

## Step 9. Review the cycle
Who: Patch coordinator, policy owner.
Do: List misses and their causes; change a maintenance plan, ring or window if the same cause occurs twice.
Record: Review notes and any change request to the policy.

```

### Where each step is explained

Each step has a longer page: [inventory](https://patchmanagementpolicy.com/process/inventory/), [monitor for releases](https://patchmanagementpolicy.com/process/monitor-for-releases/), [assess and prioritize](https://patchmanagementpolicy.com/process/assess-and-prioritize/), [acquire and test](https://patchmanagementpolicy.com/process/acquire-and-test/), [approve and schedule](https://patchmanagementpolicy.com/process/approve-and-schedule/), [deploy](https://patchmanagementpolicy.com/process/deploy/), [verify](https://patchmanagementpolicy.com/process/verify/), [report](https://patchmanagementpolicy.com/process/report/) and [review the cycle](https://patchmanagementpolicy.com/process/review-the-cycle/). The windows used in step 3 come from the [general policy](https://patchmanagementpolicy.com/templates/patch-management-policy-template/).

### Questions

**what is a patch management procedure**

A patch management procedure is the step-by-step routine that carries out a patch management policy: who finds releases, who tests, who approves, who deploys and what record each leaves. The template on this page has nine steps. It runs monthly, starting on the second Tuesday.

**patch management procedure template**

The nine-step template above is full text and can be pasted into your document system. Fill the brackets for roles, observation periods and stop conditions. Link it from section 9 of the policy.

**patch management rollback process**

Write the rollback method before deployment and record it at step 4. NIST SP 800-40 Rev. 4 asks vendors whether they provide rollback for uninstalling patches. Where they do not, restore from a backup taken before the window.

### Sources

- [NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning (April 2022)](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf), read 19 Nov 2026
- [Microsoft Learn, Update release cycle for Windows clients](https://learn.microsoft.com/en-us/windows/deployment/update/release-cycle), read 19 Nov 2026

Last reviewed 19 Nov 2026

### Related pages

- [General Patch Management Policy Template, Full Text](https://patchmanagementpolicy.com/templates/patch-management-policy-template/)
- [Patch Management Process in 9 Steps (NIST SP 800-40r4)](https://patchmanagementpolicy.com/process/)
- [Step 7: How to Verify Patches Are Installed](https://patchmanagementpolicy.com/process/verify/)
- [Step 6: Patch Deployment Process and Rollback](https://patchmanagementpolicy.com/process/deploy/)
