Appeal Tracking and Follow-Up: Carrying a Filed Appeal to Resolution

Appeal tracking and follow-up is the discipline of carrying every filed appeal from the moment it is submitted to the moment it is resolved. It exists because submission changes nothing about the money: an appeal removes a denial from the pile of decisions still to be contested and adds it to a different pile — the appeals now waiting on the payer — and until one of those is decided and acted on, no revenue has moved. The work between those two piles is monitoring, following up, catching the decision, and closing the loop, and it is where recoverable money is most quietly lost, because the effort of building the appeal is already spent by the time it can go missing.

This is a different question from every other appeal page, and it deliberately restates none of them. Whether to appeal at all, what the appeal has to argue, and how long the window to file it stays open are appealing a denial; the document that carries the argument is the appeal letter; the ordered steps of working a single appeal are the denial appeal process workflow, whose track-and-follow-up step this page is the policy behind. This page takes a filed appeal as given — the decision to appeal made, the letter sent — and owns only what happens to it from there until it resolves.

Appealing a denial owns the clock that runs before you file — the appeal window, which runs from the payer's original decision and is a separate clock from timely filing. Two more clocks start the moment the appeal is submitted, and both belong to the period this page owns: the payer's own decision clock, and the next-level window that will run from whatever decision comes back.

The payer's decision clock

Once an appeal is filed, the payer owes a decision within a defined period, and that period is the payer's — set in its policy or the provider contract, and, for the plans that publish one, in regulation. Medicare's contractors decide a redetermination and a reconsideration each within a stated timeframe; a Medicare Advantage plan owes a reconsideration within a set window; an ERISA plan owes a benefit determination on review within a defined period. The number is not the point and is not printed here — what matters is that the window exists and belongs to the payer, so a practice's follow-up is anchored to it rather than to an arbitrary calendar.

The next-level window

Every appeal decision that upholds the denial starts a new, separate window to take the case to the next level — and that window runs from the decision, not from the day someone in the office reads it. Medicare makes the shape explicit: each level of its fee-for-service appeals process is a distinct appeal whose filing window runs from the receipt of the prior level's decision, and receipt is itself presumed a set span after the date on the notice, whether or not the envelope was opened. So the clock on the next appeal can be running before anyone has seen the decision that started it.

Following up is not calling the payer on a fixed weekly cycle. It is anchored to the payer's own decision window, and that changes what to do at each stage. Before the window closes, there is nothing to chase but confirmation that the appeal was received — calling to ask whether it arrived, over and over, before the payer is even due to decide, spends the follow-up capacity that a genuinely overdue appeal needs. After the window closes with no decision, the situation is different in kind: the payer is now past its own deadline, and that is an action, not a wait.

That is the part practices most often get wrong, because it feels like a dead end and is usually the opposite. When a payer does not decide within its own window, the rules generally do not leave the appeal stuck. In Original Medicare, a contractor that cannot complete its review in time must advise the appellant of the right to escalate the appeal to the next level. A Medicare Advantage plan that misses its reconsideration timeframe must treat the delay as an affirmation of the denial and forward the file to an independent entity contracted by CMS — the plan cannot simply sit on it. And an ERISA plan that fails to follow reasonable claims procedures leaves the claimant deemed to have exhausted the plan's remedies, free to pursue the remedy the statute provides. The specifics differ by plan and route, but the shape is consistent: a payer's own missed deadline is escalatable, and the tracking record — proof of what was filed and when — is what supports the escalation.

Everything above depends on one thing: that every filed appeal is a tracked open record rather than a memory. Each open appeal carries the claim and patient identifiers, the level it is at, the date and proof of filing, the payer's decision window, the next action and the date it is due, and an owner. That inventory is what a denial and appeal tracking log records; this page is the policy that keeps it current and acts on it. The log is the artifact and does not replace the discipline — a fully populated log that no one works against is still a pile of appeals aging out on schedule.

The field the method depends on is the next action and its date. For an appeal still pending, that date is when the payer's window closes, so that silence turns into a follow-up the moment it does. For an appeal just decided, it is when the next-level window closes, so an upheld decision turns into an escalation before it expires. A pending-appeals list that cannot surface that one field forces the team back onto the two failure modes it is meant to prevent — chasing appeals that are still inside the payer's window, and missing the ones already past it. Making the next-action date visible is the prerequisite, not a refinement.

The loop closes when the balance is paid, escalated, or written off — never when the appeal is sent, and never when the decision merely arrives. A decision is the branch point, and it leads to one of three terminal paths, each of which is itself a next action to be tracked.

Favorable — reprocess, then post

A won appeal is words on a notice until the claim is reprocessed by the payer and the payment posts to the account. A favorable decision that is never converted is still an open accounts receivable — indistinguishable on the aging from a denial that was never worked at all. The follow-up on a favorable decision is confirming the reprocessed claim actually arrives and posts, the same convert-the-outcome discipline a favorable post-service peer-to-peer review needs.

Upheld and still disputable — escalate within the window

If the denial is upheld and the case is still worth pursuing, the next action is to take it to the next level, whose window runs from this decision. Which body hears each level and what each one can settle is the levels of appeal; the escalation is the follow-up, and it is as deadline-bound as the first filing was. A medical necessity denial upheld at a first level is the archetype — the same record, argued to an independent reviewer at the next.

Upheld and not worth pursuing — write off deliberately

Some upheld denials are correctly the end of the road, and the balance is cleared as a recorded decision rather than left to age unworked. What governs that — the reason it is coded to, who authorizes it, and how it is reported so it can be shrunk — is a write-off policy, set out in denial write-off policy. Closing the loop this way is a decision, not a default; the appeal is resolved because someone chose to stop, not because it drifted.

Closing the loop also produces the data that says whether the appeals are worth running at all — which denials are being overturned, at which payers, and how often. That is a reporting question, read from the analytical view rather than the worklist, and it is denial reporting by payer. Keeping the pending-appeals worklist separate from that report is deliberate: it is the general discipline of separating work queues from reporting views, so that reordering the follow-up work never distorts the trend and the trend never doubles as a task list.

A filed appeal is rarely lost on the merits after it is filed. It is lost in the handling, and the failures are a short list — each one recognizable, and each one a place where the discipline above was skipped.

• File and forget. The appeal is submitted, leaves the team's attention, and the payer's silence is read as the matter being settled. It is the most expensive failure precisely because the hard part — building the appeal — was already done, and it went to waste for lack of a next action against the record.
• A fixed calendar instead of the payer's window. Following up on every appeal on the same weekly rhythm wastes effort on appeals still comfortably inside the payer's window and misses the ones already past it. The horizon that governs when to act is the payer's decision window, not a calendar the practice chose.
• Treating a verbal favorable as resolved. “It's approved, it'll reprocess” closes the item in someone's head while the balance stays open on the aging. An appeal is resolved when the money posts, not when a phone call is encouraging.
• Letting the next-level window lapse. An upheld decision arrives, is read, and is set aside — and the window to escalate it, which was running from that decision, closes unworked. The decision that ended one appeal was the start of the next one's clock, and nothing caught it.
• A won appeal never reprocessed. The rarer, quieter loss: the appeal succeeded and the payer agreed, but the claim was never reprocessed or the payment never posted, so money that was recovered on paper was never collected in fact.
• No owner. An open appeal with no one named against it is the one that ages out when the person who filed it moves on. Ownership is not administrative overhead here; it is the difference between an appeal that is followed and one that is merely filed.