ACO LEAD Model: Why 2027 Will Reward ACOs That Can Execute Between Visits

July 2, 2026

By Jay Chowdappa, MD, co-founder and CEO, Zynix AI · Updated October 1, 2026

Key takeaways

The ACO LEAD Model, which succeeds ACO REACH on January 1, 2027 and runs through 2036, will reward ACOs that can act between visits, not just see who needs attention. Readiness depends on execution: identifying events fast, prioritizing the work, reaching patients at scale, documenting every attempt and routing clinical issues to people.

  • CMS says LEAD puts more focus on preventive care, regular check-ins, outreach before problems escalate and coordination between visits.
  • Its 10-year performance period without benchmark rebasing means infrastructure choices made in 2026 shape results for a decade.
  • LEAD is designed to draw in smaller, independent and rural practices, which have the least room to solve workflow problems by adding staff.
  • The five capabilities to test are patient identification, workflow prioritization, outreach capacity, documentation and loop closure, and exception handling.
  • AI helps only when it moves work from identified to completed, with human review wherever clinical judgment is needed.

The ACO LEAD Model should not be treated as just another payment model update. It is a signal about where accountable care is going.

CMS has positioned LEAD, or Long-term Enhanced ACO Design, as the successor to ACO REACH. The model is set to launch after ACO REACH concludes at the end of 2026 and run for ten years, from January 1, 2027 through December 31, 2036. That timeline matters. A ten-year model changes how ACOs should think about infrastructure. It gives accountable care organizations a longer planning window, but it also raises the bar on whether they can build operating capacity that lasts.

The most important detail is not only the payment methodology. It is the operational direction. CMS says LEAD will put more focus on preventive care, regular patient check-ins, outreach before problems escalate, and coordination between visits. That is the exact layer where many ACOs struggle.

Most ACOs already know which patients need attention. They have dashboards, risk scores, care gap reports, discharge feeds, attribution files, and quality reports. They can identify who missed an annual wellness visit, who needs transitional care management, who has an open quality gap, and who may become high-cost if no one intervenes.

The failure point is not visibility. The failure point is follow-through.

Why the LEAD model changes the operating question

For ACO leaders, LEAD shifts the question from "Do we have the data?" to "Can we complete the work the data creates?"

That distinction matters because accountable care performance is built between visits. A discharged patient does not become safer because a discharge feed arrived. A care gap does not close because it appeared on a dashboard. A high-risk patient does not stabilize because a model assigned a score. Each insight creates operational work.

Someone has to:

  • identify the event,
  • confirm eligibility,
  • call the patient,
  • schedule the follow-up,
  • document the attempt,
  • escalate the clinical issue,
  • update the workflow, and
  • keep trying when the first call goes unanswered.
Now multiply every discharge, overdue preventive visit, care gap, and unresolved risk across thousands of patients, multiple practices, multiple EHRs, multiple payers, and different practice-level workflows. That is where accountable care becomes difficult in daily execution.

Why smaller and rural ACOs need leverage

LEAD is designed to appeal to a broader mix of providers, including smaller, independent, rural-based practices and organizations serving high-needs populations. These organizations often have the most to gain from accountable care, but the least room for administrative waste.

They cannot solve every workflow problem by adding staff. Manual work scales linearly. This is where execution infrastructure becomes a strategic requirement, not a technology preference.

Execution infrastructure is not another dashboard. It is the operating layer that turns insight into completed work: identifying eligible patients, prioritizing actions, initiating outreach, supporting scheduling, documenting attempts, surfacing exceptions, and routing clinical issues to the right human team.

The goal is not to replace care teams. The goal is to remove repetitive operational burden so care teams can focus on clinical judgment and patient relationships.

The five execution capabilities ACOs need before 2027

An ACO preparing for LEAD should evaluate five execution capabilities.

1. Patient identification

Can the organization detect events and opportunities fast enough? This includes discharge events, open care gaps, high-risk patients, preventive care opportunities, missed visits, and patients who need a timely check-in. Speed matters because many accountable care workflows lose value when the response is late. A slow TCM workflow becomes a missed opportunity. A high-risk patient who waits too long may become an avoidable emergency department visit.

2. Workflow prioritization

Can the organization determine which actions matter most based on risk, timing, contract impact, quality performance, and clinical urgency? Not every task carries the same weight. A mature ACO operating model should help teams understand what needs action now, what can wait, and what should be escalated.

3. Outreach capacity

Can the organization reach enough patients through voice, SMS, and other channels without adding proportional headcount? Outreach is one of the most underestimated constraints in accountable care. It requires persistence, timing, personalization, and documentation. One unanswered call should not end the workflow.

4. Documentation and loop closure

