Tier 3 · Lifecycle
Configured work types are a hypothesis about the work; the matters are the evidence. When one type absorbs a third of the book, it is usually hiding several distinct kinds of work that deserve their own routing, reporting, and resourcing. This audit reads the titles and the lifecycle to find the mismatch.
On-premise embedding analysis of matter titles segments a bloated configured type into the linguistically distinct kinds of work living inside it.
Multiple start phases, unreachable phases, and a missing mandatory Draft phase — structural defects that confuse routing and reporting.
Work-type inheritance beyond the sane limit (the five-level limit with the multi-dimension test) — depth that makes change risky.
Phase guards that block legitimate transitions, or are absent where a control is needed.
Reopen and pending-close phases holding years-old matters, and close velocity across the book.
Matter titles are embedded with a local model on an on-premise stack — client data never leaves a controlled environment — and segmented; configuration lenses check the phase plans, guards, and inheritance depth. Segmentation is exploratory and reviewed with your team.
One configured type absorbed 41% of the book (12,231 of 30,000 matters). Title embeddings, computed on-premise and labelled by a local model, segmented it into 7 distinct kinds of work (two of the eight AI-proposed segments read as the same kind of work and were merged before review — the audit surfaces a candidate list, a human confirms it).
A taxonomy that matches the work you actually do — sharper reporting, routing, and resourcing — and a phase-plan defect list that unblocks the matters sitting in stuck queues.