What Is the Fastest Way for a Small Business to Turn Tribal Knowledge into Written Procedures Using AI?

Summary

The steps

1. 1

   Create the SOP drafting agent

   Before you touch the canvas, create the AI agent that will turn a team member's plain-English description into a numbered procedure. Navigate to Agents in the sidebar. You need the Admin or Create role to see this section. If the section is not visible, see Why Can't I See Agents, Workflows, or Other Sections in Dave by voolama?

   Click New Agent, name it "SOP Drafter", add a description such as "Turns a plain-English task description into a numbered standard operating procedure", and click Create Agent. On the agent detail page, click Create Version. In the Config JSON editor, write a system prompt that constrains the agent to the facts supplied:

   {"systemPrompt": "You are a business process writer for a small business. A team member has described how they do a specific task. Write a standard operating procedure using ONLY the information in their description. Format the output as: (1) Purpose: one sentence. (2) Trigger: when this procedure starts. (3) Steps: numbered list, each step starting with a verb. (4) Decision points: any step where the person must choose between two paths, with the name of the person who decides. (5) Done when: one sentence defining completion. Do not add steps, tools, software names, or decision points that are not in the description.", "model": "gpt-4o", "temperature": 0.2, "maxTokens": 800}

   Low temperature (0.2) keeps the output structured and consistent rather than creative. Click Create Version. The system assigns version number v1 automatically. Version numbers are auto-incrementing integers: v1, v2, v3. You cannot choose or skip version numbers.

   The Config JSON fields Dave by voolama agents accept are: systemPrompt, model, temperature (0.0 deterministic to 1.0 creative), maxTokens, and topP. The exact fields depend on your AI provider. Dave by voolama supports seven AI provider types: OpenAI, Anthropic, Azure OpenAI, Google, OpenAI-compatible, local (Ollama), and custom.

   Do this

   • Go to Agents in the sidebar (Admin or Create role required).
   • Click New Agent, name it "SOP Drafter", add a description, click Create Agent.
   • On the detail page, click Create Version.
   • Paste the Config JSON with your system prompt, model, temperature 0.2, and maxTokens 800.
   • Click Create Version. The system assigns v1 automatically.

   Example

   A hypothetical cleaning company might add to the system prompt: "The business cleans residential properties. Steps must be specific enough that a new employee could follow them on their first day without asking questions. If a step mentions a product, include it only if the team member named it." That specificity stops the agent from inventing product names or sequences the team member did not describe.

   Best practice

   • Name the agent after its function, not its model. "SOP Drafter" is easier to find in a workflow than "GPT-4o Agent".
   • Set temperature to 0.2 or lower for procedural writing. Higher temperature produces more varied output, which is the opposite of what a numbered procedure needs.
   • If you update the SOP format your business uses, create a new agent version with the updated system prompt. Retiring the old version prevents anyone from accidentally selecting it in a new workflow. Retiring is a one-way action in Dave by voolama: you cannot un-retire a version.
2. 2

   Create the workflow and open the Workflow Editor

   Navigate to Workflows in the sidebar. You need the Admin or Curate role to see this section. If the section is not visible, your account does not hold either role. See Why Can't I See Agents, Workflows, or Other Sections in Dave by voolama? for how to diagnose and fix your role assignment.

   Click New Workflow, name it "Write Standard Operating Procedure", add a description such as "Team member describes a task, AI drafts the SOP, the person who does the job checks it, owner approves", and save. The workflow opens in the Workflow Editor: a three-panel canvas with the Node Palette on the left, the canvas in the center, and the Properties Panel on the right. A node and edge counter in the top-right corner of the canvas shows the current count as you build.

   Drag a Start node from the palette onto the canvas. Every workflow requires exactly one Start node. Click Save Version to create your first snapshot. The editor does not auto-save: click Save Version after every meaningful change. Each save creates a new immutable version; previous versions are preserved.

   Do this

   • Go to Workflows in the sidebar (Admin or Curate role required).
   • Click New Workflow, name it "Write Standard Operating Procedure", add a description, save.
   • The Workflow Editor opens. Drag a Start node from the Node Palette onto the canvas.
   • Click Save Version.

   Example

   A hypothetical bookkeeping practice might name the workflow "Document a Bookkeeping Task" and add the description: "Used when a staff member has a repeatable task that is not yet written down. Produces a numbered SOP approved by the owner." That description appears in the workflow list and helps any team member understand the process without opening the editor.

   Best practice

   • Name the workflow after the business outcome, not the technology. "Write Standard Operating Procedure" is clearer than "AI Drafting Workflow 3".
   • Save a version after every meaningful change. Each save is non-destructive: the previous version is always available if you need to roll back.
   • Check the node and edge counter in the top-right corner of the canvas as you build. It shows the current count and helps you spot missing connections before you activate.
