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 — nine sections on one file: overview, medical and QME, value, deadlines, settlement, liens, documents, client, 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
- Benefit reconciliation against the carrier’s indemnity ledger, the average-weekly-wage derivation across concurrent employments, Benson separate awards, §4553 serious-and-willful exposure, the retention and legal-hold workflow, and the intake compensability screen — all built and under test, none of them reachable by an attorney yet, and therefore not counted as capabilities 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 (SAML / Microsoft Entra ID) — available under enterprise terms, not a shipped self-serve feature
- 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.
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 · Assisted onboarding. Not legal advice · not a law firm · ABA-conduct aligned · the attorney decides.