How to write a pharmacy tiering exception to lower the copay

Tiering exceptions are one of the more underused requests a practice can file for its patients, and many practices are not writing them as effectively as they could. When a covered drug sits on a high cost-sharing tier, a well-written exception from the prescriber's office can bring the patient's cost-sharing down and help keep them on therapy. Formularies can change during the plan year, so it pays to have the process ready before a change hits one of your patients.

What is a pharmacy tiering exception?

A tiering exception is a formal request asking a patient's insurance plan to cover a medication at a lower cost-sharing tier than it's currently assigned. Most commercial plans and Medicare Part D plans use a tiered formulary, typically Tier 1 (generics, cheapest) through Tier 4 or 5 (specialty drugs, most expensive). When a drug lands on Tier 3 or higher, the copay can become unaffordable fast.

Medicare Part D plans that use a tiered formulary must have a tiering exception process (42 CFR 423.578). Commercial plans are different: for individual and small-group plans, the ACA requires an exception process for drugs that are not on the formulary, not for moving a covered drug to a lower tier (45 CFR 156.122), so whether a commercial plan accepts tiering exceptions depends on the plan and on state law. Where a process exists, approval is not automatic, but a correctly written request has a real chance.

Tiering exceptions differ from prior authorizations and from formulary exceptions, which argue that a non-covered drug should be covered at all. A tiering exception assumes the drug is already covered. You're asking the plan to apply a lower tier's cost-sharing. It's a narrower ask.

It is not available for every drug, though. A Part D plan may design its tiering exception process so that drugs on its specialty tier(s) are not eligible for an exception to a non-specialty tier, so that a brand-name drug is not approvable at a preferred cost-sharing level that applies only to generic or authorized generic alternatives, and so that a biological product is not approvable at a preferred level that contains no biological alternatives (42 CFR 423.578(a)(6)). A drug covered only because a non-formulary exception was approved cannot get a tiering exception either (42 CFR 423.578(c)(4)(iii)). Check the plan's exception criteria for these limits before anyone starts writing.

The core elements every strong tiering exception needs

This is where most practices stumble. They submit a vague letter stating the medication is "medically necessary" and stop there. That's not enough. Here's what actually moves the needle:

1. Clinical justification tied to the specific patient

Don't just describe the drug. Describe why this patient, at this moment, needs this drug rather than the plan's preferred alternatives. Reference their diagnosis, relevant comorbidities, how long they've been on the medication, and how they've responded. If they've been stable on a Tier 3 branded medication for two years, say that. Stability is a clinical argument.