3. 3

   Place the User Interaction node to collect the task description

   The first node after Start collects the team member's description of the task. This is the only source the drafting agent is allowed to use. The six fields below map directly to the seven SOP elements defined in What Should a Standard Operating Procedure Include?

   User Interaction node (code: user_interaction, color: blue): Drag a User Interaction node from the Node Palette and drop it below the Start node. Click the node to open the Properties Panel. Change the label to "Describe Your Task". Under the Fields section in the Properties Panel, configure the fields the team member will fill in:

   • Task name (text): a short name for the procedure, such as "Open the shop" or "Process a customer return".
   • Who does this task (text): the role or name of the person responsible. This becomes the named owner in the SOP.
   • When does this task start (text): the trigger, such as "When the first customer arrives" or "When an order is marked returned".
   • Describe every step, in order (textarea): the team member writes out what they do, in their own words, as if explaining it to a new hire.
   • Any decisions or choices in the process (textarea): optional, for steps where the person must choose between two paths. This becomes the decision points section of the SOP.
   • How do you know the task is done (text): the definition of completion.

   Connect Start to this node by dragging from Start's source handle (bottom circle) to this node's target handle (top circle). When a team member submits this task from the Task Inbox, the workflow resumes with those values in its context. Only Admin and Use roles can see and complete tasks in the Task Inbox.

   Do this

   • Drag a User Interaction node below Start. Label it "Describe Your Task".
   • In the Properties Panel under Fields, configure: task name, who does this task, when does this task start, describe every step in order (textarea), any decisions or choices (textarea), how do you know the task is done.
   • Connect Start to User Interaction by dragging from Start's bottom handle to User Interaction's top handle.
   • Click Save Version.

   Example

   A hypothetical small law office might add a seventh field: "Any confidentiality requirements for this task (optional)". That field prompts the team member to flag tasks that touch client data, so the owner can decide whether the SOP needs a confidentiality note before it is stored. ABA Model Rule 1.6 requires lawyers to protect confidential client information; a SOP that touches client files should note that requirement explicitly.

   Best practice

   • Keep the fields to what the agent actually needs. Six fields cover the seven SOP elements from the companion resource at What Should a Standard Operating Procedure Include?.
   • Use a textarea for the step description, not a text input. Team members need room to write naturally.
   • Tell team members in the field label to write as if explaining to a new hire. That framing produces more complete descriptions than "describe the steps".
