Sam asked whether a real treatment-status action item already exists, and proposed adding an Attorney Hub indicator when Litify damages exceed a threshold and the adjuster should receive an update. This was a read-only recommendation pass. No Salesforce metadata or live records were changed.
Live Salesforce org readback was run against LITIFY_ORG, including sf org list --all, a live litify_pm__Matter__c query, grouped stale-treatment SOQL, grouped damages-threshold SOQL, and insurance adjuster email availability SOQL.
Source metadata was inspected in /Users/samaguiar/Documents/Projects/Repos/sail-litify. The stale-treatment action item exists in dedicated AttorneyHub*ActionItemsController classes for Jon, Payton, and Abby or Payton copies, using Last_Treatment_Update__c older than 15 days or null. The Trent-style adjuster email pattern exists in AttorneyHubTrentController.addDemandNoOfferPrompts, using an Email adjuster action and the shared email URL helper.
A real stale or missing treatment signal already exists, but it is uneven. It is not the same as the cookie-cutter 30, 60, and 90 day open-date treatment prompts that were removed earlier. The existing signal is Tx compliance, labeled as treatment files without a recent update, and considers treatment current when Last_Treatment_Update__c is within 15 days.
Live count evidence for stale treatment across circulated attorneys showed: Trent Burns 16, Jimmy Brown 14, Nick Wilson 12, Austin Pollard 10, Payton Klatt 5, Jon Hollan 5. Abby and Terry did not return rows in that query.
The damages-adjuster idea is data-supported. Open Treatment, Demand Preparation, and Negotiation matters above $25k totaled 117. Of those, 109 had at least one adjuster email. Above $50k, there were 42 candidate matters, 39 with at least one adjuster email. Above $100k, there were 11 candidate matters.
Recommendation 1: Do not rebuild stale-treatment from scratch. Standardize the existing Tx compliance action item across all circulated hubs, ideally through shared logic, so all attorney hubs use the same real signal.
Recommendation 2: Add a new Damages update needed attorney action item. Start with $50k+ as the main operational threshold, escalate $100k+ as urgent, and optionally keep $25k+ as a lower-priority assistant queue. Filter to open matters in Treatment, Demand Preparation, or Negotiation, require at least one adjuster email, and use an Email adjuster action that mirrors the Trent demand follow-up pattern.
Recommendation 3: Add a companion Missing adjuster email on high-damages file action. When damages meet the threshold but no adjuster email exists, the action should be to open the insurance record or add adjuster contact information, not to generate an email.
Recommendation 4: Add a combined High damages + stale treatment item. If damages are $50k+ and treatment status is stale, the first action should be treatment status outreach, not adjuster notification. That prevents sending stale damage information to the carrier.
Recommendation 5: Before coding the adjuster update template, inspect the damages object and field history for a reliable latest-damages or latest-bill timestamp. The best long-term rule is not just total damages crossed a threshold, it is new money crossed a threshold since the last adjuster update.
Live data shows $50k+ creates a focused queue, 42 candidates and 39 with adjuster email, while $25k+ creates a much wider queue, 117 candidates and 109 with adjuster email.
$50k+, with $100k+ escalated (recommended): Best balance of signal and workload.$25k+ for the attorney action item: More comprehensive, but likely noisy.