Who takes the escalation?
Ridgewell Services tracks overdue high-priority cases. You are preparing its next risk update.
The question
Escalate at 10 or more distinct overdue high-priority cases. The service lead owns single-team issues. The operations duty lead owns cross-team escalations. The risk partner checks the evidence and recommendation.
| Distinct cases | |
|---|---|
| All open | 22 |
| Overdue and high priority | 9 |
All nine confirmed cases belong to the first service team.
“Apply the threshold and explain who owns the handoff.”
Not saved by this site. Your browser may restore text when you navigate back.
A strong answer, step by step
Open each step in turn. This is one strong answer, not the only one.
Step 1: Does the count cross the threshold?
What would you do here? Open the move you’d make.
Escalate to operations because 22 cases are open
Tempting, but it misses something. The rule applies to overdue high-priority cases.
Keep the service lead on the issue and check the next deadline
The strong move. Nine qualifying cases leave the issue below the threshold.
Close the issue because the threshold has not been met
Tempting, but it misses something. The nine cases still require action and monitoring.
See how a strong candidate says it
“The nine confirmed cases are below the threshold. I would keep this with the service lead and check when the next high-priority case becomes overdue.”
Why it works: The case policy counts distinct cases that are both high priority and overdue.
Step 2: Do 11 rows change the result?
A refreshed report lists 11 rows for overdue high-priority work. Two rows repeat IDs already present in that report.
What would you do here? Open the move you’d make.
Escalate based on the 11 rows
Tempting, but it misses something. Two rows repeat IDs already counted.
Deduplicate the IDs and keep the count at nine
The strong move. This applies the threshold to distinct cases.
Count each duplicate as a new case when it has a later timestamp
Tempting, but it misses something. A different timestamp does not create a new case ID.
See how a strong candidate says it
“The count stays at nine after I remove the two duplicate rows. I would save the distinct IDs and keep the current ownership.”
Why it works: A report can show more rows than there are cases.
Step 3: Who takes the handoff now?
A high-priority case already in the set of 22 has just passed its deadline. Its ID is distinct from the other nine, and it belongs to the second service team.
What would you do here? Open the move you’d make.
Wait until there are 11 distinct cases
Tempting, but it misses something. The policy applies at 10 or more.
Give the risk partner ownership of the team actions
Tempting, but it misses something. The partner challenges the evidence. The duty lead owns the cross-team escalation.
Escalate at 10 to the operations duty lead
The strong move. This uses the verified count and the cross-team owner.
See how a strong candidate says it
“The verified count is 10, so the rule applies. The cases now span two teams. I would send the evidence to the operations duty lead for acknowledgement and give the risk partner the count for challenge.”
Why it works: The threshold includes 10. The second team changes the escalation owner.
Step 4: What goes in the update record?
The operations duty lead acknowledges the handoff and agrees to update at 13:30 local time.
What would you do here? Open the move you’d make.
Record the duty lead and 13:30, with both team leads on their actions
The strong move. This confirms the handoff while preserving action ownership.
Record the escalation and leave the next update unassigned
Tempting, but it misses something. The duty lead has accepted the handoff and supplied a due time.
Transfer all team actions to the risk partner
Tempting, but it misses something. Each team lead still owns the actions for their cases.
See how a strong candidate says it
“I would record the ten IDs, the source time and the threshold. The duty lead owns the 13:30 update. The two service team leads still own the actions for their cases.”
Why it works: The record shows what triggered escalation, who accepted it and when the next update is due.
The answer, in short
- Decision
- Escalate to the operations duty lead and record the agreed 13:30 update.
- Because
- There are 10 qualifying cases across two service teams. The case policy assigns cross-team escalation to the duty lead.
- What would change it
- If the new record did not meet the priority or deadline condition, the verified count would stay at nine.
Common traps
- Count distinct IDs.
- Keep the update owner and team action owners clear.
Check your answer
- I used the stated threshold.
- I removed duplicate rows.
- I routed the handoff.
- I recorded the due time and action owners.
Last reviewed Nov 11, 2026