Because Spark doesn’t control the release. It has to be approved by your current top-of-hierarchy and/or the carrier—we can guide you, but we can’t approve or override it.

No. The information provided indicates that an agent may still be able to move by submitting an Intent to Move and entering the standard 90-day waiting period.

Not necessarily. Your top-of-hierarchy still needs to provide you a copy and the carrier still needs to process the hierarchy change, and blackout periods or holding periods may still apply.

The current top-of-hierarchy or the carrier, depending on what stage the process is in.

After the release has been approved and processed, especially if you need guidance on next contracting steps.

A Termination is the removal of an agent from a carrier contract entirely.

Once the carrier processes the termination, the agent no longer has access to that carrier and cannot write business under that contract.

If they want to work with that carrier again, they typically need to re-contract, and depending on the carrier, this may involve a waiting period.

A Release allows an agent to move their existing carrier contract to a new agency/top-of-hierarchy.

Once the release is approved by the current top-of-hierarchy and processed, the agent can continue writing business with that same carrier under the new top-of-hierarchy (carrier-dependent, but that’s the general expectation).

A release request is the process that allows a Medicare agent to move their carrier contracts from one agency or top-of-hierarchy to another. If an agent is currently contracted under a previous agency hierarchy, the top-of-hierarchy agency must release the agent before the contract can move to a new hierarchy.

Agents usually need a release when they want to move their existing carrier contracts to a new agency or top-of-hierarchy, change the hierarchy they are contracted under, join a different FMO, IMO, or agency structure, or transfer their book of business or writing rights to a new organization.

Not necessarily. Whether a release is required depends on the carrier and the hierarchy involved. Because carrier rules vary, agents should confirm the requirements for each carrier before beginning the process.

Yes. There are three common types:

Once a release is approved, the agent is typically able to contract under a new agency or hierarchy, write new business under the new hierarchy, and receive commissions through the new structure. The exact permissions depend on the carrier’s policies and whether a blackout or waiting period applies.

No. Even after a release is approved, the carrier may still need time to process the hierarchy change, and blackout periods or waiting periods may still apply.

In most cases, the top-of-hierarchy agency controls the release decision. This is the organization that sits at the highest level of the agent’s contracting hierarchy with the carrier.

The top-of-hierarchy, often shortened to TOH, is the agency at the highest level of the contracting structure with a carrier. The TOH is sometimes referred to as an agent's top-of-hierarchy. Because the carrier recognizes that organization as the controlling entity of the hierarchy, only the TOH can approve or grant a release for the agents underneath that structure.

It matters because the carrier only recognizes the controlling hierarchy that is officially on file. That means a release must come from the correct approving FMO. If the release is signed by someone who is not the correct top-of-hierarchy, the carrier may reject it.

Agents can usually identify their top-of-hierarchy by reviewing original contracting paperwork, checking the carrier portal, contacting their current agency, or contacting the carrier directly.

If an agent does not have contact with their previous top-of-hierarchy, Spark Support ([email protected]) or the carrier may be able to provide the name of the top-of-hierarchy.

If Spark is not the top-of-hierarchy, Spark cannot:

In that situation, the release must come directly from the agent’s current top-of-hierarchy agency.

Releases must be initiated and approved by the entities that control the hierarchy. Because Spark does not control another agency’s hierarchy or carrier contracts, Spark cannot approve or request releases on behalf of agents.

Spark acts as a guide and support resource during the release process, but Spark is not the party that controls a release being sent directly to an agent or approves releases. Release approvals are handled by the agent’s current top-of-hierarchy and or the carrier, depending on the situation. Spark helps agents understand the process, identify who needs to approve the release, and complete the correct steps.

Spark can help by explaining how the release process works, helping agents identify their current top-of-hierarchy, providing carrier-specific instructions for requesting a release, helping agents determine which carriers require a release, answering questions about hierarchy changes or contracting steps, and troubleshooting issues if the process becomes unclear or delayed.

Spark cannot request a release on an agent’s behalf, approve or deny a release, override a carrier’s release rules or waiting periods, force a previous top-of-hierarchy to sign or approve a release, provide copies of signed releases between agents and their previous top-of-hierarchy, or provide a release for carriers that an agent is not Ready to Sell with.

Release documents are agreements between the agent and the previous top-of-hierarchy. If an agent needs a copy of a signed release, the agent must request it directly from the previous top-of-hierarchy or the carrier that processed the release.

