Guide

Gap exceptions: in-network rates when the network is thin

Summary

A network gap exception gets approved by showing the plan's network lacks a provider who can deliver the needed service within its own access standards — no in-network clinician in your specialty within a reasonable distance or wait time from the patient. You request it directly from the payer's utilization management or network department before or shortly after the visit, citing the specific gap, and if granted the payer processes your claim at in-network rates and cost-sharing even though you're not contracted with that plan.

By Gale Editorial · Updated 2026-07-26. Every figure cited to a dated source. How we write.

What a gap exception actually gets you

A gap exception is the payer's acknowledgment that its own network can't meet the patient's need, and its remedy for that failure: it processes your out-of-network claim as if you were in-network, applying the patient's in-network cost-sharing instead of out-of-network terms. It does not make you a contracted provider — you remain out-of-network for every other patient on that plan — and it typically applies to a defined episode of care rather than indefinitely.

The patient benefits directly: instead of an out-of-network deductible and coinsurance, they pay what an in-network visit would have cost them. That's the argument worth leading with when you request one, since it's the plan's own network adequacy obligation you're pointing to, not a favor you're asking for.

The network-deficiency argument that gets approved

The request that succeeds names a specific, checkable gap: no in-network provider in the relevant specialty within the plan's own stated distance or appointment-availability standard, or an in-network provider who exists on paper but isn't actually accepting new patients. Vague language — "the network is inadequate" — gets far less traction than a concrete claim: you called the three in-network providers the plan's directory listed, none had an opening within the plan's stated timeframe, and here are the dates you called.

This is why the request works better coming with documentation already attached rather than as a bare ask — the payer's reviewer is checking your claim against its own network data, and a specific, dated record of the search makes that check fast instead of adversarial.

How to request one, step by step

Contact the payer's utilization management or provider network department directly — not the general customer service line — and ask specifically for a network gap exception or network deficiency exception; the term varies by payer, so ask what they call it if the first term doesn't land. Anthem, Aetna, UnitedHealthcare, and Cigna each publish their own provider-facing policies describing how requests like this are handled under their plans, and the process and required documentation differ across them, so check the specific payer's published policy before assuming a process that worked with one plan transfers to another 1Ref 1Anthem (2026).Anthem Provider Policies.Named example that Anthem publishes its own provider-facing policies describing its process for network exception requests, distinct from other payers' processes.2Ref 2Aetna (2026).Aetna Clinical Policy Bulletins.Named example that Aetna publishes its own policies governing network exception handling under its plans.3Ref 3UnitedHealthcare (2026).UnitedHealthcare Policies and Protocols.Named example that UnitedHealthcare publishes its own policies and protocols for network exception requests, illustrating payer-specific process variation.4Ref 4Cigna (2026).Cigna Coverage and Claims Policies.Named example that Cigna publishes its own coverage and claims policies, used here to show gap-exception process and documentation requirements vary by payer..

Submit the request before the visit where possible — a retroactive request, made after the claim has already denied, is a harder sell than one made in advance, though many payers will still consider it if the network gap genuinely existed at the time of service.

Gap exception versus a single case agreement

A gap exception and an SCA — a single case agreement, one patient and one negotiated rate — solve overlapping problems through different mechanisms, and providers often use the terms loosely enough to confuse the two. A gap exception is the payer applying its existing in-network terms to your out-of-network claim because its network can't meet the need; an SCA is a bespoke negotiated rate you and the payer agree to for that one patient, which may be higher, lower, or the same as the plan's in-network rate.

Which one you ask for matters: if the network genuinely can't meet the need, a gap exception gets the patient in-network cost-sharing at your usual claim; an SCA is worth pursuing when you want to negotiate a specific rate rather than simply matching the in-network fee schedule.

Why the request gets denied, and what to do next

The most common reason a gap exception request fails is that the payer's directory shows in-network providers the reviewer considers adequate, even if your documented calls found otherwise — this is where the dated record of your search matters, since it directly contradicts a directory-based denial. A second common reason is timing: requesting after the claim has already processed and denied, without having flagged the gap in advance, gives the payer less reason to treat the situation as urgent.

If denied, ask specifically what network data the payer used to reach that conclusion, and be prepared to appeal with the same documentation — a directory listing a provider who isn't actually accepting new patients is a factual dispute you can win with enough specificity, not a discretionary call you have to accept.

Documenting the request so it survives later scrutiny

Keep a record of every call made to in-network providers before requesting the exception — date, provider name, and what you were told — along with the payer's approval, its reference number, and the specific cost-sharing terms it confirmed. This record does double duty: it supports the exception request itself, and it protects you if the claim later processes incorrectly and you need to show the payer what it actually approved.

Building this into a habit rather than a one-off scramble makes future gap-exception requests faster too — many solo practices find the same specialty gaps recur with the same plans, so the documentation from one request often transfers directly to the next patient facing the identical network gap.

Common questions

Being out-of-network means the patient pays out-of-network cost-sharing and you bill your usual rate. A gap exception is the payer agreeing, for a specific patient and episode, to apply in-network cost-sharing to your out-of-network claim because its network can't meet the patient's need.

No. It applies only to the specific patient and episode of care the exception covers. You remain out-of-network for every other patient on that plan unless you separately credential and contract with the payer, so don't treat one approved exception as a standing arrangement for future patients.

Some payers will consider a retroactive request if the network gap genuinely existed at the time of service, but a request made before the visit is a stronger position. Ask the specific payer's utilization management department what their timing rules are.

No. A gap exception applies the plan's existing in-network terms to your claim; a single case agreement is a separately negotiated rate for one patient that may differ from the in-network fee schedule. Which one to request depends on whether you're pointing to a network gap or negotiating a specific rate.

A specific, dated record of your search for an in-network alternative — which providers you called, when, and what you were told about their availability — carries far more weight than a general statement that the network is inadequate. Attach it to the request itself rather than waiting for the reviewer to ask.

Run your practice on Gale

The software is free. Gale earns one flat 3.5% all-in per paid transaction — only on transactions that actually pay. No subscription, no setup fee, no network cut.

Start or manage a practice →

References

1.Anthem (2026). Anthem Provider Policies. Anthem provider portal. link ✓Named example that Anthem publishes its own provider-facing policies describing its process for network exception requests, distinct from other payers' processes.
2.Aetna (2026). Aetna Clinical Policy Bulletins. Aetna provider portal. link ✓Named example that Aetna publishes its own policies governing network exception handling under its plans.
3.UnitedHealthcare (2026). UnitedHealthcare Policies and Protocols. UnitedHealthcare provider portal. link ✓Named example that UnitedHealthcare publishes its own policies and protocols for network exception requests, illustrating payer-specific process variation.
4.Cigna (2026). Cigna Coverage and Claims Policies. Cigna provider portal. link ✓Named example that Cigna publishes its own coverage and claims policies, used here to show gap-exception process and documentation requirements vary by payer.
5.Centers for Medicare & Medicaid Services (2026). No Surprise Billing. Centers for Medicare & Medicaid Services (CMS). link ✓That the No Surprises Act restricts balance billing in defined out-of-network settings independent of any payer-granted gap exception, so the two protections shouldn't be assumed to overlap automatically. As of July 2026.

https://www.gale.care/for-providers/va-gap-exception-network-deficiency · 5 sources. Competitor details are cited to dated public sources and maintained as they change; figures are estimates, not commitments. Synthetic demonstration.

← Back to for providers