The litigation platform built for defense MSOs

Defense MSOs can standardize intake, records handling, and carrier reporting on Turbo Law while each affiliated firm retains control of its files and legal judgment.

A trucking petition alleges the driver never slowed. In this illustrative intake, the MSO's operations lead has dispatch notes but still needs the ELD download and dashcam clip. We built Turbo Law for the division of work that follows: shared intake and reporting procedures, with the assigned defense firm controlling its file and legal judgment.

Assume three firms in two states share that operations team. Firm B receives the assignment. A standard checklist tells staff which records to request; it cannot tell the partner whether the driver's account holds up. Our unified litigation platform puts evidence review, drafting and report preparation in Firm B's matter workspace. The trucking workflow brings ELD, dashcam and dispatch evidence into a minute-by-minute timeline and cross-references the record against FMCSA regulations. Counsel still has to examine the cited records and watch the footage.

That is the distinction an MSO arrangement has to preserve, even on a rushed intake.

What a defense MSO is, and what it is not

A management services organization (MSO) is a separate business, typically owned by nonlawyers, that supplies services such as technology, staffing support, billing administration and facilities. In the model discussed here, its affiliated law firms remain lawyer-owned and lawyer-controlled. The firms earn the legal fees and practice law. The MSO has a services agreement.

ABA Model Rule 5.4 generally prohibits sharing legal fees with nonlawyers and protects professional judgment from outside interference. States adopt their own rules. An operating agreement needs review under the rules that actually govern the participating firms.

Texas Opinion 706 addressed a nonlawyer-owned platform supplying technology, back-office and legal support services. On those facts, lawyers had to direct and oversee its use, and payment could not be a percentage of firm revenue. Lawyer equity in a company that did not practice law was permissible, subject to conflict safeguards.

Illinois added statutory restrictions through Public Act 104-0801, effective August 7, 2026, for contracts entered into on or after that date. Its scope includes Illinois-operating firms below $300 million in global legal revenue, counting affiliates, plus qualifying contingency practices. Covered attorney-client contracts must disclose the MSO arrangement and material terms. The act restricts interference with judgment; control of client-record ownership, content or disclosure; hiring and firing legal personnel; and setting their competency, productivity or proficiency parameters. Service fees cannot depend directly or indirectly on firm fees, revenue or profits. These are Illinois limits.

An MSO also differs from an Alternative Business Structure. Arizona removed ER 5.4 effective January 1, 2021, and licenses ABS entities with nonlawyer ownership or decision-making under ACJA § 7-209. An Arizona compliance lawyer is required. That is a different structure from the services arrangement described here.

Turbo Law is not an MSO, does not own or invest in law firms, and does not give legal advice. We built litigation software for this division of responsibility.

What a defense MSO is, and what it is not

Turbo Law is not an MSO, does not own or invest in law firms, and does not give legal advice. We built litigation software for this division of responsibility.

The MSO runs the machine. The firm owns the judgment.

The upload marked complete is missing a dispatch attachment. Getting it belongs on someone's intake checklist. Once it arrives, however, it may contradict the driver's account. Someone else must decide what that means for the defense.

Write both assignments down:

MSO operations: maintain intake procedures, coordinate authorized staffing support and keep the reporting calendar moving.
Firm staff: inspect classifications and chronologies, check source links and bring missing or inconsistent records to counsel.
Associates: test factual propositions, verify research and review proposed privilege or work-product flags.
Partners: choose the legal posture, approve substantive work product and communicate advice.

Firm B needs to trace the petition's braking allegation into the dispatch evidence that arrives later. In Review, our intelligent Fact Graph makes that connection as part of its understanding of the case, with links back to source pages and lines. Extracted names and dates alone cannot capture it. The graph takes a form specific to trucking litigation and to this particular matter; its shape changes as records arrive. Pleadings, discovery, case law and the collision's particulars connect there, giving the firm the same case understanding to work from when reviewing evidence, drafting, researching a defense, setting strategy or preparing a report.

Rule 5.1 and Rule 5.3 place supervision duties on firm managers and supervising lawyers. ABA Opinion 512 applies competence, confidentiality and verification obligations to AI use. Outsourcing does not transfer the lawyer's responsibility for competent services: ABA Opinion 08-451 also addresses client disclosure and confidentiality obligations in outsourced work. Florida Opinion 24-1 applies nonlawyer-assistance supervision principles even where an outside provider operates the AI.

