Skip to main content

TPMO Compliance for Medicare Lead Generation: 2026 Rules

D

DL Minds Growth Desk

• 11 min read
Share:
⚡ Quick Summary
  • CMS defines TPMOs broadly enough to capture almost anyone compensated for Medicare lead generation, marketing, sales or enrolment. Assume you are one.
  • Four obligations do most of the work: the standardised disclaimer, full call recording, monthly reporting to plans, and disclosure of subcontracted relationships.
  • The consent rule is the one that reshaped the industry. Sharing beneficiary contact data onward requires prior express written consent naming the recipient, which is fatal to unrestricted multi-buyer distribution.
  • Recent rulemaking streamlines the disclaimer, including removing the SHIP reference, and reduces call-recording retention from ten years to six. Use current text, not last year's.
  • Plans are responsible for knowing where their TPMOs source leads, which is why your traffic provenance gets audited and why sub-ID tracking is a compliance control here, not an analytics nicety.

Most people who generate Medicare leads discover they are a TPMO in one of two ways. Either a carrier's compliance team explains it during onboarding, or a plan partner terminates the relationship and explains it afterwards. The second route is expensive and entirely avoidable.

This is an operator's guide to what the designation means, what it requires you to build, and where the recent rule changes land. It is not legal advice. The authority is 42 CFR Part 422 Subpart V and its Part 423 counterpart, plus each year's Final Rule, and your carrier partners' own contractual requirements frequently go further than the regulation does.

Am I a TPMO?

CMS describes TPMOs as organisations and individuals, including independent agents and brokers, who are compensated to perform lead generation, marketing, sales and enrolment-related functions as part of the chain of enrolment. Read that broadly, because CMS intends it broadly.

ActivityLikely a TPMO?
Running a Medicare comparison site that sells leadsYes
Operating a call centre that transfers to licensed agentsYes
Buying media to drive Medicare form fills for a buyerYes
An independent agent marketing their own servicesYes
A field marketing organisation contracting downstream agentsYes
Publishing purely editorial Medicare education with no compensation tied to enrolmentGenerally no
A vendor supplying software but never touching beneficiaries or leadsGenerally no
📌
The distinguishing question is compensation tied to the chain of enrolment. A site with display ads and no Medicare-specific compensation sits outside. The moment a form fill becomes a paid lead, you are in.

The four obligations that matter most

1
The standardised disclaimer
Required CMS language on marketing materials, disclosing that you do not offer every plan available in the beneficiary's area and directing them to authoritative sources. It must appear in the material, and on calls it must be stated within the first minute.
2
Full call recording
Sales and enrolment calls with beneficiaries recorded in their entirety and retained. Not sampled, not partial, not "the enrolment portion". The entire call.
3
Monthly reporting to plans
Reporting on staff disciplinary actions and instances of non-compliance. This means you need an internal process that produces something to report, and a record of having reported nothing when there was nothing.
4
Subcontractor disclosure
Any downstream relationship used for marketing, lead generation or enrolment must be disclosed. Undisclosed traffic partners are the single most common finding in TPMO audits.
🚫
Obligation three catches people because it is a process requirement, not a content requirement. There is nothing to fix on a page. You either have a functioning internal compliance process that generates monthly reports, or you do not, and an auditor can tell in one question.

The disclaimer, and what changed

The TPMO disclaimer has been revised repeatedly since it was introduced, and recent rulemaking continues to adjust it. Notably, references to State Health Insurance Assistance Programs as a source of information are being removed from the required disclaimer text, with CMS streamlining the content overall.

Two practical implications for anyone running Medicare marketing pages:

Hardcoded disclaimer text is a liability. If the wording lives inside three hundred blog posts, a CMS revision means three hundred edits, and you will miss some. It belongs in a single versioned template component rendered everywhere.

Old text is worse than no text in an audit. A page carrying a superseded disclaimer demonstrates that you were aware of the requirement and failed to maintain it. Version the component, log the version each page rendered, and diarise a review at each Final Rule.

  • Render the disclaimer from one component, never from copy pasted into content
  • Store a version number and effective date with the component, and log which version each page served
  • Apply it to every marketing surface: web pages, landing pages, emails, ad creative and call scripts
  • On calls, deliver it within the first minute, and make it part of the recorded audio
  • Set a calendar reminder tied to the annual Final Rule publication to review the text
  • Keep dated screenshots of representative pages so you can prove what was live and when

This is the change with the largest commercial consequence, and the one most often misunderstood by people arriving from other insurance verticals.

CMS has restricted how TPMOs may share beneficiary contact information collected through marketing activity. In broad terms, onward sharing requires prior express written consent from the beneficiary, and that consent must identify the recipient rather than authorise open-ended distribution.

Set that against how shared leads work in auto insurance. A single form fill is distributed to four or five buyers, often through a ping-post auction, with a generic consent naming a long list of "marketing partners". That model does not survive contact with a rule requiring a named recipient.

Auto insurance shared-lead pattern
  • One form, many buyers
  • Consent references a partner list behind a link
  • Ping-post auction decides distribution
  • Buyer identity unknown at consent time
  • Revenue scales with number of sales per lead
What Medicare requires instead
  • Recipient named at the point of consent
  • Consent language specific and reproducible
  • Distribution decided before, not after, the form
  • One-to-one relationship is the safe default
  • Revenue scales with lead quality, not resale count

The strategic consequence is that Medicare lead generation rewards quality over distribution volume, which is a different business to run. Publishers who tried to port a ping-post architecture across found that the architecture itself was the problem, not the configuration. Our explainer on ping post lead distribution describes the model this rule constrains.

