All articles
For Agents

CY2027 Medicare Marketing Compliance Checklist for Agents

moderator · 11/13/2026 · 12 min read · 2,704 words
CY2027 Medicare Marketing Compliance Checklist for Agents

Use our CY2027 Medicare marketing compliance checklist to master new SOA rules, TPMO disclosures, call recording, and event transition requirements for agents.

Medicare marketing compliance is not a one-time training topic. It is an operating discipline that touches every part of an agency: licensing, beneficiary contact, appointment preparation, event management, call technology, data access, record retention, and audit response.

For CY2027, several Medicare marketing changes take effect on October 1, 2026. The most important operational updates include the elimination of the 48-hour wait between a completed Scope of Appointment (SOA) and a personal marketing appointment, the removal of the 12-hour gap between educational and marketing events under the required transition controls, and updated timing for the Third-Party Marketing Organization (TPMO) disclaimer.

This checklist is designed for agents, agencies, field marketing organizations, and support teams preparing for CY2027. It separates the CMS baseline from additional requirements that may come from plan contracts, state law, privacy rules, or agency policy.

Important: This article is general compliance information, not legal advice. Review your current plan contracts, applicable law, written procedures, and compliance counsel guidance before changing your workflow.

CY2027 Medicare marketing compliance at a glance

Before changing a form, script, event process, or recording system, review these core points:

  • CY2027 changes take effect October 1, 2026.

  • The 48-hour wait between a completed SOA and a personal marketing appointment is eliminated.

  • The SOA itself is still required where applicable. Written SOA requirements and exceptions must be checked for each interaction.

  • The TPMO disclaimer must be provided before any discussion of plan benefits.

  • The 12-hour gap between an educational event and a marketing event is removed. A transition is permitted when the required notice is provided and attendees have a sufficient opportunity to leave.

  • SOAs may be collected at educational events under the CY2027 rules.

  • The 2027 Annual Election Period (AEP) is October 15 through December 7.

  • Do not treat a proposed reduction from 10 years to 6 years as a universal record-retention rule. Retention must be reviewed across CMS requirements, contracts, state law, privacy and records rules, and agency policy.

Read the CMS CY2027 Agent and Broker Training and Testing Guidelines and compare them with the written requirements that apply to your organization.

Master checklist: CMS minimums versus other requirements

Use this table as a review framework. The “CMS baseline” column should not be treated as the only source of obligations. Your plan contract, state, privacy requirements, or internal policy may be stricter.

Compliance areaCMS baseline to verifyPlan contract and state-law reviewPrivacy and agency-policy reviewIndividual credentialsConfirm that each person participating in Medicare marketing activity has the credentials and training status required for the role.Verify state licensing, appointments, product authority, and plan-specific credentialing before activity begins.Maintain an up-to-date credential file and suspend access when credentials expire or cannot be verified.Written SOADetermine whether the interaction requires an SOA and use the current approved form or process. The SOA remains required where applicable.Check written SOA rules and exceptions for the plan, state, interaction type, and appointment channel.Store the completed SOA with the correct beneficiary and appointment record.PMA timingThe 48-hour wait between completed SOA and personal marketing appointment is eliminated for CY2027.Confirm how each contracted plan defines and documents a personal marketing appointment.Update scripts, scheduling tools, and staff training so the removed wait is not confused with removal of the SOA requirement.Inbound and outbound contactClassify how the interaction began and whether it became an individualized marketing discussion.Review plan procedures for inbound calls, web forms, chats, walk-ins, referrals, and outbound outreach.Require staff to document the contact source, purpose, consent or opt-out status, and escalation path.TPMO disclaimerProvide the TPMO disclaimer before discussing any plan benefits.Use the approved wording and confirm the required organization and product information.Lock the disclaimer into scripts and workflows so it cannot be skipped or delivered late.Call recordingIdentify required marketing, sales, and enrollment calls, including applicable web-based technology interactions.Confirm which systems, call types, vendors, and subcontractors are covered by the plan contract.Test recording, access, storage, retrieval, quality checks, and failure escalation.Retention reviewDo not rely on an unconfirmed universal retention period.Review the plan’s written retention instructions and applicable state requirements.Reconcile CMS requirements, plan contracts, privacy and records rules, litigation holds, and agency policy.Educational eventsKeep educational content separate from marketing content and use the current event controls. SOAs may be collected at educational events under CY2027 rules.Confirm approved event descriptions, materials, notices, and transition procedures.Track event versions, attendee notices, opt-outs, and staff assignments.Marketing eventsVerify that plan-specific discussions and marketing materials occur only under the applicable marketing-event process.Review plan approval requirements, venue rules, scripts, materials, and reporting.Keep an event file with approvals, materials, attendance information, and incident notes.Event transitionsThe 12-hour gap is removed. A transition is permitted with required notice and a sufficient opportunity for attendees to leave.Confirm the exact notice language and timing required by the plan or state.Train presenters to pause, announce the transition, document the notice, and honor departures.Support-staff accessConfirm what access is necessary for each role.Check vendor, downstream entity, and plan requirements for staff handling beneficiary information.Apply role-based access, minimum necessary permissions, individual logins, and access reviews.Beneficiary opt-outsProvide and document applicable opt-out opportunities.Review contact, event, communication, and plan-specific opt-out rules.Maintain suppression records and ensure opt-outs are visible to agents, call-center staff, and vendors.Escalation proceduresEstablish a process for suspected noncompliance or missing documentation.Follow plan reporting and incident-notification requirements.Define who can pause activity, correct a script, preserve records, and notify leadership or counsel.Audit filesMaintain evidence that required procedures are being followed.Retain plan approvals, training evidence, monitoring results, and requested reports.Organize a complete, access-controlled file that can be retrieved without reconstructing the history later.

