The Future Operating Model for HCBS, LTSS and Community-Based Care Providers

Home- and community-based services providers are being asked to operate in environments that are more complex, interconnected and accountable than those for which many traditional organizational structures were designed.

Organizations may now support people across Medicaid HCBS waivers, long-term services and supports, intellectual and developmental disability services, behavioral health, aging services, supportive housing, crisis response and complex community-based care. At the same time, they face persistent workforce shortages, rising acuity, changing payment models, tighter margins, greater survey scrutiny and increasing expectations around measurable outcomes, health equity, community integration and system impact.

Many providers have responded by adding new reporting processes, leadership roles, electronic systems, quality committees, dashboards and compliance controls. Yet more organizational activity does not automatically create a stronger provider. It can also produce duplicated reporting, unclear accountability, fragmented data and additional administrative pressure on frontline leaders.

The future challenge is therefore not simply to improve isolated functions. It is to redesign how the organization works as a connected system.

The Leadership, Governance and Organizational Capability Knowledge Hub brings together practical guidance on board accountability, executive oversight, risk ownership, organizational readiness, learning systems and cross-sector governance. These capabilities form the foundation of a credible future operating model for community-based care.

The provider of the future will not be defined primarily by its size, ownership model or technology platform. It will be defined by its ability to connect people, evidence, decisions, resources and accountability around safe, person-centered and sustainable support.

What Is a Community-Based Care Operating Model?

An operating model explains how an organization turns its mission, strategy and contractual obligations into day-to-day delivery.

It determines:

• How services and care pathways are designed
• How referrals, eligibility and service authorization are managed
• How decisions are made and delegated
• How direct support professionals, clinicians and managers are deployed
• How information moves across teams and partner organizations
• How quality and safety risks are identified and escalated
• How compliance, performance and outcomes are monitored
• How Medicaid, managed care and contract requirements are translated into operations
• How people receiving services, families and advocates influence decisions
• How leaders know whether the organization is achieving its mission

An operating model is much more than an organizational chart. Two providers may have similar reporting structures but operate very differently because their decision rights, management expectations, information flows, quality systems and assurance arrangements are not the same.

A future operating model must help providers remain governable, responsive and financially sustainable while adapting to changes in demand, regulation, technology and funding.

Why Traditional Provider Models Are Under Increasing Pressure

Many community-based care organizations have grown incrementally. New programs are added, waiver populations expand, payer requirements change, geographic regions develop and specialist functions are introduced in response to operational need.

Over time, this can produce a provider in which:

• Operations, quality, workforce, finance and compliance hold different versions of organizational performance.
• Program directors receive repeated requests for similar information from multiple departments.
• Executive leaders rely on retrospective reports instead of current operational intelligence.
• Important decisions depend on individual relationships rather than defined authority.
• Policies describe processes that do not reflect frontline practice.
• Corrective actions are dispersed across several disconnected tracking systems.
• Electronic systems increase documentation burden rather than reducing it.
• Boards receive large volumes of information without a clear view of material risk.
• Contract compliance appears strong even where workforce stability or participant experience is deteriorating.

The problem is not usually a lack of commitment. It is a lack of connection between the organization’s component parts.

Strong board governance and accountability must therefore extend beyond meeting schedules, policy approval and financial review. Boards need a clear understanding of organizational risk, service fragility, workforce capacity, regulatory exposure and the lived experience of people receiving support.

The Eight Capabilities of the Future Operating Model

A future-ready HCBS, LTSS or human services provider can be organized around eight connected capabilities:

1. Intelligence-led governance
2. Person-centered operating systems
3. Clear decision rights and accountable leadership
4. Workforce intelligence and capability
5. Digital-first but human-led operations
6. Predictive quality assurance
7. Funding, contracting and system resilience
8. Continuous organizational learning

These capabilities should not become eight separate transformation initiatives. Their value comes from the way they reinforce one another.

Workforce data becomes more useful when connected to incident, service continuity and participant outcome data. Quality assurance becomes more effective when linked to clear risk ownership. Digital systems create greater value when they reduce administrative burden and support person-centered decisions. Funder and regulator reporting becomes stronger when it draws directly from reliable organizational evidence.

Capability One: Intelligence-Led Governance

Traditional governance often concentrates on what has already happened:

• Critical incidents
• Abuse, neglect or exploitation reports
• Medication errors
• Complaints and grievances
• Survey findings
• Corrective action plans
• Hospitalizations or emergency department utilization
• Financial variance

These measures remain essential, but they are mainly retrospective. They tell leaders about harm, failure or noncompliance after it has occurred.

Intelligence-led governance also examines the conditions that make deterioration more likely.

These may include:

