Thomson Reuters Legal Tracker is excellent at what it was built for: ingesting LEDES, routing approvals, applying standard timekeeper rules, and producing reporting that finance trusts.
What it was not built for: reading the prose of your Outside Counsel Guidelines and applying that language to the narrative of each line entry.
Where the gap shows up
Legal Tracker's native billing guideline engine handles the deterministic cases well:
- Hard rate caps per timekeeper class
- Block-billing detection above a duration threshold
- Task and activity code restrictions
- Minimum and maximum increment rules
Those rules catch the obvious violations. They miss the rest.
The cases that need language understanding
Here are the patterns Legal Tracker's rules engine consistently misses on real invoices:
1. Internal conferences
Your OCG says: "Internal conferences between two or more of the firm's timekeepers on the same matter are not billable except where pre-approved in writing."
Legal Tracker can flag two timekeepers logging time on the same day. It cannot tell you whether their narratives describe the same meeting, or whether the topic was strategic enough to qualify as pre-approved.
2. Vague narratives
Your OCG says: "Time entries must describe the specific task, the matter context, and the work product produced."
Legal Tracker can flag entries shorter than N characters. It cannot tell you that "research re: motion" fails the OCG even though it has 22 characters.
3. Non-billable administrative work
Your OCG lists a dozen categories of admin work that are never billable - filing, calendaring, travel coordination, organizing binders. Legal Tracker has no native way to detect those when they hide inside otherwise legitimate-looking entries.
4. Staffing limits
Your OCG might cap the number of timekeepers on any given matter, or restrict partner involvement to specific phases. Legal Tracker can report staffing; it cannot enforce a nuanced policy.
The right architecture
The fix is not to leave Legal Tracker. Your matters, firms, approvers, budgets, and reporting all live there, and they should stay there.
The fix is to add an AI reviewer inside Legal Tracker's existing approval routes - one that reads every line against the prose of your OCGs and writes adjustments back where they live.
That is exactly how 42B is built.
