Do's and Don'ts of Requesting a Rush Medical Chronology Before an MSC

The rush request that actually works starts a few days before the deadline, on a complete file, with a narrow scope and a quick feasibility check before you promise anyone a date. A mandatory settlement conference (MSC) doesn’t move because your medical chronology ran late, so the point of a rush request isn’t speed for its own sake. It’s a complete, usable timeline in your hands with enough room to read it before you sit down at the table.

A medical chronology is the date-ordered record of a claimant’s treatment, built from the raw files, with each entry referenced back to its source page. Getting one fast is very doable. Getting one back fast, complete, and usable takes a few simple steps on your end.

Here’s what helps, and what quietly costs you the time you were trying to save.

What to Do

1. Confirm feasibility before you commit to a date

Give the reviewer three things before you promise anyone a date:

• The page volume
• The number of providers
• Your hard deadline

A 600-page file from two providers and an 8,000-page file spanning a decade are different jobs. Only one of them fits into a single day. Ask early, not the afternoon before the deadline.

2. Send a complete file, and flag what’s still outstanding

• A complete record set makes for a clean, fast rush job
• A file missing two providers sets up the worst kind of surprise, the kind that surfaces while you’re on the record
• If records are still in transit, say so up front so the gap gets tracked instead of discovered late

3. Narrow the scope to what the MSC turns on

For a settlement conference, you rarely need every entry weighted the same. Tell the reviewer what matters on this file:

• Prior conditions
• Apportionment-related evidence
• Treatment sequence since the work injury
• Current work status

A tightly scoped rush chronology comes back faster and reads sharper than a “summarize everything” request made under a clock.

4. Build in a buffer

Don’t set the MSC date as your delivery date. Leave room to actually read the chronology before you walk in.

• Ask for delivery the day before the MSC, not the morning of
• A few hours of margin is the difference between reviewing the chronology and reading it for the first time in the parking lot
• Treat the conference date as your deadline to use the work, not receive it

What to Avoid

1. Don’t assume rush always means same-day

Turnaround depends on the file size. Standard chronologies take three to five business days, and a true 24-hour turnaround needs low volume and clean records. Cramming 8,000 messy pages into one afternoon doesn’t make it faster, it just makes it thinner.

2. Don’t skip the scope conversation to save time

Sending the file and saying “rush, please” feels quick, but it isn’t. No scope means you’ll likely have to send it back, and fixing it under deadline costs more time than a five-minute scope call up front.

3. Don’t treat the extra fee as the real cost

Rush work usually costs extra, and that’s the price you see. The real cost is a chronology that misses the prior injury or a treatment gap, exactly what your QME and defense need, so speed without completeness isn’t a win.

4. Don’t let the rush quietly cut the review step

A chronology is reliable because more than one person checks it before it reaches you. Ask if that check still happens on a rush job. Skipping it doesn’t save you time, it just moves the risk onto you on the day of the conference.

A Real Case: When Fast Wasn’t Actually Fast

We worked with a Texas workers’ compensation attorney who’d been burned by this exact pattern before. Their prior vendor’s summaries came back long, partly copied straight from the source records, and missing key history. Every “finished” report still had to be manually re-checked before it could be trusted.

Things changed once the work moved to professional medical chronology services, with structured summaries built around documented diagnoses, prior history, and the treatment chronology. The firm reported cutting case-preparation time by roughly 75%.

The lesson for a rush request is simple: speed only counts when the output is complete and built the way you actually read a file. A fast chronology you can’t trust isn’t faster at all. It just moves the late-night reading back to your desk.

One line worth keeping in mind through all of this: a medical chronology organizes and flags the prior-injury and apportionment-related evidence in the record. It doesn’t decide apportionment or causation. Those calls stay with your evaluator, and with you.

That’s exactly why the chronology has to be complete before the MSC, not a week after it.

What a Well-Planned Rush Request Looks Like

Picture an MSC set three weeks out. Here’s how the timeline plays out when the request is made the right way:

• Day 1 (MSC gets scheduled): You send the reviewer the page count, provider count, and hard date. They confirm a 24-hour turnaround is realistic, since it’s a clean 900-page file from three providers.
• Day 2: The complete file goes out, with a note that one provider’s supplemental records are still in transit and will follow in a few days.
• Day 2 (same day): You flag exactly what the chronology needs to focus on: the prior back injury, the treatment gap, and current work status.
• Day 18 (three days before the MSC): The chronology arrives, quality-control review intact, a full day ahead of your buffer date.
• Days 19 to 20: You read it, cross-check it against your notes, and walk into the MSC with a timeline you trust, not one you’re seeing for the first time.

None of this is complicated. It just has to happen in this order, and it has to start the moment the MSC lands on your calendar, not the week before it.

Speed matters. Predictability matters more. The rush request that protects your MSC is the one you make early, on a complete file, with a scope tight enough to come back sharp and on time.