Automation

Neos Legal Case Management Workflow Rebuild & Document Automation

Freelance Legal-Tech Implementation Consultant

Business summary
Personal Injury Law Practice • Consolidate fragmented PI case workflows into a single auto-scheduling engine
  • Pruned case checklist from 54 to 33 tasks while protecting statutory limitation deadlines
  • Role-based task routing across 4 roles with stage tracking and overdue reporting
  • Rebuilt core firm letters as merge templates and unblocked Microsoft 365 SharePoint sync

What I built

Rebuilt and consolidated personal-injury workflows in Neos (Assembly Software) for a South Carolina law firm. Streamlined redundant case types into a single auto-scheduling workflow, pruning checklists from 54 to 33 tasks while securing statutory limitation deadlines (SC 3-year statute of limitations and government notices). Configured role-based task routing across 4 legal roles, case-stage pipeline reporting, automated merge templates for firm letters via the Neos Word Add-in, and resolved Azure/Microsoft 365 SharePoint admin consent blockers.

Tech stack

Neos (Assembly Software)Legal TechWorkflow AutomationDocument AutomationMicrosoft 365NeosAssembly SoftwareNeedlesLegal Case ManagementPersonal InjuryStatute of LimitationsRole-Based RoutingMerge TemplatesSharePointSOP Documentation
Deep Dive Case Study

Neos Legal Case Management Implementation - Personal Injury Workflow Redesign

Freelance legal-technology configuration, workflow automation, and document-template engineering.

Confidentiality note: The client is anonymized in this case study as it was delivered under a subcontract. Firm name, branding, and staff names can be added if disclosure is permitted.


Snapshot

Role Freelance Neos / legal-tech implementation consultant
Platform Neos by Assembly Software (cloud legal case-management; formerly Needles)
Client A U.S. (South Carolina) personal-injury law firm
Engagement Phase 1 - Personal Injury workflow rebuild, configuration, and handover
Effort ~40 hours
Delivery model Remote configuration over AnyDesk + programmatically generated documentation and templates
Status Built, tested, and documented; final template test + go-live remaining; Phase 2 scoped

The Problem

The firm was running personal-injury cases across several near-identical Neos case types, each with its own long, hand-maintained task checklist. Deadlines were tracked manually, task ownership was inconsistent, letters were produced by hand, and management had no clean way to see where cases sat in the pipeline. The goal for Phase 1 was to collapse all of that into one streamlined, self-scheduling Personal Injury workflow that any new case could run on - with the firm's statutory deadlines protected automatically.

My Role

I owned the end-to-end configuration and documentation of the new workflow: analyzing the existing setup, redesigning the checklist and automation, wiring staff routing and reporting, rebuilding the firm's letters as merge templates, diagnosing the Microsoft 365 integration, and producing the full handover package. Neos is a configuration-only platform with no public API, so the work was done directly in the application (remotely) plus a set of generated deliverables.


What I Delivered

1. Workflow consolidation & checklist redesign

Merged multiple duplicate PI case types into a single Personal Injury workflow. Pruned the primary checklist from roughly 54 tasks down to ~33, removing redundancy while preserving every legally required step. Rebuilt the task set around clean, coded stages and verified the integrity of every cascading reference after the prune.

2. Automatic deadline & statute engine

Configured due dates to cascade automatically from predecessor tasks and case-date anchors (Date of Incident, Client-Released/MMI, demand sent, settlement). Built the statute safety net so the statute of limitations (3 years in SC), the government-entity notice, and the 1-year / 6-month warnings all calculate from the Date of Incident, with the controlling deadline surfaced as the LIM date in the case header. These deadline tasks were locked down as protected.

3. Role-based task routing

Assigned every task to the correct role - Front Desk, Pre-Litigation Paralegal, Litigation Paralegal, Attorney - so the right work reaches the right person, and verified routing end-to-end across all roles.

4. Case staging & pipeline reporting

Wired a Class (stage) tag on every case - Treatment → Demand → Negotiation → Litigation → Settled - driving management reporting, including the Checklist Overdue Status report (overdue tasks by staff member, filterable by stage and case status).