Once Spark sends the release to the agent’s current top-of-hierarchy for review, the document is no longer managed by Spark. From that point forward, the release is managed between the agent, the top-of-hierarchy, and the carrier.

No. Spark cannot force a prior top-of-hierarchy or another agency to act. Spark can explain the process and help the agent understand the next step, but Spark cannot override another agency’s authority within the hierarchy.

Carrier contracting systems are designed to protect hierarchy structures and agent relationships within each organization. Because of that, releases must follow a defined approval path that starts with the current hierarchy and then moves through the carrier’s system.

Spark cannot bypass the carrier’s contracting structure or the wishes of the top-of-hierarchy. The required process exists to ensure the correct hierarchy is updated, carrier compliance rules are followed, and agent commissions and relationships are properly reassigned.

The process may feel slow because multiple parties control different parts of it. The current hierarchy must approve the release, and the carrier must process the change. Spark does not control either of those steps when another hierarchy is involved.

Some release requests require a signed release form authorizing the agent to be released from the current hierarchy. Depending on the carrier, the required documentation may also include a carrier-specific release form, a signed letter of release from the current top-of-hierarchy, an agent release request form submitted through a carrier portal, or additional carrier contracting forms if the hierarchy change is part of a new appointment.

Release forms typically require:

All releases must also be time-stamped and are typically only valid for 90 days.

Yes. Many carriers have their own release forms and submission requirements. Some carriers require their specific release form template, some require portal submission, some require the release to be sent directly from the current top-of-hierarchy, and some require submission to a specific contracting or licensing inbox.

Yes. Some carriers have extra requirements beyond a standard release form. For example, Aetna requires wet signatures, meaning handwritten signatures, on release documents. Some carriers require the release to come directly from the top-of-hierarchy rather than the agent. Certain carriers may also enforce holding periods before the release becomes effective.

Common mistakes include missing NPN or agent information, release forms not being signed by the correct top-of-hierarchy, using the wrong carrier release form, submitting electronic signatures when wet signatures are required, sending release forms to the wrong carrier inbox, leaving dates or fields incomplete and outdated releases (ie a release from the year prior will be rejected by carrier).

Agents should carefully review all release documentation before submission and make sure they are following the carrier’s specific instructions. Small details, such as signatures, timestamps, and the correct form, can determine whether the request is processed or delayed.

When an agent is leaving an agency in the Spark hierarchy, the agent or the current top-of-hierarchy is responsible for submitting the release to the carrier. Because releases are agreements between the agent and the current hierarchy, the carrier usually requires the documentation to come directly from the agent or the top-of-hierarchy granting the release.

No. For agents leaving the Spark hierarchy of agencies, Spark does not submit release requests to carriers on behalf of agents.

Spark is not a party to the release agreement between an agent and the previous hierarchy. Carriers require release requests to be submitted directly by the agent or the top-of-hierarchy so they can confirm the release was properly authorized.

The typical process is:

That depends on the carrier. Submission may happen through email, a portal, or a carrier contracting team. Some carriers also require submission to a specific contracting or licensing inbox.

Spark can help provide carrier-specific instructions and guidance, but the submission itself still must come from the appropriate party.

The overall structure stays the same, but Spark may be more directly involved in the early part of the process when Spark is the top-of-hierarchy.

No. Even when Spark is the top-of-hierarchy, Spark does not control the full process from beginning to end. Once the release is sent to the current top-of-hierarchy for review and signature, the top-of-hierarchy is responsible for getting the release to the requested carriers for processing.

Once a release request is submitted, Spark attempts to provide releases for Spark carriers within one business week. That timing reflects Spark’s portion of the process, not the carrier’s full turnaround time.

No. Even when Spark is involved, the overall timeline still depends on signatures being completed correctly and the carrier processing the change.

Release timelines vary depending on the carrier and the hierarchy involved. In general, most releases take anywhere from a few days to several weeks after all required documentation has been submitted.

The speed of the release process is primarily controlled by the current top-of-hierarchy, who must approve or sign the release, and the carrier, who must process and update the hierarchy in its system.

No. Spark does not control the overall timeline. Spark can help guide the process, but the approval and processing steps are controlled by the top-of-hierarchy and the carrier.

A blackout period is a time during which agents are not allowed to transfer between hierarchies for a specific carrier. During a blackout period, the carrier will not process release requests or hierarchy changes, even if a release form has already been signed.

