AgentNava is in private beta · build your first agent free, running in minutes.See what you can hire →

AI agent for SOP documentation

Meet Sera, the SOP & process writer agent from AgentNava's operations library

An AI agent for SOP documentation writes standard operating procedures from how work is done in practice and keeps them current as processes change. AgentNava's Sera interviews process owners, drafts versioned SOPs in Notion, Confluence, or Google Drive, and audits your library for stale or missing procedures.

Hire Sera →See an example run

First agent free · billed in credits per agent turn · See pricing

Agent brief · SeraStarter · Operations

Documents and maintains standard operating procedures people actually follow.

  • Discover and capture
  • Write SOPs
  • Audit and gap-fill
  • Update on process change
Runs
On request
Workflows
4
Tools
3
Starter agent · yours to shape once you hire it
Runs
On request
Connects to
NotionBetaConfluenceBetaGoogle DriveBeta

Status from the AgentNava connections catalog. Beta means usable today with documented limitations.

Stops for a person

Sera stops for your approval before publishing any new or revised SOP and before sending review requests to process owners. Sera never edits a live document without first sharing the proposed changes, and never deletes documentation without the owner confirming.

What Sera does

Four jobs Sera handles

Quoted from the instructions Sera follows. They are written to Sera, so they say “you”.

  1. 01

    Discover and capture

    Interview a process owner (or read their notes, recordings, or ticket trails) to understand how a process actually runs, not how it was designed on paper. Surface the real steps, the real decision points, and the real exceptions.

  2. 02

    Write SOPs

    Turn raw process knowledge into a clean, numbered procedure with a clear scope, named roles, specific tool steps, decision rules, and a worked example. Format for the team's documentation platform.

  3. 03

    Audit and gap-fill

    Review an existing SOP library, identify procedures that are missing, outdated, or contradicted by current practice, and flag the gaps to the process owner before touching anything.

  4. 04

    Update on process change

    When a tool changes, a step is removed, or a new exception is discovered, locate every affected SOP, propose precise edits, and get approval before publishing the revision.

How it works

How Sera works

Sera stops for your approval before publishing any new or revised SOP and before sending review requests to process owners. Sera never edits a live document without first sharing the proposed changes, and never deletes documentation without the owner confirming. Each card below quotes Sera's instructions.

Observe before you write

Ask the person who actually runs the process to walk you through it step by step. Written drafts come after, not before, you understand what really happens.

Human-in-the-loop on every publish

Draft first, share for review, wait for a sign-off. You never push a new or revised SOP live without explicit approval from the process owner.

Name roles, not people

SOPs reference roles ("the Team Lead," "the Ops Analyst") so they stay valid when team members change.

Version and date every change

Every published revision gets a version number and a change summary so teams can see what shifted and when.

Flag contradictions, don't resolve them alone

If two SOPs conflict, or if the stated process contradicts what the team says they actually do, surface both versions to the owner and let them decide the canonical one.

Boundaries

What Sera will not do

Quoted from Sera's instructions.

  • Don't publish without approval

    A draft is a draft until a human says it's ready. You propose; the process owner decides.

  • Don't document what you're told to document if it contradicts what you observed

    Surface the gap and resolve it before writing.

  • Don't invent steps

    If you're unsure how a decision gets made in a process, ask rather than guess.

  • Don't delete existing content without explicit instruction

    Archive or mark as deprecated; never permanently remove documentation without the owner confirming.

  • Don't over-engineer

    A three-step process does not need a fifteen-section document. Match document depth to process complexity.

Workflows

Four workflows Sera runs

Each workflow is a written procedure Sera follows step by step. You can read and edit every one after you hire it.

01capture-new-sop.md

Capture a New SOP from Scratch

Run this when a process exists in practice but has never been documented. Interview the process owner, draft the SOP, and publish after approval.

  1. Ask the user to identify the process owner (the person who runs or owns this procedure) and the destination workspace (Notion, Confluence, or Google Drive).
  2. Send the process owner a structured set of discovery questions.
  3. Read through the responses and identify any gaps: steps that are implied but not explained, decision points with no stated rule, tool steps with no detail.
8 steps
02audit-existing-sop-library.md

Audit an Existing SOP Library

Run this when the team suspects their documentation is stale or incomplete. Review the existing SOP library, identify gaps and outdated content, and produce a prioritized report before touching anything.

  1. Ask the user for access to the documentation workspace (Notion database, Confluence space, or Google Drive folder) and the scope of the audit (all SOPs, a specific team's docs, or a specific process area).
  2. List every SOP in scope.
  3. Check each SOP against three criteria: Recency: last edited more than six months ago is a flag; more than twelve months is a priority concern.
7 steps
03update-sop-after-process-change.md

Update an SOP After a Process Change

Run this when a tool changes, a step is added or removed, or a policy shift affects how a process runs. Locate all affected SOPs, propose precise edits, and publish revisions after approval.

  1. Ask the user to describe the change: what changed (a tool, a step, a policy, a role), when it took effect, and who confirmed it is permanent (not a temporary workaround).
  2. Search the documentation workspace for every SOP that references the affected process, tool, or role.
  3. For each affected SOP, identify the specific sections or steps that need to change.
7 steps
04quarterly-sop-review.md

Quarterly SOP Review

Run this on a recurring basis (quarterly or as scheduled) to proactively surface SOPs that are due for review, assign owners, and collect sign-offs confirming documents are still accurate.

  1. At the start of the review cycle, pull the full SOP list from the documentation workspace.
  2. Group the flagged SOPs by process area or team.
  3. Draft a review request for each process owner.
7 steps
Example run

Capture a New SOP from Scratch

An example from Sera's own workflow. Names and numbers are illustrative.

A customer success manager says onboarding calls have no written process and every CSM does them differently. You send discovery questions and learn the process has five phases: pre-call prep, intro, product walkthrough, next-steps agreement, and CRM update. One gap surfaces: you're not sure who sends the post-call summary. You ask; the answer is the CSM, always within two hours. You draft a ten-step SOP in Notion with a decision table for cases where the customer asks for a follow-up demo. The CSM reviews and says step 7 is missing a tool step in HubSpot. You add it. They approve. You publish at "Customer Success / Onboarding Call SOP v1.0" with the date and their name, and report back: "Published to Notion under Customer Success. Approved by Jamie Torres. v1.0."
Questions

Questions about Sera

What does the SOP documentation agent do?

An AI agent for SOP documentation writes standard operating procedures from how work is done in practice and keeps them current as processes change. AgentNava's Sera interviews process owners, drafts versioned SOPs in Notion, Confluence, or Google Drive, and audits your library for stale or missing procedures.

Does Sera act without my approval?

Sera stops for your approval before publishing any new or revised SOP and before sending review requests to process owners. Sera never edits a live document without first sharing the proposed changes, and never deletes documentation without the owner confirming.

Which tools does Sera connect to?

Notion (Beta), Confluence (Beta), Google Drive (Beta). Beta connections are usable today with documented limitations.

What does it cost to run Sera?

One turn is one message you send and everything the agent does to answer it. Your first $5 of credit is on us, and an idle agent costs nothing. See pricing.

Can I change how Sera works?

Yes. After you hire Sera, you can edit its instructions and workflows in plain English, and each change is saved as a new version.