We respect attorney-client confidentiality. No tracking pixels in our emails.
Needles remains a leading case management platform for personal injury firms. This guide covers intake setup, medical record linking, SOL tracking, demand letter automation, settlement tracking, and lien management workflows.
A personal injury attorney in Dallas nearly missed a two-year statute of limitations deadline on a motor vehicle accident case because her firm's intake staff entered the accident date incorrectly into their case management system. The system's SOL tracking calculated from the intake date, not the accident date. The error was caught by a second attorney doing a routine caseload review three weeks before the deadline — just in time to file. The firm subsequently rebuilt their Needles intake workflow to auto-populate the SOL calendar trigger from a dedicated accident date field, audited by a paralegal before matter opening.
That story illustrates the stakes of case management workflow design in personal injury practice. Needles — now part of the Ngage portfolio of legal practice management software — remains one of the most widely used case management platforms for PI firms in the United States. Its PI-specific workflow structure, medical record linking, and settlement tracking capabilities are built for the specific demands of contingency fee personal injury practices in ways that general practice management platforms are not. This guide covers how to configure and use Needles across every major PI workflow.
Personal injury case management has specific workflow requirements that distinguish it from other practice areas. Cases span months to years. The primary asset — the case value — depends on medical documentation that arrives from multiple providers on unpredictable timelines. Settlement involves complex calculations accounting for medical liens, attorney fees, and case costs before client distribution. Missing a statute of limitations deadline or failing to satisfy a Medicare lien can expose the firm to malpractice liability and disciplinary action.
Needles was built from the ground up for this environment. Unlike general practice management platforms that were adapted for PI work, Needles' data architecture reflects PI-specific concepts natively: each matter has structured fields for the at-fault party, insurance carrier information, medical providers linked to the matter, and treatment status tracking. This native PI data model reduces the configuration and workarounds that PI firms face when adapting general platforms.
Needles has evolved through several ownership cycles. Currently positioned as a mature, stable platform, it competes with newer PI-focused platforms like CasePeer and Filevine that offer more modern interfaces and stronger automation capabilities. Needles retains a substantial installed base among firms that have invested in its configuration and training over years of use — migration costs and workflow disruption make platform switches expensive even when newer alternatives are more capable in some dimensions.
The platform's relevance in 2026 depends heavily on how individual firms have configured it. A well-configured Needles installation with up-to-date templates, properly calibrated SOL tracking, and integrated medical record workflows is a competitive platform. A poorly configured installation becomes a liability management risk.
Needles intake begins with the Client screen, which captures party information, and the Matter screen, which captures case-specific data. The critical configuration decision is which date field drives SOL calendar calculations. For most PI matters, this should be the date of loss (accident date), not the intake date. Configure the Matter's SOL calendar trigger to reference the Date of Loss field, and build an intake checklist that requires paralegal verification of the Date of Loss before matter opening is completed.
The Liability section of the Matter screen captures insurance carrier information — both the at-fault party's liability carrier and the client's own carriers (PIP, UIM). Complete this section at intake even if information is preliminary; update as coverage confirmation letters arrive. The Insurance module's coverage tracking directly affects demand letter calculations later in the case.
For new matter workflow, build a Needles checklist (using the Workflow feature) that must be completed before a matter is marked as Active. Minimum intake checklist items: Date of Loss verified, Insurance carrier identified, SOL calendar entry confirmed, conflict check completed, and retention agreement uploaded to the document section.
The Providers module is where Needles earns its PI specialization. Each medical provider involved in a case is linked to the matter with fields for treatment dates, outstanding records requests, bills received, and treatment status. This module drives both demand letter preparation and lien management.
Best practice: create a Providers entry for each treating provider at the time the client first reports treatment, even before records are received. Set the record request status to Pending and assign a follow-up date. Use Needles' task system to generate automatic follow-up reminders when records have not been received within your firm's standard timeframe (typically 30 days after request submission).
When records arrive, upload them to the provider's document section and update the treatment summary fields. This keeps demand letter preparation from becoming a last-minute document gathering exercise — records are organized and linked throughout the case.
Needles' calendar and docketing features provide automatic SOL alerts when configured correctly. The configuration requires: (1) setting the SOL calculation rule for each matter type in your jurisdiction, (2) verifying that the Date of Loss field — not the intake date — is the trigger date, and (3) setting alert thresholds (most PI firms set alerts at 6 months, 3 months, and 1 month before the SOL date).
For cases with potential tolling issues — minors, incapacitated persons, late-discovered injuries — configure a Tolling flag in the Matter screen that requires manual SOL review when triggered. Do not rely on automated calculation for tolled SOL dates; assign a senior attorney review obligation.
Needles' document automation system uses merge fields that pull live case data into letter templates. A properly built demand letter template merges: party names and addresses, date of loss, description of injuries (from the Matter narrative fields), treating providers and treatment summary (from the Providers module), total medical specials (calculated from provider bill fields), lost wages (from the income documentation fields), and insurance information.
Building the demand template requires initial investment — typically 4-8 hours for a legal assistant familiar with Needles' merge field syntax. Once built, demand letter generation takes approximately 20-30 minutes per case (pulling current data, reviewing accuracy, and customizing narrative sections) rather than 2-3 hours of manual drafting.
Needles' Settlement screen tracks offer history, acceptance, and distribution. The distribution calculator takes the gross settlement amount and applies deductions in order: case costs, attorney fees, and then lien obligations. For Medicare and Medicaid liens, Needles has fields for lien amounts that feed the distribution calculation — but the lien amounts must be entered manually from MSPRC correspondence or state Medicaid agency notifications.
Configure a settlement workflow checklist: lien search completed, Medicare conditional payment letter received, final lien amount confirmed, disbursement authorization signed by client. Do not release settlement funds until all lien items are checked. Needles' checklist system can enforce this workflow if configured as a required step before Settlement status is set to Closed.
End-to-End PI Case from Intake to Settlement
Week 1 (Intake): Paralegal opens matter, verifies Date of Loss, enters insurance carrier information, generates records requests to three treating providers, sets SOL alerts. Retention agreement uploaded.
Months 2-8 (Treatment): Monthly provider follow-ups via Needles task reminders. Records received and uploaded as they arrive. Medical bills logged in provider fields. Case status reviewed quarterly.
Month 9 (Demand Preparation): Treatment confirmed complete. Paralegal runs demand letter merge from Needles — letter auto-populates with current provider data, specials total, and insurance information. Attorney reviews and customizes narrative. Demand sent.
Month 12 (Settlement): Carrier offers settlement. Offer entered in Settlement screen. Lien search completed, Medicare lien confirmed. Distribution calculation run. Settlement approved, disbursement worksheet generated from Needles template. File closed.
Needles — The subject of this guide; strongest for established PI firms with existing Needles configurations; evaluate upgrade path for older installations.
CasePeer — Modern PI-focused alternative with stronger automation and a more contemporary interface; worth evaluating for firms considering platform migration.
Filevine — Flexible case management with strong PI workflow capabilities; better integration with external tools but requires more configuration than Needles' PI-native structure.
Clio — General practice management with PI capabilities; best for firms with mixed practice areas who need one platform.
JusticeText — Specialized tool for deposition preparation and transcript analysis; integrates with case management workflows for PI deposition prep.
See also: Clio vs MyCase comparison and our glossary entries on matter management and litigation hold.
Q: Should we migrate from Needles to a newer platform like Filevine or CasePeer?
A: Migration has real costs: data migration, staff retraining, workflow rebuilding, and productivity dip during transition. Evaluate whether the specific capabilities you need (better automation, stronger integrations, more modern UI) justify those costs. Firms with 10+ years of Needles configuration often find that optimizing their existing Needles setup delivers more value than migrating.
Q: How should we handle SOL tracking for cases with potential tolling — minors or late-discovered injuries?
A: Never rely solely on automated SOL calculation for tolled cases. Flag them in Needles with a manual review requirement and assign a senior attorney to personally verify the SOL date with a jurisdiction-specific analysis. Automated tools should support judgment, not replace it for high-stakes deadline calculations.
Q: Can Needles integrate with medical records portals like CommonWell or PointClickCare?
A: Needles' direct integrations with specific medical portals are limited. Most integrations require document upload rather than live API connection. Review your current Needles version's integration capabilities — newer versions have added more connection options. For high-volume medical record retrieval, consider a dedicated medical records retrieval service that delivers records in a format that uploads cleanly to Needles.
Q: What is the best way to track case costs in Needles for distribution calculation?
A: Use the Costs module consistently from matter opening. Assign costs to specific categories (filing fees, expert fees, medical records costs) as they are incurred. The Settlement distribution calculation automatically pulls from the Costs module when configured — but only if costs were entered in real time rather than reconstructed at settlement.
Q: How do we handle cases where the client has both Medicare and a private health insurance lien?
A: Enter each lien as a separate line item in the Settlement screen's lien section. Process Medicare lien reduction negotiations through MSPRC before entering the final amount. The distribution calculation will apply all liens sequentially. Do not estimate lien amounts — use confirmed figures from each lienholder.
This article reflects independent editorial analysis. LawyerAI does not accept payment for editorial coverage. Tool scores are based on methodology described in Our 5-Dimension Methodology. Last reviewed: 2026-06-13.
