How Do You Request a Network Exception From Your Insurer?
When the right specialist for a specific condition simply isn’t in a plan’s network, the plan itself sometimes offers a formal way to close that gap rather than leaving out-of-network cost-sharing as the only option.
The short answer
A network exception, sometimes called a gap exception or network deficiency request, is a formal request asking an insurer to cover care from an out-of-network provider as if that provider were in-network, usually because no in-network provider can reasonably meet a specific medical need. Approval isn’t automatic — it typically requires documentation showing the network genuinely can’t meet the need, and the process and standards vary by plan.
When this request tends to make sense
- No in-network specialist exists for a specific condition within a reasonable distance, a gap that ties directly back to network adequacy shortfalls for certain specialties or regions.
- The only in-network option has an unreasonably long wait for an appointment given the medical urgency involved.
- Continuity of care matters, such as an ongoing treatment relationship with a specialist who becomes out-of-network mid-treatment due to a contract change, a scenario that echoes how hospital and physician contracts can shift independently of each other.
What documentation typically supports a request
Requests are generally stronger when they include a treating physician’s written explanation of why the specific out-of-network provider is medically necessary and why no in-network alternative is adequate, rather than a general preference for one provider over another. Some plans also want evidence that in-network options were explored first, such as records of calls made or referrals sought, before concluding no reasonable alternative existed. Keeping dates, names, and outcomes of those earlier calls organized as they happen tends to make this part of the request far easier to assemble than trying to reconstruct the timeline afterward.
How the process typically works
The request usually starts with the insurer’s member services or utilization management department, sometimes requiring a specific form completed by the treating physician rather than the patient directly. Response times vary by plan and by the urgency of the underlying medical need, and a decision can come back approved, denied, or approved with modified terms, such as a limited number of visits covered at the exception rate. An approval is also often tied to a specific time window or a set number of visits rather than standing indefinitely, so it can be worth asking whether renewal is possible if the underlying treatment continues past that window. If the request is denied, the standard process for appealing an insurance decision generally applies to a denied network exception the same way it applies to other coverage denials.
What to weigh
A network exception is worth exploring specifically when the network gap is genuine and documentable, rather than as a general workaround for wanting a particular out-of-network provider. Because some categories of care are especially prone to network gaps — specialty care, certain regions, and behavioral health among them — understanding this process in advance, before a specific need arises, can save time if a request ever becomes necessary.
The bottom line
Network exceptions exist because networks are imperfect by design, built around contracts rather than around any single patient’s specific situation. Treating the request as a documentation-driven process, built on medical necessity rather than convenience, gives it the best chance of being taken seriously by the plan reviewing it.