• Rising vacancy, turnover or absenteeism
• Reduced continuity of direct support staff
• Increasing overtime or contract staffing dependency
• Delayed supervision or competency validation
• Repeatedly overdue corrective actions
• Weak program-management capacity
• Unusual changes in incident-reporting patterns
• Falling employee engagement or psychological safety
• Increasing grievances within one program or region
• Changes in health, behavior, participation or daily functioning
• Growing service authorization delays
• Repeated gaps in closed-loop referral follow-up

No single indicator necessarily demonstrates that a program is unsafe. The value comes from recognizing relationships between them.

An IDD residential program may remain within its formal incident threshold while simultaneously experiencing high DSP turnover, declining supervision completion and growing reliance on unfamiliar staff. Individually, each measure may appear manageable. Together, they may indicate that the program is becoming fragile.

This is where executive leadership and strategic oversight must move beyond reviewing routine performance reports. Leaders need to understand where confidence is weakening, which indicators provide early warning and whether intervention is reducing risk.

The Governance Maturity Assessment can help organizations evaluate whether board oversight, leadership accountability and assurance arrangements remain reactive, developing, embedded or adaptive.

Governance Should Be Designed Around Questions, Not Reports

Many organizations begin governance design by asking what information is already available. A stronger approach begins with what leaders need to understand.

Boards and executive teams may need answers to questions such as:

• Which programs are becoming less stable?
• Where is workforce pressure beginning to affect safety, continuity or participant choice?
• Which controls are not operating as intended?
• Where are outcomes deteriorating despite acceptable compliance data?
• Which programs carry the greatest regulatory or financial exposure?
• Where is assurance based mainly on management opinion?
• What are participants and families experiencing that formal reports do not show?
• Which contract requirements are creating operational risk?
• Where are payer expectations misaligned with actual service capacity?

Reports and dashboards should then be designed around those questions.

This creates a more purposeful governance rhythm. Program-level meetings focus on immediate delivery and exceptions. Quality forums examine trends, controls and corrective action. Executive meetings make organizational and resource decisions. Boards test whether the organization is effectively governed.

This approach supports stronger risk ownership and assurance lines because each level of governance has a distinct role rather than repeatedly reviewing the same information.

Clear Lines of Assurance

Future operating models require greater clarity about where assurance comes from.

A practical model may include:

• Frontline assurance: direct support professionals, clinicians and care coordinators follow approved practice, document accurately and report concerns.
• Operational assurance: program managers supervise delivery, review exceptions and maintain local controls.
• Independent assurance: quality, compliance, clinical or audit functions test whether standards and controls are effective.
• Executive assurance: senior leaders review material risk, organizational trends, payer exposure and improvement progress.
• Board assurance: the board challenges the reliability of evidence, the strength of controls and the adequacy of executive response.

The purpose is not to create rigid bureaucracy. It is to prevent the same person or team from delivering a service, evaluating its quality and providing the final assurance that everything is working effectively.

This connects directly with provider risk management and assurance. Organizations should know which controls protect each material risk, who tests those controls and what evidence demonstrates that they are operating reliably.

Capability Two: Person-Centered Operating Systems

Person-centered practice is often described as a value, planning method or direct-care expectation. In the future operating model, it must also influence organizational design.

A provider cannot credibly describe itself as person-centered if its wider systems prioritize organizational convenience over people’s lives.

Person-centered operating systems should shape:

• Intake and eligibility decisions
• Person-centered planning
• Staff matching and continuity
• Scheduling
• Risk assessment
• Service authorization reviews
• Electronic record design
• Quality monitoring
• Outcome measurement
• Board reporting

For example, a schedule may be operationally efficient but still produce poor continuity, rushed support or frequent staff changes. An individual service plan may be technically complete but fail to explain what matters to the person. A quality dashboard may show that annual reviews occurred without demonstrating whether people achieved meaningful goals.

Strong person-centered, strengths-based planning requires providers to connect organizational resources with the changes people want in their lives.

From Service Activity to Personal Outcomes

Traditional operating models often measure whether activity occurred:

• Authorized hours delivered
• Assessments completed
• Reviews conducted
• Training attended
• Audits completed
• Community activities offered

Future operating models must also examine what changed as a result.

Relevant outcomes may include:

• Greater independence
• Improved choice and control
• Better physical and emotional well-being
• Reduced use of restrictive interventions
• Improved family confidence
• Greater community participation
• Improved housing stability
• Reduced avoidable hospital or emergency department utilization
• Increased employment or educational participation
• Improved quality of life

Activity measures remain useful because they show whether required services and processes occurred. They become more meaningful when connected to participant experience, functional outcomes and longer-term system impact.

