What the drafter reads — The repair orders plus the RISC (and registration when provided). The client's legal name comes from the RISC buyer and co-buyer exactly as printed; the demand amount is the RISC total sale price per the settlement team's SOP; repair dates come from inside each RO, never the file name; RO VINs are cross-checked against the RISC VIN, and mismatches are excluded and flagged.

Repair narrative (house style) — One paragraph per repair date, chronological. Each paragraph opens with the defect, then the technician's findings, the repair performed, mileage, and days in service. Formal clinical tone, no bullets, never "the customer reported." Only lemon-relevant defects are included: recurring, safety-related, drivability-impacting, or substantial. Routine maintenance is excluded unless tied to a defect, and a reported concern with no work performed that never recurs is left out.

Numbers — Days out of service are computed from each RO's drop-off and completion dates, never estimated. The letter closes the facts section with cumulative days out and the count of repair attempts.

Letter mechanics — Fixed firm template: representation and revocation, facts and liability, the damages table at the RISC total, a settle-for figure (defaults to the total, editable), a 29-day response window, and the Magnuson-Moss Warranty Act bolded throughout. Citations name the MMWA, the state's lemon/warranty statute, and only case law the drafter is confident is real — when unsure it cites fewer and says so, because a wrong citation is worse than a missing one.

One continuous case file — Every demand connects to the CPLG Settlement Maximizer. After you download a letter, a "continue this case in the Settlement Maximizer" link appears right here, and every row in the admin portal has a "Maximizer →" link. Opening it pre-fills the Maximizer with this case's client, RISC total, demand amount, state, purchase date, and manufacturer — so when the manufacturer responds, the negotiation starts from the same file the demand came from, and the outcome you log there teaches both tools.

Guardrails — Anything the drafter cannot verify lands in the "could not find" box above the draft, including VIN conflicts and a missing RISC. Manufacturer addresses stay flagged until an admin verifies them against a served demand. Nothing is ever sent automatically: a demand writer reviews every field, and an attorney signs off before service. Every draft is logged, and logged outcomes feed back into how the firm calibrates demands over time.