Patch planning to verification

Step by step

1. Catalog the patch Admin

   Admin records the patch ID, title, product, version, severity and release date. The operator checks that identity against the intended release before selecting work.

   • Release identified
   • Updates Patch catalog

2. Select the asset Patch Operator

   Patch Operator confirms the asset tag and service. The service owner reviews criticality where the planned work may affect availability.

   • Equipment and owner confirmed
   • Updates Assets, Services

3. Review the change Change Manager

   Change Manager examines risk, the scheduled window and rollback plan with Service Owner. Approved work proceeds; a rejected change returns for revision.

   • Risk and window decision recorded
   • Updates Changes, Services
   ApprovalA person approves before the work moves on.

4. Schedule the attempt Patch Operator

   Patch Operator creates the attempt for the selected asset and patch. The planned service window remains visible on the change.

   • Asset-specific work planned
   • Updates Patch attempts, Patch catalog, Assets

5. Record installation Patch Operator

   Patch Operator enters the actual start date and marks the attempt Installing. If the service is disrupted, Incident Responder records an incident for the affected asset and service.

   • Actual work and impact recorded
   • Updates Patch attempts, Incidents

6. Verify the outcome Patch Operator

   Patch Operator enters the completion date and records Verified, Failed or rolled back. Change Manager reviews the result before closing the change decision.

   • Result reviewed
   • Updates Patch attempts, Changes

Admin

, Patch Operator, Change Manager, Service Owner, Incident Responder.