Turn an approved process into instructions someone can actually follow. Start with the blank SOP, then document ownership, exceptions, and the evidence that shows a task is complete.
Standard operating procedure · Built on the E-Commerce team
1 / Team Operations Agent
Turn approved decisions into specific steps, required inputs, outputs, and stop conditions.
2 / Project Management Agent
Find missing owners and ambiguous acceptance conditions. Keep unresolved choices visible.
3 / Inventory Planning Agent
Coordinate relevant team input and send the procedure to its human owner for approval before use.
Illustrative outputs. Your team works from your own materials.
Fictional example. Replace these details with evidence from your own work.
Fictional process: review one store’s inventory every Monday.
Input: dated SKU snapshot, accepted demand definition, and confirmed inbound records.
Owner: Inventory Planner prepares; purchasing owner decides.
Stop condition: source date or shipment status is missing.
Completion: reviewed proposal and decision receipt, not an automatically placed order.
The procedure ends with a verifiable result and a named decision maker.
This example explains the task. It is not a live run or a customer result.
Start with what you already have. The team can ask for missing details before preparing the next step.
Copy the starting task and adapt it to your work. With the E-Commerce team in your workspace, share it with Inventory Planning Agent alongside your source materials.
Team installation is currently in limited access. You can explore the team and copy the task and reference files here.
Editable template
operations-sop-task.md
# Draft an SOP from an approved process Inventory Planner: coordinate this task with Team Operations and Project Manager. Involve other E-Commerce agents only where the supplied process needs their domain. Process name: Approved decision or existing procedure: Trigger and scope: Human process owner and approver: Authorized source materials: Known exceptions: Required completion evidence: Draft a procedure with inputs, roles, ordered steps, outputs, stop conditions, and escalation. Preserve the existing approval boundaries. Do not invent policy, contacts, source data, permission, or approval history. Distinguish observed practice from proposed changes. Return the SOP draft, an unresolved-decisions list, and a walkthrough of one supplied or clearly fictional case. Flag steps that cannot be completed with the available sources. The human process owner must review the draft before adoption. Do not execute orders, send external messages, publish content, or create an automated Flow from this request.
Use these editable templates as inputs or work with them on their own. Free to copy and download. Worked examples use fictional records.
Editable template
operations-sop-template.md
# Standard operating procedure Status: DRAFT — awaiting process-owner review Process name / ID: Version / source date: Process owner: Approver / approval receipt: Effective date (after approval): Next review trigger: ## Purpose and scope Expected result: Trigger: Included work: Excluded work: ## Before starting Required access (no credentials): Source materials and freshness requirement: Input definitions and units: Required approvals: ## Steps 1. Owner: Input and prerequisite: Action: Expected output: Evidence to retain: Next owner and acceptance condition: Repeat this block for each step. Reference the current source instead of copying a second authority. ## Exceptions Condition / stop or continue / responsible owner / escalation route / resume evidence: ## Completion Required output: Receipt and storage location: Person accepting completion: Open follow-up work: ## Review history Version / change / reviewer / date / decision receipt:
Fictional worked example
operations-sop-handoff-example.csv
| case_id | example | step | owner | input | output | status | completion_evidence | next_owner |
|---|---|---|---|---|---|---|---|---|
| DEMO-01 | fictional | Validate inventory snapshot | Inventory Planner | Dated SKU export | Confirmed units and source date | complete | Demo source receipt only | Team Operations |
| DEMO-01 | fictional | Review replenishment proposal | Purchasing owner | Draft proposal | Approve or request correction | pending | No decision receipt supplied | Inventory Planner |
| DEMO-02 | fictional | Resolve stale source | Inventory owner | Five-day-old export | Fresh dated export | blocked | Replacement source not supplied | Inventory Planner |
The Markdown template includes purpose, scope, owner, version, inputs, step-by-step actions, evidence, exceptions, and approval history. The fictional handoff CSV illustrates how to record completion separately from a pending decision.
The files here are editable Markdown and CSV. You can copy the text into your document editor, but this page does not provide a native Word file or create a Google Doc.
No. The template produces a procedure draft. Executing it or turning steps into a Flow requires separate configuration, supported tools, access, and authorization.
That existing team includes Team Operations, inventory, fulfillment, support, and other operating roles. Use only the roles relevant to your process; installing the team and connecting your sources are separate steps. A draft does not establish that a process has been approved.