A run is a live execution instance of a process. When Diego at Bayou & Co. starts their weekly opening checklist, the system snapshots the current version of every step and creates a dedicated run he works through — his completion history is recorded independently of any future edits to the original SOP.
Here's how to start and finish a run.
Before you start
The process must have status Active (not Draft or Archived). You need at least contributor-level access to start a run.
Navigate to Process → Library in the sidebar and find the process you want to run.
Step 1: Start the run
Click Start run from either the library table row or the process detail page header. The system creates a run, snapshots all steps at their current state, and navigates you to the run detail page.
If a step has a Seat ID configured, the system resolves the current primary occupant of that seat at run-start and assigns the step to that person. Step assignments are fixed when the run starts; later changes to seat assignments do not affect an in-progress run.
Step 2: Work through the steps
Each step appears as a collapsible card on the run detail page. The steps are shown in the order defined in the process.
Expand a step to complete it. If the step has required fields, fill them in before the Complete step button becomes active:
- Text fields — type the response directly.
- Photo fields — tap Add photo to upload one or more images (PNG, JPEG, or WebP, up to 25 MB each).
- Signature fields — draw your signature on the canvas and click Save signature.
- Attachment fields — upload a single file (PDF, document, or image).
An optional notes field is always available on every step, regardless of the step's configured fields.
Steps assigned to someone else
If a step is assigned to another person:
- Members and viewers see a lock indicator. They cannot complete the step.
- Admins see an "admin unlock required" banner. Clicking Unlock lets an admin override the assignment and complete the step themselves.
The person who completed a step can also undo it using the Undo button — as long as the run is still in progress. An admin can undo any step.
Step 3: Complete the run
When all steps are done, a Complete run button appears. Click it to mark the run completed. The run's completion time is recorded.
If not all steps are finished but the run needs to close anyway, an admin can click Complete with override. This requires entering a reason, which is recorded in the audit log.
Abandoning a run
If the run needs to be cancelled entirely, the person who started it (or any admin) can click Abandon run in the danger zone. Enter a reason and confirm. Abandonment is permanent and cannot be undone.
Viewing your run history
Completed and abandoned runs are accessible from Process → Runs. Use the filter tabs to switch between In progress, Completed, Abandoned, and All. You can also filter by Assigned to me to see only runs where you have steps.
The process detail page's Runs tab shows only in-progress runs for that specific process. To see completed or abandoned run history for a process, go to Process → Runs and search there.
Run status reference
| Status | Meaning |
|---|---|
| In progress | Run is active; steps can be completed or undone. |
| Completed | All steps done (or admin override). No further changes. |
| Abandoned | Run was stopped early with a stated reason. No further changes. |
Stall detection
On the Runs list, a run is flagged Stalled if it is in-progress and the total elapsed time since start exceeds twice the estimated duration of any incomplete step. This is client-side detection based on the run's start time — not a per-step timer.
What comes next
To understand how to configure a process so it runs automatically on a schedule, see How to schedule recurring runs.
To set adherence targets and see how consistently this process is being run, see How to track adherence reporting.