Standard operating procedures for IT: how to write them and why they matter

Every time a technician resolves a ticket the same way their colleague does it, efficiently, correctly, first time, it’s either because they’re both experienced enough to know the right approach, or because a standard operating procedure (SOP) documents exactly what to do. The first depends on people. The second works regardless of who’s on shift.

The people dependency is getting more expensive. According to the 2026 Kaseya State of the MSP Report, difficulty hiring skilled technicians jumped from 9% to 16% year over year. Well-documented SOPs are one of the most direct ways to reduce that dependency, because they transfer institutional knowledge from the individuals who hold it into a system that any technician can use. Download the full report.

SOPs are one of the highest-use investments in IT operational quality. A well-written SOP for a common task reduces resolution time, reduces errors, enables less-experienced technicians to handle more complex issues, and ensures that service quality doesn’t degrade when key people are unavailable. The challenge has always been keeping them current. This guide covers what IT SOPs should include, how to write them effectively, and how automated SOP creation through IT Glue’s Cooper Copilot Smart SOP Generator has changed what it takes to maintain a knowledge base that stays useful over time.

What is an IT SOP?

An SOP is a documented, step-by-step procedure for completing a specific task or handling a specific type of situation. In an IT context, SOPs cover the routine work of IT operations: onboarding new users, configuring devices to baseline security standards, responding to specific alert types, performing backup verification, troubleshooting common application errors, and executing change management procedures.

The value of an SOP is consistency. The same procedure followed by any technician produces the same outcome. That’s what allows IT teams and MSPs to scale service delivery without proportionally scaling the expertise required at each level of the team. It’s also what protects service quality when a senior technician is unavailable, on vacation, or gone. The knowledge lives in the system, not the person.

What IT SOPs should cover

A knowledge base built around the highest-frequency, highest-consequence tasks earns the most return. The SOP categories that consistently deliver the most immediate value are the following.

New user onboarding

Account creation in Active Directory and Microsoft Entra ID (formerly Azure AD), email provisioning, application access grants, device configuration, security profile application (MFA setup, EDR enrollment), and equipment ordering and provisioning. A complete onboarding SOP ensures nothing is missed and that every new employee starts with the correct access and security baseline.

Device provisioning and configuration

Steps for setting up a new Windows or macOS device: OS configuration, security baseline application, software installation, domain or Entra ID join, endpoint enrollment in RMM and EDR, backup agent installation, and asset registration in the documentation system.

User offboarding

Account disablement, access revocation across all systems, email and data archiving, device recovery, and asset record update. Offboarding SOPs are critical for security. An account that stays active after an employee’s departure is an access risk that a documented procedure prevents.

Incident response procedures

For common incident types: disk space alert workflows, service restart procedures, password reset workflows, connectivity troubleshooting sequences. These SOPs let Tier 1 technicians resolve common incidents consistently without escalation.

Security baseline verification

Periodic checks that endpoint security controls are in place: MFA status, EDR running, OS patched within policy, backup agent connected, disk encryption enabled. Standardized checklists ensure consistent security posture verification regardless of who performs the check.

Client-specific procedures

For MSPs, client-specific SOPs covering applications, configurations, and support approaches unique to individual clients. These are the SOPs that prevent tribal dependency on the one technician who “knows that client.”

How to write an effective SOP

The most common reason SOPs fail to get used is that they were written by someone documenting a process rather than someone thinking about the person doing the task. An SOP written from the perspective of the documenter tends to be long, narrative, and general. An SOP written from the perspective of the technician is short, specific, and actionable.

Specific steps, not general guidance, is the core principle. “Configure security settings” is not a useful step. “Open Local Security Policy, navigate to Account Policies, Password Policy, and set Minimum Password Length to 14 characters” is. The level of specificity should match the expertise level of the technician expected to follow it.

Expected outcomes turn a list of steps into a verification tool. After each significant step, document what the screen should show, what confirmation message should appear, what the system state should be. This lets technicians verify they’re on track and identify when something has gone wrong before it compounds.

Decision branches should be explicit. Real procedures branch. “If X, do Y; if Z, do W.” Documenting those branches prevents a technician from stopping when they encounter a condition the SOP didn’t anticipate, which is exactly when the error usually happens.

Related documentation should be linked in context. An onboarding SOP should link to the device provisioning SOP, the application access matrix, and the credential records for systems being configured. A step that requires another resource but doesn’t provide it tends to get skipped.