1. Confirm individual credentials before marketing activity

A compliant process starts with the people who are permitted to perform the work. Create a credential checklist for every agent, broker, employee, contractor, downstream entity, and support staff member who may participate in Medicare marketing, sales, enrollment, or related administrative activity.

At minimum, your internal review should identify:

  • State license status and expiration date

  • Required appointments or authorizations

  • Plan-specific contracting status

  • Required training and testing completion

  • National Producer Number or other identifying information used in enrollment workflows

  • States and products in which the individual is authorized to operate

  • Date of the most recent credential review

  • Person responsible for approving or suspending access

Support staff may not be agents, but they can still affect compliance. A scheduler, call-center representative, lead manager, or administrative employee might control an appointment, deliver a script, access an SOA, handle a recording, or process an opt-out. Assign access according to job duties rather than giving every user the same permissions.

2. Review the SOA process and PMA timing

The CY2027 change removes the 48-hour wait between a completed SOA and a personal marketing appointment. That does not mean the SOA process disappears.

The practical checklist is:

  1. Identify whether the contact is an interaction for which an SOA is required.

  2. Use the current written SOA process.

  3. Check the applicable rules and exceptions for that interaction.

  4. Confirm that the appointment stays within the documented scope.

  5. Record when and how the SOA was completed.

  6. Make the SOA available for monitoring and audit.

The key training message should be simple: the waiting period is gone; the SOA requirement where applicable remains.

Avoid relying on old scheduling software that automatically blocks an appointment for 48 hours. At the same time, do not remove SOA prompts entirely. Have compliance or operations review every automation change before it reaches agents.

3. Classify inbound and outbound contact correctly

Inbound contact is not automatically outside the compliance workflow. Outbound contact is not the only contact that deserves review.

Your process should distinguish among:

  • Agent- or plan-initiated outreach

  • Beneficiary-initiated calls

  • Web forms and chats

  • Walk-in or unscheduled office conversations

  • Referrals and lead transfers

  • General educational questions

  • Individualized discussions that become marketing or sales conversations

The classification should be documented before the conversation advances. If a general inquiry turns into a discussion of plan benefits, staff should know which controls activate next. This is particularly important when a person moves between a lead form, a call queue, a web chat, and a licensed agent.

A short contact-classification field in your customer relationship management system can help, but the field should not replace training. Staff need a clear escalation path when they are unsure whether a contact has become an individualized marketing interaction.

4. Deliver the TPMO disclaimer before discussing benefits

For CY2027, the TPMO disclaimer must be provided before any discussion of plan benefits. This is a timing requirement, not merely a disclosure that can be added somewhere in a script.

