What is SOP?
An SOP turns a routine job into written steps that anyone qualified can follow and get the same result. In IT, SOPs cover recurring work such as installing a line-of-business application with company-specific settings, setting up a new employee, offboarding a departing one, verifying backups and patching servers.
What a good SOP includes
- Title, ID and version: so people know they have the current copy
- Purpose and scope: what the procedure is for and where it applies
- Roles: who performs each step and who approves
- Prerequisites: tools, accounts, permissions, license keys and installers
- Numbered steps: exact settings and commands, with screenshots where they help
- Verification: how to confirm the task succeeded
- Exceptions and escalation: what to do when a step fails
- Owner, review date and revision history
Example: custom installation of a software package
- Confirm the user's department is licensed for the application and the PC meets the requirements.
- Get the approved installer version from the internal software share.
- Run the installer with the documented options, for example
msiexec /i app.msi /qnfor a silent install. - Apply the company configuration file that points the application to the correct server.
- Verify the application launches, connects and shows the right license, then record the installation in the ticket and the asset record.
Why SOPs matter
- Consistency: every technician configures systems the same way, which cuts down on "works on one PC but not another" tickets.
- Training: new staff can do the work correctly sooner.
- Compliance and audits: documented procedures show auditors and regulators how work is controlled.
- Change management: the SOP describes the approved way to do a task. Changing the procedure, or the systems it touches, goes through change control, and the SOP is updated afterward.
- Automation: a clear SOP is a ready-made specification for a script.
An SOP is only useful while it matches reality, so it needs an owner and a regular review, plus an update after any incident that exposes a missing or wrong step.
SOP vs. related documents
| Document | What it answers |
|---|---|
| Policy, such as an AUP | What is required or allowed, and why |
| SOP | How to carry out a routine task, step by step |
| Checklist | A short list to tick off while doing the work, such as a new-user setup or end-user termination checklist |
| Knowledge base article | How to fix a specific known problem |
SOP on the CompTIA A+ exam
SOPs are Core 2 documentation material, listed with procedures for custom installation of software packages, new-user setup and end-user termination checklists, and knowledge base articles. Cues:
- Technicians install the same software in different ways and results vary: create and follow an SOP.
- Where to find the approved steps for a custom software installation: the SOP.
- A rule about what users may do with company equipment is a policy, not an SOP.