When should I escalate a project issue?
Unclear escalation boundaryEscalate when impact, authority, urgency, or repeated failure exceeds the team's ability to resolve the issue. Escalation should request a decision or resource, not merely forward a complaint.
What to do now
- State the verified facts and impact
- Identify the decision beyond your authority
- Present feasible options and a recommendation
- Request a decision by a justified deadline
When to escalate
Escalate when
Waiting would remove viable options or worsen material harm.
Who decides
The issue owner or delegated decision authority
Example
A shared specialist conflict goes to the portfolio owner because neither project manager can resolve the allocation.
Mistake to avoid
Escalating every inconvenience without attempting authorized resolution.
Prevent a repeat
Track unresolved decision age and verify the outcome before treating an issue as closed.
Suggested ApprovedFlow setup
- Tasks
- Documents
- Approvals
Record the issue and next action on an owned task, attach evidence, and route the unresolved decision to the proper authority. See the platform
Related cases
- How do we report a serious issue without alarming everyone?Unclear incident communication
- Someone reports a safety concern during delivery. What should happen?Potential immediate harm
- Our project overlaps with another team's system. Where should the boundary be?Unclear scope interface
- No one will accept the service owner role. What should I escalate?Unassigned operational accountability