This is central to outcomes frameworks and indicators. Providers need measures that are meaningful enough for people receiving support, operational enough for managers and credible enough for Medicaid agencies, managed care organizations and funders.

Positive Risk Enablement as an Operating Capability

A future-focused provider should not equate quality with the removal of all uncertainty.

People may wish to travel independently, manage aspects of their medication, develop relationships, seek employment, use technology, spend time in the community or make choices that professionals would not make for themselves.

The operating model should help teams make proportionate and defensible decisions by considering:

• The person’s goals, preferences and rights
• The nature and likelihood of potential harm
• Decision-making authority, consent and legal requirements
• Reasonable safeguards and supports
• The impact of preventing the activity
• How responsibility will be shared
• When the decision will be reviewed

The Positive Risk Enablement Planner can support structured decisions around autonomy, rights, safeguards and accountable review.

This aligns with positive risk-taking and least restrictive practice. The future operating model should make supported autonomy easier rather than allowing defensive systems to create unnecessary restriction.

Operational Example One: Redesigning Governance Across a Growing HCBS Provider

An HCBS organization expands from 15 programs in one region to more than 40 programs across several counties. The original leadership structure remains largely unchanged, and the chief executive becomes increasingly involved in routine operational decisions.

Step 1: Map How Decisions Are Currently Made

The organization reviews referral acceptance, staffing approvals, incident escalation, corrective action, contract communication and high-risk service decisions. It finds that several recurring decisions depend on informal conversations rather than defined authority.

Step 2: Clarify Accountability

Program, regional, executive and board responsibilities are documented. Escalation thresholds distinguish routine operational issues from material risks requiring executive or board attention.

Step 3: Redesign Governance Forums

Program reviews focus on immediate delivery, regional meetings examine cross-program risk, the executive team makes organizational decisions and the board receives assurance linked to principal strategic risks.

Step 4: Standardize Core Information

Common definitions are introduced for incidents, vacancies, overdue actions, service continuity, participant outcomes and payer exceptions so that variation between programs becomes visible.

Step 5: Verify Whether the New Model Works

The organization monitors decision speed, repeated escalation, management workload, overdue corrective actions and program-level confidence.

The redesign does not simply add another management tier. It creates clearer authority, more proportionate oversight and better organizational visibility.

Capability Three: Clear Decision Rights and Accountable Leadership

Future operating models need to make decision-making faster without weakening governance.

Providers often experience delay because authority is unclear. Program managers may be responsible for outcomes but unable to approve additional staffing, adjust service delivery, suspend an unsafe process or commit resources to corrective action.

At the same time, excessive delegation can create inconsistency where significant clinical, financial or regulatory decisions are made locally without sufficient oversight.

The solution is not simply more centralization or more local autonomy. It is clearer decision rights.

Organizations should define:

• Which decisions belong at program level
• Which decisions require regional or operational approval
• Which matters must be escalated to an executive leader
• Which risks require board visibility
• Who may approve urgent staffing or temporary expenditure
• Who can accept or decline complex referrals
• Who validates closure of high-risk corrective actions
• Who communicates with Medicaid agencies, managed care organizations, regulators and protective services

This strengthens decision rights and delegation frameworks by connecting formal authority with real operational responsibility.

Leadership Capacity Is an Organizational Control

Leadership capacity is often treated as a workforce issue, but it is also a governance control.

A program may have a manager formally assigned while still lacking effective management capacity because that leader is:

• Responsible for too many sites or contracts
• Covering persistent workforce gaps
• Carrying excessive documentation or reporting work
• Managing repeated critical incidents
• Supporting an inexperienced supervisory team
• Unable to complete supervision, audits or corrective actions

Future operating models should therefore monitor leadership capacity alongside vacancy, turnover, service acuity and regulatory risk.

This connects with leadership accountability and performance management. Providers need succession plans and leadership pipelines that prepare supervisors, program directors, regional leaders and specialist leads before vacancies or growth expose capability gaps.

Capability Four: Workforce Intelligence and Capability

The workforce remains the principal delivery system across HCBS, LTSS, IDD, behavioral health and other community-based services.

Future providers will need to understand workforce conditions with greater precision than simple headcount, vacancy and training-completion data allow.

Useful workforce intelligence may include:

• Vacancies by program, role, geography and shift
• Turnover by manager, team and length of service
• Absenteeism and unscheduled call-out patterns
• Overtime and contract staffing dependency
• Continuity of direct support professionals and care teams
• Scheduling instability and travel burden
• Supervision frequency and quality
• Observed practice competence
• Management span of control
• Internal promotion and succession readiness
• Employee engagement, burnout and psychological safety