2. Documentation of alternatives tried (or why they're not appropriate)

Most plans want to see that cheaper alternatives were considered. Either the patient tried them and they failed (side effects, inadequate response, contraindication) or there's a clinical reason those alternatives don't apply. Be specific. "Patient tried metformin and experienced significant GI intolerance requiring discontinuation after six weeks" carries far more weight than "alternatives were tried."

3. A supporting statement built on the Part D standard

For Medicare Part D, the plan grants a tiering exception when it finds the requested drug medically necessary, consistent with the prescriber's supporting statement that the preferred drug(s) for the patient's condition would not be as effective for the patient as the requested drug, would have adverse effects for the patient, or both (42 CFR 423.578(a)). The copay amount is not part of that standard. Build the statement from the patient history and the alternatives in points 1 and 2, and name the preferred drugs you are comparing against.

Cost belongs in the letter only as context: it explains why the request matters to the patient, not why the plan should grant it. For a commercial plan, argue only what the plan's own exception criteria allow. If the plan does not publish tiering exception criteria, ask for them before you write.

4. The specific request

Be explicit. State clearly: "We are requesting a tiering exception to cover [Drug Name] at the Tier [X] cost-sharing level." Don't leave the reviewer guessing what you're asking for. For Part D, the tier to name is the one where the preferred alternatives sit: an approved tiering exception is covered at the cost-sharing level that applies to the preferred alternative drugs, and at the lowest applicable tier when those alternatives are on more than one tier (42 CFR 423.578(c)(3)(ii)).

Common mistakes that sink tiering exception requests

• Generic templates with no patient-specific detail. Payers see these constantly. If it reads like a form letter, it gets treated like one.
• Missing provider credentials or NPI. Sounds basic, but it happens regularly. Missing information is an easy reason to delay or deny.
• Not addressing the plan's own formulary language. Some PBMs publish specific tiering exception criteria in their formulary guidelines. If you can reference those criteria and show your patient meets them, you're speaking the reviewer's language.
• Submitting without supporting clinical records. A letter alone often isn't enough. Attach relevant chart notes, lab results, or prior treatment records. More documentation gives the reviewer what they need to approve the request.
• Waiting too long. For Part D, the decision clock on an exception request starts when the plan receives the prescriber's supporting statement, so send the statement with the request. If the statement has not arrived within 14 calendar days of the request, the plan must decide no later than 72 hours after the end of those 14 days, or 24 hours for an expedited request (42 CFR 423.568(b), 42 CFR 423.572(a)). When a Part D plan changes a drug's tier during the year while the patient is taking it, the plan's tiering exception process has to cover that situation (42 CFR 423.578(a)(1)), so file as soon as you learn of the change.

The submission process

The clinical argument is only half the work. Submission mechanics matter too.

Start by checking the plan's specific tiering exception requirements, which vary by payer. Some require the prescriber to submit; others accept a request that practice staff send on the prescriber's behalf. A Medicare Part D exception request can come from the enrollee, the enrollee's representative, or the prescriber (42 CFR 423.566(c)), but the supporting statement has to come from the prescriber (42 CFR 423.578(a)(4)). It can be oral or written. If it is oral, the plan can require a written statement as follow-up, along with additional supporting medical documentation (42 CFR 423.578(a)(5)).

Quick process checklist:

• Confirm the drug's current tier and what tier you're requesting
• Get the plan's tiering exception form (many have their own; others accept a letter)
• Verify the submission fax number or portal, because these change more often than they should
• Set a follow-up reminder: for Part D, 24 hours for an expedited request and 72 hours for a standard one, both counted from the plan's receipt of the prescriber's supporting statement
• If denied, keep the written denial notice. For Part D it must state the specific reasons for the denial (42 CFR 423.568(g)). You'll need it for the appeal.

Under Medicare Part D, a standard exception request must be decided no later than 72 hours after the plan receives the prescriber's supporting statement (42 CFR 423.568(b)). An expedited request must be decided no later than 24 hours after that statement arrives (42 CFR 423.572(a)). Expediting is warranted when the standard timeframe may seriously jeopardize the patient's life or health or ability to regain maximum function, and the plan must expedite when the prescriber indicates that the standard timeframe may do so (42 CFR 423.570(c)(3)). A plan that misses either deadline is treated as having made an adverse coverage determination and must forward the request to the independent review entity within 24 hours of the missed deadline (42 CFR 423.578(c)(2)). Commercial timelines vary by plan and state. Flag urgency when it's real.

Using technology to speed up the process

Writing individualized, clinically grounded tiering exceptions takes time, and most practices don't have much of it. AI-powered appeal and exception generators are starting to help in this space. These tools can pull patient-specific data and produce a customized draft in a fraction of the time it takes to write from scratch, leaving the clinician to review and sign off rather than stare at a blank page.

No tool replaces clinical judgment, though. Whatever produces the initial draft, a clinician still needs to confirm that the clinical narrative actually reflects the patient's situation. A polished letter built on the wrong clinical story can create problems if a reviewer starts asking follow-up questions.

Where to focus next

For Part D, the prescriber's supporting statement does not by itself guarantee approval (42 CFR 423.578(f)). What the practice can control is specificity: specific patient, specific clinical history, specific request. Give the reviewer documentation they can approve against.

If your practice isn't tracking tiering exception outcomes yet, start a simple log now. Record submissions, approvals, denials, and denial reasons. Patterns show up quickly: which plans approve most readily, which arguments land, and where patient access is slipping through the cracks.

A few concrete starting points:

1. Pull your most common high-tier medications and identify which patients might benefit from a tiering exception request
2. Review the formularies for your top payers to understand what the tier structure looks like mid-2026
3. Build a simple intake flag so anyone on the team can identify a tiering exception need before it gets missed
4. Draft a master template with the core structure, then customize it every single time