Recertification: Catch the 90-Day Window Before It Closes

Recertification lapses are almost never discovered by the treating therapist. They are discovered by the biller, weeks or months later, when a claim comes back unpaid and someone works backward to the ugly answer: the certification period ended in March, treatment continued into May, and nobody noticed. The visits happened, the notes are good, the care was appropriate — and every session after the end date is now a problem that has to be argued rather than a claim that simply pays. What failed was not clinical judgment or documentation quality. What failed was a date that nobody was tracking.

This article is about running recertification as a system: what the certification actually authorizes, the two dates that govern every episode, and a tracking workflow that surfaces each expiring plan while there is still time to chase a signature. It goes deep on one document on purpose — for the full map of how certification fits alongside daily notes, progress reports, and discharge notes, see our companion article on the Medicare document clock.

Under Medicare Part B, outpatient therapy is payable only when it is furnished under a plan of care that a physician or non-physician practitioner (NPP) has certified. The plan itself is usually established by the treating therapist, and the regulation is specific about what it must prescribe: the diagnosis, the anticipated goals, and the type, amount, frequency, and duration of the therapy services. Certification is the physician or NPP signing and dating that plan — attesting that the patient needs the care and is under a plan they approve.

Two details in the rules make the logistics easier than many practices assume. First, the signer does not have to be a physician: a nurse practitioner, clinical nurse specialist, or physician assistant who has knowledge of the case can certify and recertify, which matters when the supervising physician is the bottleneck. Second, certification is not an order — for Medicare Part B therapy, the certified plan itself carries the authorization, so the practical work is not getting permission to treat but getting a signature returned on a schedule. That distinction is exactly why this is a tracking problem: nothing about the patient’s care pauses while the signature is outstanding, so nothing forces anyone to notice the date.

Every certified episode runs on two dates, and both are computable the day treatment starts. The first is the initial certification deadline: CMS expects the physician or NPP to certify the plan as soon as possible after it is established, and within 30 calendar days of the initial treatment — which includes the evaluation that produced the plan. The second is the certification end date: a certification covers the duration the certifier approves, up to a maximum of 90 calendar days from the start of treatment, whichever is less. Recertification is due when that period ends, and earlier if the plan is significantly modified — a change to the long-term goals, or to the type, amount, frequency, or duration of treatment beyond what the certified plan already allows.

The calendar-day detail is the one that catches practices. A twice-weekly patient reaches the 90-day boundary around visit 24, and their therapist has usually written two progress reports by then — plenty of natural moments to notice the plan needs recertifying. A once-weekly patient with shaky attendance might reach the same boundary at visit 9, before the first progress report is even due. The visit count feels early; the calendar disagrees. Any tracking system built on “we will catch it at the progress report” fails exactly on the caseloads where attendance is worst.

The workflow below assumes nothing about your EHR beyond the ability to record a date and see it again later — a plan-of-care field, a task system, even a shared spreadsheet works. The design principle is that every step is triggered by a date you logged earlier, never by someone happening to remember. Six steps, and the first one carries most of the weight.

1. 01

   Log the certification end date the day the signature lands

   When the signed plan comes back — or, for initial certifications under the 2025 exception, when you log the transmission evidence — compute the end date immediately: the earlier of the certified duration’s end or 90 calendar days from the start of treatment. Record it in a field you can report on across the caseload, not in the note text. A date buried in a PDF is a date nobody is tracking.

2. 02

   Set the recertification trigger 21 days before the end date

   Three weeks covers the realistic path of an updated plan: a few days for the therapist to update goals, transit time to the physician’s office, a week of sitting in someone’s inbox, and one round of follow-up. Practices that set the trigger at one week are not building in the follow-up round, and the follow-up round is usually needed.

3. 03

   Update the plan before you send it

   A recertification request is the updated plan of care — current goals, current frequency and duration for the next period — not a signature line under the old one. Attach the most recent progress report: the certifier is attesting to continued need, and the progress report is the document that makes that case. If goals or frequency are changing materially, this is also the moment the change gets certified rather than discovered later.

4. 04

   Send it and log the transmission

   Record the date, the method, and the destination — fax number, portal, or staff email — in the same tracking field set. This is the evidence that the delay was not yours if the signature comes back late, and it is what turns the day-7 follow-up call from “did you get our fax?” into “confirming the plan we faxed to this number on the 12th.”

5. 05

   Chase on a fixed cadence, not on worry

   Follow up at day 7 and day 14 after sending. Ask the office to name their preferred channel and turnaround the first time you work with them, and write it down — most offices have a person and a rhythm for signatures, and requests that match the rhythm come back faster. Escalate from fax refill to phone call on the second contact.

6. 06

   Close the loop and start the next window

   When the signature returns, file it, verify it is signed and dated by a physician or NPP with knowledge of the case, and immediately log the next certification end date — step one, again. An episode that outlives several certification periods should feel like a wheel turning, not a series of surprises.

The slow step is rarely your side. A recertification that leaves your office in one day can still spend two weeks in a physician practice’s fax queue, and no tracking system shortens someone else’s inbox. What does shorten it: making the request effortless to act on. One page on top, the signature line visible without scrolling, the progress report attached behind it, and a return fax number or portal path stated explicitly. Offices sign what is easy to sign.

Two habits compound over time. Batch the chase: one front-desk block on a fixed weekday working every outstanding signature beats five people making ad-hoc calls. And track turnaround by office, not just by patient — once you know a practice reliably takes twelve days, you stop being surprised by it and start sending their requests earlier. The offices themselves rarely change; your lead time can.

A missed window is recoverable more often than teams assume — Medicare’s rules are built to avoid punishing the patient for signature logistics. The manual provides for delayed certification: a certification or recertification signed later than required, submitted with whatever evidence justifies the delay — the request you sent before the deadline, the fax confirmation, a note that the original was lost. CMS instructs contractors to accept delayed certifications of otherwise covered services unless there is reason to believe no physician or NPP was actually involved in the patient’s care. For very long delays — the manual discusses delays beyond six months — expect to add more: orders, progress notes, or other records showing the patient was under a physician’s or NPP’s care during the treatment.

Treat delayed certification as the safety net it is, not as slack in the system. Every delayed certification is an argument you have to make and a reviewer has to accept, where a timely one is a box already checked; a chart that leans on the net routinely reads very differently in an audit than a chart that used it once. This is also where the transmission log from step four of the workflow pays for itself — “requested on the 3rd, followed up on the 10th and the 17th, signature returned on the 29th” is a delay with a documented cause, which is precisely what the manual asks for.

Nothing above transfers automatically to other payers. Commercial plans and Medicaid programs set their own plan-of-care intervals, signature rules, and reauthorization requirements, and many tie continued treatment to an authorization cycle rather than a certification one — a different document with its own end date. The workflow transfers even though the numbers do not: whatever the payer calls the thing that expires, log its end date the day it is granted, trigger the renewal on a lead time, and chase on a cadence. Run every payer’s clock through the same weekly report, with the interval pulled from that payer’s current contract or provider manual rather than from memory — and when a rule matters to a specific claim, verify it with the payer first.