Pend Management Under a 72-Hour Clock: Playbook for Expedited Queues

The most dangerous belief on a UM floor in 2026 is that pending a request buys time. On a standard request it sometimes did, culturally if not legally: the case sat in "waiting on records," someone chased documentation, and the clock felt suspended because nobody was watching it. On a 72-hour expedited request, that belief is a compliance incident with a short fuse. The pend does not stop the clock. Nothing stops the clock except a decision — or a regulatory extension with conditions your team probably cannot recite.

This playbook covers what a pend actually is in transaction terms, what the federal clocks do while a case sits pended, how extensions really work for Medicare Advantage versus Medicaid managed care, and how to design an expedited queue where pends are resolved in hours instead of quietly aging into breaches.

What a pend is, mechanically

On the 278 rail, a pend is HCR01 = A4: the utilization management organization has received a processable request but has not decided. The 005010X217 TR3 ties the pend to its cause — when the outcome is pending additional medical information and the response requests it (via a PWK segment or LOINC-coded HI segment), the HCR segment must carry A4 with a decision reason code saying more information is required. A well-formed pend, in other words, names what it is waiting for. An A4 with no articulated ask is a queue entry with no exit condition, and your intake tooling should flag it the moment it arrives.

The FHIR rail formalizes the same state more aggressively: under the Da Vinci PAS guide, a pended response obligates the payer to support subscriptions so the submitter is notified when the determination changes, and initially-pended authorizations must remain queryable for months afterward. Either way, the pend is an open promise with an audience — the provider's system is now instrumented to watch you.

What the clock does while you wait: nothing different

CMS-0057-F set the expedited decision floor at 72 hours (and standard at 7 calendar days) for impacted payers beginning January 2026 — QHP issuers on the FFEs are outside the timeframe provision, and drugs are outside the rule's prior authorization provisions entirely. Those are calendar clocks. They run through the weekend, through the holiday, and through every hour a case sits pended awaiting clinical documentation.

So the arithmetic of an expedited pend is brutal. A request arrives Friday at 4 PM and intake pends it for records an hour later; the office you are waiting on reopens Monday at 8 AM, and the clock expires Monday at 4 PM — eight hours to receive, review, and decide, assuming the records show up the moment the office opens. Pend-plus-wait is not a strategy on this queue. The only honest strategies are: decide on what you have, get the information fast enough to decide inside the window, or invoke an extension that actually satisfies the regulation.

Extensions: MA and Medicaid are cousins, not twins

Both programs allow the 72-hour expedited timeframe to be extended by up to 14 calendar days — but the conditions differ, and an extension taken under the wrong program's logic is a breach with paperwork.

Medicare Advantage. Under 42 CFR 422.572(b), an MA organization may extend the 72-hour deadline for a service or item request by up to 14 calendar days only if the enrollee requests the extension; or the extension is justified, and in the enrollee's interest, by the need for additional medical evidence from a noncontract provider that may change a decision to deny; or extraordinary, exigent, or other nonroutine circumstances justify it and it serves the enrollee's interest. Extending must come with written notice to the enrollee explaining the delay and their right to file an expedited grievance about the extension itself. Two sharp edges: routine slowness from your own contracted network does not fit the noncontract-evidence prong, and expedited Part B drug determinations cannot be extended at all.

Medicaid managed care. Under 42 CFR 438.210(d)(2), an MCO, PIHP, or PAHP may extend the expedited 72-hour period by up to 14 calendar days if the enrollee requests it, or if the plan justifies — to the state agency upon request — a need for additional information and how the extension is in the enrollee's interest. The justification standard reads more generally than MA's, but it points at a different auditor: your state Medicaid agency, and the contract sitting on top of the federal floor may be tighter than the regulation. The federal text is a ceiling on extensions and a floor on speed; your state contract can narrow both.

The operational takeaway: the extension decision is program-specific, justification-specific, and notice-generating. It belongs to a small set of trained people with a template — never to an intake reviewer under deadline pressure discovering the extension button at hour 70. And every extension is a data point in a story regulators can read: extension rates on expedited queues are conspicuous precisely because the queue exists for members whose health cannot wait 14 more days.

Queue design: the pend is the emergency

• Sort by time-to-breach, and let pends inherit the request's clock. A pended expedited case is not "parked" — it is the most urgent thing you own, because its remaining runway is shrinking while the ball is in someone else's court. The SLA dashboard spec treats pend age against remaining clock as the core pend metric; on a 72-hour queue that ratio turns red in hours.
• Make the information request specific, multi-channel, and timestamped. The A4's documentation ask should name the exact artifacts (the TR3's LOINC-coded request machinery exists for this), go out on every channel the provider actually watches, and log send time — both because follow-up automation needs it and because, if you later invoke an extension, the record showing you asked early and specifically is the difference between a justification and an excuse.
• Schedule the re-ask before the first ask goes out. On a 72-hour clock, the escalation cadence is measured in hours: re-request at +12, phone outreach at +24, physician-reviewer decision point at +48 on whatever is in hand. Every step pre-assigned, none requiring a supervisor to notice.
• Decide the hour-60 policy in a conference room, not a queue. When the information has not arrived, the options are decide on available evidence or extend where conditions are genuinely met. Which path applies to which scenario is a medical-policy and compliance decision that should be written down per program — the worst version is fifty reviewers improvising it case by case.
• Attack pend causes upstream. Pull the top pend reasons on the expedited queue monthly and treat each as an intake defect: if the same three document types cause most pends, front-load them into submission requirements, portal prompts, and — as the 2027 FHIR stack arrives — DTR questionnaires that collect them at order time. A pend prevented outranks any pend managed. The same discipline applies to requests arriving by fax and legacy channels, where the documentation gap is usually widest.
• Watch the expedited-to-standard downgrade path. Reclassifying a pended expedited request to standard because the clock got uncomfortable is the move most likely to draw auditor attention. Downgrades need clinical rationale, a named reviewer, and a trend line someone owns.

The metric that tells you if it's working

One ratio summarizes expedited pend health: of pends opened on the 72-hour queue, what share resolve to a determination inside the original window without an extension? If that number is high and extensions are rare, justified, and documented, the queue is doing its job. If pends routinely resolve only after extension — or worse, after breach — the queue design is telling you the intake process upstream is starving reviewers of information, and no amount of heroic hour-70 effort will fix that. Under CMS-0057-F you also publish prior authorization metrics annually, so timeliness on this queue is not a private number anymore. Build the queue as if the report card is public. It is.

Verify extension conditions against the current eCFR text of 42 CFR 422.572 and 42 CFR 438.210(d), your state Medicaid contracts, and the CMS-0057-F rule text at 89 FR 8758; state and contractual overlays are frequently stricter than the federal floor.