Analyze the Entity 360 register
Review a read-only counterparty register derived from contracts, case parties and settlements.
Last updated July 20, 2026 · 6 min read#Page purpose
Review a read-only counterparty register derived from contracts, case parties and settlements.
| Application route | Intended audience |
|---|---|
| /lex/entities | Legal leaders, dispute teams and contract teams |
#Before you start
- Sign in as legal leaders, dispute teams and contract teams and confirm WatheeqTech shows /lex/entities; 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
Search the normalized organization name and use the KPI strip to understand total exposure, settlement exposure, recovery, open cases and active contracts.
- 2Interpret the evidence
Open the matching Entity 360 row and compare the organization’s exposure and connected legal-work counts.
- 3Act on the finding
Correct inaccurate names, parties or values in the owning contract, case or settlement record; the Entity 360 register itself is derived and read-only.
#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/entities to review a read-only counterparty register derived from contracts, case parties and settlements. The result is visible in WatheeqTech and traceable to the acting user, tenant and source legal record.