Your SOPs become the context AI follows.
Most teams have policies, checklists, and playbooks that nobody opens when the work actually happens. Hubson turns them into approved execution context — so AI follows how your company really operates, and every important run shows which SOP guided it.
Manuals → Sections → SOPs
A clear, versioned structure your team already understands — not a prompt library. Each SOP is a small, owned unit Hubson can attach to a workflow and follow step by step.
From a doc nobody opens to work AI follows
Before
The refund SOP sits in Notion. When a big refund comes in, support asks the founder in Slack — and the answer depends on who's online.
After
- The refund workflow checks finance.refunds.v3
- Refunds above $2,000 pause for approval
- The receipt shows SOP version, approver, and action taken — SOP used: finance.refunds.v3
No SOP yet?
Start from a checklist, policy note, or messy doc. Hubson can draft a starter SOP from the workflow description — but the workflow stays in simulation until an owner approves the starter SOP.
SOPs become operating context
Point a workflow at the policy, checklist, or doc that should guide it — Hubson drafts the rest of the workflow around it.
SOPs carry versions and owners, so a change to the standard changes the work — without re-prompting anyone.
Activity and the Action Receipt name which SOP version guided the run — e.g. finance.refunds.v3 — so you can prove the work followed your SOPs.
Repeated guidance and feedback can become owner-reviewed SOP changes — operating memory the next run starts from.
Start with the SOP you wish people actually followed
Map a workflow around an existing policy, or let Hubson draft a first SOP from how the work happens today.