Outcome
- Ran a focused live audit on the exact subject
Bi-Weekly Status Call with Client.
- Saved the local audit pack under
analytics/biweekly-status-call-audit-2026-04-29/.
Top-line Counts
- total rows:
6,383
- open:
3,950
- closed:
2,433
- overdue open:
1,478
- future-dated open:
2,472
- undated open:
0
Important Classification
- This family is not using the Task recurrence flag:
- open recurring count:
0
- closed recurring count:
0
- This means the problem is not the same kind of recurrence holdout that existed in the old stale-task lane.
Strongest Findings
- Open rows are almost entirely untouched:
3,941 of 3,950 open rows are Not Started
- Open load is highly concentrated:
Jordan Hatfield: 1,370Chymez Bradshaw: 655Austin Johnson: 460Christine Tingle: 380Sam Aguiar: 364Adam McDonald: 338
- Completion behavior is not uniform:
Josh Hollan: 74 open vs 231 closed tasks created in 2026Austin Johnson: 460 open vs 221 closed in 2026Jordan Hatfield: 1,370 open vs only 4 closed in 2026Christine Tingle: 380 open vs only 6 closed in 2026Adam McDonald: 338 open vs 0 closed in 2026
- Duplicate/open-overlap signal is strong:
424 matters currently have more than one open copy of this task family- several matters have
5 or 6 simultaneous open copies
- Creator-owner patterns suggest mixed generation paths:
Sam Aguiar -> Jordan Hatfield: 885Sam Aguiar -> Chymez Bradshaw: 441Jordan Hatfield -> Jordan Hatfield: 464- this likely reflects a mix of automation-context creation and direct owner-side creation, but source verification is still needed
Working Conclusion