4. 4

   Add the Agent Interaction node and the first Human Review node

   After the team member submits their description, the workflow passes it to the drafting agent, then immediately routes the draft to the person who does the job for a factual check. This sequence puts the person with first-hand knowledge of the task in the review chain before the owner, because that person is the only one who can catch a step the AI got wrong or missed.

   Agent Interaction node (code: agent_interaction, color: purple): Drag an Agent Interaction node below the User Interaction node. Label it "Draft the SOP". In the Properties Panel under Agent Assignment, select the "SOP Drafter" agent and version v1. Connect the User Interaction node's source handle to this node's target handle. The agent receives the workflow context, including all the fields the team member submitted, and produces a numbered SOP draft. The Agent Interaction node runs automatically and does not create a task.

   Human Review node (first): the person who does the job (code: human_review, color: amber): Drag a Human Review node below the Agent Interaction node. Label it "Check: Does This Match How You Actually Do It?". In the Properties Panel under User Assignment, assign it to the team member who submitted the description, or to the role that covers that function. Connect the Agent Interaction node's source handle to this node's target handle.

   When the workflow reaches this node, it creates a human_review task in the Task Inbox. The task payload contains the original description and the AI-drafted SOP. The team member reads both, checks every step against how the job actually works, and clicks Approve, Reject, or Request Changes. Connect the Reject edge back to the User Interaction node so the team member can re-describe and the agent can redraft.

   For a parallel approval pattern using the same node types for a different business process, see How Do I Build a Refund Request Workflow in Dave by voolama Where a Manager Must Approve Every Refund?. The SOP workflow differs in that it places two Human Review nodes in sequence and routes the first to the person who does the job rather than a manager.

   Do this

   • Drag an Agent Interaction node below User Interaction. Label it "Draft the SOP".
   • In the Properties Panel under Agent Assignment, select "SOP Drafter" and version v1.
   • Connect User Interaction to Agent Interaction.
   • Drag a Human Review node below Agent Interaction. Label it "Check: Does This Match How You Actually Do It?".
   • In the Properties Panel under User Assignment, assign it to the team member or their role.
   • Connect Agent Interaction to this Human Review node.
   • Connect the Reject edge from this Human Review node back to the User Interaction node.
   • Click Save Version.

   Example

   A hypothetical retail shop might assign the first Human Review node to the role "Use" rather than a specific person, so any staff member holding that role can check a draft for their own task. The owner can then see in the audit log which team member approved each SOP draft before it reached the owner's queue.

   Best practice

   • Assign the first Human Review node to the person who does the job, not the owner. The owner approves; the team member checks for accuracy. These are different judgments and should be separate tasks.
   • Connect Reject back to User Interaction, not to Start. This lets the team member update only the description that needs changing, not restart the whole process.
   • Ask team members to use the Comment field when they reject or request changes. The comment is stored in the audit trail and tells the workflow owner what was wrong with the draft.
5. 5

   Add the owner's Human Review node and the End nodes

   After the team member approves the draft, the workflow routes it to the owner for final sign-off. This gate makes the SOP official: only procedures the owner has approved become part of the business's documented processes.

   Human Review node (second): the owner (code: human_review, color: amber): Drag a second Human Review node below the first. Label it "Owner Approval". In the Properties Panel under User Assignment, assign it to the owner or the person responsible for approving procedures. Connect the Approve edge from the first Human Review node to this node's target handle.

   The task payload for this node contains the original description, the AI-drafted SOP, and the team member's approval decision and any comment. The owner reads all of it, optionally adds a comment, and clicks Approve, Reject, or Request Changes. Per the Dave by voolama tasks documentation, task decisions are recorded with the acting user's identity and support SOC 2 CC6.1 (logical access controls) and GDPR Article 30 (records of processing activities) when those compliance modes are active in Dave by voolama.

   End nodes: Connect the Approve edge from the owner's Human Review node to an End node labeled "SOP Approved". Connect the Reject edge to an End node labeled "SOP Declined". Connect the Request Changes edge back to the first Human Review node so the team member can revise the description and the agent can redraft. Every path must end at an End node: dangling paths cause instances to hang at runtime.

   Click Save Version when the graph is complete, then check the node and edge counter in the top-right corner to confirm every node is connected.

   Do this

   • Drag a second Human Review node below the first. Label it "Owner Approval".
   • In the Properties Panel under User Assignment, assign it to the owner.
   • Connect the Approve edge from the first Human Review node to this node's target handle.
   • Drag an End node and label it "SOP Approved". Connect the Approve edge from the owner's Human Review node to it.
   • Drag a second End node and label it "SOP Declined". Connect the Reject edge from the owner's Human Review node to it.
   • Connect the Request Changes edge from the owner's Human Review node back to the first Human Review node.
   • Confirm every path leads to an End node. Check the node and edge counter in the canvas top-right.
   • Click Save Version.

   Example

   A hypothetical accounting practice might configure the owner's Human Review node with a Custom audience notification so the owner gets an email when a new SOP draft is ready for approval. The owner opens the Task Inbox, reads the draft and the team member's approval comment in the Payload section, and clicks Approve. The workflow reaches the "SOP Approved" End node and the instance completes.

   Best practice

   • Do not skip the owner's approval step. The team member checks for accuracy; the owner checks for completeness, business policy alignment, and whether the procedure should be documented at all.
   • Add a comment when rejecting or requesting changes. The comment is stored in the audit log and helps the team member understand what to correct.
   • Connect Request Changes back to the first Human Review node, not to the User Interaction node. If the owner wants a revision, the team member should see the owner's comment and revise the description accordingly, not start from scratch.