This supports stronger workforce data and capacity planning. Providers should be able to identify where shortages, skill gaps or supervisory pressure may threaten future service delivery before those risks become established.

From Staffing Numbers to Workforce Risk

A program may appear fully staffed while still carrying significant workforce risk.

Examples include:

• A high proportion of newly hired staff
• Limited behavioral, medical or communication expertise within the schedule
• Heavy reliance on a small number of experienced DSPs
• High overtime among supervisors or lead staff
• Weak continuity for people with complex support needs
• Training completion without demonstrated competence
• Frequent last-minute shift changes
• Low confidence in incident reporting or escalation

Future operating models should connect these indicators with critical incidents, missed services, grievances, restrictive interventions, hospital utilization and participant outcomes.

This is central to workforce capability and skill mix. Assurance should establish not merely that sufficient staff are scheduled, but that the right people with the right skills are available in the right programs at the right times.

Capability-Based Workforce Design

Traditional workforce structures organize people primarily by job title. Future operating models may increasingly organize work around required capabilities.

Depending on the service model, these capabilities may include:

• Relationship-based direct support
• Medication administration and monitoring
• Positive behavioral support
• Clinical observation and escalation
• Augmentative and alternative communication
• Trauma-informed practice
• Digital confidence
• Safeguarding and mandatory reporting judgment
• Outcome measurement
• Community connection and employment support
• Leadership, coaching and practice validation

Providers should map which capabilities are essential within each program and identify where organizational risk is concentrated in a small number of individuals.

This may support:

• Specialist practice leads
• Regional clinical or behavioral support teams
• Peer coaching
• Competency passports
• Cross-program staffing pools
• More flexible career pathways
• Structured DSP advancement models

The objective is not to make roles less clear. It is to ensure that workforce design reflects what people, programs and contracts actually require.

Operational Example Two: Preventing Workforce Instability From Becoming Program Failure

An in-home supports provider continues to deliver most authorized hours, but turnover, absenteeism and missed visits begin to rise within one service area.

Step 1: Connect Workforce and Operational Information

The provider examines turnover, overtime, travel time, schedule changes, missed visits, continuity, grievances and supervision data together.

Step 2: Identify the Underlying Pattern

DSPs are covering fragmented schedules with excessive travel, unpaid gaps and frequent last-minute changes. Experienced staff are absorbing the instability through overtime.

Step 3: Redesign the Operational Response

Schedules are reorganized geographically, travel assumptions are reviewed and minimum expectations are introduced for sustainable work patterns.

Step 4: Strengthen Local Management

Managers receive support to forecast demand, identify coverage risk and respond to employee concerns before resignation or burnout becomes established.

Step 5: Verify the Impact

The organization monitors retention, punctuality, continuity, overtime, absenteeism and employee feedback over several months.

The provider prevents a workforce issue from becoming a quality and access failure because staffing information is treated as organizational intelligence rather than as a separate human resources report.

Capability Five: Digital-First but Human-Led Operations

Digital systems will become increasingly central to community-based care delivery, but technology should support professional judgment rather than replace it.

Core digital capabilities may include:

• Electronic health records and electronic service documentation
• Electronic medication administration records
• Scheduling and electronic visit verification
• Incident and protective-services workflows
• Quality dashboards
• Remote monitoring and assistive technology
• Automated reminders and escalation
• Integrated workforce, billing and performance reporting

The strongest providers will not simply purchase more systems. They will design an operating architecture in which information moves reliably across programs, functions and partner organizations.

This is the practical value of interoperability and data exchange workflows. Connected systems can reduce duplicate entry, improve visibility and help leaders understand relationships between service delivery, workforce pressure, quality, claims and outcomes.

Digital Transformation Should Reduce Operational Friction

A digital process is not automatically an improved process.

Technology can create additional burden where:

• Staff must enter the same information into several systems
• Programs use inconsistent data definitions
• Alerts are so frequent that they are ignored
• Frontline staff cannot easily access relevant information
• Managers manually transfer data into spreadsheets
• Reports show volume but do not support decisions
• Billing, care delivery and quality systems do not reconcile

Future operating models should redesign the workflow before digitizing it.

Providers should ask:

• What decision or action is this process intended to support?
• Who needs the information?
• Where should it be recorded once?
• Which steps can be automated safely?
• Where is human judgment essential?
• How will accessibility and digital inclusion be protected?
• How will privacy, consent and minimum-necessary access be maintained?

This aligns with digital systems, EHRs and operational tools. Technology investment should create measurable operational value rather than simply expanding the organization’s system inventory.

Automation Should Strengthen Follow-Through

Automation is particularly valuable where it removes repetitive administration and reduces the risk that important actions are overlooked.

