The 48-Hour Wait Is Gone. The SOA Itself Is Not.

Before this rule, an agent who collected a signed SOA had to wait 48 hours before holding the actual sales appointment with that beneficiary. That wait applied even if the beneficiary wanted to talk plans immediately. The CY2027 Final Rule removes that waiting period. An agent can now collect a signed SOA and move straight into the appointment — same call, same visit, same day — as long as the SOA is completed first.

That is a real operational change. It removes a scheduling bottleneck that forced agencies to call beneficiaries twice: once for the SOA, once for the appointment two days later, with a real risk the beneficiary lost interest or booked with someone else in between.

The SOA requirement itself is untouched. You still need a written, dated Scope of Appointment, signed before an in-person or personal appointment, listing the specific products to be discussed. CMS removed the delay between signing and meeting — it did not remove the signing. Any workflow that reads this rule as “SOA eliminated” and stops collecting them is reading the headline, not the rule.

Under the old rule, walk-ins and certain educational-event conversions had a narrow exception carved out specifically because the 48-hour wait made same-day conversations otherwise impossible. If a beneficiary walked into an office or stayed after an educational event and wanted to talk plans right then, agencies needed a documented carve-out to do that legally without violating the wait.

Now that the wait is gone for everyone, that carve-out mostly stops mattering — same-day is the general rule, not a special case reserved for walk-ins. What does not go away is the documentation. A walk-in who moves into a plan discussion still needs an SOA completed before that discussion happens, exactly like a scheduled appointment does. The exception got easier to satisfy across the board; it did not get optional for anyone.

The CY2027 Final Rule was published in the Federal Register, and the marketing and communications provisions — including the SOA waiting-period elimination — take effect October 1, 2026, ahead of the 2027 plan year. That timing puts the change live well before Annual Enrollment Period volume hits, which is the point: CMS wants the new workflow tested and stable before the highest-call-volume weeks of the year, not rolled out mid-AEP. If your training materials or scripts still reference a two-day wait after October 1, 2026, they are describing a rule that no longer applies, and any script revision should land before that date, not during AEP itself.

Search “SOA rule 2026” and you will find posts flatly stating the SOA requirement is gone. It is not. What is gone is the delay. This distinction is not pedantic — an agency that stops collecting or documenting SOAs because a blog post said the requirement was “eliminated” is building a real compliance gap on top of a misread headline.

The confusion is understandable. “48-hour SOA rule eliminated” is a technically true headline that omits the one word that matters — “waiting.” Drop that word and the headline reads like the whole requirement disappeared. It did not. The form, the signature, the timestamp, and the requirement that it precede the appointment are all still in force. The safest way to brief a sales team on this change is one sentence: same-day is fine now, skipping the form is not.

With the wait gone, the operational bottleneck moves from scheduling to documentation speed. If your SOA capture is still a mailed or emailed PDF that takes a day to come back signed, you are the one adding delay now, not CMS. That is a self-inflicted bottleneck the rule change was supposed to remove, and it is worth fixing before AEP volume makes the gap obvious. A same-day-capable workflow needs a few things in place:

1. 1A digital SOA that can be signed on the spot — tablet, e-signature link, or recorded verbal consent where your process allows it.
2. 2A timestamp captured at the moment of signing, not just a date field the agent fills in manually.
3. 3A record that ties the SOA to the specific appointment it authorized, so an auditor can see the SOA came before the plan discussion, not after.
4. 4A single log an agent can pull up mid-call to prove the SOA is on file, instead of digging through email or a shared drive.

• SOA can be completed and signed same-day, in person or by phone
• Signing timestamp is captured automatically, not typed in
• SOA is linked to the specific appointment and products discussed
• Agents can retrieve proof of a signed SOA without leaving the call

The SOA timestamp is not just a compliance artifact — it is the cleanest first-touch data point you have. It marks the exact moment a specific lead source turned into a real conversation, which is exactly the kind of event that last-touch attribution misses entirely. ClaimFlow records the SOA timestamp and consent alongside the call log, then ties that same lead through to the policy, commission, and renewal it produced — so the record you keep for CMS is the same record that tells you which lead source is actually worth paying for.

Pair this with the retiming on the disclaimer side: the TPMO disclaimer trigger changed too, and it is worth checking your script against the new disclaimer timing rule in the same pass, since both changes land on the same October 2026 clock.