matter-close

Closing a litigation matter requires capturing the resolution outcome, final exposure, and lessons learned. The system validates the matter slug against the portfolio log, collects the outcome fields, shows the full close entry for explicit confirmation, then updates the log, history, and matter files.

Ending active matter tracking requires the resolution type (settlement, judgment, discontinuance, dismissal, withdrawal, or consolidation), resolution date, final cost or exposure amount, and a brief lessons entry to calibrate future risk decisions.

No, the matter closure process includes a conflicts gate that blocks closure when the slug is not found in the _log.yaml file. You must validate the slug against the matters log before recording the outcome and updating the portfolio records.

No, closing a matter does not delete the record. The portfolio-safe update changes the matter log status to closed, appends a dated history entry, and writes a closing block into matter.md, preserving the full audit trail for portfolio management.

When a matter is marked as closed, the audit trail is preserved by appending a dated history entry and adding a closing block to the matter file. This ensures outcome tracking and risk exposure data remain accessible without deleting the original record.

Use a structured matter closure process when ending active tracking in a UK litigation workflow to ensure data integrity. It enforces slug validation, collects mandatory outcome fields, and requires explicit confirmation before applying consequential archival writes to your portfolio.