Concurrent Review Clock Tracker for IOP, PHP, and Residential
A tracker for the review dates that decide whether an episode continues, with the owner, evidence, and escalation fields that keep a continued stay from lapsing.
On this page: Direct answer
Direct answer
Concurrent review tracker: what operators need to know
A tracker for the review dates that decide whether an episode continues, with the owner, evidence, and escalation fields that keep a continued stay from lapsing. The review date, not the authorization end date, is the operative deadline. Working to the end date is already late.
Most programs get the initial authorization right. It has a clear owner, a known submission path, and a deadline everyone feels. Continued stay is where episodes are lost, because the work is recurring, the clock is set by the payer rather than by you, and the person who knows the clinical picture is usually not the person watching the calendar. An authorization that lapses on day eleven of a fourteen-day stay produces unbillable days that no appeal recovers cleanly.
The fix is unglamorous: treat each review as a dated obligation with one owner, one evidence set, and one escalation path, and keep them all in one view. The tracker below is that view. It is deliberately small enough to maintain during a busy week, because a tracker nobody updates is worse than none.
Key takeaways
The short version
- The review date, not the authorization end date, is the operative deadline. Working to the end date is already late.
- Give every review one owner and one dated next action. Shared ownership of a recurring deadline is how lapses happen.
- Collect the evidence the payer will ask for before the review, not during the call.
- Record whether a peer-to-peer was offered and held; its absence is an argument later if the stay is downgraded.
- Count unbillable days caused by lapses separately from days lost to downgrades. They have different fixes.
- Standard decisions for the impacted Medicare and Medicaid programs are due within 7 calendar days and expedited within 72 hours, so a late decision is a documentable issue.
Take the template with you
Free to copy · no email required
Concurrent review clock tracker
One row per episode, carrying the next submission date forward, with decision deadline, appeal deadline, peer-to-peer state, and a lapse cause field.
episode_ref,payer,plan_type,level_of_care,admission_date,review_cadence_days,cadence_source,current_auth_start,current_auth_end,approved_units_or_days,units_used_to_date,next_submission_due,reminder_date,submitted_date,receipt_reference,decision_deadline,decision_received_date,days_to_decision,outcome,approved_level,new_auth_end,peer_to_peer_offered,peer_to_peer_held,appeal_deadline,unbillable_days,lapse_cause,owner,next_action,next_action_due,notes_dated EP-0001,[payer],Medicaid MC,Residential 3.5,2026-10-01,7,stated in policy / observed,2026-10-01,2026-10-15,14,9,2026-10-13,2026-10-11,,,2026-10-20,,,pending,,,no,no,,0,,[name],assemble interval evidence,2026-10-12,2026-10-08 CIWA trend documented
Saves as concurrent-review-clock-tracker.csv
Interval evidence checklist
What to have dated and ready before a continued-stay review, so the call is a conversation rather than a chart hunt.
1. The clocks you are actually running
A continued stay involves at least four clocks, and conflating them is the root of most lapses. There is the payer's review cadence, which determines when you must submit. There is the authorization end date, which determines when billing stops. There is the payer's decision deadline, which determines when you can escalate a silence. And there is the appeal deadline, which starts if the answer is no.
Only the first is under your control, and it is the one most often tracked least precisely. A cadence recorded as 'weekly' is not actionable; a cadence recorded as 'submit by day 5 of each 7-day period, before 3pm local' is.
| Clock | Set by | What it governs | Where it is usually lost |
|---|---|---|---|
| Review cadence | Payer, by level of care | When you must submit the continued-stay request | Recorded vaguely, so submission drifts later each cycle |
| Authorization end date | The approval | The last billable day | Treated as the deadline to act on |
| Decision deadline | Regulation or contract | When silence becomes escalatable | Not tracked at all, so silence is absorbed |
| Appeal deadline | Plan type | When a denial becomes final | Starts quietly on the notice date |
| Peer-to-peer window | Payer policy | When a reviewer can still be reached pre-decision | Missed because the offer arrives by fax or portal message |
| Discharge date | Clinical | When the episode actually ends | Diverges from the authorization, creating unbillable days |
2. Collect the evidence before the review, not during it
A continued-stay review is a short conversation about whether the patient still needs this level of care. The reviewer will ask about change over the interval: what has improved, what has not, what has been tried, and what would happen at a lower level. Those answers exist in the record, but assembling them during the call is why reviews run long and why avoidable downgrades happen.
Build a small, standing evidence set per level of care, dated and updated each interval. The point is not volume. A reviewer who asks about withdrawal risk needs the serial scores, not the whole chart.
- Interval summary: what changed since the last review, with dates, not a restatement of admission acuity.
- Objective measures trended across the interval — withdrawal scores, symptom measures, vitals where relevant.
- Current risk assessment with its date, and any change in intent or plan.
- Attendance and participation data, which answers readiness and engagement questions directly.
- Medication administration and adherence facts, especially where the lower level cannot administer.
- Recovery environment facts: who is home, supervision available by hour, substances present, housing stability.
- The specific services the treatment plan orders, and which of them the next level down cannot deliver.
3. Escalate silence on a schedule
Payer silence is treated as waiting when it should be treated as a deadline breach. For the programs CMS-0057-F reaches, standard decisions are due within 7 calendar days and expedited within 72 hours, with extensions of up to 14 calendar days where the applicable rule allows. A decision outside those limits is a fact worth recording and raising, and it is also the basis for asking for expedited handling the next time.
Build the escalation ladder once and follow it without deliberation, because deliberation during a busy week means it does not happen.
| Elapsed | Action | Record |
|---|---|---|
| Submission + 1 business day | Confirm receipt through the portal or by call | Receipt reference and time |
| Submission + 3 business days | Request status and ask whether anything further is needed | Name of person spoken to, what was asked for |
| Approaching the decision deadline | Request expedited handling where clinically justified and the plan allows it | Basis for expedition, who approved it |
| Decision deadline passed | Raise the missed timeframe in writing, citing the applicable rule | Date, rule cited, response |
| Any downgrade or denial | Request peer-to-peer and calendar the appeal deadline the same day | Both dates, in the tracker |
| Authorization end approaching with no decision | Escalate clinically and commercially; decide on continued treatment knowingly | Who decided, on what basis |
4. Running the tracker without it rotting
Trackers fail for predictable reasons: too many fields, no single owner, and no daily moment where someone looks at it. Keep the field list close to the one below, assign one owner per episode rather than per task, and give the tracker a fixed daily review slot tied to the morning clinical huddle that already happens.
- 01
One row per episode, not per review
Carry the next review date forward on the same row and keep a dated history in a notes column. One row per review multiplies maintenance and hides the episode.
- 02
One owner, named, per episode
A role is not an owner. If the owner is away, the handover is an explicit edit to the field, not an assumption.
- 03
Sort by next action due, every morning
The only view that matters is what is due today and tomorrow. Everything else is reference.
- 04
Two-day warning on every submission date
The reminder is on the submission date minus two, not on the authorization end date.
- 05
Close the loop on every decision
Record outcome, date, approved level, approved units, and new end date, then set the next submission date immediately. The gap between a decision and the next scheduled review is where lapses live.
- 06
Review the lapse log weekly
Every unbillable day should have a cause recorded. Within a month the pattern tells you whether your problem is submission timing, evidence quality, or payer responsiveness.
5. What to measure
- Unbillable days from lapsed authorizations, counted separately from days lost to downgrades.
- Share of reviews submitted on or before the submission date — the leading indicator for everything else.
- Median days from submission to decision, by payer, which tells you where to budget escalation effort.
- Downgrade rate by level of care and by payer, so you know which arguments to prepare at admission.
- Peer-to-peer offer and completion rate, since a missed offer is both a lost chance and a later argument.
- Decisions received outside the applicable timeframe, which is the number to bring to a contracting conversation.
Common questions
Answers before you build.
How is this different from a prior authorization tracker?+
An initial-authorization tracker follows a request to a decision and then stops. A concurrent review tracker is cyclical: each decision immediately creates the next submission date, and the risk accumulates across cycles. The field that makes it work is the next submission date, carried forward on the same row.
What cadence should we record if the payer will not state one?+
Record the cadence the payer has actually applied over the last several episodes, mark it as observed rather than stated, and ask for the written policy. An observed cadence you can plan against beats a policy you cannot get.
Should the clinician or the utilization-review coordinator own the row?+
The coordinator owns the clock and the submission; the clinician owns the clinical content. One named coordinator per episode avoids the common failure where everyone assumes the review was submitted by someone else.
Can we bill for days after an authorization lapses?+
That depends on your contract, the plan's rules, and state law, and it is a question for contracting and compliance rather than a tracker. Decide the policy in advance so the clinical team is not making a financial decision at the bedside.
What do we do when a peer-to-peer offer arrives too late to take?+
Record the offer date, the window it allowed, and the reason it could not be taken. If a downgrade follows, the timing of the offer becomes a procedural point in the appeal, and a pattern of unusable offers is a contracting conversation.
Practical closeout
Use this operator checklist.
- The review date, not the authorization end date, is the operative deadline. Working to the end date is already late.
- Give every review one owner and one dated next action. Shared ownership of a recurring deadline is how lapses happen.
- Collect the evidence the payer will ask for before the review, not during the call.
- Record whether a peer-to-peer was offered and held; its absence is an argument later if the stay is downgraded.
- Count unbillable days caused by lapses separately from days lost to downgrades. They have different fixes.
- Standard decisions for the impacted Medicare and Medicaid programs are due within 7 calendar days and expedited within 72 hours, so a late decision is a documentable issue.
Continue through the cluster
Verified customer case studies are added only with customer permission and supporting evidence; none is implied by these operational examples.
Codes on this topic
Look up the code on the remittance
Sources & methodology
Trace the operational claims.
Marsa Health Editorial reviewed the primary and research sources below on October 18, 2026. We translate them into workflow controls, distinguish proposals from final rules, and flag where plan, program, state, contract, or clinical requirements vary.
- 0142 CFR 422.568: Standard organization determination timeframes Electronic Code of Federal RegulationsSets the 7-calendar-day standard decision deadline for Medicare Advantage items and services subject to prior authorization, beginning January 1, 2026.Accessed or rechecked October 18, 2026
- 0242 CFR 422.572: Expedited organization determinations Electronic Code of Federal RegulationsKeeps the 72-hour expedited decision deadline and sets the conditions under which an enrollee or physician can demand one.Accessed or rechecked October 18, 2026
- 0342 CFR 438.210: Coverage and authorization of services Electronic Code of Federal RegulationsParagraph (d) sets 7-calendar-day standard and 72-hour expedited decision limits for rating periods beginning on or after January 1, 2026; (c) governs notice of adverse benefit determination.Accessed or rechecked October 18, 2026
- 04ASAM Level of Care Assessment Guide American Society of Addiction MedicineThe printable dimensional assessment and level-of-care decision structure, useful for mapping a downgrade argument back to the criteria a payer cites.Accessed or rechecked October 18, 2026
- 05CMS Interoperability and Prior Authorization Final Rule CMS-0057-F Centers for Medicare & Medicaid ServicesThe fact sheet listing which payers are impacted, the four required APIs, the denial-reason duty, and the compliance dates.Accessed or rechecked October 18, 2026
- 06Electronic Prior Authorization Centers for Medicare & Medicaid ServicesCurrent CMS provider-readiness guidance for 2027 electronic prior authorization, EHR questions, FHIR testing, and workflow preparation.Accessed or rechecked October 18, 2026
- 07Minimum Necessary Requirement U.S. Department of Health and Human ServicesHIPAA guidance on limiting uses, disclosures, and requests for protected health information when the standard applies.Accessed or rechecked October 18, 2026
Organizational author. Editorial review covers source accuracy, search intent, workflow boundaries, and human-oversight requirements. This material is educational and does not provide clinical, legal, coding, or coverage advice.
No named clinical or legal expert reviewer is attributed to this version. Marsa Health does not invent reviewer credentials.
Read our editorial methodRevision history
What changed and when
October 18, 2026
Initial publication, source review, and operational editing.