Sam identified that Current Treatment Plan is a disorganized mess and should become cleaner with roadmaps. I treated this as a workflow redesign, not another text cleanup.
Live validation confirmed the core issue: litify_pm__Matter__c.Current_Treatment_Plan__c is only Text(255), and real values mix provider names, cadence, MRI status, referral status, appointment reminders, release/waiting status, and vague notes. Providers_Seen__c is also only Text(255), so it should not be the durable source of truth either.
Current_Treatment_Plan__c: Text(255).Providers_Seen__c: Text(255).Primary_Treatment_Provider__c: lookup to Account/Party.Treatment_Update__c: exists and is heavily used, with 32,732 records. This appears to be the current treatment-call workflow surface.litify_pm__Treatment__c: exists but has only 89 records. It has useful structured fields, but it does not appear to be the main staff workflow today.litify_pm__Role__c: already links Matter to selected Account/Party with Role Category and Role Sub-Category.litify_pm__Request__c: supports draft request rows tied to Matter and provider.Build a Matter-first Treatment_Roadmap_Item__c child object. Each row should represent one treatment roadmap item with selected provider Account, provider Role, treatment type, treatment stage, treatment status, cadence, last and next appointment dates, primary flag, records-needed flag, linked Request, source, confidence, and notes.
Then make Current_Treatment_Plan__c a generated summary snapshot, not the source of truth. Example snapshot: Primary: ExactaCare PT active 1x/week; Aptiva ortho scheduled; MRI completed.
Snapshot rules should exclude ER when active follow-up care exists, show no more than three active/scheduled roadmap items, and stay under 255 characters.
Saved plan: /Users/samaguiar/Documents/Projects/docs/superpowers/plans/2026-05-26-litify-treatment-roadmap.md
The plan includes metadata scaffolding, field design, draft Requests-tab automation, Matter snapshot automation, staff Screen Flow, migration candidate export, and QA checklist.
This session ended at live-validated design and implementation planning. I did not deploy Litify configuration because this changes staff workflow and should go through a check-only deployment plus approval before production activation.