Your Benchmark Exposure Review Should Start Before the Final Benchmark Arrives
Waiting for the final number leaves very little room to change the story.
The final benchmark may arrive as a number, but it does not begin as one.
It develops through beneficiary assignment, population risk, historical and regional expenditures, utilization patterns, participant composition, quality performance, and the policies CMS applies during financial reconciliation.
By the time the final calculation reaches an ACO’s leadership team, many of the underlying conditions have already been in motion for months.
This creates a familiar problem for ACO CFOs and contracting leaders. They may know the final benchmark will determine an important part of the organization’s financial story, but they may not have enough visibility into the signals shaping that story today.
Waiting for the final benchmark to begin the review is a little like waiting for the closing statement to decide whether a contract was affordable. The math may be accurate. The timing is not especially helpful.
A Benchmark Exposure Review should begin earlier.
Its purpose is not to recreate CMS’s final reconciliation or promise a precise shared-savings result. It identifies material changes, tests assumptions, estimates plausible exposure, and gives the organization time to respond.
The final benchmark is a lagging result
CMS uses an ACO’s benchmark to evaluate financial performance under the Medicare Shared Savings Program. The methodology involves several elements, including expenditures for assigned beneficiaries, applicable risk adjustment, regional expenditure information, benchmark updates, and other program-specific adjustments.
Beneficiary assignment is central to that process. CMS states that assignment helps calculate the financial benchmark, assess financial performance, and determine the beneficiary population used for quality reporting. CMS Shared Savings Program Guidance
That means attribution is not merely a headcount exercise.
A population can remain similar in size while changing materially in clinical complexity, expenditure history, utilization patterns, geographic concentration, or provider relationships. A stable number at the top of a report can conceal considerable movement underneath it.
CMS calculates the benchmark using its methodology. However, an ACO can still examine the operational and financial signals that may influence its position.
A practical review should address five areas:
Population movement
Risk documentation
Utilization concentration
Coding integrity
Operational response
These five steps will not produce a crystal ball. They will produce something more useful: a defensible view of emerging exposure.
Step 1: Review population movement
Begin with the population, but do not stop at total assigned lives.
A stable beneficiary count does not necessarily indicate a stable financial profile.
The review should identify:
Newly assigned beneficiaries
Beneficiaries no longer assigned
Movement among Medicare enrollment types
Changes in primary-care utilization
Changes in participant or provider relationships
Geographic shifts within the service area
Changes involving high-cost or clinically complex populations
Voluntary alignment patterns, when applicable
Participant-list changes that may affect assignment
The central question is not simply, “How many beneficiaries do we have?”
It is, “Who is now included in the population, who is no longer included, and how does that movement change our financial assumptions?”
Suppose an ACO’s total assigned population changes very little from one period to the next. Leadership may reasonably assume that its expected expenditure profile is also stable.
A closer review may show otherwise.
The ACO may have gained beneficiaries with greater care-management needs while losing beneficiaries with lower historical utilization. Participant changes may have shifted the geographic or specialty mix. New patterns of primary-care use may be influencing assignment. A group of beneficiaries who previously received services inside the ACO may now be receiving more care elsewhere.
None of these observations independently determines the final benchmark. Together, however, they may change the ACO’s exposure.
Finance, contracting, clinical operations, analytics, and quality teams should therefore evaluate population movement. Assignment affects more than one department, so reviewing it in one departmental silo is an excellent way to obtain an incomplete answer with impressive formatting.
Step 2: Evaluate risk documentation
Once the ACO understands population movement, it should examine whether documented risk accurately reflects the clinical reality of the assigned population.
This is not an invitation to manufacture diagnoses, inflate risk scores, or treat coding intensity as a substitute for care management.
The objective is accuracy.
CMS applies the applicable Hierarchical Condition Category risk-adjustment methodology when calculating beneficiary risk scores used in Shared Savings Program calculations. The methodology and applicable models depend on the ACO’s agreement-period timing and other program requirements. CMS Shared Savings and Losses, Assignment, and Quality Performance Standard Methodology
An ACO’s review should ask:
Are clinically active conditions documented appropriately?
Are diagnoses supported by the medical record?
Are chronic conditions being evaluated and managed during the relevant period?
Are documentation practices consistent across participants?
Are some locations or specialties producing unusual risk patterns?
Do risk trends correspond with observed clinical complexity?
Are changes in risk scores explainable?
Are education, audit, and correction processes appropriately separated?
Risk documentation should be complete, current, and defensible.
If the data suggest that population complexity is increasing while documented risk remains flat or declines, the organization should investigate. The explanation could involve documentation gaps, population turnover, coding variation, data timing, model changes, or legitimate differences in clinical status.
The review should not begin with a preferred conclusion. It should begin with the discrepancy.
For CFOs, the key issue is whether financial projections rely on risk assumptions supported by the available clinical and coding evidence.
For contracting leaders, the issue is whether those assumptions remain credible when evaluating future performance obligations.
Step 3: Identify utilization concentration
Aggregate expenditure trends can tell leadership that spending changed.
They do not always explain where, why, or whether the organization can respond.
A Benchmark Exposure Review should identify the services, settings, populations, providers, and episodes driving utilization concentration.
The analysis may examine:
Inpatient admissions
Emergency department use
Skilled nursing facility utilization
Post-acute care patterns
Specialty-service concentration
Out-of-network or out-of-ACO utilization
High-cost drug use
Diagnostic and procedural spending
Readmissions
Potentially avoidable acute-care use
High-cost beneficiary cohorts
Geographic differences
Provider-level variation
The purpose is not to label every increase as inappropriate.
Higher spending can reflect necessary care, changes in population complexity, access limitations, local market conditions, or clinically appropriate treatment. A responsible review distinguishes between expenditure concentration and avoidable expenditure.
That distinction prevents the analysis from becoming a cost-cutting scavenger hunt.
The more useful questions are:
Which categories are driving the change?
Is the change temporary or persistent?
Does it involve a small number of beneficiaries or a broader pattern?
Is the utilization clinically expected?
Did the care occur inside or outside the ACO’s influence?
Does the organization have an operational intervention available?
What would happen if the trend continued?
A concentration analysis also improves forecasting.
Instead of using one broad assumption for total expenditure growth, the ACO can model the effects of specific utilization patterns. That produces a more credible range of financial outcomes and a clearer list of operational priorities.
Step 4: Test coding integrity
Coding integrity connects clinical documentation, claims, analytics, quality reporting, and financial forecasting.
When those functions are misaligned, the ACO may make decisions based on several versions of the truth.
The review should test whether:
Claims data align with documented services
Diagnosis coding is supported and current
Provider and participant identifiers are accurate
Coding patterns differ unexpectedly across locations
Duplicate, missing, or delayed data affect the analysis
Changes in service mix explain changes in expenditures
Clinical, financial, and reporting systems classify populations consistently
Quality-reporting data reconcile with the attributed population
Vendor reports can be traced to source data
Corrections are documented and monitored
Coding integrity is broader than coding accuracy at the individual claim level.
An accurately coded claim can still enter an analytically unreliable environment if the clinician roster is outdated, the beneficiary population is mismatched, the data feed is incomplete, or the reporting system applies inconsistent classifications.
This is where ACOs should compare claims, clinical, quality, and financial data rather than reviewing each stream separately.
If one report describes a rising-risk population, another shows declining clinical complexity, and a third cannot account for several participants, the answer is not to select the most comforting report.
The answer is reconciliation.
Step 5: Define the operational response
A Benchmark Exposure Review is not complete when the organization identifies risk.
It is complete when leadership decides what to do about it.
Every material finding should have:
A named owner
A defined action
A completion date
A measurement method
An escalation threshold
A financial or operational rationale
A scheduled follow-up review
Potential responses may include:
Improving care-management outreach
Reviewing transitions of care
Addressing avoidable emergency department use
Strengthening post-acute coordination
Correcting participant or provider data
Validating documentation and coding workflows
Investigating geographic or specialty-level variation
Refining network-management strategies
Updating financial forecasts
Revising contract assumptions
Escalating unresolved vendor or data issues
Preparing leadership and participant communications
Not every signal will support an immediate intervention. Some findings may require continued monitoring. Others may be outside the ACO’s direct control.
That does not make them irrelevant.
A CFO still needs to understand risks the organization cannot fully control. A contracting leader still needs to account for them when evaluating terms, reserves, risk corridors, participation decisions, and future obligations.
Operational response includes deciding what to change, what to monitor, what to escalate, and what to price into the forecast.
Build scenarios before committing to one forecast
The final benchmark will be calculated under CMS rules, not according to the ACO’s internal forecast.
For that reason, an exposure review should produce a range of scenarios rather than one suspiciously confident number.
At minimum, model:
Expected scenario
Assume current population, risk, and utilization trends continue within reasonable ranges.
Adverse scenario
Model the effect of unfavorable population movement, persistent high-cost utilization, weaker risk capture, or unresolved data problems.
Improvement scenario
Estimate the effect of realistic operational improvements. Avoid treating every intervention as immediately successful or assuming that clinical changes will produce instant financial results.
Each scenario should document:
Population assumptions
Risk assumptions
Utilization assumptions
Data limitations
Operational dependencies
Timing considerations
Potential financial range
Confidence level
The exercise is not intended to predict CMS’s final calculation exactly.
It is intended to show leadership which assumptions carry the greatest exposure and which operational decisions may still matter.
The review must be cross-functional
Benchmark exposure is too consequential to be owned by finance alone.
Finance may understand the forecast but not the clinical workflow behind the utilization. Clinical leadership may understand the population but not the contractual consequences. Coding teams may identify documentation gaps without seeing how they connect to broader financial assumptions. Contracting leaders may understand risk terms while lacking visibility into data-quality limitations.
The review should bring together:
Finance
Contracting
Clinical leadership
Population health
Quality
Coding and documentation
Compliance
Data analytics
Network operations
Relevant technology and reporting partners
The goal is not to invite everyone to another recurring meeting with no decision rights. Healthcare has already conducted that experiment at scale.
The goal is to make sure each major assumption has an informed owner and each material discrepancy has a path to resolution.
What CFOs should expect from the review
A decision-grade Benchmark Exposure Review should produce more than a collection of charts.
Leadership should receive:
A summary of material population changes
An assessment of risk-documentation trends
A map of utilization concentration
Identified coding and data-integrity concerns
A range of financial scenarios
A list of unresolved assumptions
Prioritized operational recommendations
Assigned owners and deadlines
Defined escalation triggers
A schedule for reassessment
It should also state what the review cannot conclude.
For example, preliminary internal analysis should not be presented as a guaranteed shared-savings result. Do not promote an observed association as a proven cause. Do not treat a coding opportunity as permission to report an unsupported diagnosis. Do not automatically describe a utilization increase as waste.
Decision-grade work includes boundaries.
Do not let the final benchmark become the first serious review
CMS calculates the benchmark using program rules, assigned beneficiary information, expenditure data, risk adjustment, and applicable financial methodology. Historical and regional expenditures are among the elements used in establishing and updating benchmarks. CMS Specifications of the ACPT and Three-Way Blended Benchmark Update Factor
The ACO may not control every component of that calculation.
It can control whether leadership examines emerging signals early enough to make informed decisions.
It can review changes in the attributed population.
It can test whether risk documentation reflects clinical reality.
It can identify where utilization is concentrating.
It can reconcile coding, claims, clinical, and reporting data.
It can assign an operational response before the final number arrives.
Waiting may feel prudent because the final benchmark is authoritative. But authority and timeliness are not the same thing.
When the final number arrives, the organization should already understand the conditions likely shaping its financial position. The benchmark should confirm, refine, or challenge an existing analysis.
It should not introduce the ACO to its own exposure.
Waiting for the final number leaves very little room to change the story.