6. 6

   Store the approved SOP as an Information node and activate the workflow

   When the owner approves a SOP, copy the final text into an Information node on any workflow canvas where that procedure is relevant. The Information node (code: information, color: indigo) does not affect execution and does not create a task. It keeps the procedure visible to anyone editing the workflow and can be referenced in the system prompt of an Agent Interaction node so the AI agent follows the documented steps when it runs.

   To add the SOP to another workflow: open that workflow in the Workflow Editor, drag an Information node onto the canvas beside (not in) the execution path, label it with the SOP name, and paste the approved procedure text into the node's config. Click Save Version for that workflow.

   To activate the SOP drafting workflow itself: in the Workflows list, open the workflow and change its status to Active. Before you activate, run test instances in Draft status to confirm the agent produces a sensible SOP from a complete description and that the routing logic works. Submit a complete hypothetical task description to test the Approve path, and test the Reject path to confirm the workflow routes back to the User Interaction node correctly.

   Once active, brief two groups: staff who will describe their tasks (they complete User Interaction tasks in the Task Inbox), and the owner (they complete Human Review tasks). Confirm all team members have the Admin or Use role to see and complete tasks.

   For a parallel documentation workflow that uses the same User Interaction plus Agent Interaction sequence for a different output, see How Can AI Turn My Client Meeting Notes into Follow-Up Emails and Tasks?. That workflow routes to a single Human Review node and sends the output externally rather than storing it as an Information node.

   Disclosure: Dave by voolama is the product described in this guide, published by its maker, voolama LLC. This is vendor documentation, not independent legal or compliance advice.

   Do this

   • When a SOP is approved, copy the final text from the completed instance's output.
   • Open any workflow where this procedure is relevant in the Workflow Editor.
   • Drag an Information node onto the canvas beside the execution path. Label it with the SOP name. Paste the approved text into the node's config.
   • Click Save Version for that workflow.
   • To activate the SOP drafting workflow: open it in the Workflows list and set status to Active.
   • Run test instances in Draft status first: one with a complete description (Approve path) and one designed to test the Reject path.
   • Brief staff: they complete User Interaction tasks. Brief the owner: they complete Human Review tasks.
   • Confirm all team members have the Admin or Use role to see the Task Inbox.

   Example

   A hypothetical small marketing agency might store the approved SOP for "How to onboard a new client" as an Information node on their client onboarding workflow canvas. When the onboarding workflow runs, the agent that drafts the welcome email can reference the SOP in its context, so it follows the documented onboarding sequence rather than improvising one.

   Best practice

   • Name the Information node after the SOP, not after the workflow. "SOP: Process a Customer Return" is easier to find than "Information Node 4".
   • Update the Information node when the SOP is revised. When the owner approves a new version of a procedure, update every workflow canvas that references it.
   • Test the Reject path deliberately before going live. It is easy to confirm the Approve path works; the Reject path is the one that matters when a team member catches an error in the draft.
   • Check that every approver has the Admin or Use role. See Why Can't I See Agents, Workflows, or Other Sections in Dave by voolama? if someone reports they cannot find their tasks.

The complete node sequence at a glance

Who needs which role before you start

What this guide does not cover