Review each channel:

  • Inbound telephone calls

  • Outbound calls

  • Web-based calls

  • Video appointments

  • One-on-one meetings

  • Event transitions

  • Follow-up calls

  • Calls transferred between support staff and agents

The approved disclaimer should be easy to find, accurately reflect the organizations and products represented, and appear at the correct point in the workflow. If the conversation is recorded, the recording should make it possible to verify that the disclaimer was delivered before benefits were discussed.

Do not place the disclaimer only in a footer, email signature, or general website disclosure if the operating process requires it to be delivered during the interaction. Review the words, timing, delivery method, and documentation together.

5. Validate call recording from end to end

Medicare insurance professionals reviewing a call recording procedure in a modern office

Call recording is a technology control and a people control. A recording system can be active while the process still fails because the wrong calls are excluded, a transfer is not captured, audio is missing, or staff do not know how to report a recording failure.

For each required call category, verify:

  • The interaction is correctly classified

  • Recording starts at the required point

  • The full required interaction is captured

  • Web-based audio is handled correctly when applicable

  • Transfers do not create an unrecorded gap

  • The beneficiary receives any required recording notice

  • The recording is associated with the correct contact and agent

  • Retrieval works for monitoring and audit

  • Access is limited to authorized personnel

  • Failed recordings trigger an escalation and remediation process

Test the process using real operational scenarios, not only a standard inbound call. Include warm transfers, disconnected calls, callbacks, conference calls, remote agents, and vendor-handled interactions.

6. Review retention without adopting an unconfirmed six-year rule

Retention deserves a written review because the applicable period may depend on several overlapping requirements.

Do not state or implement “six years” as a universal rule without approval. A proposed reduction from 10 to 6 years is not confirmed as universal. Retention depends on applicable CMS requirements, plan contracts, state law, privacy and records rules, and agency policy.

Flag for Linda’s explicit approval: any agency-wide change from a 10-year retention practice to a six-year practice, or any policy that treats six years as sufficient for every recording, SOA, enrollment-related record, or audit file.

Your retention review should address:

  • Completed SOAs

  • Call recordings

  • Contact and consent records

  • Event notices and materials

  • Training and testing evidence

  • Credential files

  • Monitoring and corrective-action records

  • Beneficiary opt-out records

  • Vendor and downstream-entity documentation

  • Legal holds or investigation-related preservation

Document the source of each retention period. If two requirements conflict, preserve the record according to the longer or otherwise controlling requirement until the issue is resolved by the appropriate compliance or legal reviewer.

7. Separate educational and marketing events

Older adults attending a clearly divided Medicare educational event in a bright community meeting room

Educational and marketing events should be designed, advertised, staffed, and documented as different event types.

Before an event, confirm:

  • The event type is clearly identified

  • The presentation and materials match that event type

  • Staff know when marketing content may begin

  • The required notices are prepared

  • Attendees are not pressured to remain

  • The event file includes the approved version of materials

  • Any collected information is handled under the applicable privacy process

For CY2027, the 12-hour gap between an educational event and a marketing event is removed. A transition is permitted when the required notice is provided and attendees have a sufficient opportunity to leave before the marketing portion begins.

Train the presenter to make the transition visible and understandable. The announcement should identify that the educational portion is ending and that a marketing event will begin shortly. Staff should allow attendees to leave without pressure and document that the transition notice was given.

Also note that SOAs may be collected at educational events under the CY2027 rules. Update event scripts and forms carefully so this change does not blur the distinction between an educational presentation and a marketing presentation.

8. Build beneficiary opt-outs into the workflow

An opt-out should not be treated as a verbal side note. It should be captured in a system that the people responsible for future contact can actually see.

Review whether your agency can:

  • Record an event attendee’s decision not to stay for marketing

  • Record contact opt-outs

  • Suppress future outreach when required

  • Share suppression information with authorized vendors

  • Prevent staff from re-adding an opted-out individual accidentally

  • Document the date, source, and scope of the opt-out

  • Escalate disputed or unclear requests

Pay particular attention to lead transfers. If contact information moves from one agency, vendor, or call system to another, the opt-out status must move with it.

9. Create escalation procedures for exceptions

A checklist is only useful if employees know what to do when the process fails.