Practical applications include:

• Reminders for overdue service-plan reviews
• Escalation of incomplete incident actions
• Identification of missing documentation
• Alerts for repeated late or missed visits
• Tracking corrective actions to verified closure
• Flagging expired credentials or competencies
• Identifying unusual patterns in incidents or medication records
• Highlighting unclosed referrals or authorization issues

This supports responsible AI and automation in care.

Every automated process still requires a named human owner. A system may identify an exception, but someone must investigate, interpret, decide and act.

Data Governance Must Develop Alongside Digital Capability

As providers collect and exchange more data, the governance of that information becomes increasingly important.

Future operating models should define:

• Who owns key data sets
• Which definitions are used across the organization
• How data accuracy is tested
• Who may access protected information
• How consent and legal authority are recorded
• How corrections are managed
• How long information is retained
• How cybersecurity and continuity risks are controlled

This strengthens data governance and information accountability. Poor-quality or poorly governed data can create false assurance, obscure risk and undermine regulatory or payer evidence even where the underlying service is performing well.

Capability Six: Predictive Quality Assurance

Traditional quality assurance often asks whether standards were met during the previous month, quarter or survey cycle.

The future model should also ask:

• Where is quality most likely to deteriorate?
• Which programs are becoming fragile?
• Which controls are weakening?
• Where are corrective actions repeatedly overdue?
• Which trends require earlier intervention?
• Where does positive compliance data conflict with participant experience?
• Which programs are most exposed to survey or contract risk?

Predictive assurance does not mean claiming certainty about future events. It means using leading indicators and connected evidence to identify where the likelihood of failure is increasing.

The Quality Dashboard Builder can help providers structure governance measures, early-warning indicators and board assurance questions around material risks.

This supports stronger assurance dashboards and metrics by moving reporting away from activity totals and toward organizational understanding.

Leading and Lagging Indicators Must Be Used Together

Lagging indicators describe events or outcomes that have already occurred, such as:

• Critical incidents
• Abuse, neglect or exploitation reports
• Medication errors
• Grievances
• Hospital admissions
• Missed services
• Survey deficiencies

Leading indicators describe conditions that may make those events more likely, including:

• Rising absenteeism
• Reduced supervision
• High manager turnover
• Delayed service-plan reviews
• Unresolved audit actions
• Increasing use of unfamiliar staff
• Deteriorating documentation quality
• Frequent schedule disruption

Neither category is sufficient alone. Lagging indicators provide accountability and evidence of actual failure. Leading indicators create an opportunity to intervene earlier.

Assurance Should Become More Dynamic

Annual audits, licensing surveys and scheduled program reviews will remain important, but they should be supplemented by more responsive assurance activity.

This may include:

• Real-time exception reporting
• Risk-based audit frequency
• Targeted record sampling
• Focused management reviews
• Rapid thematic analysis
• Short-cycle improvement checks
• Independent validation of high-risk corrective actions

The Regulatory Readiness Gap Analyzer can help providers identify where evidence is missing, disconnected or insufficiently linked to practice and outcomes.

This strengthens regulatory readiness and inspections. Regulatory evidence should emerge from normal organizational operation rather than being assembled only when a survey, audit or monitoring review is expected.

Corrective Action Must Move Beyond Administrative Closure

Corrective action plans frequently contain tasks such as:

• Update the policy
• Deliver refresher training
• Remind staff of expectations
• Introduce a new checklist
• Complete a follow-up audit

These actions may be appropriate, but they do not in themselves demonstrate that practice has improved.

A future operating model should distinguish between:

• Action completion: the planned task was carried out.
• Control improvement: the process or safeguard now works more reliably.
• Outcome improvement: the risk, experience or result has changed.

The Quality Improvement Action Plan Builder can help providers connect findings, root causes, accountable actions, verification evidence and sustainable closure.

This aligns with corrective action, remediation and recovery. Closure should require evidence that the intended change has been embedded and sustained.

Operational Example Three: Identifying Quality Deterioration Before a Serious Failure

An IDD residential program continues to report acceptable internal audit scores, but employee call-outs, medication delays and family grievances begin to increase.

Step 1: Review the Combined Pattern

The quality team compares absenteeism, overtime, medication exceptions, grievances, supervision and audit findings rather than reviewing each measure separately.

Step 2: Test the Reliability of Existing Assurance

Record sampling shows that audits are being completed, but actions are being closed without checking whether practice has changed.

Step 3: Introduce Targeted Support

The provider increases management capacity, reviews medication workflows and deploys an experienced practice leader to coach staff.

Step 4: Strengthen Oversight

The program moves to a higher-frequency assurance cycle with weekly review of leading indicators and independent validation of corrective actions.

