Triage contract playbook deviations

#Page purpose

Rank scored contracts by playbook compliance so low-scoring agreements receive review first.

#Before you start

• Sign in as heads of contracts, contract lawyers and knowledge managers and confirm WatheeqTech shows /lex/playbooks/portfolio; 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

   Filter by contract type and maximum compliance score, then keep ascending order to place the worst-scoring contracts first.

2. 2
   Interpret the evidence

   Compare scored, average, at-risk and healthy indicators for the visible page and inspect each contract’s deviation summary.

3. 3
   Act on the finding

   Open the affected contract or return to the playbook catalog to correct a contract deviation or improve the governing playbook.

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