Create a written escalation path for:

  • Missing or incomplete SOA

  • Unclear contact classification

  • Late TPMO disclaimer

  • Failed call recording

  • Unauthorized access to beneficiary information

  • Incorrect event transition notice

  • Missing opt-out documentation

  • Expired credentials

  • Unapproved marketing materials

  • A beneficiary complaint or regulator inquiry

The first response may be to pause the activity, preserve the relevant records, and notify the designated compliance contact. Avoid coaching staff to overwrite, delete, or “fix” records without documentation. Corrections should be traceable.

10. Assemble an audit-ready file

Medicare agency compliance team auditing organized records in a bright conference room

An audit file should show not only what your agency says it does, but also what it actually did.

A practical CY2027 audit file may include:

  • Current written policies and procedures

  • Approved SOA forms and version history

  • TPMO disclaimer language and script controls

  • Recording-system test results

  • Retention review and approval records

  • Event approvals, notices, materials, and transition documentation

  • Credential and training verification

  • Access reviews for support staff and vendors

  • Opt-out and suppression reports

  • Monitoring samples

  • Complaints, incidents, and corrective actions

  • Escalation logs

  • Plan communications and contract requirements

Schedule a pre-AEP review before October 15, 2027, and do not wait until the AEP ends on December 7, 2027 to identify process failures. Test the workflow during normal operations, when staff are handling real calls, events, transfers, and follow-up requests.

Keep eMavio outside your Medicare compliance workflow

eMavio is a lead-generation platform and insurance directory. It is not a licensed insurance agent, broker, or insurance company. eMavio does not provide Medicare advice, plan comparisons, recommendations, guidance, enrollment assistance, or CMS-compliance services, and it does not enroll consumers in Medicare plans.

eMavio does not perform or manage your SOA process, TPMO disclaimer, call recording, retention program, event controls, beneficiary opt-outs, credential review, or audit files. Your agency remains responsible for selecting and operating the systems and procedures required by applicable CMS requirements, plan contracts, state law, privacy rules, and agency policy.

Agents interested in connecting with potential customers through a lead-generation directory can sign up through the eMavio agent page. For additional business-development ideas, see Growing Your Book of Business: Agent Lead Strategies.

Final CY2027 review

Before October 1, 2026, confirm that your agency has:

  • Removed the 48-hour PMA wait without removing applicable SOA controls

  • Reviewed written SOA rules and exceptions for each interaction type

  • Placed the TPMO disclaimer before any plan-benefit discussion

  • Tested required call recording across phone and web-based workflows

  • Completed a retention review without adopting six years as a universal rule

  • Updated educational-event and marketing-event procedures

  • Added the required notice and opportunity to leave during event transitions

  • Documented how SOAs may be collected at educational events

  • Reviewed inbound and outbound contact classification

  • Limited support-staff and vendor access

  • Captured beneficiary opt-outs

  • Defined escalation procedures

  • Built a complete audit file

  • Obtained explicit approval for unresolved legal or retention questions

Medicare marketing compliance works best when it is treated as a connected operating system rather than a collection of isolated forms. Review the rules, your contracts, state requirements, privacy obligations, and agency procedures together: and document each decision before the CY2027 marketing season begins.

TAGS
#medicare compliance
#agent resources
#cms regulations
#medicare marketing
#soa rules
#tpmo disclosures
#health insurance agents
#cy2027

Ready to find your plan?

Important disclosures

eMavio is a marketing and lead-generation platform. We are not an insurance company, agent, broker, or government agency, and we do not sell insurance, provide quotes, determine plan eligibility, or enroll consumers. All insurance information, plan comparisons, and enrollment assistance are provided by independent, state-licensed insurance agents in our network. eMavio is not affiliated with or endorsed by any insurance carrier, the U.S. government, the federal Medicare program, Medicaid, the Health Insurance Marketplace, or HealthCare.gov.

Plan availability, benefits, provider networks, pricing, agent licensing, and premium tax-credit (subsidy) eligibility vary by state, ZIP code, household size, and personal circumstances. Any savings, ratings, or wait-time figures shown are averages and are not a guarantee of your experience or of any specific plan or price.

By submitting your information you agree to be contacted by a licensed agent as described in our TCPA consent. See our Privacy Policy, Terms, all legal disclosures, Do Not Call, and Do Not Sell or Share.