SOP document and screenshots

Turn the saved workflow into a readable procedure, edit its instructions, and attach the right recorded screen to each step.

Open the written procedure

Open a compiled workflow, select Editor, then choose SOP in the canvas toolbar. If you are still demonstrating the task in Builder, finish the demonstration and select Save first. Compilation creates the blocks and instructions that this document displays.

The SOP is the workflow's written procedure. It shows what the workflow needs to start, what each task should do, when that task is finished, and what it should report. Graph and SOP are two views of the same saved definition: a direct edit here changes the corresponding graph field.

The Explore a guide SOP with its title, purpose, task description, and recorded-screen controls

This example opens a documentation guide, checks the page, and reports three headings. The screenshots come from the actual authoring session.

Start by reading the document from top to bottom as if you were the person performing the task. Can you identify the starting page, the value to enter, the control to choose, and the evidence of success without asking the original author? A procedure such as “process the page” needs more detail before it is useful for either a reviewer or a future run.

Understand the parts of the document

Part	What to put there	Example for a guide-review workflow
Title and description	The purpose and boundaries of the whole workflow.	Open a selected guide and report its title and first three headings.
What this needs to start	The inputs an operator or launcher supplies.	A guide name; omit this requirement for a fixed-guide workflow.
Task title and description	The job performed by this block.	Find and verify the selected documentation article.
Numbered instructions	Ordered actions with enough detail to carry them out.	Open the docs, select the exact sidebar guide, verify its URL, read the headings.
Done when	The condition that ends this block.	The correct guide has loaded and three headings have been identified.
Hands off	What the next part of the workflow can rely on.	The selected article is open and its title has been verified.
What to report back	The result expected from the task or final output.	The title, URL, three headings, and confirmation of screenshot capture.

Tool calling and technical instructions can expose additional execution detail. Review it when a procedure depends on a particular tool or data contract; the ordinary numbered instructions should still explain the task clearly.

Edit an instruction directly

Click an instruction's text to turn it into an editable field. For example, change:

Open https://ramain.ai/docs.

into:

Open https://ramain.ai/docs and confirm that the documentation sidebar is visible.

Finish the edit by leaving the field, then wait for Saved in the editor toolbar. Direct wording edits do not need an Editor-chat model turn. Use Editor chat when the change also requires a new input, a parser, a branch, or coordinated changes across multiple blocks.

An SOP instruction in its text field, with screenshot, movement, insertion, and deletion controls beside it

The third instruction is being edited. The camera, arrows, plus, and delete controls act on that instruction; completion and output fields appear below the list.

The instruction controls let you:

Attach a recorded screen with the camera control.
Move up or Move down to change the order. An instruction's existing screenshots move with it.
Add an instruction below, insert before an instruction, or use Add instruction at the end.
Delete this instruction when that action is no longer part of the procedure.

Keep one coherent action or verification per instruction. “Open the account, change the amount, submit it, and check the result” is hard to illustrate and review as one step. Separate the navigation, data entry, submission, and confirmation when they have distinct screens or failure cases.

Browse the recorded evidence

Select Recorded screens above the document. The drawer contains screens and actions captured during authoring, with titles, timestamps, and action labels where available. Its filters let you focus on screens or particular action types, and search helps find a page or control.

Recorded screens drawer beside the procedure, showing thumbnails, timestamps, search, and action filters

The drawer is open for browsing. A screen can appear both as a whole-screen entry and as evidence for an associated action.

A screenshot is a record of a past page state. It is not a live preview of the next run. Use the title, timestamp, visible page, and action together to decide whether it belongs beside an instruction. A matching word in the action label alone is not enough: the image must show the relevant control or result.

Attach a screen to a specific instruction

There are two ways to make the relationship explicit:

Drag a screen or action from Recorded screens onto the intended instruction.
Select Attach a recorded screen beside that instruction, then choose Add on the desired drawer entry.

For the second method, read the line at the top of the drawer before adding anything. It should say Adding to instruction … and name the correct task. When you open the drawer only to browse, Add buttons can be disabled because no target instruction has been selected.

The recorded-screen picker after selecting an instruction, with an explicit target and Add or Remove controls

The target instruction is stated above the search field. An already attached entry offers a removal control instead of adding the same attachment again.

After adding a screen, close the drawer and inspect it in the document. Check that it sits beneath the right instruction and that the caption and image explain that step. Wait for Saved. For our example, the documentation home page belongs with opening the docs; the SOP article belongs with navigating to that article.

To replace poor evidence, use Remove this screenshot on the attachment and then add a more suitable screen. Removing an attachment changes the instruction's evidence; it does not erase the procedure's text. A whole-screen entry can be more useful than an action entry when an action label is misleading.

Re-match after a broader edit

Re-match screens asks the matching process to associate the recorded evidence with the current instructions again. Use it after substantial wording or structural changes, then review the result. It is a starting point for evidence placement, not a substitute for checking each important step.

Edits made through chat or elsewhere in the graph can cause existing evidence to be marked stale. For example, changing “open the SOP article” to “open the guide supplied by the operator” broadens the instruction, while the old screenshot still shows only the SOP article. Keep it as an explicitly understood example where appropriate, or replace it with better evidence for the revised procedure.

Check image size, highlights, and completeness

Open a screenshot to inspect the full image when a label is too small. Screens retain their natural aspect ratio so a highlight stays aligned with the original control. A highlight should point to the action described by the instruction; it should not be accepted merely because an image is present.

Before using the SOP for training or review, verify:

A reader can follow the written sequence without relying on chat history.
Screens show the important starting state, difficult choice, submitted values, or successful result.
Each attached image supports its own instruction, rather than repeating the same generic page everywhere.
Completion criteria explain how to distinguish success from a page that merely opened.
The toolbar reports that your edits are saved.

If screens are missing or incorrect

What you see	What to do
Empty recorded-screen drawer	Check whether this authoring session captured usable screenshots. Older sessions may have none; re-matching cannot recreate evidence that was never recorded.
Disabled Add buttons	Select Attach a recorded screen on the target instruction, or use drag and drop.
Image beside the wrong instruction	Remove that attachment, select the intended instruction, and attach the appropriate entry there.
Action label disagrees with the image	Verify the page and action from the visible evidence. Prefer a suitable whole-screen entry or another capture instead of treating the label as proof.
Stale evidence after an edit	Review the changed instruction, re-match if useful, and manually correct the attachments.
No screenshot of the final result	The authoring evidence may not contain that state. Capture it during an appropriate demonstration; do not use an earlier screen as if it proved completion.

The former generated Visual SOP slideshow is retired from the main UI. Older settings or history may still mention it. You do not need to generate a slideshow to read, edit, or illustrate the current SOP document.

The workflow now accepts a changing guide title, so earlier evidence needs review before re-matching.

Was this page helpful?