Chapter 4 of 425% of exam
Operational Procedures
Operational procedures are the professional practices that keep IT work safe, consistent, and accountable. They include documentation, change management, physical and electrical safety, privacy and environmental responsibility, professional communication, and the basics of scripting for automation. This chapter explains why these procedures matter and how a technician applies them every day.
Documentation
Good documentation captures how systems are built and what has changed, making support faster and more reliable. Diagrams, inventories, and knowledge bases turn individual experience into shared, reusable knowledge. Without them, troubleshooting becomes slow and accountability suffers.
Keep documentation current
Accurate network diagrams and asset inventories speed troubleshooting and support consistent, informed decisions.
Track issues in a ticketing system
A knowledge base and ticketing system record incidents and proven solutions for consistent, efficient support.
Maintain an asset inventory
A bill of materials or asset inventory lists components and devices with details for tracking and procurement.
Log who changed what
A change log and updated documentation record who made each change and when, supporting accountability and troubleshooting.
Change Management
Change management controls how modifications are proposed, reviewed, and implemented so that changes improve systems without causing avoidable outages. A defined process weighs risk, sets scope, and provides a way back if something goes wrong. It brings order and accountability to production changes.
Require approval before changes
Significant changes need a documented request, risk analysis, and approval by a change board before implementation.
Prepare a rollback plan
A rollback or back-out plan defines how to revert a change safely if it causes unexpected problems.
Define the scope
Documenting scope clarifies exactly what will and will not be affected, guiding testing and communication.
Verify end-user acceptance
A verification step after implementation confirms the change works as intended before the change is closed.
Safety
Safety protects both the technician and the equipment from harm. Electrostatic discharge, physical injury, and fire are real risks that established practices mitigate. Following them consistently prevents accidents and costly damage.
Guard against ESD
An anti-static wrist strap connected to ground equalizes charge and prevents static from damaging sensitive components.
Lift with proper technique
Bend the knees, keep the back straight, use the legs, and hold heavy loads close to the body to avoid injury.
Use the right fire extinguisher
Class C extinguishers are rated for energized electrical fires and use a non-conductive agent.
Clean with compressed air safely
Use short bursts, keep the can upright, and hold fans still so they do not over-spin and get damaged.
Privacy and Environment
Technicians routinely handle sensitive data and hazardous materials, both of which carry legal and ethical obligations. Respecting privacy and disposing of materials responsibly protects people and the environment. These duties are core to professional conduct.
Protect regulated data
PII and PHI are protected categories that must be safeguarded from unauthorized disclosure during support work.
Access only what is needed
Handle customer data by accessing only what the task requires and keeping the information confidential.
Consult the SDS for chemicals
A Safety Data Sheet provides handling, storage, and disposal guidance for batteries, toner, and other hazardous materials.
Recycle e-waste properly
Dispose of old electronics through certified e-waste programs in line with local environmental regulations.
Communication and Scripting
Professional communication builds trust, and basic scripting skills let a technician automate repetitive work. Handling difficult interactions calmly and notifying users of impact are marks of professionalism. Understanding script fundamentals extends a technician's effectiveness.
De-escalate with active listening
With an upset customer, listen actively, stay calm, and avoid arguing or being defensive.
Communicate maintenance windows
Notify affected users of planned maintenance and expected impact in advance to set expectations.
Know Windows-native scripting
PowerShell scripts (.ps1) use cmdlets and are the native automation language for Windows, while Bash (.sh) is native to Linux.
Understand scripting basics
Constructs such as variables, loops, and comments let scripts store values, repeat instructions, and stay readable for automation.
Test your knowledge
Practice questions on Operational Procedures