Blackout periods are set by carriers and often occur during AEP (Annual Enrollment Period) or other high-volume sales periods, during carrier system updates, during compliance review periods, or during specific contracting freeze windows established by the carrier.

In most cases, the agent must wait until the blackout period ends before the release can be submitted or processed.

Generally, no. Spark cannot expedite release requests because approval and processing are controlled by the current hierarchy and the carrier.

Spark can help by providing carrier-specific release instructions, helping agents confirm whether a blackout period applies, making sure the documentation is completed correctly, and helping agents identify the correct submission process.

Once Spark sends the release to the agent’s current top-of-hierarchy for review, the document is no longer managed by Spark. The process then moves between the top-of-hierarchy and the carrier.

In most cases, the carrier or the agent’s current top-of-hierarchy will notify the agent once the release has been processed.

No. If the agent wants a copy of the signed release, the agent must request it directly from the current top-of-hierarchy, because the top-of-hierarchy is the party responsible for approving and returning the document.

If the top-of-hierarchy has agreed to send the release directly to the carrier, rather than directly to the top-of-hierarchy to handle, the agent should contact the current top-of-hierarchy if they want confirmation that the release was signed or submitted to the carrier.

Once the release has been approved and processed by the carrier, the agent should confirm the release has been completed with the carrier or the new hierarchy, begin or complete contracting with the new top-of-hierarchy or agency if required, and submit any required carrier contracting documentation associated with the new hierarchy.

If the agent plans to contract through Spark after the release has been processed, the agent can contact Spark’s Support Team ([email protected]) for guidance on next steps.

If the former top-of-hierarchy does not approve or sign the release, the agent may still be able to move to a new hierarchy by submitting a intent-to-move request without a release.

A no-release transfer is a hierarchy change that allows an agent to move to a new agency or top-of-hierarchy without a signed release from the previous hierarchy. Instead of requiring approval from the previous top-of-hierarchy, the carrier processes the transfer after a mandatory waiting period. The waiting period is typically 90 days, but this is carrier-dependent.

If an agent does not receive a release, the agent can still leave that agency by submitting an Intent to Move. Submitting the Intent to Move starts the 90-day waiting period.

First, the 90-day waiting period is typical for most major carriers, but not all. For those carriers that honor a 90-day waiting period, once an agent submits an Intent to Move, the waiting period begins. During that time, the agent remains in the current hierarchy and can still write business. Once the waiting period ends, the carrier typically processes the hierarchy change to the new top-of-hierarchy.

The information provided indicates that this process is generally standard. A transfer with release means an immediate move, while a transfer without release means entering a waiting period (typically 90 days, but this varies) before being able to move. However, this does not account for carrier-specific blackout periods, which may extend the timing beyond 90 days depending on the carrier.

No. The agent can still write business during their waiting period, but the previous top-of-hierarchy still receives credit during that time.

No. Releases are controlled by the agent’s current top-of-hierarchy and the carrier, not Spark.

No. Spark cannot approve, deny, force, or override a release decision.

No. Even after a release is signed, the carrier must still process the hierarchy change, and that may take time.

No. Carrier policies such as blackout periods and waiting periods still apply even if a release is signed.

Agents can improve the process by confirming whether a release is required before starting, checking the carrier portal first, identifying the current top-of-hierarchy early, communicating directly with the current top-of-hierarchy in advance, following carrier-specific instructions carefully, and ensuring all required information is included on release documents.

Many carriers now allow agents to submit release requests or Intent to Move requests directly through their contracting portals, such as Evolve, which means Spark does not need to facilitate the request.

Yes. HealthSpring, Molina, Clover, and Wellcare are examples listed as carriers that are handled through their carrier portals and do not require Spark to facilitate. This is otherwise known as a carrier that does not accept a “paper release”.

Before requesting a release, agents should review the carrier’s transfer policy, including whether the carrier allows an Intent to Move if a release is not granted, check whether the request can be completed directly in the carrier portal, ensure they are ready to contract with the new hierarchy, and reach out to their current top-of-hierarchy in advance.

Clear communication with the current top-of-hierarchy can often make the release process faster and smoother by making sure the top-of-hierarchy is aware that the request is coming and can review it promptly.

Agents should make sure the documentation includes the required NPN, signatures, carrier name, and dates, along with any carrier-specific form requirements.