Step 5: Confirm Sustained Improvement

Leaders monitor medication timeliness, absenteeism, grievances, observed practice and family confidence before returning the program to standard oversight.

The provider intervenes before the combined pressures develop into a serious safety, contract or regulatory failure.

Capability Seven: Funding, Contracting and System Resilience

The future operating model must connect quality, capacity and financial sustainability.

Providers cannot make sound operational decisions where finance is considered separately from workforce pressure, participant acuity, utilization controls and changing service authorization.

Boards and executive teams need to understand:

• The true cost of different service models
• The financial effect of vacancies, overtime and contract staffing
• Whether reimbursement reflects actual levels of need
• Which contracts carry disproportionate operational risk
• How quality changes under financial pressure
• Where investment may prevent future cost or program failure
• Which care pathways are becoming less sustainable
• Where payers need stronger evidence of unmet demand or access risk

This links directly to provider finance, cost controls and sustainability. Financial resilience should not mean reducing cost regardless of impact. It means sustaining safe, effective and person-centered services under changing funding and demand conditions.

From Contract Compliance to Shared Intelligence

Payer and funder relationships have traditionally focused heavily on contract monitoring, utilization reporting, claims performance and exception management.

These remain necessary, but the future model should support more strategic and evidence-led dialogue.

Providers should be able to explain:

• Where demand is changing
• Which workforce risks threaten future access
• Which outcomes are improving
• Where referrals or authorizations are becoming delayed
• Which risks require system-level action
• What evidence demonstrates quality and value
• Where payment assumptions no longer reflect operational reality

This strengthens contract management and provider performance by creating a clearer line between operational evidence, payer confidence and provider sustainability.

System Partnership Must Be Designed Into the Operating Model

Community-based care providers increasingly work within systems involving:

• State Medicaid agencies
• Managed care organizations
• County and local government
• Hospitals and health systems
• Primary care and behavioral health providers
• Housing organizations
• Schools and transition programs
• Families, guardians and advocates
• Technology and service vendors

Partnership working is often described as a relationship skill, but it also requires operational design.

The provider should define:

• How referrals are received and triaged
• How information is shared
• How risk is escalated across organizational boundaries
• Who participates in interdisciplinary decisions
• How urgent issues are resolved
• How pathway performance is reviewed
• How disagreement is managed

This supports stronger system integration and multi-agency working. People experience care as a pathway, not as a sequence of separate contracts, departments or organizations.

Design Around Pathways, Not Organizational Boundaries

People experience community-based care as a journey rather than as a sequence of separate contracts, programs or agencies.

Future operating models should therefore support pathways such as:

• Hospital to home
• Post-acute care to long-term community support
• Children’s services to adult HCBS
• Institutional settings to community living
• Crisis stabilization to ongoing behavioral health support
• Homelessness services to permanent supportive housing
• Rehabilitation to greater independence
• Family caregiving to formal LTSS support

Each pathway requires clear handoffs, shared understanding of risk, named accountability and closed-loop communication.

Where pathways are poorly designed, the person may experience repeated assessment, delayed authorization, conflicting information, medication discrepancies and gaps in responsibility even where every individual organization believes it has completed its own process.

This makes closed-loop care coordination and data exchange a core operating capability rather than a specialist administrative function.

Operational Example Four: Redesigning a Hospital-to-Community Pathway

An HCBS provider receives increasing numbers of urgent referrals from hospitals and managed care care-transition teams. Services are initiated quickly, but several arrangements become unstable during the first two weeks.

Step 1: Review the Whole Pathway

The provider examines referral information, functional assessment, medication needs, behavioral risks, home accessibility, informal caregiver capacity, authorization status and early incidents.

Step 2: Identify the Recurring Gaps

Several referrals contain insufficient information about cognition, medication reconciliation, equipment, delegated healthcare tasks and likely fluctuations in need.

Step 3: Redesign Intake and Acceptance

A rapid-response assessment process is introduced with clearer acceptance criteria and access to clinical, behavioral and care-coordination expertise.

Step 4: Strengthen Cross-System Communication

The provider agrees escalation routes with hospitals, health plans and primary care partners and introduces 48-hour and seven-day transition reviews.

Step 5: Measure System Impact

Leaders monitor service stability, readmissions, emergency department use, incident rates, authorization delays, caregiver confidence and participant experience.

The provider moves from processing urgent referrals to actively managing a high-risk transition pathway.

Value-Based Care Requires a Different Operating Model

As more funding arrangements connect payment with quality, utilization, access or outcomes, providers will need stronger operational links between service delivery and evidence.

A value-based operating model should enable organizations to:

