AI Can Write the SOP. It Cannot See Your Weird Environment.
AI is very good at writing an SOP.
Give it a topic and a few instructions, and it will happily produce a beautiful document with headings, numbered steps, warnings, helpful tips, and a conclusion that sounds like it has been working in your IT department since 2007.
There is only one problem.
It has never actually been in your IT department.
It does not know that the official process says one thing, the real process says another, and one ancient exception is being held together by a service account named tempadmin.
It does not know that the SharePoint site has three permission groups with nearly identical names. It does not know that the button in the instructions moved six months ago. It does not know that the “temporary” workaround has been in production since the last presidential administration.
AI can write the SOP.
It cannot see your weird environment.
What AI does well
AI is useful for the parts of documentation that require structure and language.
It can help you:
- Turn rough notes into a readable procedure
- Organize steps into a logical order
- Rewrite technical language for a nontechnical audience
- Create a troubleshooting checklist
- Suggest missing sections
- Convert a long incident report into a knowledge-base article
- Create a first draft from meeting notes
- Produce alternate versions for technicians, managers, and end users
That is valuable. Documentation often gets delayed because the person who understands the system does not have time to make the notes pretty.
AI can take the ugly notes and give them a spine.
What AI cannot know by itself
AI cannot safely fill in facts it has never been given.
It does not know:
- Which version of Microsoft 365 your organization uses
- Whether a user has the permissions required for a step
- Which legacy systems are still in production
- Whether a change requires approval
- Which exceptions exist in your environment
- What your naming standards are
- Whether the documented process is still accurate
- What will break if someone follows the instructions literally
This is where people get into trouble.
AI writes a confident sentence such as, “Select the Manage Permissions button.”
You open the screen.
There is no Manage Permissions button.
There is a button called something else, the user lacks access, or the option only appears for a different role. The document looks professional, so someone assumes the problem is user error.
Now the organization has a polished wrong answer.
The human still has to validate reality
The safest workflow is simple:
- Give AI the actual notes, screenshots, error messages, and system details you are allowed to share.
- Ask it to draft the procedure.
- Review every technical step against the real environment.
- Test the procedure with an account that has the intended permissions.
- Have someone unfamiliar with the process follow it.
- Correct anything unclear or inaccurate.
- Add an owner and review date.
- Store the final version where people can find it.
That last part matters.
A perfect SOP hidden in someone’s desktop folder is still a scavenger hunt.
Put it in the SharePoint knowledge base, service desk system, onboarding site, or other location people already use.
Use AI as the documentation assistant
AI should help create the document.
It should not quietly become the system owner, security reviewer, change manager, and person who gets blamed when production catches fire.
The IT professional still decides:
- What is accurate
- What is safe
- What requires approval
- What belongs in the final procedure
- Who is allowed to perform the task
- When the document needs review
AI can suggest.
The environment gets the final vote.
The practical test
Before publishing an AI-assisted SOP, ask:
- Did this step work in our actual environment?
- Does the intended user have the required permissions?
- Are the screenshots current?
- Does the process include exceptions?
- Does it explain what success looks like?
- Does it say what to do if the step fails?
- Has someone else tested it?
- Is the owner and review date recorded?
If the answer to those questions is no, you have a draft.
You do not have documentation yet.
AI is excellent at turning chaos into a first draft.
It is terrible at knowing which part of the chaos is load-bearing.
That is still our job.
