Runs Best Practices

Structured Approach to Placing Procedure Steps on HOLD

Objective

Provide a standardized method for placing procedural steps on HOLD within ION while maintaining contextual visibility and operational transparency.

Strategic Rationale

• Enables frontline teams to clearly communicate blockers or required interventions

• Improves visibility of process interruptions across departments

• Supports compliance and continuous improvement workflows

Recommended Workflow

1. Initiate HOLD Action

   • Navigate to the target step within the procedure

   • Use the dropdown control to place the step on HOLD

   
2. Document the Rationale via Comment

   • Add a comment to clearly communicate the reason for the HOLD

   • Example: "Step placed on hold due to lack of material availability"

   
3. Alternative HOLD Scenarios

   • Training in progress: defer execution until personnel are qualified

   • Pending redline or procedural update

   • Identified improvement opportunity under evaluation

4. Confirm Comment Visibility

   • Verify the comment is attached to the step and visible in the step sidebar

   • Ensures others can immediately understand the context of the HOLD

   
5. Visual Indicators Across Contexts

   • There are symbols on step cards for comments on the procedure, step, and redline objects

   • Provides a unified reference point for all exception/ HOLD-related documentation

Deployment Recommendation

• Use clear, concise language in comments to eliminate ambiguity

• Periodically audit steps on HOLD to ensure timely resolution or escalation