Home›Solutions›Settlement Compliance›Rated Age Submission Packets
RATED AGE SUBMISSION PACKETS

Three thousand pages in. Twenty pages out.

Rated age submission packets compress a full personal injury file — often five hundred to three thousand pages — into the twenty pages of current, relevant records an annuity carrier underwrites from. Submit one packet and four to eight carriers return independent rated ages within twenty-four to seventy-two hours.

Click any row → the source page it cites
Packet build · Case #IME-4812 cited
Adams, Timothy · rated-age submission file
342 pp / 2 packets received logged
11 duplicate pages removed free
p.140 — wrong patient quarantined
Pages 342 Documents 27 Cited 100%

Six graders. One packet. Seventy-two hours.

We do not build for a case type until we can name the standard that defines a correct output and the person who grades the file against it. In rated-age underwriting both exist, and the grading comes back in writing, from several desks at once.

The rulebook and the referee
The rulebook
  • Each carrier's substandard annuity manual: a debit table run over the 2012 IAM or a2000 mortality table with an improvement scale
  • IRC §104(a)(2), §130 and §5891, which govern the tax treatment of the periodic payments and the qualified assignment
  • The 50-state Structured Settlement Protection Acts
  • Broker guidance is explicit that the submission packet must stay under 20 pages
The referee
  • Submit one packet, get 4 to 8 independent rated ages back within 24 to 72 hours
  • The spread between carriers is a direct quality score on the packet
  • The best rated age is worth real money: a 20-year rate-up cuts annuity premium by 25 to 40 percent
Roughly fifteen hours of broker and case-manager time per rated-age request, spent reading and re-reading the same production Flat 10¢/page here, duplicates free
Production inventory · Case #IME-4812 cited 100%
Typical injury file500 to 3,000 pagesrange
This production342 pp / 2 packets · 27 documentslogged
Overlap between packets11 duplicate pages removedfree
Co-mingled pagep.140 — wrong patientquarantined
Packet budgetUnder 20 pages, carrier-readytarget
Every retained page traced to its production
What the file actually looks like

Nobody sends a clean twenty pages.

A rated-age request arrives on top of a personal injury file that runs 500 to 3,000 pages, usually in several productions from several custodians. The same discharge summary appears in three of them. Therapy notes are handwritten. Older records are scanned crooked, faxed twice, and re-scanned. Nothing about that shape is convenient for a twenty-page budget.

So the work is not summarising. It is deciding, page by page, what is current and relevant to mortality, and proving where each retained line came from.

~33,500
structured settlement annuities written in 2024, on $9.48B of premium and up about 10% year over year (NSSTA)
50–80k
carrier reviews a year: roughly 10,000 to 12,000 rated-age requests, each fanned out to about six carriers
What we'd build with you

A packet build, scoped against one real file.

We do not sell a rated-age product off a slide. You send one production you have already worked, we read it and hand back what the platform can see, and then we decide together whether a packet build for your desk is worth constructing.

The boundary stays fixed throughout. We organise, compress and cite the medical record. The rated age comes from each carrier's medical underwriter, and the decision about which offer to take belongs to the broker and the claimant.

The co-build, in four steps no obligation
01

You send one real file

A production you have already built a packet from, in whatever shape it arrived. In the demo case that is 342 pages across 2 packets, with a wrong-patient page quarantined before the read starts.

02

We return the read

Duplicates collapsed, handwriting transcribed, the conditions and their progression laid out on one timeline, and every line clickable back to its source page. You compare it against the packet you built by hand.

03

We scope the build

Your packet template, your inclusion rules, your page budget, your carrier list. If the case type is not buildable to that standard we say so instead of shipping something that reads badly at six desks.

04

You run it

Your team drafts from the cited read, edits what it wants, and submits under its own name. Nothing leaves your desk that a person has not approved.

Every access logged · file deleted 30 days after delivery
Why Medrecords AI

The rules the platform never breaks.

Medrecords AI EVERY LINE CITED
CASE #IME-4812 · ADAMS, T.342 pp
2/14 — ER visit, right knee p.4
4/18 — arthroscopic surgery p.61
p.140 — wrong patient quarantined
Medrecords AI
Read every page · cite every line

HIPAA, under a signed BAA

Every file is handled under our Business Associate Agreement, from the first byte.

Never trains a model

Your records are never used to train any AI model — ours or anyone else's.

Every line cited

If we can't cite it, we don't say it. Every sentence links to its source page.

Deleted after delivery

Files are deleted 30 days after delivery, with a full audit log of every access.

Powered by the platform

Four capabilities behind every submission packet.

The rated-age packet is one deliverable of the same platform that reads, sorts, and cites the whole record.

Medical Summary Reports

The medical summary that goes to the carrier, in your template and on your letterhead, with the page budget enforced rather than hoped for.

IN ACTION · 342 pp / 2 packets → one carrier-ready summary

Medical Chronology

Every treating encounter on one timeline, in date order, synced to the source page — so an underwriter can see the course of care without reading the file.

IN ACTION · 27 documents → one continuous timeline

Condition Progression Tracking

Whether each documented condition is improving, stable, or worsening across the record, with the visits that show it cited line by line.

IN ACTION · 7 visits improving since 4/02, each cited

Document Sorting & Packet Builder

Several productions sorted into one clean set, duplicates collapsed and co-mingled pages pulled out, then assembled into the packet you actually send.

IN ACTION · 11 duplicates removed · p.140 quarantined
FAQ

Rated age submission packets, answered.

The broker assembles a submission packet out of the claimant's medical records and sends it to several annuity carriers at once. Each carrier's underwriting desk reads that packet against its own substandard annuity manual and returns an independent rated age, typically four to eight of them inside 24 to 72 hours. We build and cite the packet; the rated age itself is always the carrier's call.

The current, relevant ones: recent treating and specialist notes, diagnostics, medication lists, and the records that establish the severity and progression of the impairing conditions. Broker guidance is explicit that the packet should stay under 20 pages, so a 500 to 3,000 page personal injury file has to be compressed rather than forwarded. Every line we carry forward is cited to the page it came from.

No. We organize, compress, and cite the medical record. Rated ages come from each carrier's medical underwriter applying that carrier's own debit table over the 2012 IAM or a2000 mortality table with an improvement scale. We never assign a rated age, rate an impairment, price an annuity, or predict what a carrier will send back.

Because the same packet is read by roughly six underwriting desks at once, under a 24 to 72 hour clock, and length works against a clean read. A page budget turns the job into a compression problem: keep what is current and relevant to mortality, drop what is not, and make every retained page traceable back to the production it came from.

No. Medrecords AI does not retrieve records from providers or facilities. You bring the production you already have and the read starts in minutes from upload. Retrieval vendors take days; you can keep yours and still cut the packet build down to minutes.

Send one file. We'll tell you what we can read.

No obligation. If the case type is buildable we'll scope it; if it isn't, we'll say so.