Automate Project Escalation Procedures

The Escalation Procedure Expert Agent helps create and manage project escalation frameworks. It organizes escalation triggers, levels of authority, communication templates, meeting agendas, tracking metrics, crisis response steps, and criteria for returning to normal work. The framework is intended to resolve critical issues while preserving stakeholder trust and project momentum.

Escalation triggers can be time-based, such as an issue remaining unresolved beyond its SLA; impact-based, such as effects on critical path, budget, or quality; risk-based; stakeholder-driven, including customer complaints or management concerns; or resource-based, such as team conflict or unavailable capacity.

Use this skill when a project needs explicit criteria for when an issue moves beyond its current owner, a repeatable path to decision makers, or shared expectations for what information accompanies an escalation. It can help teams document how to handle routine delays as well as critical issues requiring an emergency response.

The source focuses on project management escalation procedures. It does not establish a domain-specific process for incidents outside project work, and the framework should not be treated as a substitute for an organization's own authority, contractual, or emergency requirements.

Useful inputs include the issue, its impact, its risk, elapsed time against applicable SLAs, stakeholders involved, resources available, actions already attempted, and the decision or support being requested. The issue escalation email template captures an executive summary, impact, requested action, timeline, technical details, root cause, attempted solutions, and the reason for escalation. It also records schedule, budget, quality, and stakeholder impact, recommended actions, a resolution deadline, the escalator's identity and role, and the prior escalation level.

The output is a documented procedure with measurable triggers, response timeframes, decision authority, communication channels, and information-capture requirements. A sample matrix progresses from self-resolution to team lead, project manager, and executive sponsor. Its example ranges are 0-4 hours, 4-24 hours, 1-3 days, and 3+ days or critical impact. These are example thresholds in the source, not universal service guarantees.

The procedure assigns responsibility and accountability across team members, team leads, project managers, program managers, executive sponsors, technical leads, business stakeholders, SMEs, and legal or finance roles. A RACI-style example identifies who is responsible, accountable, consulted, and informed at issue identification and each resolution level.

Examples include reusable email, meeting agenda, escalation log, and metrics examples. The metrics cover response time, resolution effectiveness, and process efficiency, including acknowledgment and decision times, re-escalation, resolution success, stakeholder satisfaction, false escalations, escalation volume, and cost per escalation.

One source-provided example metric structure is:

# Escalation Metrics Dashboard
escalation_metrics = {
    'response_time': {
        'level_1': 'avg_hours_to_acknowledgment',
        'level_2': 'avg_hours_to_decision',
        'level_3': 'avg_days_to_resolution'
    },
    'resolution_effectiveness': {
        're_escalation_rate': 'percentage_requiring_higher_level',
        'resolution_success_rate': 'percentage_fully_resolved',
        'stakeholder_satisfaction': 'post_resolution_survey_score'
    },
    'process_efficiency': {
        'false_escalations': 'percentage_resolved_at_lower_level',
        'escalation_volume': 'total_escalations_per_project_phase',
        'cost_per_escalation': 'resource_hours_invested'
    }
}

For a crisis, the example process calls for immediate notification within 1 hour, assembling a crisis team within 4 hours, and ongoing rapid-resolution cycles with 4-hour progress checkpoints. It also describes an escalation meeting with issue presentation, solution discussion, decision making, and next steps.

Project managers, team leads, program managers, and project teams that need a shared escalation path can use the framework to clarify triggers, decision rights, communication, and follow-up. Teams can use its de-escalation criteria to determine when the issue is resolved to stakeholder satisfaction, risk is acceptable, normal processes can resume, lessons are documented, and improvements are identified.