⚠️
TCPA one-to-one consent runs in parallel with the CMS rule. They are separate regimes with overlapping practical effect: name the recipient, keep the artefact, make it reproducible. Building for the stricter of the two is simpler than trying to satisfy each minimally. See TCPA consent for lead buyers.

Call recording and retention

Sales and enrolment calls with beneficiaries must be recorded in their entirety and retained. Recent rulemaking reduces the retention period from ten years to six, which lowers storage cost and administrative burden but changes nothing about the obligation to capture.

RequirementWhat it means for the build
Entire callRecording starts at connect, not at the enrolment step. No pause-and-resume for "the non-sales part".
Retention periodSix years under the streamlined rule. Model storage cost across full AEP call volume, not an average month.
RetrievabilityYou must be able to produce a specific call on request. Searchable by beneficiary identifier, date and agent.
TransfersWarm transfers span two systems. The recording obligation does not pause at the handoff, so both legs need capture.
SecurityRecordings contain health-adjacent and personal data. Encryption at rest, access logging, and a defined retention-expiry job.
6
Years of call-recording retention under the streamlined rule
1
Minute you have to deliver the disclaimer on a call
4
Core TPMO obligations to build for

The transfer row is where systems quietly fail. A publisher captures its own call leg, hands off to a licensed partner, and assumes the partner's recording covers the rest. Then an audit asks for a complete call and neither party has one continuous artefact. Agree the recording architecture with your transfer partner in writing before the first call, not during the first audit.

Why plans audit your traffic sources

CMS has been explicit that it is the plan's responsibility to know how and where their TPMOs obtain leads and enrolments. That obligation flows downhill. Your carrier or FMO partner has to be able to answer for your traffic, which means they will ask you, and "we buy from a vendor" is not an answer that satisfies anyone.

This turns provenance tracking from an analytics preference into a compliance control:

  • Every lead carries a sub-ID identifying the exact placement, creative and partner that produced it
  • Every sub-ID maps to a declared source in a maintained register, reviewed quarterly against actual referrer data
  • Consent artefacts are stored with the lead record, not in a separate system that can drift out of sync
  • A rendered snapshot of the landing page as it appeared at consent time is retained
  • You can kill a single source in one action without disrupting the rest of the operation
  • Anything you cannot trace to a declared source is quarantined rather than sold

That last point is the discipline that separates operations that survive audits from ones that do not. Untraceable leads are not a data-quality problem to clean up later. They are inventory you cannot lawfully monetise.

Building compliance into the stack

1
One disclaimer component, versioned
Rendered on every marketing surface, with version and effective date logged per page view. A rule change becomes one deploy.
2
Consent capture that names the recipient
The recipient is rendered into the consent text dynamically, stored with the lead, and reproducible as displayed. If distribution is decided after the form, the architecture is wrong.
3
Page snapshots on a schedule
Monthly rendered captures of every marketing page to object storage, retained for the audit window. Cheap to build, decisive in a dispute.
4
Recording pipeline with retention expiry
Full-call capture, encrypted storage, searchable index, and an automated job that deletes at the end of the retention window. Keeping recordings forever is its own liability.
5
A source register in version control
Declared partners, sub-ID mappings, effective dates, all reviewed quarterly. When a plan asks where a lead came from, the answer is a query rather than an investigation.
6
A monthly compliance report that actually gets produced
Automate the gathering, keep the review human, and file it whether or not there is anything to report. The record of consistent reporting is itself the evidence.

Common questions

Does the TPMO disclaimer apply to a blog post? It applies to marketing materials. A page whose purpose is to generate Medicare leads is marketing, whatever its format. Purely educational content with no compensation tied to enrolment sits differently, but the boundary is easy to cross without noticing.

Do I need to record calls if I only transfer them? Assume yes for your leg, and agree with the receiving partner in writing who captures what across the handoff. Gaps at the transfer point are a recurring audit finding.

Can I still sell a Medicare lead to more than one buyer? Only where you have consent that names each recipient. Open-ended, partner-list consent is not adequate. In practice this pushes most operations toward one-to-one distribution.

How long do I keep call recordings? Six years under the streamlined rule, but check your carrier contracts, which sometimes require longer, and check the current-year rule before you set a deletion job.

What happens if a plan finds an undisclosed subcontractor? Expect termination of the relationship at minimum. Plans carry the oversight obligation, so an undisclosed downstream partner is their exposure as well as yours, and they resolve it decisively.

Does any of this apply to Medicare Supplement? Medigap is regulated differently, primarily at state level rather than under the CMS MA and Part D marketing rules. Do not assume a single compliance posture covers both.

✅ Bottom Line

If you are paid to generate Medicare leads, build as though you are a TPMO. That means a versioned disclaimer component rather than pasted text, consent that names the recipient before the form is submitted, full-call recording with a defined retention expiry, sub-ID provenance you can query on demand, and a monthly report that actually gets filed. Every one of these is an engineering task, which is good news: engineering tasks stay done.

Need a Medicare funnel that survives a plan audit?
We build consent capture, disclaimer components, page snapshotting and source-provenance tracking for US Medicare marketers and TPMOs.
Get a Free Quote →
D

DL Minds Growth Desk

Digital marketing and web development expert at DL Minds. Passionate about helping businesses grow through innovative technology solutions and strategic digital marketing.

Enjoyed this article?

Subscribe to our newsletter to get more insights and tips delivered straight to your inbox.