Blog · · Benatar Brands
Write the SOP before you automate the task
A recurring task is ready for automation when somebody can explain what starts it, what information it needs and what a correct finish looks like. If those answers change depending on who you ask, begin with a short standard operating procedure. The document gives you something concrete to test before connecting tools.
You do not need to document the entire business. Choose one task that repeats often enough to observe, such as preparing a weekly stock exception note. Describe how a person should complete that task today. An automation can come later, after the decisions and exceptions are visible.
Start with the result someone needs
Write a sentence that names the recipient and the decision the work supports. For an anonymous hypothetical shop, the result might be a purchasing note that identifies products needing a human review. That is clearer than a vague request to automate inventory. It also keeps ordering, supplier outreach and changes to stock records outside the initial procedure.
Define completion in observable terms. The note should identify the source snapshot, show the relevant product records, explain each exception and name the person responsible for reviewing it. A document existing in a folder is insufficient if nobody can tell which stock file it used or what needs attention.
Draw the boundaries before the steps
Asana's process documentation guide recommends defining where a process begins and ends, alongside its roles and resources. Use that distinction to keep your procedure small enough to test. A purchasing review can start when an approved stock export becomes available and end when the owner receives a decision packet.
Record what happens when that starting condition is absent. If the export is missing, the correct output may be a brief blocked status naming the missing file. Reusing an old snapshot silently would make a polished report less trustworthy. The same rule should apply whether a person or an assistant prepares the note.
Write the steps as observable actions
Use verbs that describe something a reader can actually do: open, compare, record, flag and verify. Replace instructions such as check everything looks right with a specific comparison. For example, compare the export date with the reporting period and stop if they do not match.
Asana's SOP template guidance distinguishes simple sequential instructions from more detailed and branching formats. A short checklist works for a straight path. When different conditions lead to different outcomes, give each condition its own instruction rather than burying the decision in a paragraph.
For the hypothetical stock note, a useful first version could include these steps:
- Confirm the approved file and reporting period.
- Read the product identifier and the fields the owner has approved.
- Apply the owner's documented exception rule.
- Record the original values alongside each flagged identifier.
- Separate missing data from products that meet the exception rule.
- Save a review note for the named owner, without changing stock records.
Avoid inventing the exception threshold while writing the procedure. If the owner has never defined it, label that as an unresolved decision. Automating an undefined rule simply repeats an assumption faster.
Give exceptions their own instructions
List the situations that make the normal path unsafe or incomplete. A product might appear twice. A required field could be blank. The export could cover a different location. An identifier could have changed since the previous review. Each case needs a next step, even if that step is to ask the owner to investigate.
Separate a recoverable formatting problem from a business decision. A reader may be able to interpret a clearly labeled date format. They should not decide which of two conflicting stock counts is authoritative without a rule. Include the source record in the exception note so the owner can inspect the disagreement directly.
Let an AI assistant review a copy
An assistant can help find ambiguity in the written procedure before it touches an operational system. Provide an approved copy of the SOP and a small fictional example. Keep the connection read-only, or use an export when the available integration grants unnecessary write access. The assistant's deliverable is a separate review, not an edited procedure or a live action.
A useful prompt is: Read this procedure and identify instructions that require an unstated assumption. For each finding, quote the relevant step briefly, explain the missing decision and propose a question for the owner. Walk through the fictional input using only the written rules. Do not fill gaps, update records or contact anyone.
Ask for two outputs: an ambiguity list and a step-by-step dry run. The first helps improve the document; the second reveals where the process stalls. Treat the assistant's suggestions as proposed wording that a human must evaluate, especially when they would change who owns a decision.
Test the procedure with another person
Give the document and an approved sample to someone who did not write it. Ask them to explain what they would do at each step. Notice where they need background knowledge that lives only in the original operator's head. Those questions are useful evidence about the procedure, rather than a reason to make the document longer indiscriminately.
Test an ordinary case, an incomplete input and a conflicting input. Record the expected outcome before comparing it with the reader's answer. If two competent readers reach different decisions, revise the rule or assign that decision to a person explicitly. A clear stop condition is a valid outcome.
Keep ownership visible after the first version
Add an owner, revision date, source links and a short change note. Preserve the last approved version so a later review can explain which rule produced a particular result. When the underlying system changes, check the procedure before assuming the old steps still apply.
Only then choose a small part to automate. Begin with gathering approved inputs or formatting a review note. Keep consequential decisions and write actions with their designated owner until the process has separate authorization for them. The SOP should make that boundary easy to see.
Book a free session to turn one recurring task into a clear procedure and a practical first automation scope.
Related service: AI implementation.
Get our notes on AI and how businesses run in your inbox: subscribe to The Beyond Brief.
