Scope of Appointment Record Keeping for the 2027 AEP
CMS removed the 48-hour Scope of Appointment wait for the 2027 plan year, but the SOA itself, its required content, and its ten-year retention window are unchanged. Here's what to fix before AEP.
What changed, in one sentence For the 2027 plan year, CMS removed the mandatory 48-hour wait between a signed Scope of Appointment (SOA) and the personal marketing appointment it covers, defined "personal marketing appointment" for the first time, and now requires the SOA to be in writing for in-person meetings — but the SOA itself, and the rules for keeping it on file, have not gone away. If your agency built its AEP process around the old 48-hour rule, the workflow changes. The record-keeping obligation does not. Here is what actually changed, what did not, and how to keep the paper trail (or the digital trail) in shape for the 2027 Annual Enrollment Period. The three requirements that haven't moved Before getting into what's new, it's worth being clear about what CMS still requires of every agent and broker who holds a personal marketing appointment with a Medicare beneficiary, per the Medicare Communications and Marketing Guidelines : An SOA is still required before the appointment. The CY2027 Agent and Broker Training & Testing Guidelines confirm that collection of an SOA is required prior to any personal marketing appointment as defined under 42 CFR §§ 422.2264(c)(3) and 423.2264(c)(3). It applies to both directions of contact. The same guidance is explicit that an SOA is required "for plan/agent/broker-initiated outbound contact and for beneficiary-initiated inbound contact (including walk-ins, unscheduled calls and web-based chats, and web-based forms), as long as the contact is tailored to an individual or small group for purposes of discussing marketing topics" — regardless of who started the conversation. You still need a new one for a new product type. The Medicare Communications and Marketing Guidelines state that a new SOA is required if the beneficiary asks to discuss a different plan type than the one previously agreed to. What is exempt: marketing events. CMS is direct about this — an SOA is not required for a marketing event, because a room full of prospects at a seminar does not meet the definition of a personal marketing appointment. The four things that actually changed for 2027 The CY2027 Agent and Broker Training & Testing Guidelines list four specific changes to the SOA rule: Removed the 48-hour waiting period between SOA completion and the personal marketing appointment. Defined "personal marketing appointment" for the first time in the regulation text. Clarified that an SOA is required for every appointment that meets that new definition. Required the SOA to be in writing for in-person marketing appointments specifically. In practice, the change agents will feel most is the first one. Under the old rule, a beneficiary who called in on a Tuesday asking for a Medicare Advantage comparison usually could not sit down with an agent until Thursday, unless the call fell inside one of CMS's narrow exceptions (a walk-in, or a request made within 48 hours of the end of a valid election period). For the 2027 AEP, that same-day conversation is allowed again, as long as a compliant SOA is documented before the appointment starts. That is a scheduling win. It is not a record-keeping shortcut. The fourth change actually adds a requirement: an in-person appointment now needs the SOA in writing, where CMS previously allowed some flexibility (a form or a recorded call) depending on the channel. What CMS still expects on the form or the recording Whether it is a signed form or a recorded phone call, CMS guidance is specific about the minimum content: the product types to be discussed, and the date of the appointment. A generic "yes, they agreed to meet with me" note in a CRM field is not a Scope of Appointment — it has to name the products on the table, so that if the conversation drifts into a product the beneficiary never agreed to discuss, that drift is visible on paper. Retention has not changed either. Medicare Advantage and Part D record-keeping requirements call for agents and brokers to retain SOA documentation, along with other marketing and enrollment records, for a period of ten years . That is a decade of forms, recordings and metadata that has to survive employee turnover, a change of CRM, and the eventual retirement of whoever collected it. Building an SOA record-keeping system that survives an audit An audit does not ask whether you know the rule. It asks you to produce a specific document, for a specific client, from a specific date, in under a few minutes. A checklist that gets you there: Capture the SOA on the same record as everything else about that client. An SOA saved as a loose PDF in someone's email, disconnected from the client's file, is a document you will not find in year seven of the retention window. Record the product types and the appointment date on the form itself , not just in a follow-up note, so the scope is provable without cross-referencing three systems. Treat inbound contact the same as outbound. Since the rule applies to beneficiary-initiated walk-ins, calls, chats and web forms as much as to agent-initiated outreach, a workflow that only prompts for an SOA on outbound campaigns will miss a real share of appointments that need one. Flag a second SOA when the topic changes mid-conversation. If a Medicare Supplement conversation turns into a Medicare Advantage conversation, that is a new SOA, not an amendment to the old one. Keep an access log, not just a storage folder. A ten-year retention requirement is only useful if you can also show who viewed, exported or edited the document during those ten years — which is a HIPAA and CMS audit question in its own right, not just a storage question. Decide now who owns the January cleanup. AEP generates the largest single batch of SOAs an agency will collect all year; someone should own confirming that every one of them is where it belongs before the next enrollment period stacks another year on top. Example: a five-agent Medicare agency during AEP This is an illustrative example, not a real agency. A five-agent Medicare-focused shop runs an AEP call campaign, but also fields a steady stream of inbound calls from clients who saw a plan change letter and want to talk it through. Under the old rule, an agent taking an inbound call on October 20th had to schedule the actual appointment for October 22nd at the earliest, and a share of those clients never called back. Under the 2027 rule, the agent can collect a compliant SOA — product types, date, method of documentation — and move directly into the appointment, as long as it is documented before the conversation turns into a personal marketing appointment. The record-keeping load does not shrink, though: the agency still needs the SOA attached to that client's record, dated correctly, and retrievable a decade later if a state insurance department or CMS program audit asks for it. Where this fits in a Medicare agent's CRM Whatever tool an agency uses for intake and client records, an SOA process needs to answer three questions on demand: where is the signed form, what products did it cover, and who has touched it since. In AgencyView, an intake form can include a built-in Scope of Appointment section that captures the appointment type, the products of interest and the meeting details as part of the same intake session as the rest of the client's information. The signed document itself — whether it is the form or a related consent or HIPAA authorization — can be uploaded straight to that client's record and reviewed later as a signed PDF, rather than living in a separate folder disconnected from the contact. If the appointment happens over a recorded call instead of a form, calls placed through the RingCentral integration can be recorded and transcribed, so the SOA and the conversation that followed it sit on the same timeline. And because every view, export or edit of a compliance document is written to an audit trail, the…
Where AgencyView fits
Keep reading
All articles · AgencyView