How to run a procedure digitally
Digital execution turns a current published procedure into a durable operator session. Progress, evidence, handoffs, and completion remain tied to the exact revision that was launched.
Get to the launcher
- Sign in with an account that belongs to the organization running the work.
- Open Digital execution from the landing page, application navigation, or Builder.
- Choose a procedure marked Current publication, then select Open executor.
Only published procedures appear in the launcher. A draft must be published by an authorized organization member before an operator can start it.
Run the exact revision
Starting creates an attributed session against the current controlled publication, not an editable draft.
Enter declared text, number, date, and boolean values. Decisions and calculations use the rules defined by that revision.
Pause when work stops. Durable values and the append-only event history remain available when the session is reopened.
Required values and validations must pass before completion seals the audit history.
Evidence and handoff
When the revision declares evidence requirements, upload supported files from the executor. Files are checked for size, type, and digest before they are stored and linked to the exact execution revision.
The active operator can hand off an active or paused session to another authorized organization operator. The handoff is recorded as an attributed event; ownership changes immediately, so the former operator can no longer write progress or upload evidence.
Activity and supervision
Operators can recover sessions they started or currently own. Members with audit-read permission can open the read-only activity dashboard and inspect organization sessions, durable values, attributed events, and evidence links without receiving executor edit controls.
Long execution histories load in bounded pages. Use Load more history to view later events instead of refreshing the whole trace.
Important boundaries
- Digital execution requires an authenticated organization member and a current published procedure.
- Evidence upload and ownership handoff require a live connection.
- Progress can be queued locally when connectivity is interrupted and synchronized after reconnect; queued events are replayed idempotently.
- The feature is in beta. Confirm the procedure, controls, equipment details, and applicable requirements using your organization’s review process.