• Define outcomes that can be influenced through service delivery
• Understand the cost of achieving those outcomes
• Segment risk by population, acuity and pathway
• Identify avoidable utilization and service instability
• Track whether interventions are producing measurable change
• Explain variation between programs or populations
• Share credible evidence with payers and funders

This supports value-based payment and outcomes-led design.

Providers should be cautious about accepting outcome risk where measures are poorly defined, data is incomplete or outcomes depend heavily on factors beyond their control. A mature operating model should help leaders distinguish between meaningful accountability and unmanaged financial exposure.

Community Impact Should Be Embedded, Not Added Later

Community impact should not sit separately within grant reports, procurement responses or annual communications.

It can shape how organizations:

• Recruit and develop local residents
• Create DSP and peer-support career pathways
• Work with community-based organizations
• Reduce rural and transportation barriers
• Support family caregivers
• Address digital exclusion
• Improve access for underserved populations
• Use local and diverse suppliers
• Strengthen housing stability and community participation

The Community Impact Report Builder can help organizations connect commitments, measures, evidence and reporting responsibilities across HCBS and human services.

This strengthens social value and community impact by making wider benefit part of organizational planning rather than an isolated reporting exercise.

Capability Eight: Continuous Organizational Learning

The future provider must be able to learn faster than risk develops.

Organizational learning should draw from:

• Critical incidents and near misses
• Complaints, grievances and appeals
• Abuse, neglect and exploitation investigations
• Audits, surveys and monitoring reviews
• Employee feedback
• Participant and family experience
• Service disruption and business continuity events
• Pilots and innovation initiatives
• Claims, authorization and utilization patterns
• External reviews and regulatory findings

Strong organizational culture and learning systems require more than distributing lessons-learned summaries.

Providers should demonstrate how learning changes:

• Policies and procedures
• Training and competency expectations
• Supervision and coaching
• Program design
• Technology and workflows
• Resource allocation
• Leadership decisions
• Contract and payer discussions
• Board assurance

Improvement Must Be Verified

An action should not be considered complete simply because:

• A policy was revised
• Training was delivered
• A reminder was issued
• A form was changed
• A manager marked the item closed

The organization should test whether the intended outcome was achieved.

This may require:

• Follow-up audits
• Observation of practice
• Record sampling
• Employee interviews
• Participant and family feedback
• Trend analysis
• Independent validation
• Reassessment of the original risk

This is the difference between task completion and genuine audit, review and continuous improvement.

Organizational Culture Is Part of the Operating Model

No future operating model can succeed where employees are afraid to raise concerns, acknowledge uncertainty or challenge unsafe decisions.

Culture affects:

• Whether incidents are reported promptly
• Whether managers escalate deteriorating conditions
• Whether frontline knowledge reaches senior leaders
• Whether errors lead to learning or blame
• Whether people receiving services feel heard
• Whether improvement actions reflect operational reality

Boards and executives should therefore treat psychological safety, ethical leadership and employee voice as governance issues.

A low incident rate may indicate strong practice, but it can also indicate underreporting. A lack of complaints may reflect satisfaction, but it may also reflect inaccessible complaint routes or fear of consequences. Intelligence-led leadership tests the meaning behind the number.

The Role of Program Managers and Frontline Leaders

Program managers, service coordinators, clinical supervisors and frontline leaders will remain central to the success of community-based organizations, but they must be supported differently.

Future operating models should reduce unnecessary administrative burden and provide leaders with:

• Clear delegated authority
• Accessible operational intelligence
• Responsive quality and compliance support
• Workforce planning assistance
• Clinical or behavioral consultation
• Peer networks and mentoring
• Leadership development
• Clear escalation routes
• Usable digital systems

Managers should be enabled to lead programs rather than spend disproportionate time reconciling disconnected systems, repeating data entry or chasing decisions across multiple departments.

Board and Executive Expectations

A future-ready board should be able to answer:

• What are the organization’s most significant risks?
• Which programs are becoming less stable?
• What evidence supports management assurance?
• Where is workforce pressure affecting quality or access?
• Which controls have been independently tested?
• Where are corrective actions overdue or repeatedly reopened?
• How are participant rights, outcomes and experience reflected in oversight?
• Which contracts or payment models create material exposure?
• How resilient is the organization during disruption?
• What has the organization learned and changed?

This is central to governance maturity and organizational readiness.

Boards do not need to manage operations directly, but they do need sufficient evidence to test whether executive leadership is identifying and controlling material risk.

Regulator, Payer and Funder Expectations

State agencies, accrediting bodies, Medicaid programs, managed care organizations and other funders are likely to expect providers to demonstrate that the organization is effectively controlled, responsive to risk and capable of sustained improvement.

