escalate

A structured escalation requires fields for escalation type, situation, options, recommendation, and deadline. Providing a situation summary and context generates clear, actionable guidance to prevent progress stalls when critical thresholds are reached.

An escalation template is needed when workflow automation hits thresholds requiring prioritization, scope changes, or risk management. It formats critical situations into clear guidance, preventing progress stalls when decision-maker intervention is required.

Supported escalation types include prioritization_decision, scope_change, external_dependency_failure, timeline_impact, irreversible_action_approval, budget_exceeded, repeated_failure, and shippability_assessment. These categories standardize communication across various project risk scenarios.

To communicate a scope change or timeline impact, use a structured escalation template outlining the situation, available options, a recommendation, and a deadline. This framework eliminates ambiguity and accelerates stakeholder approvals during project execution.

Yes, this escalation format supports budget_exceeded and repeated_failure scenarios. The template applies standardized fields to these thresholds, ensuring decision-makers receive consistent, actionable information to resolve financial or systemic workflow issues.

The best way to prevent progress stalls during an external_dependency_failure is to issue a structured escalation with defined options and a strict deadline. This forces timely prioritization and provides decision-makers with actionable recommendations to unblock the workflow.