Documentation & Change Management
Key Takeaways
- Proper documentation includes network diagrams, asset management records, knowledge base articles, standard operating procedures (SOPs), and incident reports — documentation enables consistent and efficient IT support.
- A change management process requires formal requests, risk assessment, approval from a Change Advisory Board (CAB), implementation planning, testing, rollback plans, and post-implementation review.
- A ticketing system tracks all IT support requests from creation to resolution, providing accountability, metrics, trend analysis, and a searchable knowledge base.
- Network documentation should include topology diagrams, IP address assignments, cable labeling, equipment inventory, configuration backups, and vendor contact information.
- Standard Operating Procedures (SOPs) ensure consistent responses to common scenarios like onboarding new employees, handling security incidents, performing backups, and deploying software updates.
Last updated: March 2026
Documentation & Change Management
Documentation Types
Network Documentation
| Document | Contents | Purpose |
|---|---|---|
| Network Topology Diagram | Physical and logical network layout, devices, connections | Visualize network architecture for troubleshooting and planning |
| IP Address Table | IP assignments, subnet ranges, DHCP scopes, static reservations | Prevent IP conflicts, track address usage |
| Cable Management | Cable runs, labeling scheme, patch panel mappings | Quick troubleshooting and maintenance |
| Equipment Inventory | Make, model, serial number, location, warranty status | Asset tracking, replacement planning |
| Configuration Backups | Router, switch, firewall, server configurations | Disaster recovery, quick restoration |
| Vendor Information | Contact details, support contracts, account numbers | Efficient vendor communication during outages |
IT Documentation
| Document | Purpose |
|---|---|
| Knowledge Base (KB) | Searchable articles for common issues and solutions |
| Standard Operating Procedures (SOPs) | Step-by-step instructions for routine tasks |
| Incident Reports | Detailed record of security incidents and responses |
| Acceptable Use Policy (AUP) | Rules for how employees may use company IT resources |
| New Employee Setup Checklist | Standard steps for onboarding (accounts, equipment, access) |
| Offboarding Checklist | Steps when employee leaves (disable accounts, collect equipment) |
Change Management
Change management is a formal process for making changes to IT systems to minimize risk and disruption:
Change Management Steps
- Submit Change Request — Describe the proposed change, reason, and impact
- Risk Assessment — Evaluate potential risks and impact on users/systems
- Approval — Change Advisory Board (CAB) reviews and approves or rejects
- Plan Implementation — Define schedule, steps, resources, and responsible parties
- Create Rollback Plan — Define how to undo the change if it fails
- Schedule Maintenance Window — Choose a time with minimum user impact
- Notify Affected Users — Communicate the change, timeline, and expected impact
- Implement the Change — Execute the planned steps
- Test and Verify — Confirm the change works as intended
- Document — Record what was done, results, and lessons learned
Change Types
| Type | Description | Approval |
|---|---|---|
| Standard | Pre-approved, routine changes (e.g., monthly patches) | Pre-approved |
| Normal | Non-routine changes requiring review | CAB approval |
| Emergency | Urgent changes to address critical issues | Expedited approval (post-implementation review) |
Ticketing Systems
A ticketing system tracks all IT support requests:
Ticket Lifecycle
- New — User submits a request or incident is detected
- Assigned — Ticket is assigned to a technician
- In Progress — Technician is working on the issue
- Escalated — Passed to a higher-level technician if needed
- Resolved — Issue has been fixed
- Closed — User confirms resolution, ticket is archived
Ticket Information
| Field | Purpose |
|---|---|
| Ticket Number | Unique identifier for tracking |
| Priority | Urgency level (Critical, High, Medium, Low) |
| Category | Type of issue (Hardware, Software, Network, Account) |
| Description | Detailed description of the problem |
| Assigned To | Technician responsible |
| Status | Current state (New, In Progress, Resolved, Closed) |
| Notes/Updates | Running log of all actions taken |
| Resolution | How the issue was resolved (added to knowledge base) |
Asset Management
| Concept | Description |
|---|---|
| Asset Tags | Physical labels with barcode/QR code for tracking equipment |
| Asset Database | Centralized inventory of all IT equipment |
| Lifecycle Management | Track from procurement → deployment → maintenance → retirement |
| Warranty Tracking | Track warranty dates to ensure timely vendor support |
| License Management | Track software licenses to ensure compliance |
| Decommissioning | Proper data destruction and disposal of retired equipment |
Test Your Knowledge
What is the primary purpose of a change management process in IT?
A
B
C
D
Test Your Knowledge
What should ALWAYS be created before implementing a significant system change?
A
B
C
D
Test Your KnowledgeOrdering
Arrange the IT ticket lifecycle stages in the correct order:
Arrange the items in the correct order
1
Resolved
2
Assigned
3
Closed
4
In Progress
5
New
6
Escalated (if needed)