When the Scope of Appointment Must Be Obtained

The Scope Of Appointment (SOA) is a key compliance tool in U.S. health plan marketing, especially for Medicare Advantage and Medicare Part D. It documents exactly which items a beneficiary agrees to discuss with a licensed adviser during an appointment. Understanding when the SOA must be obtained helps agents, brokers, and plan sponsors stay compliant and protect beneficiary rights.

What Is A Scope Of Appointment

A Scope Of Appointment is a written record that specifies the topic areas a beneficiary agrees to discuss with an agent or broker. It prevents agents from steering conversations into topics the beneficiary did not authorize, such as changing plans or discussing non-covered services. In most cases, an SOA must be completed before an in-person or telephonic appointment with a plan representative about specific products. The document should clearly list topics such as medical services, prescription drug coverage, and plan cost-sharing structures.

Timing Requirements For SOA

The timing of obtaining an SOA depends on the interaction type and plan rules. Generally, an SOA must be signed before discussing items listed on the form with a plan representative. In many plans, the SOA is required for each appointment and before the disclosure of any plan-specific information. If the beneficiary only seeks general information about multiple plan options, an SOA may not be necessary, but once topics narrow to specific products or benefits, the SOA becomes essential.

For marketing events and enrollment opportunities, the SOA should be completed prior to discussing or presenting plan benefits that fall under the listed topics. If a discussion veers into a new topic not covered by the current SOA, the agent should obtain an updated SOA that includes the new topics. This practice reduces the risk of non-compliance and ensures an accurate record of consent.

Who Must Obtain An SOA

The primary obligation to obtain the SOA falls on licensed agents or brokers marketing Medicare plans. Organizations sponsoring sales events or call centers also bear responsibility for ensuring SOAs are obtained and stored appropriately. In some states or plan arrangements, marketing representatives may delegate SOA collection to licensed agents, but ultimate accountability rests with the sponsoring organization. It is important that the individual collecting the SOA verifies the beneficiary’s identity and ensures consent is voluntary and informed.

Capturing The SOA For Medicare Plans

SOAs should be captured in a durable manner that supports auditability. Common methods include electronic forms linked to the beneficiary’s record, or paper forms that are later scanned into a secure system. Key elements include the beneficiary’s name, plan name, marketing date, topics authorized, and the signature or electronic consent of the beneficiary or authorized representative. Time-stamped records help demonstrate compliance if questions arise during compliance reviews or audits.

Organizations should maintain a master list of covered topics and ensure the SOA aligns with the specific plan or product being discussed. When plans update their benefit structures or when new products enter the market, updated SOAs may be necessary so the topics match current offerings.

Common Scenarios And Exceptions

There are several scenarios where the SOA is particularly important. Before enrolling in a Medicare Advantage plan, an SOA ensures the appointment covers medically relevant topics and drug coverage choices. For Part D drug plans, the SOA typically specifies prescription drug coverage topics and formulary discussions. If an appointment is limited to general information or a non-benefit topic, an SOA may not be required, but caution is advised because plan rules can vary.

Exceptions may include follow-up calls for existing beneficiaries where topics are already authorized, or situations where a beneficiary requests information only about plan basics such as costs or network coverage without discussing specific benefits. Even in these cases, explicit consent through an SOA is often recommended to establish a clear record of the scope.

Best Practices For Compliance

• Guard each appointment with an SOA update: If topics expand beyond the original scope, obtain a revised SOA to cover new areas.
• Train staff on proper documentation: Ensure teams understand when an SOA is required and how to store records securely.
• Keep records easily retrievable: Use centralized, time-stamped digital systems to support audits and beneficiary requests.
• Audit readiness: Periodically review SOA processes, including form templates, storage, and accessibility for beneficiaries and regulators.
• Clear, plain-language topics: List topics in user-friendly language to avoid ambiguity and ensure informed consent.

Frequently Asked Questions

1. Can an SOA be obtained electronically? Yes. The SOA can be completed electronically or on paper, provided it captures all required fields and is stored securely.
2. What happens if an SOA is missing? Without a proper SOA, discussions about eligible topics may violate regulations, potentially leading to enforcement actions or plan disqualification in extreme cases.
3. How long should SOA records be kept? Retention periods vary by plan and regulator guidelines, but many organizations keep records for several years to support audits and beneficiary inquiries.
4. Is the SOA needed for every appointment? Not always. If the discussion remains within non-benefit topics or falls outside the scope, a formal SOA may not be required, but consistent practice is recommended.