Can every attempt, response, escalation, and completed action be captured without creating additional administrative burden? If the action is not documented, the organization stays blind. If documentation is too manual, staff capacity disappears into recordkeeping instead of patient engagement.

5. Exception handling

Can clinical issues, appointment barriers, language needs, transportation concerns, unanswered outreach, and unresolved cases be routed to humans quickly? The strongest AI-enabled workflows are not unsupervised. They know when to execute and when to hand off to a human-in-the-loop.

Why healthcare AI matters here

Healthcare AI becomes relevant to LEAD readiness only if it is applied to the right problem.

Many AI conversations in healthcare still center on documentation, coding, summarization, and clinical decision support. Those use cases matter, but they do not fully solve the accountable care problem. ACOs do not only need AI that helps someone write faster or find information faster. They need AI that helps work move from identified to completed.

That is the distinction between AI assistance and AI execution.

For LEAD readiness, leaders should ask one simple question: when the model creates an incentive to check in earlier, coordinate faster, and prevent avoidable utilization, do we have the operating capacity to act consistently?

If the answer depends entirely on manual calling, manual worklists, and care managers toggling between systems, the organization is exposed. The problem may show up as lagging TCM completion, missed AWVs, unresolved care gaps, late documentation, incomplete follow-up, or avoidable emergency department visits.

The strategic window is now

LEAD creates a strategic moment because infrastructure choices made in 2026 will shape performance in 2027 and beyond. Waiting until the model begins creates risk. By the time performance starts, the organization should already understand which workflows can be automated, which require human review, which practices need support, and which patient segments are falling through the cracks.

At Zynix AI, we believe that value-based care does not fail because physicians do not care. It fails when the operating model cannot keep up with the volume of work.

ACO leaders should not prepare for LEAD by buying more analytics alone. They should build a repeatable execution layer around the workflows that drive cost, quality, and patient engagement:

Core workflows that drive cost management, quality performance, and patient engagement under LEAD

A repeatable execution layer built around these workflows is what will separate ACOs that capture shared savings from those that leave performance on the table under LEAD.

The ACOs that win under LEAD will not be the ones with the most reports. They will be the ones with the strongest follow-through.

LEAD is a payment model on paper. For operators, it is a capacity test in practice. Accepting accountability was never the hard part. Executing it across every patient, practice, and workflow that matters is what will separate performers from reporters under LEAD.

Frequently asked questions

When does the CMS LEAD Model start, and how long does it run?

LEAD is a voluntary CMS Innovation Center model that succeeds ACO REACH after REACH concludes at the end of 2026. It runs for ten years, from January 1, 2027 through December 31, 2036, and CMS describes the 10-year performance period as a predictable window without benchmark rebasing. That long horizon is why infrastructure decisions made now carry through the whole model.

What execution capabilities does an ACO need for LEAD?

Five, in practice: identifying events such as discharges and open gaps quickly, prioritizing actions by risk, timing and contract impact, reaching patients by voice and SMS without proportional headcount, documenting every attempt and closing the loop, and routing clinical issues and access barriers to people fast. Many ACOs already have the analytics; the gap is the operating capacity to finish the work.

Can smaller, independent or rural practices take part in LEAD?

Yes. CMS designed LEAD to appeal to a broader mix of providers, including those new to ACOs such as smaller, independent or rural-based practices, and to better serve high-needs patients such as people dually eligible for Medicare and Medicaid. Those organizations have the least room for administrative waste, so outreach and gap programs that scale without adding staff matter most for them.

Which workflows should an ACO automate first to prepare for LEAD?

Start with workflows that drive cost, quality and patient engagement and already follow clear rules: post-discharge follow-up, annual wellness visits, HCC suspect review, quality gaps, high-risk outreach and after-hours access. Map each step, decide which steps agents can run, which need human review and which stay human-owned, and give every step an owner through care plans for TCM, AWV and gap closure.

Is population health analytics enough to succeed under LEAD?

No. Analytics shows who needs attention, but LEAD rewards what happens between visits: the call that reaches a discharged patient, the visit that gets scheduled, the gap that gets closed and the clinical issue that reaches a clinician in time. If that work depends on manual calling and worklists, performance will lag no matter how good the dashboards are.

Related reading

Source notes

CMS: LEAD (Long-term Enhanced ACO Design) Model. https://www.cms.gov/priorities/innovation/innovation-models/lead

About the author

Jay Chowdappa, MD is co-founder and CEO of Zynix AI. He is a physician, and ACOs led by him generated $300M+ in shared savings before he started Zynix AI to help care teams follow through on what their data already shows.

Ready to close the execution gap?

See how Zynix AI helps ACOs turn population health analytics into completed care actions at scale.

Book a 30-min walkthrough →

Explore More Insights

Visit Our Blog