diff --git a/Policies & Guidelines/IT/Change Management.md b/Policies & Guidelines/IT/Change Management.md
index 640aa09..69a689f 100644
--- a/Policies & Guidelines/IT/Change Management.md	
+++ b/Policies & Guidelines/IT/Change Management.md	
@@ -6,6 +6,10 @@ Permission changes are sometimes necessary if a role of an employee changes or i
 
 Permissions should always be defined as low as possible and only get expanded if required. The IT department can decide to reject a permission change if they consider the request inappropriate.
 
+Potential documents to be changed are:
+
+* Permission List
+
 ### Flowchart
 
 ```mermaid
@@ -24,6 +28,23 @@ graph TD;
 
 ## Software
 
+Software changes include software updates, new software or functional/feature changes. Change requests can be made by any employee but must get approved by the respective HOD. If the change request is justified the IT department performs the change in a testing environment where the employee or HOD can test the change.
+
+The IT department can decide to reject a permission change if they consider the request inappropriate.
+
+Potential documents to be used are:
+
+* Third Party Software Validation - New.md
+* Third Party Software Validation - Update.md
+
+Potential documents to be changed are:
+
+* IT Equipment & Software
+* Automated Jobs
+* Permission List
+* Approved Customer Software
+* Key Supplier Evaluation
+
 ### Flowchart
 
 ```mermaid