Suppose the ELD labels an interval differently from dispatch. Our Assistant can work through a multistep assignment and assemble a cited deliverable for attorney review. Exportable assignment logs show what was requested, read and produced. The associate's job is to open both records and assess the discrepancy. A citation is a lead for review, not proof that the proposed explanation is correct.

Where the file does not support an answer, the Assistant identifies that limit. Counsel must distinguish a record that has not arrived from one that supports an adverse fact. In the first carrier report, “not yet confirmed” should not silently become “no evidence”.

The Assistant does not serve, file or send.

Three firms on one platform, and no shared files

A second illustrative assignment puts the access problem in sharper focus. Firm A defends a general contractor. Firm C handles a related coverage-adjacent matter involving interests that may diverge. A shared services employee recognizes the project name in both files and remembers a damaging daily log.

Remembering the log does not authorize passing it along.

Our Security commitments include tenant isolation across firms, matters and carriers. We prohibit training on client data through contractual and technical controls. Vendor access requires an explicit support ticket and client-side approval; exportable audit logs record access, queries and exports. Firms can assess these commitments against Rule 1.6(c)'s reasonable-efforts duty and Opinion 512's vendor-diligence expectations.

The firms still need to assess conflicts and staffing. If a shared paralegal has authorized access to both matters, counsel must assess that arrangement and any necessary screens. SSO, role-based access control and configurable ethical walls are coming soon. Assess the proposed staffing against today's controls.

The existing DMS remains the system of record. For drafting, firm identity matters as much as matter identity: Draft uses the matter, that firm's own prior briefs and jurisdiction rules. The services agreement does not make Firm A's brief bank available to Firm C. Establish the authorized inputs before anyone starts an assignment.

One report format for the carrier, one partner signature per report

A claims handler reading three monthly reports needs to find what changed without first learning three reporting conventions. The MSO can coordinate a common format and deadline. Each firm's lawyer supplies the judgment behind the entries.

A blank section and a checked “no change” box carry different meanings. The format should preserve that distinction, particularly when the firm is still waiting for evidence it requested last month.

Our carrier offering supports consistent status reporting and exposure-modeling discipline across panel firms. It also provides a carrier-side view across those firms' matters without migrating the carrier's own data. That visibility belongs to the carrier. It is not an MSO dashboard.

The Assistant can schedule monthly report preparation. With Strategy & Settlement, drafts draw from the matter file to address coverage, key developments and updated exposure, along with proposed next actions and reserve recommendations. The partner reviews and sends the report. Reserves remain the carrier's decision; settlement authority stays with the authorized client or carrier.

For Firm B, one newly received dispatch message might change the reading of an ELD entry. The report should make that development easy to locate. Its significance is the partner's call, including whether the earlier assessment needs correction.

What an MSO should not ask its litigation platform to do

The difficult boundary questions tend to arrive with an ordinary business request: explain a late report, improve staffing or make billing more predictable. We would write four limits into the operating relationship:

No MSO-imposed attorney productivity scorecards. Illinois expressly restricts these parameters within its statutory scope. Elsewhere, business oversight must still respect lawyers' professional independence.
No MSO control of client-record ownership, content or disclosure. Records administration operates within authority the firm gives it.
No substantive work product goes outside without lawyer review. Completing a draft is a preparation step. Approval and transmission require their own responsibility assignments.
No service-fee formula tied to legal revenue. Texas Opinion 706 and the Illinois statute show why counsel must examine the commercial terms under applicable law.

These are design principles for the relationship. Software cannot certify that an MSO agreement, staffing decision or fee arrangement complies with the law.

Before the first matter loads

Bring the managing partner, operations lead and person responsible for tenant administration to a setup review. Use a proposed matter and name the people who would actually touch it:

Show what the assigned shared staff can access, including who holds tenant administration under today's controls.
Name the firm representative who approves a vendor support request involving its data.
Identify the firm's authorized drafting priors and the person who checks those inputs.
Assign responsibility for exporting and reviewing access and assignment logs when a question arises.
Review the engagement letter for applicable MSO, outsourcing and AI disclosures, and determine where consent is required for the proposed arrangement or use.

Put those decisions in the operating instructions staff use. A services agreement reviewed at signing will not tell a newly assigned intake specialist which approver to contact when a support issue occurs.

Then follow one disputed ELD entry into a proposed carrier paragraph. Have the assigned reviewer open the source, explain the conclusion and identify who approves transmission. An unclear answer is a setup issue to resolve before the next matter loads.