5. Auxiliary (case-specific) checklists

Reused the existing Litigation and Arbitration add-on checklists and built a new Premises / Slip-and-Fall checklist, so specialized tracks attach on demand without cluttering the core workflow.

6. Live validation

Created a live test case and confirmed the whole engine end-to-end: date entry triggered the correct cascade, the statute of limitations computed to the correct date, routing resolved to the right roles, and stage tags flowed into the reports.

7. Document automation - letter templates & merge fields

Rebuilt three of the firm's core letters - Welcome, Letter of Representation & Preservation, and Policy-Limits Request - on the firm letterhead as Neos merge templates. Reverse-engineered the platform's template mechanism (merge tags are authored through the Neos Word Add-in as [[ Label | Field.Path ]] and compiled internally), produced upload-ready templates with color-coded placeholders (merge-field vs. fixed-text), and wrote a field-mapping / tagging guide so the firm can wire and maintain them.

8. Microsoft 365 integration

Diagnosed why document generation stalled: the Neos↔Microsoft 365 connection required admin consent for the Neos app (AssemblySoftwareAPI) plus a SharePoint document-library approval. Produced a concise admin action sheet for the firm's IT; the connection was approved, unblocking letter generation/storage and the Phase 2 client-email features.

9. Documentation & handover

Produced a full handover package: a one-page staff quick-reference, a client workflow guide with live screenshots, a consolidated setup & handover document, and a detailed 7-page handoff documentation covering the lifecycle, roles, deadlines, letters, reporting, go-live steps, administration, and a quick-reference glossary - all on the firm's letterhead and brand.


Technical Challenges I Solved

  • Undocumented, config-only platform. Neos has no public API; I mapped and rebuilt the workflow entirely through the application UI and verified behavior empirically on a live test case.
  • Merge-field mechanism. After hitting a "Document type has no contact fields" wall, I researched the platform and confirmed the real authoring path (the Word Add-in and [[ Label | Field ]] tags), corrected an earlier assumption about the stored «fN» codes, and reworked the templates and guide to match the supported method.
  • Integration blocker. Isolated the document-generation failure to an Azure/Microsoft 365 admin-consent requirement rather than a configuration error, and turned it into a clear, actionable step for the firm's administrator.
  • Programmatic, verified deliverables. Generated every branded .docx programmatically and visually verified each one (render → inspect) before delivery, fixing layout, pagination, and placeholder-highlighting issues along the way.

Deliverables Produced

  • Consolidated Personal Injury workflow (single case type, ~33 tasks, auto-scheduling)
  • Statute-deadline automation with protected LIM/statute tasks
  • Role-based routing across four roles
  • Stage tagging + overdue/pipeline reporting
  • Premises / Slip-and-Fall auxiliary checklist
  • 3 rebuilt letter templates (letterhead + merge placeholders) + tagging guide
  • Microsoft 365 admin action sheet
  • Staff quick-reference, client workflow guide, consolidated handover, and 7-page detailed handoff documentation

Tools & Skills Demonstrated

Legal-tech: Neos / Assembly Software (Needles) configuration · case-management workflow design · legal document automation & merge templates · Microsoft 365 / SharePoint integration troubleshooting
Domain: personal-injury case lifecycle · statutes of limitation & statutory notice deadlines · law-firm operations & staff workflows
Craft: business-process redesign · requirements analysis on an undocumented system · technical writing & client-facing documentation · stakeholder/broker communication · programmatic document generation (Node.js / docx) with visual QA


Outcome & Next Phase

Phase 1 was delivered: one consolidated, self-scheduling PI workflow - tested live, statute-safe, role-routed, reportable, with built-in letters and a complete handover package. The firm's remaining steps are the final letter-template test and go-live (retire the old case types; new intakes on the new workflow). Phase 2 - "Client Compass", an automated client-communication sequence (welcome guides, 30-day check-ins, and milestone updates), is scoped and recommended as the next engagement.