Interpret legal-operations workload and velocity

#Page purpose

Assess active-matter workload, officer allocation, throughput and cycle time from the current legal portfolio.

#Before you start

• Sign in as legal leaders and operations analysts and confirm WatheeqTech shows /lex/analytics; 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

1. 1
   Establish the scope

   Read the KPI strip first to establish active matters, recent closures, average close time, settlement cycle and weekly throughput.

2. 2
   Interpret the evidence

   Use the officer-by-practice-area heatmap to find workload concentration, then compare opened-versus-closed and days-in-phase velocity charts.

3. 3
   Act on the finding

   Refresh after operational data changes and take the identified staffing or process action in the owning matter or team workflow.

#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.