Run a workflow and resolve a blocker
Follow approved instructions, capture observations, and understand what holds an action.
Check what the work requires
Start from your assignment or the relevant operating record. Confirm the workspace, site, record identity, and source revision before acting. A requirement panel explains what must be true for the next consequential action.
- Suitable materials, equipment, and people.
- Current instructions and applicable specifications.
- Required predecessor steps, observations, attachments, or reviews.
Capture what actually happened
- Read the instruction and open its source when you need context.
- Enter the observation with its unit, or check the imported value and its source.
- Attach supporting evidence when the step requires it.
- Review the action summary before committing a movement, completion, or decision.
- Confirm the resulting state and reference before continuing.
Resolve the requirement behind a blocked action
A blocked action should explain whether evidence is missing, a limit is exceeded, a prerequisite is incomplete, or your role lacks authority. Follow the linked requirement instead of changing unrelated fields to make the action available.
If the work cannot proceed as approved, record the exception and its context. Required review or disposition is part of the workflow; editing the instruction after the fact is not a substitute.
When the outcome is uncertain
If a connection fails after you commit, inspect the record and activity history before repeating the action. A timeout does not establish whether a consequential operation succeeded. Reconcile the original attempt before starting another one.