The announcement gives you six weeks and no plan
Salesforce published its Winter ’27 announcement on August 31, 2026, and the one date in it that matters for planning is October 12, 2026, when the post says the release goes generally available. That is six weeks from today. The post lists ten featured items and five further updates, and none of them carries a date other than October 12.
Our sibling pieces take the release apart by theme. This one is about the calendar. A release announcement is written to be forwarded, and by Wednesday, September 2, most platform owners will have it in their inbox from three directions. The useful response is a dated plan with names on it, and the post gives you enough to start one this afternoon.
Sort the fifteen items into three piles before anyone reads them twice
Every item in the post lands in one of three piles for your org. The first pile is what arrives on October 12 whether you do anything or not, such as changes to the Service Rep Assistant if your service team already uses it. The second pile is what you would have to turn on, and that is most of the list. Agent Skills and Plugins, with what Salesforce says is over 100 prebuilt skills, and Autonomous Scheduling with Agentforce Voice both sit here. The third pile is what does not apply to you this cycle. If you run no commerce site, the 13 percent conversion lift Salesforce quotes for Agentic Commerce Search is someone else's number, and Third-Party Agent Orchestration matters only if you already have A2A-compliant agents on AWS, Azure, or Google.
The sort takes an hour and it is the difference between a calendar and a wish list. We described the same triage for change notes in a better way to read change notes, and the rule holds for an announcement. Pile one gets a regression owner. Pile two gets a decision owner. Pile three gets a line in the register saying you looked, so nobody asks again in November.
Work backwards from October 12 and give each week a job
With the piles sorted, the dates fall out. By Friday, September 4, the sort is written down and shared with the admins, the integration lead and whoever owns the service desk queue. In the week of September 7, each pile one and pile two item gets a named owner, and the owner's first job is to write one sentence on what would break. In the week of September 14, the pile one items are checked in a sandbox. The post does not say when sandboxes pick up the release, and that is the first question we would put to the account team, since it decides whether September 14 is realistic.
The week of September 21 is the change board. Pile two owners bring a yes, a no, or a not yet for each item, and a not yet needs a date of its own. The week of September 28 is for whatever the sandbox check turned up. Monday, October 5, is the freeze decision: what reaches production untouched on October 12, what gets held, and who is on call that week. Our release checklist for shared solutions was written for internal releases, and the same conversation works for a vendor release with Salesforce as the maker.
The questions the post leaves open need a date as well
Some calendar entries are questions rather than tasks. The post describes Adaptive Experiences and Dynamic Plans, where the Service Rep Assistant updates a resolution plan while a conversation is still happening, and says four customers are live with it, including PowerSchool with more than 550 users. What it does not say is whether an earlier version of the plan is kept. That question belongs on the calendar with a name and a date, so it is asked by September 11 rather than discovered on October 13.
Two more we would book. Who each agent runs as, and whether that user can see fields the human rep never could, which our companion piece on governed CRM data works through. And who owns a run that is still going when the October 12 change lands, which is the argument in who owns a longer-running agent. A question with a date gets answered. A question on a slide without one gets forwarded.
The week after October 12 belongs on the calendar too
Most readiness plans stop at the release date, and that is where they fail. Book the week of October 12 as a watch week, with one person reading the agent run logs each morning and a fifteen minute call where pile one owners report what changed. The post says the Service Rep Assistant program has passed 100 customers. If you are one of them, yours is the team most likely to see behaviour move on day one, and the person on that morning call should be the one who can switch the assistant off.
Then book a review for Friday, October 23. The question for that review is whether any pile two item should move from not yet to yes, now that pile one has settled. The agent readiness check gives you the questions for that meeting, and the Agentforce hub has the rest.
Open the calendar before you forward the post
Before you forward the announcement, open the shared calendar, put October 12 on it as the fixed point, and book the September 4 sort with the three people who will do the work. Everything else on the plan can move. That first meeting decides whether Winter ’27 arrives in your org on a date you chose or on a date you noticed.
