Why does a Medicare broker need a signed form before discussing plan options when a health insurance broker quoting an ACA plan does not? The difference is that Medicare is a federal program with CMS-enforced marketing rules that apply to every entity receiving compensation for enrolling beneficiaries into Medicare Advantage or Part D plans. The Scope of Appointment is not a suggestion from carriers. It is a CMS requirement codified in the Medicare Communications and Marketing Guidelines, and it is the document most likely to be missing from a broker's file when a carrier audit runs.
Key Takeaways
- The SOA must be collected at least 48 hours before a Medicare Advantage or Part D appointment. The two exemptions are walk-ins (beneficiary arrives without scheduling) and beneficiary-initiated same-day contact.
- The SOA form must explicitly list which plan types the broker will discuss. Covering an unlisted product type, even briefly, is a compliance violation that can trigger a carrier correction action.
- CMS's Medicare Communications and Marketing Guidelines (MCMG) require SOA documentation to be retained for 10 years. Carriers enforce this at the broker level through periodic audits.
- Telephonic SOA is permitted. The broker must document the verbal consent with the date, time, beneficiary name, and plan types covered, and retain that record with the same 10-year requirement.
- The SOA does not apply to outbound educational events. The moment a one-on-one sales discussion begins, the SOA requirement activates, regardless of where the conversation started.
What the SOA actually requires
The SOA must document the beneficiary's advance consent to a sales discussion covering specific plan types. The form must include the beneficiary's name, the date and location of the upcoming appointment, the plan types that will be discussed (Medicare Advantage, Part D prescription drug plans, or both), and the beneficiary's signature or telephonic attestation. A form that lists only “Medicare plans” without specifying the product type does not satisfy the requirement.
The plan-type specificity is where brokers create problems without realizing it. If a client signs an SOA for Medicare Advantage and then asks about a stand-alone Part D plan during the meeting, covering Part D at that point is a compliance violation. The broker must pause the Part D conversation, obtain a new SOA covering Part D, and only then continue. In a single appointment where the client's needs evolve, this can feel procedurally excessive, but the requirement exists precisely to prevent clients from being drawn into discussions they did not specifically authorize.
The 48-hour rule and its two exceptions
The standard requirement is that the SOA be obtained at least 48 hours before the appointment. For a Monday meeting scheduled on Friday, the SOA must be signed or documented no later than Friday before the appointment time. For a Friday meeting scheduled by phone on Thursday morning, the 48-hour window almost certainly cannot be satisfied, which means either the appointment must be moved or the broker must determine whether the walk-in or beneficiary-initiated exception applies.
The two recognized exceptions to the 48-hour rule are walk-in appointments and beneficiary-initiated same-day contact. A walk-in occurs when a beneficiary arrives at a broker's office without a scheduled appointment. Beneficiary-initiated same-day contact covers situations where a beneficiary calls the broker requesting an immediate discussion. In both cases, the SOA must still be completed before any sales conversation begins. The exception eliminates the 48-hour advance requirement, not the SOA itself.
CMS does not define “beneficiary-initiated” loosely. If the broker sent a mailer, ran an ad, or followed up on a lead list before the client called, the contact has a broker-initiated element. Carriers interpret this conservatively and document it narrowly. The safest practice is to default to the 48-hour rule unless the client contact was entirely unsolicited on the broker's part.
| Scenario | SOA Required | 48-Hour Advance Rule | Notes |
|---|---|---|---|
| Scheduled in-person appointment | Yes | 48 hours before appointment | SOA must be signed by beneficiary before the meeting |
| Scheduled telephone appointment | Yes | 48 hours before appointment | Telephonic consent documented with date, time, and plan types |
| Walk-in (unscheduled) appointment | Yes | Exempted; complete before discussion | 48-hour rule does not apply; SOA still required before any sales conversation |
| Beneficiary-initiated same-day contact | Yes | Exempted; complete before discussion | Beneficiary calls the broker requesting immediate discussion; 48-hour rule waived |
| Educational event (seminar, health fair) | No | Not applicable | No individual sales discussion permitted during the event itself |
| One-on-one follow-up after an educational event | Yes | Standard rules apply | The event exemption ends the moment a private sales conversation begins |
Illustrative summary based on CMS Medicare Communications and Marketing Guidelines. Rules may be interpreted more strictly by individual carriers. Confirm current MCMG requirements before each plan year.
Educational events and the line that activates the SOA
CMS distinguishes educational events from sales events. An educational event can cover Medicare plan options generally, discuss coverage concepts, and answer questions about how Medicare works, but cannot involve one-on-one discussions about specific plan options or enrollment. No SOA is required at a properly structured educational event.
The compliance risk is at the boundary. If a beneficiary approaches a broker at a health fair and the conversation becomes specific to that person's situation, plan options, or coverage needs, the educational exemption ends and the SOA requirement begins. The fact that the meeting happens to be in a gymnasium with 200 other people does not convert a one-on-one sales conversation into an educational event. Brokers who work health fairs need a process for capturing SOAs at the moment a general conversation becomes specific, not a policy of treating the entire event as education.
Documentation that survives a 10-year audit
CMS requires SOA forms to be retained for 10 years. Carriers enforce this at the broker level through periodic file audits. An audit request typically asks for every SOA associated with clients enrolled with the carrier in a given plan year. Brokers who operate on paper forms without a systematic filing process commonly fail this request within 2 to 3 years of an enrollment because paper files move, offices change, and staff turnover creates gaps in institutional memory.
The practical standard is a digital system that associates each SOA with the client record by name and plan year. Carrier portals sometimes provide SOA storage as part of the enrollment workflow, which is the most defensible position: if the carrier's system captured the SOA at enrollment, the carrier itself holds the primary record. Brokers who use carrier portals for enrollment should confirm whether the portal stores the SOA as part of the transaction or just the enrollment application. Storing only the application leaves the SOA documentation responsibility with the broker.
Quotit and other quoting platforms focused on ACA and Medicare plan comparison do not advertise SOA compliance tracking or 10-year retention functionality on their public sites as of August 2026. Brokers with large Medicare books typically use a carrier portal, a CRM with compliance document storage, or a dedicated Medicare compliance platform alongside their quoting tool.
What a correction action actually looks like
When a carrier audit identifies a missing SOA for an enrolled client, the standard outcome is a written notice to the broker requiring a response within 30 days and documentation of corrective steps. A first-occurrence finding typically results in a written warning and a requirement to complete a compliance training module. Repeat findings in the same audit cycle or across multiple plan years escalate to suspension of the broker's carrier appointment, which terminates the ability to enroll new clients with that carrier and often triggers a review of existing client assignments.
CMS direct enforcement is rarer but more consequential. A pattern of marketing violations documented across multiple carriers or complaint-driven investigations can result in exclusion from Medicare programs, which effectively ends Medicare broker activity regardless of how many carrier appointments remain. The SOA requirement is not the only path to exclusion, but it is one of the most preventable. See the Medicare enrollment window guide for a full breakdown of which activities during AEP and OEP require marketing compliance documentation beyond the SOA.
Building the SOA habit into client intake
The brokers with the fewest compliance issues treat the SOA as the first client touchpoint, not the last administrative step before an appointment. When a prospect calls to schedule a Medicare conversation, the SOA collection happens in that same call: verbal consent documented, plan types listed, note entered in the CRM. By the time the appointment occurs, the 48-hour requirement is satisfied and the documentation already exists.
For D-SNP clients with dual-eligible status, the SOA requirement applies exactly the same way as for standard Medicare Advantage clients. The D-SNP enrollment guide covers the additional enrollment timing and eligibility verification steps that apply to that population on top of the standard marketing compliance requirements.
Medicare Scope of Appointment
SOA requirements, the 48-hour rule, documentation standards, and what happens when a form is missing.
What exactly is a Medicare Scope of Appointment?
A Scope of Appointment is a written or telephonically documented agreement between a broker and a Medicare beneficiary specifying which plan types will be discussed in an upcoming appointment. CMS created the SOA requirement to prevent brokers from using an unrelated pretext to pivot into a sales conversation the beneficiary did not expect or consent to. The form must be signed by the beneficiary (or a designated representative) and must identify whether the discussion will cover Medicare Advantage plans, Part D plans, or both. The broker must retain the completed form and cannot discuss plan types that were not listed on it without obtaining a new SOA.
When does the 48-hour rule apply and when can you skip it?
The 48-hour advance requirement applies whenever a broker schedules a Medicare Advantage or Part D sales appointment in advance. If you are calling a prospect to set up a meeting, the SOA must be signed or verbally recorded at least 48 hours before the appointment itself. The rule has two recognized exceptions: walk-in appointments, where the beneficiary arrives at the broker's office without a scheduled meeting, and beneficiary-initiated same-day contact, where the beneficiary calls the broker and requests an immediate discussion. In both exception cases, the SOA must still be completed before any plan-specific discussion begins. The 48-hour clock is measured from the SOA completion to the appointment, not from the initial outreach.
What happens if the beneficiary wants to discuss a plan type not on the SOA?
If a client asks about a product type that was not listed on the original SOA, the broker must stop the sales discussion for that product type and obtain a new SOA before proceeding. For example, if the SOA covered Medicare Advantage only and the client asks about a stand-alone Part D plan, adding a verbal note to the file is not sufficient. A new SOA must be completed, the 48-hour rule evaluated (typically it does not apply if the client initiated the question in the same meeting), and the discussion can then continue. Carriers flag this scenario in audits because brokers often do not realize that adding Part D to a conversation already underway without a new SOA is a compliance event.
How should telephonic SOA be documented?
When collecting a SOA over the phone, the broker must verbally read the SOA language to the beneficiary, confirm their agreement to discuss the listed plan types, and document the call with the beneficiary's name, the date and time, the plan types consented to, and a confirmation that the beneficiary verbally agreed. Some carriers provide recorded telephonic consent systems that capture this automatically. If the broker is using a manual documentation process, the note should be entered into the client file immediately after the call, time-stamped, and retained for 10 years alongside any written SOA forms. CMS does not require a specific form for telephonic consent, but the documentation must contain all the same elements as a written SOA.
What are the consequences of not having a signed SOA?
Operating without a signed SOA for an enrolled client is a CMS and carrier compliance violation. When a carrier audits broker files and discovers a missing SOA for an enrollment, the typical corrective action is a written warning for a first occurrence, followed by suspension or termination of the broker's appointment for repeat violations. CMS can also initiate direct enforcement action against brokers who pattern-market outside of SOA requirements, which can result in exclusion from Medicare programs. In practice, most brokers who lose a carrier appointment due to SOA violations also lose access to that carrier's book of business, including renewal commissions on all clients enrolled with that carrier.
