Visual SOPs

A visual SOP is a generated, slide-based standard operating procedure for a workflow: a human-readable walkthrough of what the automation actually does, step by step. It isn't written by hand and it isn't a guess. It's built from the workflow itself: the graph, the steps, and screenshots and evidence captured while the workflow was authored, where available.

Why it exists

Most automation documentation has the same flaw: someone writes it once, the automation changes, and the document quietly becomes fiction. A visual SOP is pinned to a specific workflow version, so it can never drift from the automation it describes. The SOP for version 3 stays an accurate record of version 3 forever; when you publish version 4, you regenerate and get a document that matches version 4. There is never a moment where the documentation claims something the automation doesn't do, and never a document whose accuracy depends on someone remembering to update it.

That version pinning is also what makes SOPs trustworthy as records: an auditor reading the SOP for the version that ran in May is reading what actually ran in May, not the current state of the workflow.

What's on the slides

Each SOP opens with a plain-English summary of the whole workflow: what it does, what it needs, and what it produces. Then it walks the process one slide per step, organized into sections that mirror the shape of the work (signing in, gathering data, entering it, confirming). The viewer in the screenshot above is on slide 3 of 6, "Navigate to Books to Scrape".

Every slide carries:

• Per-step instructions, written for a human reader: what happens at this step, on which system, with what data. A person could follow the slide and perform the step by hand.
• Real screenshots, drawn from the workflow's authoring evidence where available, so the reader sees the actual screens the process touches rather than an artist's impression of them.
• Tips and warnings: the judgment calls, edge cases, and gotchas the process involves, surfaced on the slide where they matter so a person following along doesn't miss them.

Generating an SOP

Step 1

Open the workflow in the editor and click Generate SOP in the toolbar.

Step 2

Progress streams into the editor chat while the slides are assembled. It doesn't block anything; you can keep editing while it works.

Step 3

When it's ready, the button becomes View SOP. Open it and page through the slides with Previous and Next.

From the viewer you have two more controls:

• Regenerate rebuilds the SOP from scratch, which you'd do after publishing meaningful changes to the workflow. The new SOP documents the new version; the old one remains an honest record of the old one.
• Export PDF produces a portable copy you can attach to an audit package, drop into a shared drive, or send to anyone, no RamAIn account required.

Note

Generation takes real work behind the scenes, so it's rate-limited to a few generations per workspace per hour. Since each SOP is pinned to a version, you only need to regenerate after you've published meaningful changes.

Three ways teams use them

• Audit and compliance. A reviewable, version-accurate record of exactly what the automated process does, in slides an auditor can read rather than a graph they'd need training to parse. Paired with the per-run history on the Sessions page, you can show both what the process is and what any individual execution did.
• Training the manual fallback. If the automation is ever unavailable, or a new hire needs to understand the underlying process, the SOP is the procedure a human can follow by hand: same steps, same screens, same warnings.
• Sharing beyond the platform. Export a PDF and hand it to stakeholders, clients, or leadership: people who will never open RamAIn but need to know how the process works. The SOP is the workflow, translated for them.

Where to next

Browser Workflows

The lifecycle behind every SOP: Build, Edit, Test, and Publish.

Sessions & Runs

The other half of the audit story: what each individual run actually did.