The build

Templates into rules

Every rule is deterministic, written in plain language, and confirmed by the person who owns it — no black box. A sample of the 23:

• R1
  The carrier and claim address are never retypedthe letter of representation to the at-fault carrier uses template v4; both fields come from the intake recordconfirmed: intake paralegal
• R2
  The PIP application drafts only when the policy carries PIPotherwise the pack flags it as a named blockerconfirmed: assigned attorney
• R3
  Referrals come only from the maintained provider listcurrently accepting liens, reviewed quarterlynew rule — born from audit finding K1
• R4
  The crash report is ordered on signaturefrom the state portal, automatically; the file shows “ordered · watching” until it landsnew rule — born from audit finding K2
• R5
  Deadlines are computed, never rememberedPIP window and statute date from the crash date, written to the calendar with their arithmetic shownconfirmed: case manager

System integration — zero migration

Three connection methods across the six mapped systems. The firm's tools stayed exactly where they were.

Training mode — three weeks beside the team

The agent drafted every document for every new case; the team kept working by hand. Each week, the drafts were compared against what the team actually sent.

• Week 125 documents compared · 14% needed correction — template-version drift and two carrier-address rules fixed.
• Week 231 documents compared · 4.2% corrections — the letter-of-protection wording aligned with the attorney's edits.
• Week 328 documents compared · 0 corrections on 10 consecutive cases — build 1 accepted, per the roadmap's written criterion.

The approval configuration

Who releases what. Below the line, nothing moves without a person.