CMS ACCESS Model Timeline: Application, Build Work-Back, and Five-Year Performance Cadence

This is a cluster article under the CMS ACCESS Model Complete Provider Readiness Guide. The pillar covers the full readiness framework. This article goes deeper on the timeline question: when do you decide to apply, when do you build what, and how does the operating cadence evolve across the five performance years.

The single most common mistake we see in ACCESS readiness work is collapsing an 18-month build into 9 months because the application timeline created urgency. The application timeline does create urgency. It does not change the build timeline. ACOs that compress the build either underperform in performance year one or quietly miss requirements that show up in CMS scoring later.

Application timeline

CMS opens application windows for each cohort entry. Performance year one (January 2026) applications closed in mid-2025. Subsequent cohort entries (January 2027, January 2028) follow a similar pattern. Watch for CMMI announcements roughly 12 months ahead of each performance year start.

Application timing decisions have three components.

Readiness scoring. Score yourself against the 12-capability readiness checklist. If you score 8 or above, performance year one is realistic. If you score 5 to 7, performance year two is the better fit. Below 5, plan for performance year three.

Financial capacity for downside risk. ACCESS is a single risk track with progressive downside exposure. Performance year one downside is modest, but by performance year three the asymmetry of upside-to-downside narrows. ACO boards should model expected performance under both optimistic and conservative scenarios before committing.

Clinical leadership bandwidth. PROMs adoption and outcome attainment are clinical-leadership-driven changes. If your CMO and clinical operations leadership are mid-implementation on a major initiative, layering ACCESS readiness on top creates execution risk that the platform cannot solve.

The decision is rarely close once these three are honestly assessed. Most ACOs that consider performance year one entry should plan for performance year two if any of the three is meaningfully weak.

18-month build work-back

For a January performance year start, the work-back from go-live looks like this.

Months 18 to 12 out: Architecture and platform decisions. Lakehouse vendor (Microsoft Fabric, Databricks, Snowflake) chosen based on existing tenancy, team skills, and contract footprint. Data residency stance documented. Application timeline aligned with build milestones. Clinical-content governance forum stood up.

Months 12 to 9 out: Foundation and first FHIR ingestion. Platform foundation live including identity, network isolation, BAA-covered cloud zones, baseline governance. First FHIR ingestion pipeline (typically your largest EHR participant) ingesting USCDI v3 core resources into bronze layer.

Months 9 to 6 out: Multi-EHR FHIR and claims. Multi-EHR FHIR ingestion live across participating provider organizations. Payer claims feeds integrated for ACCESS-eligible attributed population. Canonical patient-encounter-claim graph in silver. Attribution logic live.

Months 6 to 3 out: PROMs, HCC NLP, outcome attainment in pilot. PROMs platform integrated across delivery channels with workflow trained. First sustained-response measurement period running. HCC NLP soft-launched on a single specialty or pod with a labeled gold-standard set. Outcome attainment scoring running on a defined goal set with at least one chronic condition.

Months 3 to 0 out: Multi-pillar shadow run. Outcome attainment dashboards live for clinical leadership. PROMs response rates trending toward 40 percent. HCC NLP rolled out across attributed population with defensible audit trail. Care management workflow integration in clinician daily UI.

Performance year start: Cutover and stabilization. Production cutover with documented rollback. 30-day stabilization window with active engineering and clinical operations support. Weekly performance reviews against scoring framework.

ACOs inside 9 months from performance year start with no FHIR build underway should plan for performance year two entry rather than rush. The compressed build does not produce a defensible result.

Performance year 1 operating cadence

Three rhythms have to ship before performance year start.

Weekly clinical-operations rhythm. Care team review of PROMs response rates, outcome attainment dashboards, HCC NLP suggestion volume and confirmation rates, and care management worklist drift. Named accountability per panel.

Monthly leadership review. ACO leadership review of trajectory against scoring framework, with formal go-or-no-go decisions on workflow changes or platform investments.

Quarterly platform retrospective. Engineering and clinical informatics review of platform health (data quality, freshness, accuracy of HCC NLP, drift on outcome attainment scoring) and the runbook for the next quarter's evolution.

The cadence has to be in place before performance year start. Mid-year course corrections are operationally expensive. Building cadence muscle in performance year one prepares the operating model for the more demanding performance years two through five.

How risk-track economics evolve

Performance year one is structured to give well-prepared ACOs asymmetric upside with limited downside. The minimum savings rate (MSR) and minimum loss rate (MLR) thresholds are set so that small variances do not trigger settlement in either direction.

By performance year three, the MSR / MLR asymmetry narrows. Downside exposure becomes meaningful enough that ACO operators have to be confident in their performance trajectory before committing.

By performance year five, the risk track is fully matured. The economic decision is no longer about year one. It is about whether your platform and operating model produce a strengthening trajectory across measurement periods.

The strategic implication for your build: do not build a platform that is just enough for performance year one. Build a platform that supports continuous improvement across performance years two through five. Platforms built to a PY1 readiness ceiling underperform platforms built thinner but with strong continuous-improvement loops.

Decision points along the timeline

Three decision points typically emerge during a performance year that ACO leadership has to handle.

End of Q1 stabilization (March or April of performance year). Is the platform stable enough to support performance year scoring, or does CMS scoring need to be paused and platform stabilization prioritized? Rare but consequential. Has happened on at least 1 in 5 ACO platform builds we have observed.

Mid-year trajectory check (June or July of performance year). Is the trajectory tracking toward favorable scoring or unfavorable? If unfavorable, what workflow or platform changes can be committed in the second half of the year that will measurably move the score?

Performance year close-out (December into Q1 of next performance year). What did and did not work this year? What are the priority improvements for performance year two? Captured in a formal retrospective with engineering, clinical, and executive leadership.

The retrospective at performance year close-out is the most underrated of the three. ACOs that run it well sustain trajectory across the five-year program. ACOs that skip it or run it superficially struggle to compound year-over-year.

For deeper coverage of the operating model that runs on top of the platform, see our ACO data platform consulting deep-dive.

Where to start today

Three concrete next steps depending on where you are.

More than 12 months from performance year start. Run a readiness assessment, decide between performance year one and performance year two entry, and start the architecture work. The earlier you decide, the cleaner the build.

Inside 12 months and behind on the build. Have an honest conversation about performance year two entry. The compressed PY1 build rarely produces a defensible result, and PY2 entry costs you nothing relative to a poor PY1 performance.

Mid-build with timeline pressure. Run a focused readiness review. Identify the two or three highest-leverage gaps. Decide whether to absorb them in PY1 or accept their absence as a known shortfall going into the performance year. The honest acknowledgment beats the heroic build that breaks at month 11.

---

How DATA4AI helps: We run readiness reviews that produce a defensible application-timing decision and a scoped 18-month build plan. We also embed for the build itself. Senior practitioners only, no handoffs. Book a working session to walk your timeline with us, or download the readiness checklist to score yourself first.