AI tools generally work like a worksheet: you enter inputs (injury level, age, treatment), and the program returns a range. The problem is that spinal cord injury outcomes are highly individualized.
In Davis, the cases we see often involve factors that AI calculators typically can’t “see,” such as:
- Traffic and impact details from rear-end and lane-change collisions on commuter routes
- Delay between the crash and discovery of symptoms (which can become a causation fight)
- Visibility and crosswalk timing when pedestrians or cyclists are involved near high-foot-traffic areas
- Pre-existing conditions that insurers try to blame for neurological findings
When those issues are missing—or simplified—an AI estimate can feel confident while being grounded in incomplete assumptions.


