portfolio-status

To get a litigation portfolio overview, you parse the matters log to summarize risk distribution, upcoming deadlines, stale matters, and anomaly flags into a structured rollup report. This provides actionable litigation portfolio health at a glance.

Litigation portfolio tracking involves monitoring risk distribution, upcoming deadlines, stale matters, and anomaly flags across active files. It transforms a matters log into an actionable health report by highlighting overdue deadlines, unresolved conflicts, and missing legal holds.

Track upcoming litigation deadlines by grouping next_deadline items into 14, 30, and 60-day windows. This horizon tracking highlights overdue entries and upcoming hearings, ensuring no critical litigation deadlines are missed across the portfolio.

Yes, you can filter an active matters report by risk band, staleness, matter type, and owner using interactive arguments. This filters the YAML log data to produce customized portfolio status rollups for specific risk bands or ownership groups.

Stale matters and operational anomalies are flagged by applying rule checks to the matters log. This process identifies matters inactive for over 30 days, unresolved conflict statuses, missing outside counsel for high-risk items, and missing legal holds.

Yes, parsing litigation matter status requires a specific YAML file structure, specifically the matters/_log.yaml file. Risk calibration and flag rules are applied from the repository's CLAUDE.md file to generate the structured rollup report with proactive warnings.