Every ministry and department carries a portfolio of court cases and arbitrations. Individually each is managed by a law officer; collectively they are a financial liability that is rarely added up, and an ageing problem that is rarely seen whole.
What one view makes visible
Modules in the litigation platform we built
From our public-sector case study
| Module | What it answers |
|---|---|
| Executive dashboard | How many cases, how many open, win rate, financial exposure |
| Ministry analysis | Which ministries and departments carry the load |
| Court & status | Where cases are and how courts compare |
| Financial analysis | Exposure on open cases; high-value cases flagged |
| Ageing & pendency | How old cases are, across nine ageing buckets |
| Category analysis | Which of 43 service-matter types drive cases |
| Advocate analysis | Outcomes and duration by advocate |
| Case explorer & reports | Drill to any case; build custom reports |
Note: Capabilities as built.
Source: DaasLabs, “Public-sector case study: from case files and spreadsheets to a decision record” (2026)
From insight to action
For a law ministry's arbitration work we went a step further: decisions from a review are emailed to the owning office with the relevant data extract, a priority, an SLA and an escalation path; progress is updated from a link, and overdue actions are flagged. The dashboard stops being a report and becomes a way of running the portfolio.