AI for SOPs: Turn a Real Process Into Checked Instructions

Use AI for SOPs by giving it evidence of how a task is actually performed, asking for a structured draft, and testing those instructions with the people who do the work. An SOP, or standard operating procedure, should describe the approved process; an AI draft is only a proposal until that process has been checked.

The hardest parts are usually hidden assumptions, exceptions, and outdated instructions. fenbs can keep the process rules, reusable drafting prompts, and approved changes together so another assistant does not rewrite the procedure from an incomplete conversation.

How do you create an SOP with AI step by step?

Start with one ordinary process, such as handing approved design files to a client. Choose a process owner who can answer questions and approve the final instructions. Draft one complete path before trying to document every activity in a department.

1. Define the trigger and finish. For example, the process begins when a client approves the final design and ends when delivery is confirmed.
2. Observe someone performing the task. Record the actual actions, required inputs, checks, and points where they ask another person for help.
3. Remove private details from the material you will share with the AI. Provide approved notes, sample forms, and relevant source instructions.
4. Ask the AI for a numbered draft using only those sources. Require it to list missing information separately rather than inventing steps.
5. Have a suitable person follow the draft and record where they hesitate, stop, or need information the document does not provide.
6. Revise, have the process owner approve it, and record the current version, owner, and reason for the next review.

Keep “what happens now” separate from “what we want to improve.” Otherwise, a draft can quietly change the workflow while pretending to document it. Put a proposed improvement in a separate task so someone can assess its effects before approval.

What source material should you give the assistant?

Provide the smallest complete set of evidence for the chosen process. A generic job description rarely contains enough detail. Notes from a walkthrough, the form someone actually fills out, and a sample of an acceptable result are more useful than a broad request to “write a professional SOP.”

• Purpose and scope: who uses the procedure and which situations it covers.
• Start conditions: approvals, access, equipment, or information needed before beginning.
• Observed actions: the sequence people actually follow and the names they use for things.
• Checks: what someone inspects before continuing and what a passing result looks like.
• Exceptions: when to stop, who to contact, and which cases this procedure does not handle.
• Ownership: the person responsible for approving and maintaining the instructions.

For the design-file example, distinguish creating an export from approving its contents. The assistant should not assume that clicking Export means a client has approved the work. Give it the actual approval rule and require the draft to preserve that distinction.

This is a practical use of an AI brain: keeping the approved facts around the task available when another session helps revise the instructions.

What makes AI-generated instructions easy to follow?

Write actions in the order a person performs them. State where the action happens, what to do, and what result to expect when a check is necessary. Replace “handle the delivery appropriately” with the specific action and decision that your team has approved.

Google’s procedure-writing guidance↗ (opens in a new tab) recommends numbered steps, generally one action per step, and clear context. Apply those principles to ordinary office work too. A short step with a visible outcome is easier to test than a paragraph mixing instructions, explanations, and exceptions.

Keep the terminology stable. If a form calls a field “Delivery contact,” use that name rather than alternating between recipient, customer owner, and account lead. Define genuinely necessary specialist words once. The goal is a reader completing the task correctly, not a document sounding more formal.

What prompt keeps the AI from inventing the process?

Ask for a draft and a gap list together. Make the source boundary explicit, and tell the assistant how to handle a contradiction. A blank marked for the process owner is easier to fix than an invented rule buried in confident prose.

Draft an SOP from the approved notes below.
Audience: [who performs this task]
Trigger: [what starts it]
Finished result: [what ends it]
Source material: [walkthrough notes and approved instructions]

Include purpose, prerequisites, numbered actions, checks, exceptions, and owner. Use only the supplied process facts. Preserve explicit approvals and stop conditions. Do not invent tools, responsibilities, deadlines, or safety instructions. List missing or contradictory information as questions for the process owner. Keep proposed improvements separate from the current process.

Use a second pass to ask which steps contain assumptions or combine several actions. Save the useful prompt in fenbs Skills and prompts, and keep process choices in Decisions and rules so the shared record separates reusable instructions from human approval.

How do you test an SOP before people rely on it?

Ask a suitable reader to follow it using a safe example. Watch without filling in every missing detail. When they pause, record the precise missing input, unclear term, or unexpected result. A reader needing your verbal explanation is evidence that the written procedure needs work.

Test at least one exception as well as the ordinary path: an absent approval, an unavailable file, or a failed check. Confirm that the instructions explain how to stop and reach the responsible person. Do not improvise dangerous situations just to test a document; use an appropriate review method for the work.

For safety-related processes, involve workers and qualified reviewers who know the job. OSHA’s worker-participation guidance↗ (opens in a new tab) calls for worker involvement in developing and revising safety procedures. AI drafting does not replace their knowledge or the specialist review your process needs.

Mark the result accurately: draft checked against a sample, approved for use, or still waiting on a specific question. Keep publishing separate from approval. The broader guide to using AI at work explains why review remains part of the task.

How to do this with fenbs

1. Create a free account, free for one person with no credit card, and add a project for the process you are documenting.
2. Add tasks for observation, drafting, walkthrough testing, and resolving gaps. Keep the source document links and current process notes with the project.
3. Save the drafting prompt in Skills and prompts. Record the owner’s approved instructions in Decisions and rules, with unanswered questions left open.
4. Connect your supported assistant through Integrations and ask it to read the project context before drafting or proposing revisions.
5. Keep the repeatable process in Routine processes and record checks on its tasks. Save Where we left off with the current document, unresolved questions, and next review step.

fenbs is useful for keeping the work and decisions around a procedure available to connected assistants. It does not record screen walkthroughs or replace a specialist document-control system. Use a document tool for the final formatted SOP when that is what your readers need.

How do you keep the procedure current?

Review it when a tool, approval rule, or source process changes, and when someone reports that the steps no longer match the work. Record what changed and why. Do not silently replace a tested instruction with an AI suggestion because the new wording reads more smoothly.

Keep a short example of the mistake each revision fixed. For more reusable drafting patterns, see AI documentation prompts; technical API references have their own needs, covered in API documentation. The AI at work hub collects related workflows.