Write for the reader, not the record. A two-page procedure a technician follows delivers more value than a six-page SOP that lives in the knowledge base unread.

Why SOPs go stale and what it costs

The structural problem with SOPs isn’t creating them. It’s keeping them current. Systems change. Tools get replaced. Applications get updated. A configuration step that was accurate in January may be wrong by April, but the SOP still says January.

An outdated SOP is worse than no SOP. It misdirects a technician who trusts the documentation, produces a wrong outcome they may not immediately recognize as wrong, and erodes trust in the knowledge base. Once technicians learn that the SOPs are sometimes outdated, they stop using them, and the knowledge base stops working.

The traditional answer to SOP currency is review cycles: quarterly reviews, ownership accountability, update triggers linked to change management. All of those are still valid and necessary. But they depend on technicians taking time they don’t have to write documentation for work they’ve already finished.

Automated SOP creation with IT Glue’s Smart SOP Generator

Cooper Copilot’s Smart SOP Generator inside IT Glue is purpose-built to solve the documentation-from-finished-work problem. Instead of requiring a technician to write up a procedure after completing a task, the Smart SOP Generator captures what the technician does during the task and turns those actions into a structured SOP automatically.

The workflow is simple. A technician opens the IT Glue browser extension and starts a Smart SOP Generator session. As they work through a procedure in their browser, every click, keystroke, and navigation step is recorded. Each action becomes a documented step, with an automatically captured screenshot, in a structured procedure that follows the sequence of what was actually done.

When the session ends, the technician names the SOP, assigns it to the relevant client or folder inside IT Glue, and publishes it. The result is a step-by-step procedure with screenshots built from the exact actions of the actual process, not a retrospective reconstruction. Screenshot editing tools allow sensitive information to be blurred before publication. Steps can be reordered, annotated, or manually edited. Smart section detection groups related steps into logical sections automatically.

The adoption numbers reflect how much this changes the documentation calculus. IT Glue users generated more than 100,000 SOPs in the first six months after the Smart SOP Generator launched. That’s documentation that would previously have required a separate work session after each procedure, now being produced as a byproduct of normal work.

The Smart SOP Generator is also available in MyGlue, the end-user portal inside IT Glue, which extends the same capability to clients and end users who need to document their own workflows alongside the IT-managed documentation and credentials they already access in MyGlue. For MSPs, this removes the friction of documenting processes on the client side that previously required a technician’s time to capture.

Explore the Smart SOP Generator inside IT Glue.

SOP management for MSPs: client-level documentation

For MSPs, SOPs serve two distinct purposes. Inside the MSP’s own operations, they standardize how work gets done across the team. Across client environments, they capture the client-specific knowledge that allows any technician to serve any client at a consistent standard.

The second purpose is the more operationally fragile one. Client-specific documentation tends to live in the memory of whoever has been serving that client longest. When that person is unavailable, the team’s ability to serve that client at the same level degrades. A ticket that normally takes 15 minutes takes 45. The client notices. The relationship absorbs the cost.

Consider the common shape of this problem. An MSP’s most experienced technician, who manages the relationship with a 75-user legal firm running a specialist case management application, goes on extended leave unexpectedly. The client’s SQL database service crashes. The on-call technician knows the general troubleshooting approach for SQL Server but doesn’t know this client’s specific licensing configuration, the non-standard port the application uses, or the particular restart sequence the vendor requires. Without a client-specific SOP, the ticket escalates, resolution time stretches, and the client calls to ask why this is taking so long.

With an IT Glue knowledge base that holds client-specific SOPs alongside asset records, network documentation, and credentials, that ticket resolves in the same 15 minutes it would have taken the regular technician. The knowledge is in the system, not the person.

IT Glue’s integration with Datto RMM, Kaseya VSA 10, and Datto Autotask PSA means that asset data populates the knowledge base automatically from discovery, and SOPs are accessible directly within the service desk workflow. The Smart SOP Generator means client-specific procedures get built from the live sessions technicians already run, not from documentation sessions scheduled separately and consistently deprioritized.

IT SOPs work when they’re current, specific, and accessible at the point where the work happens. For most IT teams, the gap between those requirements and operational reality has been a resourcing problem. Documentation takes time. Keeping documentation current takes more time. In a team that’s already stretched, that time loses to urgent work every week. Tools that generate SOPs from live technician sessions, and surface those SOPs in the service desk at the moment a ticket opens, are what close that gap practically rather than aspirationally.