Relevant evidence may include:

• Clear accountability and delegated authority
• Effective board and executive oversight
• Reliable quality, workforce and outcome data
• Timely incident reporting and escalation
• Effective corrective action
• Competent and supported staff
• Meaningful participant and family involvement
• Evidence of sustained outcomes
• Strong continuity and emergency arrangements
• Accurate and defensible documentation
• Reliable contract and authorization management

This supports quality assurance, oversight and accountability. Regulatory readiness should emerge from normal operations rather than from an intensive evidence-gathering exercise immediately before a survey or audit.

Common Operating-Model Pitfalls

Adding Technology Without Redesigning the Workflow

Digitizing an inefficient process usually produces a digital version of the same problem.

Centralizing Every Decision

Excessive central control delays action, weakens local ownership and overwhelms executive leaders.

Delegating Without Assurance

Local authority must be supported by clear standards, competence, information and escalation.

Separating Workforce From Quality

Workforce instability is frequently an early indicator of service risk.

Using Dashboards as a Substitute for Leadership

Information creates value only when leaders investigate, challenge and act.

Designing Around Departments Rather Than People

People’s pathways often cross several programs, payers and agencies.

Measuring Service Volume Rather Than Outcomes

Delivering authorized hours does not by itself demonstrate impact.

Closing Corrective Actions Without Validation

Administrative closure can conceal recurring weakness.

Accepting Value-Based Risk Without Data Readiness

Providers may carry financial accountability for outcomes they cannot reliably measure or influence.

Treating Innovation as a Separate Program

Innovation should solve operational problems rather than remain at the edge of the organization.

Ignoring Culture

No structure or technology platform can compensate for a culture in which people do not speak openly about risk.

A Practical Roadmap for Operating-Model Redesign

1. Define the Future Mission and Strategic Direction

Clarify what the organization exists to achieve for people, families, communities and system partners.

2. Map the Current Operating Model

Review structures, decisions, systems, governance forums, duplicated processes, information flows and accountability gaps.

3. Identify Critical Capabilities

Determine which organizational capabilities are essential for future populations, contracts and service models.

4. Redesign Decision Rights

Clarify ownership, delegation, escalation and board visibility.

5. Connect Organizational Intelligence

Integrate program, workforce, quality, clinical, financial, claims and outcome evidence.

6. Simplify Governance Rhythms

Ensure meetings have distinct purposes, clear authority and defined outputs.

7. Redesign Workforce Capacity

Align roles, competencies, supervision and leadership capacity with future demand.

8. Improve Digital Architecture

Use technology to reduce friction, strengthen data quality and support human judgment.

9. Strengthen Assurance and Corrective Action

Use leading indicators, risk-based review and verified closure.

10. Test the Model

Pilot redesigned arrangements within selected programs, populations or regions.

11. Measure Impact

Assess decision speed, workforce stability, service continuity, participant outcomes, regulatory confidence and financial sustainability.

12. Adapt Continuously

Use evidence and feedback to refine the operating model as the organization and external environment change.

What the Community-Based Care Provider of the Future May Look Like

The provider of the future is unlikely to be defined by size, tax status or service category.

It will be an organization that:

• Recognizes risk before failure becomes established
• Connects frontline delivery with strategic decisions
• Uses data without losing human judgment
• Builds services around people’s rights, goals and lives
• Deploys workforce capability intelligently
• Works confidently across organizational boundaries
• Learns quickly and verifies improvement
• Balances quality, access, value and sustainability
• Demonstrates credible outcomes to payers, regulators and communities
• Adapts its structure as needs, technology and funding models evolve

Its systems will become more digital, but its mission will remain human.

Its governance will become more analytical, but also more transparent.

Its workforce model will become more flexible, but still grounded in competence, continuity and trust.

Its payer relationships will become more evidence-led, but should also become more collaborative.

Conclusion

The future operating model for HCBS, LTSS and community-based care providers is not simply a new organizational chart, technology platform or compliance framework.

It is a connected way of operating that brings together governance, person-centered practice, workforce capability, digital infrastructure, predictive quality assurance, funding resilience and organizational learning.

Providers that continue to manage these areas separately may struggle to recognize risk, adapt capacity, demonstrate outcomes or sustain increasingly complex services. Those that connect them will be better positioned to respond to change while preserving the quality, rights and humanity of support.

The strongest future providers will not abandon compliance, professional judgment or local leadership. They will strengthen them through clearer accountability, better information, more responsive systems and a deeper understanding of outcomes.

The future operating model is therefore not about replacing the foundations of community-based care. It is about creating an organization capable of protecting and improving those foundations under changing conditions.