Audit SLA escalation coverage
Find timing-order and recipient-coverage gaps across active SLA targets and the organization hierarchy.
Last updated July 20, 2026 · 6 min read#Page purpose
Find timing-order and recipient-coverage gaps across active SLA targets and the organization hierarchy.
| Application route | Intended audience |
|---|---|
| /lex/admin/escalations | Legal operations and organization administrators |
#Before you start
- Sign in as legal operations and organization administrators and confirm WatheeqTech shows /lex/admin/escalations; hidden controls indicate that your account lacks the required permission.
- Confirm the reporting scope and source-data freshness before interpreting a KPI, score or derived portfolio value.
- Collect the reason, authority and supporting evidence required for any governed decision or state transition.
#How to use this page
- 1Establish the scope
Review the active-target, ordered-ladder, recipient-coverage and open-gap indicators to identify the weakest escalation configuration.
- 2Interpret the evidence
Use the SLA timing matrix and L1–L3 chain preview to locate an out-of-order offset or missing inherited role holder.
- 3Act on the finding
Open SLA Targets to correct timing or Organization Registry to assign the missing role, then return and confirm the gap count falls.
#Governance and expected result
- Operate only within the tenant, role and record visibility granted to you.
- Record the decision, reason and supporting evidence before completing a governed action.
- Treat dashboard and derived Entity 360 values as decision support; verify material conclusions against the linked source record.
- Correct data in the owning legal record rather than editing an aggregate or exporting an ungoverned copy.
You used /lex/admin/escalations to find timing-order and recipient-coverage gaps across active SLA targets and the organization hierarchy. The result is visible in WatheeqTech and traceable to the acting user, tenant and source legal record.