Change management: request forms, purpose and scope, risk analysis, change advisory board approval, sandbox testing, rollback and backup plans, end-user acceptance

Many IT outages are caused not by attacks or hardware failures but by well-intended changes made without planning: a firewall rule, a patch, a new driver pushed to every PC. Change management is the formal process for proposing, reviewing, approving, implementing and documenting changes to systems, so they happen in a controlled way with minimal disruption and a clear record. As a technician you will submit change requests, carry out approved changes, and be expected to follow the process even when a change seems small.