You have decided your agency needs remote supports. Maybe the staffing crisis forced the conversation. Maybe a person you serve asked for more independence. Maybe you saw a competitor restructure their service model and realized you are behind. Whatever brought you here, the question is the same: where do you start?
But before we answer that, we need to correct a common misconception that derails most agencies before they begin.
The Difference Between Buying a Device and Building Infrastructure
If you are thinking about buying a tablet for one person, putting a motion sensor in one apartment, or trying a wearable device on one individual to “see if it works,” you are thinking about assistive technology. One device, one person, one problem. There is nothing wrong with assistive technology. It addresses specific assessed needs for specific individuals. But it is not what this article is about.
This article is about enabling technology: the infrastructure layer that transforms how your entire agency delivers services. Enabling technology is not a device you give to a person. It is an ecosystem that includes the devices in the home, the platform that connects them, the staff who monitor them, the environment they operate in, and the organizational systems that make the whole thing sustainable.
Think about it this way. You would not buy paper and binders for one house and then decide whether to adopt an electronic health record system. You would not run payroll by hand for one department to see if ADP works. When you adopted your EHR, you made an organizational decision. Then you rolled it out location by location, house by house, person by person. The decision was organizational. The implementation was phased.
Enabling technology works the same way. The decision to build enabling technology infrastructure is an agency-level commitment. The rollout happens location by location. But the infrastructure decision comes first.
Step 1: Get Leadership Alignment
This is not a technology project. It is a service delivery transformation. Before anything else, your executive leadership and board need to understand what this means for the organization.
This conversation should cover the financial model, including how enabling technology changes your labor cost structure and where the investment goes. The service model impact, including which individuals and locations are candidates for remote supports and which are not. The staffing implications, including how DSP roles change and what new roles are needed. The regulatory landscape, including what your state’s Medicaid waiver allows and what documentation is required. And the timeline, because this is a 6 to 12 month build, not a 30-day technology install.
If leadership is not aligned on these points before you start, the program will stall the first time a challenge arises. And challenges will arise.
This is the same conversation your agency had before adopting its EHR, before changing payroll providers, before restructuring any core operational system. The question is not “should we try a device.” The question is “are we ready to change how we deliver services.”
Step 2: Assess Your Current State
Before selecting an infrastructure partner, take an honest look at where your agency stands today.
How many individuals do you currently serve with overnight in-home staffing? Of those, how many have goals around increased independence? What are your current overnight staffing costs and vacancy rates? Does your state Medicaid waiver include billing codes for remote supports or enabling technology? Do you have staff with experience in assistive or enabling technology? Do you have physical space that could serve as a remote supports center, or will you need to contract that function? What is your current technology infrastructure, including internet connectivity at residential sites?
The answers to these questions determine the scope of your first deployment, the budget you need to build, and the gaps you need to fill before going live. They also determine which locations and individuals make sense for your first rollout.
Step 3: Select Your Enabling Technology Infrastructure Partner
This is where most providers make their first critical mistake. They buy devices instead of building infrastructure. They order a GrandCare tablet for one house, put an Apple Watch on one person, try a standalone sensor in one apartment, and then wonder why it does not feel like a program. It does not feel like a program because it is not one. It is assistive technology deployed piecemeal without an ecosystem to connect it.
Selecting an enabling technology partner is an infrastructure decision, the same category of decision as selecting your EHR or your billing system. You are choosing the platform your agency will operate on for enabling technology and remote supports. This partner should conduct individualized assessments for each person entering the ecosystem. They should recommend and source equipment based on the assessment, not a standard package. They should configure all devices to work together on a unified platform so that sensors, smart home devices, and communication tools function as an integrated system, not a collection of disconnected gadgets. They should install the equipment professionally, test it, and train both staff and individuals on how it works. They should provide ongoing platform management, equipment maintenance, and system updates as needs change over time. And they should scale with you as you expand from your first location to your twentieth.
The partner you choose should have experience in your specific sector, whether that is IDD, aging services, or both. They should understand your state’s regulatory requirements. They should be structured for a long-term relationship, not a one-time device sale, because an enabling technology ecosystem requires ongoing management to work. You would not select an EHR vendor who disappears after installation. The same standard applies here.
Step 4: Deploy Your First Location
Do not try to launch enabling technology across your entire agency at once. Start with your first location: one house, one apartment cluster, or one small group of 3 to 5 individuals who are strong candidates for remote supports.
This is not a pilot. This is not a trial. This is your first deployment. Your agency has already made the organizational commitment to enabling technology infrastructure. Now you are activating that infrastructure for the first cohort of individuals, the same way you enrolled your first house in Therap or onboarded your first department in ADP. The decision has been made. The rollout is beginning.
Your first deployment requires real investment. Each individual needs an assessment. Equipment needs to be selected, purchased, and installed based on that assessment. The platform needs to be activated and configured for each person. Staff need to be trained. The remote supports center needs to be operational. This is not a simulation. People are being supported. The system is live.
Good candidates for your first deployment are individuals who have some level of independence in daily living skills. They do not require hands-on personal care during the hours you plan to cover remotely, typically overnight. They and their guardians or representatives have provided informed consent. Their homes have reliable internet access. And there is a clear service delivery change that can be measured, such as transitioning from in-person overnight staffing to remote monitoring.
Use the first 90 days as your measurement window. Track incident response times, alert volumes, individual satisfaction, staff feedback, cost comparisons, and compliance documentation. This data is what justifies expanding to your second location, your third, and beyond. You are not proving whether the model works. You are documenting how it works at your agency so you can replicate it.
Step 5: Build or Contract Your Remote Supports Center
The remote supports center (RSC) is where trained specialists monitor the enabling technology platform and respond to alerts. This is the human layer of the system. Without it, you have sensors generating data that nobody is watching.
You have two options. Build an in-house RSC by designating physical space, hiring and training remote support specialists, and operating the center yourself. Or contract with an infrastructure partner who provides RSC design consulting and can help you build the capability or connect you with established monitoring operations.
For agencies launching their first deployment, working with your enabling technology partner to design the RSC function is often the fastest path. It lets you focus on the individual assessments, equipment deployment, and organizational change while building monitoring capability with expert guidance. As your program grows and you develop internal expertise, you scale the RSC operation alongside your deployments.
Regardless of which model you choose, the remote support specialists need specific training in the technology platform, person-centered decision-making, de-escalation, emergency protocols, and the specific needs and preferences of the individuals they are supporting. This is a skilled role, not a passive monitoring job.
Step 6: Develop Policies and Compliance Infrastructure
Your enabling technology program needs written policies covering informed consent (how you obtain, document, and update consent for technology use and monitoring), privacy (what data is collected, who accesses it, how it is stored, and how long it is retained), incident response (what constitutes an alert, how alerts are triaged, when in-person response is dispatched, and how incidents are documented), backup systems (what happens when technology fails, power goes out, or internet connectivity drops), staff roles and responsibilities (how DSP roles change, what remote support specialists do, who supervises the program), and billing and documentation (how services are documented to meet your state waiver’s requirements for reimbursement).
Your compliance team or consultant should review these policies against your state’s specific regulatory requirements before your first deployment goes live. Remote supports and enabling technology are still relatively new service categories in many states, and the rules are evolving. Your infrastructure partner should be able to support this work based on their experience across multiple states and regulatory environments.
Step 7: Scale Location by Location
After a successful first deployment, you expand to your next location. And then your next. This is the same phased rollout every provider has done with every major operational system: house by house, location by location, with each deployment building on the lessons of the one before.
Each new location requires assessments for the individuals being added, equipment selection and installation based on those assessments, platform configuration, staff training, and integration into the RSC monitoring workflow. Rushing this process leads to poorly configured systems, overwhelmed staff, and unhappy individuals.
A reasonable scaling pace for most agencies is adding one to two locations per quarter after the initial deployment, depending on the complexity of needs and your RSC capacity. Build the muscle before you build the volume. The providers who succeed treat every new location as a deployment, not an afterthought.
Common Mistakes to Avoid
The providers who struggle with enabling technology almost always make one of these errors. They treat it as a device purchase rather than a service delivery transformation. They buy individual gadgets without an integration platform. They skip the assessment and deploy a standard package for every individual. They launch without staff training and wonder why DSPs resist the change. They do not invest in the remote supports center and assume alerts will just be handled somehow. Or they try to “pilot” with no organizational commitment and then wonder why they cannot scale.
The biggest mistake of all is thinking about this the way you think about assistive technology: one device, one person, one problem. Enabling technology is infrastructure. You do not pilot your infrastructure. You implement it, learn from the first deployment, and scale deliberately.
Vista Supports partners with IDD and HCBS providers to implement enabling technology infrastructure. Vista Enterprise™ is your organizational platform for enabling technology and remote supports. Vista Link™ activates for each person in the ecosystem, following the individual across providers and settings. From technology assessment to RSC design to phased deployment strategy, Vista is the infrastructure partner that stays. Visit vistasupports.com or book a strategy session at meet.vistasupports.com.
