73+ capabilities, in eleven groups.
This is the unabridged Workers’ Comp list — the rating argument, the statutory clocks, the indemnity math for three states, the drafting, the named agents that work the book overnight and still have to ask, the trust ledger, search and deposition testimony cited to page and line, and the portal the injured worker signs in to. Every item below is reachable by an attorney today: a route you can click, or something you can ask Justine for. Where a capability has a real limit — a scope it does not cover, a file type it will not take, an end of it that has no screen yet — the limit is written into the entry rather than left for you to find. Code we have written and tested but that you cannot yet reach is named at the foot of the page rather than counted here. For the guided tour, start on the WC overview; for what shipped and when, see the WC release notes.
Decision support, bound by the ABA Rules. Justine reasons and drafts; the attorney reviews, attests and signs every output. Rating and settlement figures are projections the attorney verifies against the current schedule. Nothing here is legal advice, and nothing here decides on its own.
The book, triaged
Open the app and it already knows what today is about.
- Today — the morning briefing: what needs you, what moved, and what Justine handled while the office was shut
- Matters — the whole book in one filterable, triage-fast list
- The matter workspace — one file in five stages: intake (overview, compensability, client, documents, depositions, search), medical and QME, rating (rating and value, benefits paid), negotiation (deadlines, settlement) and resolution (liens, trust ledger, file and retention, and what Justine did)
- Case-facts and injury-claims cards — the facts the statutory clocks depend on, held where a human can check them, with each injury claim carrying its own §5405 clock because they do not run together
- Jurisdiction card — which state governs, with the competing bases set out and the reasoning shown
- A guided first-run tour and the owner’s manual inside the app, searchable, without leaving the matter you were in
- Bring an existing book in — matters import from a CSV or TSV export, with columns matched by header name and the file read and checked before anything is written. It is honestly not a transaction: matters are created one request at a time, so a file that fails partway leaves the matters before the failure already created, and the importer recognises rows already in the book when you run the corrected file again. Up to 2,000 rows at a time, and the run belongs to the tab you started it in
Permanent disability & the rating argument
The rating string, end to end — and the rebuttal it invites.
- The PD Value Engine — WPI → the 1.4 FEC factor → occupational variant → age modifier, computed to the 2005 schedule with the statute cited. Deterministic code, never a generated number
- Kite alongside the Combined Values Chart — the additive total, the CVC total, and the delta between them in disability points and, when the average weekly wage is supplied, in dollars. Justine computes both and selects neither: Kite is persuasive panel authority available only on substantial medical evidence that the disabilities do not overlap, and that is a finding for the attorney and the judge
- The Escobedo substantial-evidence screen — where a physician’s stated basis for apportionment does not carry the burden, Justine says so and shows what it would cost. Report-only: it never silently restates the rating, and an indeterminate answer stays indeterminate
- Per-region apportionment applied before the regions combine, and a §4664(b) prior-award credit
- An apportionment-conflict view, a Combined Values Chart walkthrough, and an estimate badge on every figure that consumed an unverified schedule table
- WPI rating engines for internal medicine, digestive and endocrine impairment
- AME / PQME record reading feeding the rating, with the attorney reviewing every result
Indemnity, benefits & three states
Each state on its own law, not California applied elsewhere.
- California indemnity — the temporary-disability rate under §4653/§4453, the permanent-disability rate under §4658/§4453(b), total PD weeks and dollars, the §4658.7 return-to-work voucher, and the §4659 life pension once PD reaches 70%
- Georgia PPD / TTD / TPD and death benefits, and Texas TIBs / IIBs / LIBs with the 90-day impairment-rating finality deadline — computed and displayed alongside California
- Labor Code §5814 penalty computation, and life-pension commutation math
- A benefit ledger per claim — indemnity paid, owed and projected reconciled onto one surface instead of assembled by hand
- Which-forum-governs resolver — when more than one state could take jurisdiction, Justine says which forum governs and why
- Every figure carries its provenance: values that consumed an unverified schedule table are flagged as estimates rather than presented as settled
Deadlines & statutory clocks
The clocks that decide a comp case, computed with their basis.
- The Deadline Guardian — every jurisdictional clock across the book, plus a calendar view and per-matter deadlines
- The §4610 utilization-review clocks — the five-business-day decision, the 72-hour expedited clock, the outer 14-day cap, and the physician-notification and written-notice clocks, each with its statutory or regulatory basis
- The §4610.5 IMR clock that follows a denial, with the mail extension flagged for confirmation rather than assumed
- Business days and court days counted as genuinely distinct from calendar days against the judicial-holiday calendar, with service-method extensions applied
- A statute-cited California docketing catalog you can preview against the matter before anything is written to it
- Deterministic statute-of-limitations tracking, and deadline reminders at 7 days, 24 hours, 1 hour and overdue
- A notification centre with one tier that cannot be switched off: a statutory deadline warning reaches you past a muted preference, a global unsubscribe and quiet hours. Exactly one kind of notice carries that status — it is a narrow guarantee on purpose, not a category
- What that override does and does not do, said plainly: it overrides a preference, never a consent. Without SMS consent on file the same warning is delivered in the app and by email rather than by text, because the app record is itself the delivery and does not depend on a message leaving the building. Email and SMS a provider will not confirm are reported as unconfirmed rather than as sent
The agent fleet & the approval inbox
Nine named agents that can ask, and cannot act alone.
- Nine named agents on one queue — docket sentinel, inbound mail, benefit reconciler, QME packet assembler, correspondence, standing red team, book of business, client communication, and fee leakage
- One authorization function classifies every action an agent proposes. Reading, computing, drafting, saving and telling someone inside the firm are kinds an agent may perform. Sending outward, filing outward and touching money are kinds it may only queue for an attorney — and an action kind nobody recognises is refused rather than allowed
- The approval inbox — the outward-facing work Justine is holding, each item approvable or rejectable with a reason, none of it moving until an attorney says so
- The record of what she declined to do — the same surface shows what Justine considered and refused, per matter and across the firm
- Agents start in shadow, where they propose and log and execute nothing. Five are promoted to live in the production deployment and four are still held in shadow; promotion is a declared change to the deployment that a build gate refuses to let stay implicit
- A per-matter activity feed — what ran on this file, what it found, and what it was not permitted to do
Drafting, documents & the firm’s letterhead
Justine writes it. The firm owns it. Nothing sends itself.
- Drafts as a document workflow — open what Justine wrote, read it, edit it in place, and save the edit as a new version with the original preserved
- Export as Word or PDF, rendered server-side on the firm’s own letterhead — with a preflight that says plainly when no letterhead is set, rather than inventing stationery
- Firm identity applied deterministically — the letterhead and the firm’s own not-legal-advice notice are stamped by the renderer at export time, not written by the model. The signature block and house style are handed to the drafter verbatim
- No Send button in the editor. Outward correspondence goes through the approval inbox instead, and only when the firm has switched sending on
- Client letters in English or Spanish, chosen per letter where the document type is one addressed to the client — and the composed prose is verified to have come back in the language that was requested, failing loudly rather than delivering an English letter labelled Spanish
- A document library on the matter, and Bates-labelled exhibits
- Deposition transcripts read in with page-and-line citation — paste or upload a plain-text excerpt, roughly forty pages at a time rather than a full volume, and every passage afterwards is addressable and quotable as page:line. Plain text only today: a PDF transcript has to be converted before it comes in
- A transcript the parser cannot read with confidence is refused rather than guessed at, and the refusal is a report — what it read, where it stopped and which of the reasons applied, carrying line numbers and no testimony. A refused transcript stores nothing at all, including the pages that read cleanly, so a partial ingest never masquerades as a whole one
- Records requests tracked on the matter — each request carrying its status and its deadline, with a past-due flag that is derived when the page is drawn and labelled as derived, because nothing on the server marks a request overdue on its own
- Document blockers surfaced against the QME packet — records that cannot go in because service was never recorded or the page count is missing. Justine reports how many are blocked; naming each one individually is not something this surface can do yet, and it does not pretend otherwise
Settlement, liens & the money out
C&R against Stips, with the net the client actually sees.
- Settlement pipeline — Compromise & Release modelled against Stipulations, with ranges and net-to-client under each path
- The WCMSA flag raised before a C&R is papered — a flag and an analysis, not a dollar calculator
- Lien management across the book — medical, copy service and interpreter liens
- Offer tracking on the matter, and the negotiation history behind the number
- The contingency-book view — costs fronted, expected fees and velocity across the practice
Client money, on its own ledger
A records surface for trust accounting — recorded, never certified.
- A trust book for the firm — the trust accounts, their balances and the full transaction ledger on one surface, with the per-matter sub-ledger sitting on the matter file where the rest of that case already lives
- Three-way reconciliation — the book closing balance, the bank statement balance, and the adjusted bank balance (the statement plus the outstanding items) set against one another, with the outstanding items that explain a difference listed rather than netted away. The third leg is the ADJUSTED BANK balance, not the sum of the per-matter sub-ledgers; the sub-ledgers are readable per matter but are not a leg of this computation
- Completed reconciliations are kept and can be reopened, so a period that was reconciled can be shown to have been reconciled. A reconciliation completed over a difference nobody explained is recorded as forced, not as clean — the distinction survives in the record instead of being smoothed out of it
- What this is not, stated on the page itself: a records surface, not an audit and not a certification of compliance with any state bar trust-accounting rule. The statement balance is entered by a person — Justine reads no bank, and there is no bank feed
The injured worker’s own view
A matter-scoped portal for the client. Firm-issued, and narrow by design.
- A portal the injured worker signs in to and sees one thing — their own matter: where it stands, the injury type, the dates that matter and the firm acting for them
- Documents appear only when the firm has released that document. Release is a decision recorded per document, not a switch that opens the file, and access to the matter never implies access to what is in it
- What a client is never shown is enforced on the server rather than hidden in the page: case value, settlement ranges, the rating figure, the limitations date and the firm’s own internal fields are not sent to the portal at all, so there is nothing there to leak through a mistake in the interface
- No self-registration. Access begins with an invitation the firm issues, and where one email address turns up on more than one matter the portal declines to guess and tells the client to use the link their firm sent them
- Read and download only — no messaging, no uploads, nothing to sign. Access can be withdrawn, and the withdrawal takes effect on the client’s next request rather than whenever a session happens to end
Ask Justine
A query layer over the matter — with the tool call shown.
- Ask Justine — a natural-language layer over the matter that answers with citations and shows the lookup as a visible tool call rather than asserting from memory
- The capability library — “what you can ask Justine”, generated from the live tool registry and the verified rule corpus, so it cannot describe a capability that no longer exists
- 399 verified California workers’-comp rules, adversarially author-to-reviewer verified before they ship, plus 43 Georgia and 27 Texas rules and statute search across 50 states and DC
- Rule checks at the point of work, AMA Guides search, and citation verification against CourtListener
- Ask over the matter’s own documents, with the answer carrying its sources
- Med-legal, settlement and red-team specialist panels that reason in parallel and visibly, rather than returning one opaque answer
- Search in two scopes — across the firm, over its documents and its matter records; and on a single matter, where deposition testimony and case notes come in as well. The two scopes deliberately read different corpora, and the page names which are in play rather than implying one search reads everything
- Every hit carries where it came from: testimony cites page and line, a document result names the document it came from, and a matter-record hit says plainly that it matched on the record — the title, the WCAB reference, the injury type — and not on anything inside the file
- The limit on document search is published on the surface that has it: documents are searched across the firm and not within one matter, and only the strongest matches come back, so a document that ranks below them firm-wide will not appear on the matter. The caveat renders next to the results every time, not in a footnote
- A document that has been uploaded but not yet analysed is not searchable yet — and rather than being quietly missing, those files are counted and named beside the results, so an empty answer can be told apart from an unindexed one
The firm around the matter
The settings that actually reach the work.
- Firm settings that are wired to behaviour — letterhead, signature block, the firm’s own not-legal-advice notice, default letter language, record-retention period, default service method, and the capability toggles that genuinely gate the features they name
- Personal settings — deadline alerts, daily briefing time, and the language Justine dictates and reads aloud in
- Injured-worker records with contact cadence and language
- The in-app owner’s manual — what, where and how for every capability, rendered inside the app shell
- Tenant-isolated case access, a tamper-evident hash-chained audit trail, and an AI disclosure on every surface where Justine produces work
Named plainly, so you can trust the rest.
We label roadmap and not-built capabilities as exactly that — they are never presented as shipped. The last item is the one most vendors would leave out: work that is finished and tested but that has no screen yet, which we count as nothing until you can reach it. The following are not live today:
- A WCAB board integration. Justine reads no board, holds no board credential, and files nothing — no docket is fetched and nothing is transmitted to the Board. Where a docket matters, a person records it and Justine reconciles it against the firm’s own filings and calendar, reporting “unverified” rather than “clean” when no board record has been read
- Direct WCAB e-filing submission — Justine prepares and tracks the packet; she does not file it
- A firm-side screen for the client portal. The portal is live and an invited client can sign in, but issuing the invitation and releasing a document are API operations today with no page in the workspace, and invitations are not emailed by the product — the firm passes the link to the client itself. Until that screen exists, this is a capability with a live client end and an unfinished firm end, and it is described that way rather than counted whole
- A client-portal password reset, portal messaging, client uploads and e-signature. A portal session is short and deliberately not persistent, and there is no self-service recovery — a client who cannot get in goes back to the firm
- The average-weekly-wage derivation across concurrent employments — not reachable by an attorney yet; the rating and indemnity figures use the average weekly wage recorded on the matter, and it is not counted as a capability on this page
- In-app e-signature, and the bring-your-own DocuSign connection beside it. The signing envelope, its hash-chained audit trail and the Certificate of Completion are built; no mail provider is wired, so no signer is ever reached, and the workspace has no screen that starts or finishes a signature. A C&R, a Stipulation and an engagement letter are drafted and exported for a wet or out-of-band signature today. On the roadmap, and counted as nothing until an attorney can reach it
- A records-request model of its own. Requests are tracked on the matter, but there is no custodian record, no separate date the records came back, and no link from a request to the documents that answered it — the request and the file it produced are not joined for you
- Filevine, Clio and other third-party case-management connectors
- Single sign-on for firms (OIDC / SAML) — not available today; the backend has a flow but no sign-in or settings screen in either app
- The four other practice-area editions (MT, MM, IB, EL) — only PI and WC (applicant-side; California, Georgia, Texas) are calibrated today
JustineAI™ WC is legal-workflow software, is not a law firm, and its outputs are not legal advice. Bilingual client letters are verified to be in the language that was requested; that is a check on the language, not on the quality of the translation, and a person who reads Spanish should review a Spanish letter before it goes to the client.
Win more comp cases — and stop leaving value behind.
Leave no money on the table.
The California permanent-disability rating computed both ways — as reported, and with the apportionment challenged — through the impairment chain and the indemnity dollars, with every figure that rests on a table Justine has not verified labelled an estimate rather than a rating. Georgia and Texas benefits compute from the evaluator’s impairment rating.
Never get caught by a deadline.
Justine tracks the statutory clocks that quietly end cases — including the Texas 90-day impairment-rating finality deadline most attorneys never see coming.
An associate’s output, at software cost.
399 statute- and case-cited rules in California alone. Justine drafts, computes, and cites while you sleep — you review and decide. The reasoning is the product; your judgment is the check.
Three states. Built to real depth. Not a checkbox.
Everyone claims fifty states. We built three to the depth a workers’-comp attorney actually needs — the real statutes, the real benefit math, and the real deadline traps of each — and Justine tells you which state’s law governs when more than one could. Depth you can cite in front of a judge, not a checkbox on a feature grid.
- Rating basis
- 2005 PDRS (state schedule)
- Computes
- Full permanent-disability chain + indemnity, TTD, apportionment, SJDB voucher, penalties & interest, life-pension commutation
- Cited rules
- 399+ statute- and case-cited
- Deadlines tracked
- §5405 SOL · §4062.2 QME · §5410 reopening
- Statute search
- 399-rule cited base + AMA Guides 5th
- Rating basis
- AMA Guides 5th
- Computes
- PPD · TTD · TPD · death benefits
- Cited rules
- 43+ statute- and case-cited
- Deadlines tracked
- 1-yr §34-9-82 SOL · WC-240 · 400-week TTD cap
- Statute search
- O.C.G.A. Title 34, Chapter 9
- Rating basis
- AMA Guides 4th
- Computes
- TIBs · IIBs · LIBs
- Cited rules
- 27+ statute- and case-cited
- Deadlines tracked
- 1-yr §409.003 SOL · 104-week MMI · 90-day IR finality
- Statute search
- Texas Labor Code, Title 5
Every other state, DC, and the federal programs (Longshore, FECA, and the Defense Base Act) are recognized by the jurisdiction resolver today — it identifies the governing forum and can ground and cite the controlling rules. Full benefit computation is built state by state, next.
And grounded in all fifty.
Ask Justine about any US state or DC — “what’s the permanent-disability schedule in Ohio?”, “the filing deadline in Florida?” — and she answers with that state’s own workers’-comp statute, the governing section quoted. Every one of the fifty. So a case in a state we haven’t fully rated yet still starts with the law in front of you, cited.
- Fully rated — computes the benefit dollars
- California · Georgia · Texas
- Statute-grounded — cites the governing law
- All 50 states + DC
Pick a state. See the governing law.
This is the nationwide grounding, live: choose any of the fifty states or DC and Justine returns that state’s own workers’-comp statute, the controlling section quoted. In the product she searches the full text on demand — the passages below are real samples from the same corpus.
(A) In cases of permanent total disability, the employee shall receive an award to continue until the employee's death in the amount of sixty-six and two-thirds per cent of the employee's average weekly wage, but, except as otherwise provided in division (B) of this section, not more than a maximum…
Sample passage from Justine’s statute retrieval — grounded and cited. Verify against the current statute; not legal advice, and not a computed rating.
Powerful because it shows its work.
Justine doesn’t hand you an answer and ask for trust. It shows the reasoning, cites the authority, and marks what’s verified versus what needs your eyes — the four things a workers’-comp attorney has to be able to stand behind.
- 01Which forum governs
More than one state can claim the same injury. Justine surfaces the candidate forums and how the benefits and deadlines differ — you choose. No silent guess about whose law applies.
- 02The numbers, cited
Benefits and indemnity computed to the governing statute, with the section cited. Every figure is marked either verified against the loaded schedule or flagged for confirmation — never a confident guess.
- 03The deadline that ends the case
State-specific docketing tracks the clocks that foreclose a claim — California’s §5405 SOL, Georgia’s one-year §34-9-82, Texas’s 90-day impairment-rating finality — before they pass.
- 04Grounded, yours to verify
Answers stand on statute- and case-cited rule bases, never invention. A rating is a rating aid, not a medical opinion; the analysis is work product; the attorney decides.
Not legal advice · not a law firm · a rating aid, not a medical opinion · the attorney decides.
The refusals are the product.
The question that decides a legal-AI purchase is not what the system can do. It is what it does when the record will not support an answer. Every item below is a place Justine declines — named, in the product’s own words, with the evidence it would not fabricate. A machine that tells you which of its own inputs it could not stand behind is worth more to a practice than one that always has a number.
It marks its own answer unverified.
The permanent-disability chain — impairment, the 1.4 factor, occupational variant, age modifier — carries a verification flag through every step, and where it used an adjustment table it cannot vouch for, it says so on the screen beside the number rather than printing a clean figure. A permanent-disability percentage is money. An engine that tells you which of its own inputs it could not stand behind is worth more than one that always answers.
- Benson apportionment
It refuses the comparison the record cannot support.
Benson v. WCAB requires a separate, separately-apportioned award for each industrial injury. Where the file does not carry what that comparison needs — a second recorded injury with its own date, or a finding that can be attributed to a claimed region — the comparison does not run and the screen names the missing evidence instead. It returns a reason, not an estimate.
- Deposition transcripts
A transcript it cannot number is refused, not stored.
Page-and-line numbering has to survive the export. A missing line number, a repeated page, or numbering that changes style mid-transcript is rejected with the page and line named — nothing is stored and nothing is inferred, because a guessed line number shifts every citation taken after it. That is why a page-and-line cite this product prints is quotable in a filing.
- The approvals inbox
It keeps a record of what Justine declined to do.
Declining is a titled section of the inbox, not a deletion: an attorney's refusal is stored with the written reason beside Justine's original draft, and a step the agent itself would not take is recorded as considered-and-declined. The inbox also distinguishes 'nothing is waiting for you' from 'we could not ask' — two states that most queues render identically, and that mean opposite things.
- Outbound send
Approving is not sending.
Outbound send is a per-firm capability that is off unless a firm deliberately turns it on, and it is on nowhere in the production deployment today. Approving a draft records the firm's decision and sends nothing — transmission stays a step a person takes. An agent cannot reach your client because a model decided it should.
- Reasoning streams
An interrupted answer reports itself interrupted.
If a reasoning run is cut short — a deploy, a dropped connection, a stop — the partial work is kept and labelled as partial. It does not render as a finished answer. This is the quietest failure mode in agentic software and the most dangerous one in legal work, because a truncated analysis looks exactly like a complete analysis that found less.
- Reading scanned records
Where it cannot read, it says so.
Optical character recognition runs on Azure Document Intelligence under managed identity. Where that route is not available to a tenant, the read returns an explicit not-configured result and the document is left unread. Nothing is inferred from a page that was never successfully read — which is the only version of this feature that is safe to put a medical record through.
Restraint, not absence.
Tenancy is fail-closed and actually armed in production, not staged behind a flag: Postgres FORCE row-level security with a tenant_isolation policy on every table carrying tenant_id, an application role that is NOBYPASSRLS, and CASE_ACCESS_ENFORCED and ENTITLEMENTS_ENFORCED both on in production. A missing policy on this shape of database does not raise an error — it silently returns nothing, which is why the policy shape is asserted by a build-breaking check rather than trusted.
- Hash-chained audit trail
An audit trail that would show tampering.
Every row carries a sequence number and the HMAC-SHA256 hash of the row before it, written through one serialised writer per tenant so the chain cannot fork, and verified end to end nightly. Editing history means re-deriving every hash after the edit — which is the point of a chain rather than a log.
- Per-case access
Per-case access, granted rather than assumed.
Case access is a grant a person makes, not a role that happens to have read rights. Before an administrator turns matter visibility on, the screen shows how much of the book is actually covered by assignments — so nobody flips it and finds out afterwards.
Nine stages. One Justine. The full workers’ comp lifecycle.
This is the lifecycle JustineAI™ WC runs end to end — the same supervisor pattern that runs personal injury, calibrated for workers’ comp practice. Every stage is auditable, every output attorney-attested work product.
- Stage 01Intake & compensability
Justine runs conversational intake against the workers’-comp schema for the matter’s state — date of injury, employer and carrier, body parts, compensability, prior claims, and the statute clock. She flags cumulative-trauma exposure windows and the post-termination defense before the Application goes out. Applicant-side; California, Georgia, or Texas.
- Stage 02Application & filing
Justine drafts the California WCAB documents that open and move the case — the Application for Adjudication of Claim and the Declaration of Readiness to Proceed — from the matter record, on the firm’s own letterhead. These are drafts, not the official state PDF forms: Justine fills no fillable form, and any field the record does not establish is left as a bracketed placeholder rather than invented. The DWC-1 claim form is not drafted at all — Justine recognises it on ingest and dockets the Labor Code §5402(b) compensability clock from its filing date. Every draft surfaces to the attorney for attestation before it is filed; nothing is auto-served. Client-facing letters draft in English or Spanish.
- Stage 03Treatment & utilization review
Justine tracks each authorized treatment request through the utilization-review process — flagging UR denials, the Independent Medical Review (IMR) appeal deadline, and out-of-MPN care. When a request is denied, she surfaces the reviewer’s stated basis against the treating physician’s report so the IMR appeal starts from the record itself.
- Stage 04AME / PQME analysis
Justine reads the AME or PQME report — “Justine’s read” — extracting whole-person impairment by body part, work restrictions, causation, apportionment opinions, and the P&S date. She flags where the evaluator departs from the record. Where the treating provider runs ChironAI™ Occupational Medicine, those assessments can feed the matter.
- Stage 05MMI / P&S & impairment
Justine watches every active matter for Maximum Medical Improvement / Permanent & Stationary signals across treating providers, then reads the impairment picture into the rating engine. She distinguishes the strict-AMA whole-person reading from a rebutted alternative before the attorney certifies anything.
- Stage 06PD Value Engine
In California, the Value Engine builds the rating string — WPI → the 1.4 future-earning-capacity factor → occupational variant → age modifier — and models permanent disability as a PD percent, a dollar value, and the swing between a strict-AMA rating and a rebutted one (Almaraz-Guzman / Ogilvie), with apportionment carved out under Escobedo. Georgia rates on the AMA Guides 5th and Texas on the AMA Guides 4th, each to its own benefit schedule. Figures are projections for the attorney to verify against the current schedule.
- Stage 07Settlement
Justine models Compromise & Release against Stipulations with Request for Award, applies the ~15% judge-approved contingency fee and reasonable lien values, and reports net-to-client under each path. The attorney sees the trade-off — a clean C&R buyout versus Stips that leave future medical open — before deciding the number and the posture.
- Stage 08MSA flag & analysis
Justine flags when a Workers’ Compensation Medicare Set-Aside is implicated before a C&R is papered — Medicare-beneficiary status, the CMS review thresholds, open future medical — and frames the analysis the attorney needs. She does not compute the set-aside dollar amount; that stays with a WCMSA vendor and the attorney’s judgment.
- Stage 09Closeout & compliance
On resolution, Justine delivers the final file, exports the tamper-evident audit log for ethics review, and closes the matter. The apportionment patterns and carrier behavior the firm learned inform its next case — inside the firm’s own tenant, never a shared model.
One Justine. Sub-agents built for workers’ comp attorneys.
The WC edition runs the same architecture as PI: one Justine coordinating stage-specialized sub-agents across the matter, each working from the matter’s indexed, cited records. The sub-agents aren’t separately branded — they’re facets of the Digital Employee. These are the ones it runs on.
- Compensability sub-agent
AOE/COE analysis. Cumulative-trauma date-of-injury under the last-injurious-exposure rule. Going-and-coming and personal-comfort exceptions. Post-termination and statute-of-limitations defenses. Employer/carrier identification. Concurrent-employment average weekly wage. Prior-claim apportionment exposure. Applicant-side.
For example — A warehouse picker files for a cumulative lumbar injury after termination. You drop the personnel file, the panel QME report, and three years of pay records. The compensability sub-agent fixes the CT date-of-injury, flags the post-termination defense the carrier will assert, surfaces a prior 2019 lumbar claim that opens an apportionment argument, and computes the average weekly wage across two concurrent employers — each value traced to its source page for you to weigh.
- Medical sub-agent
Treating-provider chronology. Utilization-review and IMR appeal tracking. AME/PQME impairment and apportionment review — “Justine’s read” of the report. MMI / P&S signal detection. Causation linkage. ChironAI™ OM upstream assessment ingestion where the provider runs it.
For example — A 4,000-page file across an orthopedist, a pain-management group, and a panel QME. The medical sub-agent surfaces the UR denial of a lumbar fusion, the IMR appeal window closing in eleven days, and the contradiction between the PQME’s 8% whole-person impairment and the treating surgeon’s range-of-motion measurements supporting a higher rating — with the apportionment opinion isolated for the attorney’s review.
- Rating sub-agent
The PD Value Engine — rating California (2005 PDRS), Georgia (AMA Guides 5th), and Texas (AMA Guides 4th). California rating-string construction — WPI, the 1.4 FEC factor, occupational variant, age modifier. Strict-AMA versus rebutted (Almaraz-Guzman / Ogilvie). Apportionment carve-out under Escobedo. PD percent, dollar value, and the PD/$ swing. Life-pension threshold flags.
For example — A shoulder injury with a 12% whole-person impairment from the AME. The rating sub-agent builds the California rating string, models the permanent-disability award as a PD percent and dollar value, then carves out the share apportioned to a pre-existing rotator-cuff tear — showing the swing between the strict-AMA reading and an Ogilvie rebuttal, and flagging where the adjusted rating crosses the life-pension threshold. Projections the attorney verifies against the current schedule.
- Resolution sub-agent
C&R versus Stipulations modeling. The ~15% judge-approved contingency fee and reasonable lien values. Net-to-client under each path. Open-future-medical trade-off. WCMSA-required flag against CMS thresholds — flag and analysis, not a dollar computation.
For example — An accepted back-and-knee claim with disputed future medical. The resolution sub-agent models a Compromise & Release against Stips-with-open-medical, applies the ~15% fee and known lien values, and reports net-to-client under each. It flags that a WCMSA is implicated — the client is Medicare-eligible and future medical is open — and tells you to resolve the set-aside before papering the C&R, without inventing the set-aside figure.
The client hears from the firm — in their language.
Workers’-comp clients are anxious and often Spanish-speaking. Justine keeps them informed by text and email, drafts their letters in English or Spanish, and speaks and listens in either language — every message still attorney-reviewed before it goes out.
- Client texting with a privacy relay
Opt-in, STOP-compliant SMS keeps the client updated on their case, and attorney alerts route through a number-privacy relay so the client never sees a personal cell number. Transmitted over Azure Communication Services on a toll-free line.
- Per-case client email
Real client messages threaded to the matter, sent through Microsoft 365 / Outlook — the correspondence lives with the file, not in a separate inbox.
- Bilingual EN / ES client letters
Client-facing letters draft in English or Spanish. Filings stay in English; only the client-facing correspondence switches language — so the applicant reads their own case in the language they speak.
- English & Spanish voice
Voice dictation and read-aloud honor either language — flip to Spanish once and both dictate and listen follow (es-MX / en-US). Push-to-talk in, natural speech out.
Not legal advice · not a law firm · ABA-conduct aligned · the attorney decides. Client communications are attorney-reviewed work product.
The same depth of reasoning — on workers’ comp matters.
We proved the reasoning on personal injury. Here is what the same compositional fabric surfaces on workers’ comp matters — the findings a workers’ comp practice wants caught, each presented with its evidence for the attorney to weigh.
- Compensability analysis
Justine surfaces — On a cumulative-trauma matter, Justine fixes the date of injury under the last-injurious-exposure rule, surfaces the going-and-coming defense the carrier is poised to raise, and flags a prior accepted claim to the same body part that opens an apportionment argument — each tied to the record page that grounds it, for the attorney to weigh.
- Utilization-review appeal
Justine surfaces — Justine catches that a UR denial of a lumbar fusion rested on a misread of the requesting physician’s report, that the IMR appeal window closes in nine days, and that the report already contains the documentation the reviewer claimed was absent — the appeal half-drafted from the record itself.
- AME / PQME scrutiny
Justine surfaces — Across a panel QME report, Justine surfaces that the evaluator apportioned 40% to non-industrial degeneration without substantial medical evidence explaining the “how and why” under Escobedo, that the impairment number understates the documented range-of-motion loss, and that a prior consistent treating opinion contradicts the apportionment — assembling the cross-examination the attorney can run.
- PD Value Engine
Justine surfaces — On a shoulder injury rated at 12% whole-person, Justine builds the full California rating string — the 1.4 FEC factor, occupational variant, and age modifier applied — models the PD percent and dollar value, carves out the apportioned share, and shows the PD/$ swing between the strict-AMA rating and an Almaraz-Guzman or Ogilvie rebuttal, so the attorney sees what a rebuttal is worth before pursuing it.
- Settlement & net-to-client
Justine surfaces — Justine models C&R against Stips, applies the ~15% judge-approved fee and the reasonable lien values, and reports net-to-client under each path — surfacing that leaving future medical open on Stips exposes the client to a WCMSA problem a clean C&R buyout avoids, so the number is chosen with its consequences visible.
- Citation discipline
Justine surfaces — Justine grounds every statute and decision it cites against a verifiable authority — reasoned from real law, never invented — and self-labels its rating and settlement outputs as projections to verify against the current schedule and CMS thresholds. The attorney decides.
The AI reasons; the attorney decides.
What shipped in WC, and when — 29 entries covering new capability and corrections an attorney would want to know about. Security, access-control and confidential-data handling changes are deliberately not itemised publicly, and the page says so.
Run your WC practice on Justine.
WC is in market for applicant-side workers’ comp in California, Georgia, and Texas. Request a 14-day trial, or talk to us about your firm. Every rating, apportionment, and settlement figure is a projection for the attorney to verify against the current schedule and CMS thresholds.
14-day free trial · No credit card required · Self-serve signup. Not legal advice · not a law firm · ABA-conduct aligned · the attorney decides.