Spinal cord injury cases are among the highest-value and slowest-moving files a personal injury firm handles. The medical picture takes months to stabilize. The damages calculation requires outside experts. Liability often involves multiple parties and reconstructed evidence. A generic personal injury CRM pipeline, the kind built for car accidents that settle in ninety days, loses these cases in the workflow. [SPEAKABLE] A spinal cord injury CRM pipeline needs at least nine stages because the case type carries two parallel tracks, one for medical evidence and one for liability, and collapsing them into a generic personal injury workflow hides the stage that is actually causing delay.
The nine stages below are built for the catastrophic injury file: high value, long duration, and dependent on outside experts whose timelines the firm cannot fully control. Each stage answers one question: what needs to happen before this case can move forward?
Quick Reference: The 9 Stages
- Stage 1: New lead captured from intake form or inbound call
- Stage 2: Medical records request and retrieval
- Stage 3: Treatment status verification before case acceptance
- Stage 4: Life care plan and future-damages evaluation
- Stage 5: Liability investigation and evidence-gathering
- Stage 6: Demand package preparation
- Stage 7: Negotiation or mediation
- Stage 8: Litigation filed for unresolved claims
- Stage 9: Settlement or closed-won with referral follow-up
1. New Lead Captured from Intake Form or Inbound Call
Every spinal cord injury case starts as an inquiry, and the CRM record needs to open at that exact moment, not after the intake call is finished, not after the form is reviewed the next morning. The record captures the contact's name, how they reached the firm, the date and time of contact, and the initial injury description. That timestamp becomes the start date for every pipeline metric the firm will ever run on this case.
Speed to lead matters in catastrophic injury cases just as it does in any other case type: the firm that responds first to a spinal cord injury inquiry has a measurable advantage in signing that case.
The intake source field in this stage also matters for marketing attribution. If the record captures the ad or channel that produced the call, the firm can eventually trace a signed catastrophic case back to the specific creative that generated it. Without that field at stage one, the data is gone. For firms running paid media for personal injury, the RGDM CRM automation system connects this intake record to the upstream ad at the moment the record is created.
Practical takeaway: Configure your CRM to require five fields at record creation: contact name, phone, inquiry date and time, intake source, and initial injury type. Everything else can be filled later. Nothing can be reconstructed if the record is not opened immediately.
2. Medical Records Request and Retrieval Stage
Once the intake call confirms a spinal cord injury, the next action is requesting records, and that action should be a CRM task, not a mental note. This stage tracks the date the records request was sent, the facility or provider it was sent to, and the date the records were received. When a case sits at this stage for more than two weeks without a receipt date, the CRM flags it for follow-up.
The records needed for a spinal cord injury case typically span emergency transport, the acute hospital stay, any surgical intervention, and inpatient rehabilitation. Each source is a separate request, sometimes to separate facilities. A single task field does not capture that complexity. The CRM stage should support multiple records requests within the same stage, each with its own status.
Practical takeaway: Build a records request checklist into this stage with at least four rows: emergency or transport records, acute hospital, surgical notes, and rehabilitation facility. Track sent date and receipt date for each row separately.
3. Treatment Status Verification Before Case Acceptance
A spinal cord injury case cannot be accurately valued until the medical picture is stable. If the client is still in acute rehabilitation, the long-term prognosis, the extent of paralysis or impairment, and the future care needs are all unknown. Accepting and working a case before that picture stabilizes creates a damages estimate that may need to be rebuilt from scratch.
This stage sits between records retrieval and formal case acceptance. The question it answers is whether the client has reached maximum medical improvement (MMI) or whether treatment is still ongoing in a way that will materially change the damages picture. The firm's decision to proceed or wait is documented in the CRM at this stage, along with the treating physician's most recent prognosis note.
Practical takeaway: Add a required field at this stage: "MMI reached: yes / no / estimated date." The case does not move to stage four until that field is completed by a case manager or supervising attorney.
4. Life Care Plan and Future-Damages Evaluation Stage
The life care plan stage is the one most firms leave out of their CRM pipeline, and it is the single document that makes or breaks a spinal cord injury demand.
A life care plan is a formal report prepared by a qualified life care planner or rehabilitation expert that projects the lifetime cost of care for a catastrophically injured person. It covers future medical treatment, assistive technology, home modification, attendant care, and lost earning capacity. In a spinal cord injury case, this document is not optional. It is the foundation of the damages demand.
This CRM stage tracks who was retained as the life care planner, the date the retention was confirmed, the date the expert received the medical records, and the date the completed plan was received by the firm. Those four dates tell the firm exactly where the case is within this stage and whether the outside expert is on track.
Because life care planners work on multiple cases and have their own timelines, this stage frequently becomes the longest single stop in the pipeline. Tracking it explicitly in the CRM means the delay is visible and accountable rather than invisible.
Practical takeaway: This stage requires four date fields: expert retained, records sent to expert, draft received, and final plan received. A case should not move to stage five until the final plan is in hand.
5. Liability Investigation and Evidence-Gathering Stage
The liability track runs parallel to the medical and damages track in most spinal cord injury cases. While the medical team is stabilizing the client and the life care planner is building the future-damages picture, the legal team is gathering the evidence that establishes fault. These two tracks need separate visibility in the CRM.
Liability evidence in a spinal cord injury case typically includes the police or incident report, any available surveillance or dashcam footage, the crash reconstruction expert's report (in vehicle cases), employer records and maintenance logs (in commercial vehicle cases), premises inspection reports (in premises liability cases), and witness statements. Each item is a separate task with its own deadline.
The CRM stage for liability investigation should support a checklist of evidence tasks, each with an assigned team member and a due date. When the checklist is complete, the case is ready to move to demand preparation. When items are still open, the pipeline report shows exactly which items are outstanding.
Practical takeaway: Map the standard liability checklist for spinal cord injury cases specific to your firm's most common case origin, vehicle versus premises versus product, and build that checklist into the CRM stage as a required task list.
6. Demand Package Preparation Stage
When the life care plan is final and the liability investigation is complete, the case is ready for a demand. The demand in a spinal cord injury case is a substantial document: it incorporates the full medical narrative, the life care plan projections, the liability theory, and the supporting evidence. Preparation takes time, and without a dedicated CRM stage, a fully built case can sit waiting for someone to start the demand letter.
This stage assigns the demand preparation task to a specific attorney, sets a due date, and marks the date the demand was sent to the opposing insurer or party. The CRM record also captures the demand amount, which becomes the opening data point in the negotiation log at stage seven.
Practical takeaway: Set a firm-wide standard for how many days after the life care plan is received the demand must be sent. Enter that deadline as an automated task in the CRM the moment the case enters this stage.
7. Negotiation or Mediation Stage
Every offer and counter-offer in a spinal cord injury negotiation should be logged inside the CRM record with a date, not tracked in a separate spreadsheet, so the full negotiation history is visible in one place.
Once the demand is sent, the case enters active negotiation. In a catastrophic injury case, this stage can span months. The opposing insurer may make multiple low offers before meaningful movement occurs. Formal mediation may be scheduled. The firm may retain an economist or vocational expert to support the damages position.
The CRM record at this stage should function as a negotiation log: the demand amount, each offer received with the date, each counter-offer sent with the date, and the date and outcome of any mediation session. When the file is eventually closed, this log documents the full trajectory from demand to resolution.
This stage is also where the firm decides whether the case can be resolved without filing suit. That decision point should be a field in the CRM: "Litigation recommended: yes / no / pending review." If the answer is yes, the case moves to stage eight. If the answer is no, it moves to stage nine.
Practical takeaway: Build an offer log table into this CRM stage with columns for date, party (insurer or plaintiff), amount, and notes. Every communication that includes a dollar figure belongs in this log.
8. Litigation Filed Stage for Unresolved Claims
Litigation-filed spinal cord injury cases belong in their own pipeline stage because the task set, service of process, discovery calendar, expert disclosures, is entirely different from the task set for a case still in negotiation.
When negotiation does not produce an acceptable resolution, the firm files suit. This stage captures the file date, the court and case number, and the service of process completion date. From that point, the stage generates a new set of deadline-driven tasks: the discovery calendar, deposition scheduling, expert disclosure deadlines, and any pre-trial motion deadlines.
Keeping litigation-filed cases in the same pipeline view as negotiating cases creates two problems. First, the pipeline report shows inflated case counts at the negotiation stage. Second, the litigation-specific tasks do not get created because the stage does not prompt for them.
A separate litigation stage also lets the firm monitor how many spinal cord injury cases are in active litigation at any time, which affects staffing, expert availability, and budget planning.
For firms that need to feed this pipeline data back to their marketing attribution system, the RGDM AI-powered lead response and tracking system connects CRM stage data to upstream ad performance so the firm can see which campaigns produced cases that required litigation.
Practical takeaway: When a case moves to the litigation stage, trigger an automated task list that includes service deadline, initial discovery deadline, and first expert disclosure date. These dates are usually set by local court rules and can be calculated from the file date.
9. Settlement or Closed-Won Stage with Referral Follow-Up
Closing a spinal cord injury settlement should automatically trigger a referral follow-up sequence in the CRM, because the referring attorney and the client are both realistic sources of future catastrophic injury cases.
The final stage closes the case and starts the next acquisition cycle. The CRM record captures the settlement date, the gross settlement amount, and the net recovery after liens and fees. Those figures feed the firm's cost-per-signed-case reporting: when the marketing spend that produced this case is divided by the case value, the firm has a real return metric, not a lead count.
The referral follow-up sequence at this stage serves two functions. First, it acknowledges the referring attorney with a formal thank-you and, where appropriate, a referral fee confirmation. That relationship is the most reliable source of future catastrophic injury cases for most plaintiff firms. Second, it opens a post-settlement check-in with the client at a defined interval, which is a source of reviews and word-of-mouth referrals.
Neither of these follow-ups happens consistently if they depend on someone remembering to do them. The CRM automation that triggers them on case closure is what makes them reliable.
The Nordanyan Law case study shows how this kind of closed-case attribution and follow-up sequence integrates with the full acquisition system. For firms working catastrophic injury at volume, the closed-won stage is where the next case starts.
Practical takeaway: Automate two sequences from this stage: a referral-attorney acknowledgment sent within forty-eight hours of case closure, and a client follow-up scheduled for ninety days post-settlement.
Why the Parallel Tracks Matter
Most personal injury CRM pipelines are built as a single linear sequence. That works for soft-tissue cases that move from intake to demand to settlement in a predictable line. Spinal cord injury cases do not move that way.
The medical and damages track (stages one through four) and the liability track (stage five) run simultaneously. The demand cannot be written until both tracks are complete. If the CRM treats them as sequential, the pipeline report will show the case stuck at "liability investigation" when in fact the life care plan has been waiting for three weeks with no action.
Building the parallel tracks into the CRM, as separate stages with separate task lists and separate assigned owners, is what makes the pipeline report accurate. And an accurate pipeline report is what lets the managing partner answer the question every catastrophic injury firm faces: how many high-value cases are ninety days from resolution, and how many are still two years out?
That question is also a marketing question. The answer tells the firm whether to increase spend on spinal cord injury acquisition right now or whether the current caseload is already at capacity for the team handling it.
Frequently Asked Questions
How should law firms structure a CRM pipeline for catastrophic injury cases?
Catastrophic injury CRM pipelines need at least two parallel tracks: one for the medical and damages development process (records, treatment verification, life care plan) and one for liability investigation. A single linear pipeline hides which track is causing delay. The minimum recommended structure is nine stages, from initial lead capture through closed-won with referral follow-up, with dedicated stages for the life care plan and for litigation if negotiation fails.
What stages matter most in a spinal cord injury case workflow?
The life care plan stage and the negotiation log stage are the two most commonly missing or collapsed in personal injury CRM pipelines. The life care plan is the document that supports the damages demand in a catastrophic injury case, and its absence or delay is the most common reason high-value cases stall. The negotiation log stage, when built with a full offer-and-counter record, gives the firm a complete picture of how the case moved from demand to resolution.
How do firms track life care plans inside a CRM?
The life care plan stage in a CRM should capture four dates: the date the life care planner was retained, the date medical records were sent to the expert, the date a draft plan was received, and the date the final plan was received. The case should not advance to demand preparation until the final plan is in the record. Some CRMs support document attachment so the plan itself is stored in the case record alongside the dates.
What slows down high-value injury case pipelines?
The most common sources of delay in spinal cord injury pipelines are: waiting for the life care planner to deliver the completed plan, incomplete liability evidence (especially in cases involving commercial vehicles or multiple defendants), and cases that drift in the negotiation stage without a logged follow-up date. A CRM pipeline with explicit stages, required fields, and automated task creation at each stage transition reduces all three delays because they become visible instead of invisible.
Should spinal cord injury cases use a different CRM pipeline than standard personal injury cases?
Yes. Standard personal injury pipelines are typically built for cases that resolve in under twelve months with a single demand-and-settle sequence. Spinal cord injury cases frequently take two years or longer, require outside experts whose timelines the firm cannot control, and carry a litigation rate that is meaningfully higher than soft-tissue cases. A generic pipeline produces inaccurate stage-duration data and misses the task prompts specific to catastrophic injury files.
How does CRM pipeline data connect to marketing attribution for catastrophic injury cases?
When the CRM assigns a unique record to every lead at stage one and that record carries the intake source field (which ad, which channel, which campaign), the firm can eventually trace a signed and settled spinal cord injury case back to its marketing origin. The closed-won stage is where that attribution becomes a business metric: case value divided by the cost of the campaign that produced the case gives the firm a return figure that is more meaningful than a cost-per-lead number.
What is the role of referral follow-up in the closed-won stage?
Referral attorneys are the most reliable source of catastrophic injury cases for most plaintiff personal injury firms. A closed-won stage that automatically triggers a referral acknowledgment within forty-eight hours of settlement creates a consistent, documented relationship-management practice rather than one that depends on individual attorneys remembering to make the call. The same stage can trigger a client follow-up at ninety days, which is a source of reviews and word-of-mouth referrals.
How many pipeline stages is too many for a spinal cord injury CRM?
The test is whether each stage has a distinct set of tasks and a distinct "ready to advance" criterion. The nine stages described here each have a specific set of required actions before the case moves forward. Adding stages beyond nine is reasonable if the firm handles enough cases with a specific sub-type, for example, cases involving medical malpractice as the underlying cause of the spinal injury, that a distinct stage improves visibility. Stages that have no required fields and no distinct task list are placeholders, not pipeline stages, and they inflate the stage count without improving the workflow.
Can a single CRM pipeline handle both represented clients and referred cases?
Yes, but the intake source field at stage one needs to distinguish between direct-inquiry cases and referred cases. Referred cases typically have a referring attorney record that should be linked at stage one and triggered for follow-up at stage nine. The pipeline stages are the same; the tasks and automations within those stages differ based on whether the case came in from paid media, a referring attorney, or an organic inquiry.
Managing the full acquisition system for spinal cord injury cases, from the first paid-media impression through the closed-won referral sequence, is what a Case Acquisition Review is built to assess. In thirty minutes, we pull the firm's current pipeline structure against the stages above and identify where high-value cases are stalling. No phone number, no sales call. Book directly at rgdm.com/contact to see where your catastrophic injury pipeline stands.
For firms building out the full law firm acquisition system, the law firms overview covers how paid media, intake, CRM, and attribution connect across practice areas.