Operations · Specialized agent role

SOP Assistant

The SOP Assistant supports drafting and maintaining standard operating procedures from approved process evidence and owner decisions. It works from existing procedures, process maps, interviews, tickets, policy documents, screenshots, and approved change records, applies explicit operating rules, and makes incomplete or uncertain work visible instead of silently guessing.

Get StartedReview the workflow

Best for

  • Teams that repeatedly handle drafting and maintaining standard operating procedures from approved process evidence and owner decisions and can describe a dependable operating path
  • process owners and subject-matter experts who need consistent preparation, explicit ownership, and visible exception handling

Typical inputs

  • Authoritative inputs such as existing procedures, process maps, interviews, tickets, policy documents, screenshots, and approved change records, with access restricted to what the role needs
  • Definitions, required fields, service expectations, approval thresholds, and checks for source authority, sequence, ownership, prerequisites, decision branches, safety steps, and version conflicts

Input quality determines output quality. Source permissions, retention, and field-level access should be settled before the workflow begins.

Core workflow

Each stage has a defined purpose, visible evidence, and a named owner for exceptions.

1

Frame the request

Confirm the request, responsible owner, permitted sources, and definition of completion for drafting and maintaining standard operating procedures from approved process evidence and owner decisions

2

Gather context

Collect existing procedures, process maps, interviews, tickets, policy documents, screenshots, and approved change records and retain enough context to trace material facts and decisions

3

Prepare the work

Apply the configured rules, validate source authority, sequence, ownership, prerequisites, decision branches, safety steps, and version conflicts, and prepare review-ready procedures, change summaries, decision tables, checklists, and versioned source notes

4

Review and hand off

Send the result to process owners and subject-matter experts, pausing exceptions or consequential actions for an accountable person

Actions it can perform

  • Organize and prepare drafting and maintaining standard operating procedures from approved process evidence and owner decisions using the permitted sources and documented operating rules
  • Validate source authority, sequence, ownership, prerequisites, decision branches, safety steps, and version conflicts, preserve source context, and route exceptions before consequential action

Actions should be restricted to the systems, records, and channels required for this role. Broader access is not a substitute for a well-designed workflow.

Outputs

  • A reviewable package of review-ready procedures, change summaries, decision tables, checklists, and versioned source notes with ownership, status, sources, and unresolved questions
  • An exception queue explaining which rule, field, source, or approval prevented safe completion

Every output should make its status clear: prepared, awaiting approval, completed under policy, or escalated with an explanation.

Role-specific configuration details

Use these role-specific terms to make the implementation brief concrete: resolve the relevant definitions, permissions, routes, and exception conditions before the role touches live work.

  • assistant-supports
  • supports-drafting
  • maintaining-standard
  • standard-operating
  • operating-procedures
  • process-evidence
  • existing-procedures
  • procedures-process
  • process-maps
  • maps-interviews
  • interviews-tickets
  • tickets-policy
  • policy-documents
  • documents-screenshots
  • change-records
  • records-applies
  • applies-explicit
  • explicit-operating
  • operating-rules
  • makes-incomplete
  • visible-instead
  • silently-guessing
  • guessing-produce
  • ready-procedures
  • procedures-change
  • change-summaries
  • summaries-decision
  • decision-tables
  • tables-checklists
  • subject-matter
  • matter-experts
  • trace-back
  • authoritative-inputs
  • inputs-such
  • access-restricted
  • needs-definitions
  • definitions-required
  • required-fields
  • fields-service
  • service-expectations
  • authority-sequence
  • sequence-ownership
  • ownership-prerequisites
  • prerequisites-decision
  • decision-branches
  • branches-safety
  • safety-steps
  • version-conflicts
  • conflicts-confirm
  • request-responsible
  • decisions-collect
  • collect-existing
  • retain-enough
  • trace-material
  • material-facts
  • decisions-apply

Human approval and escalation

Approval boundary

process owners and subject-matter experts approve consequential external actions, policy exceptions, irreversible record changes, and any output that represents a business commitment.

Escalation rule

Safety-critical instructions, legal interpretation, conflicting policies, unverified workarounds, and undocumented authority are routed with the source context, work completed, uncertainty, and requested decision intact.

What remains under human control

  • People define the source authority, permissions, quality rules, review gates, and acceptable boundaries for drafting and maintaining standard operating procedures from approved process evidence and owner decisions
  • process owners and subject-matter experts resolve ambiguity, approve consequential actions, and remain accountable for the final business outcome

Teams should review permissions and outcomes over time, especially when policies, data sources, responsibilities, or customer expectations change.

Recommended integrations

Connections are workflow building blocks, not proof of automatic availability. Confirm authentication, permissions, supported actions, and error handling during implementation.

NotionReview integration scopeGoogle WorkspaceReview integration scopeMicrosoft 365Review integration scopeSlackReview integration scope

Example workflow

A recurring request involving drafting and maintaining standard operating procedures from approved process evidence and owner decisions is checked against source authority, sequence, ownership, prerequisites, decision branches, safety steps, and version conflicts; routine preparation is completed, while exceptions are sent to process owners and subject-matter experts with the evidence needed to decide.

The implementation should record the source, owner, decision boundary, and recovery route for each important stage. That makes the workflow easier to review and improve without hiding responsibility.

Related agents

Use related roles only when responsibility and handoff boundaries are genuinely distinct.

Related use cases

Explore outcome-led workflows that can combine this role with approved systems and human review.

Design a responsible SOP Assistant workflow

Define the sources, controls, connected tools, exceptions, and owners before implementation.

Get Started