An Arc affiliate that operates both residential and day programs is running two fundamentally different service models under the same organizational roof. Residential programs involve 24-hour support, shift-based DSP scheduling, medication administration records in many states, and billing structures that cover continuous support rather than episodic visits. Day programs involve participant scheduling, group activities, goal-focused programming, production work in some cases, and per-unit Medicaid billing tied to daily attendance and service documentation. The clients who receive residential supports from the Arc may also attend the Arc’s day programs. The staff who work residential shifts may cover day program shifts during the same pay period. The billing for both programs flows to the same billing coordinator.
When those two program types operate in disconnected systems, the administrative overhead created at every point of overlap erodes the operational capacity that should be going into service delivery. A multi-site Arc affiliate that has solved this integration problem looks fundamentally different operationally from one that has not.
What Multi-Site Residential and Day Program Operations Actually Require
The billing complexity of running both program types simultaneously is the first operational challenge. Residential billing is typically per-diem or rate-based, covering the cost of 24-hour support, and follows a different authorization structure than the unit-based billing that day programs use. A client who lives in an Arc group home and attends an Arc day program has two separate billing streams, two separate authorization structures, and potentially two separate managed care organization relationships if their residential and day program services are funded through different waiver types.
When billing staff manage both in a single integrated system, the full financial picture of each client is visible in one place. When they manage both in separate systems, they are constantly reconciling between two different pictures of the same person.
The case management complexity is equally significant. The case manager responsible for a client who receives both residential and day program supports needs a case record that reflects both service contexts. Progress toward ISP goals that is documented in the day program needs to be accessible to residential staff who support the same goals during evening and weekend hours. Health and safety events that occur in the residential setting need to be visible to day program staff who will see the same client the following morning.
When documentation is organized around programs rather than around individuals, this continuity breaks down. Staff in each setting are working from a partial picture, and the client’s case record is split across two systems that were never designed to share information with each other.
Scheduling Across Residential Shifts and Day Program Hours
DSP scheduling in a multi-site organization running both residential and day programs requires managing two scheduling models simultaneously. Residential scheduling is shift-based and must maintain continuous coverage at every group home location. Day program scheduling is attendance-based and must accommodate participant schedules that change based on family circumstances, medical appointments, and individual preferences.
Staff who work across both program types in a given week need to be scheduled in a way that respects their total hours, their credential requirements for each setting, and the coverage needs of each program. When scheduling lives in a single system that handles both residential and day program contexts, supervisors have visibility across the full picture. When they operate in separate systems, a DSP can be over-scheduled without either system’s supervisor knowing it.
Vertex WorkforceHub Advanced provides real-time scheduling and time and attendance management that works across multiple sites and program types. For Arc affiliates where some DSPs work residential shifts at group homes and day program hours at day centers, the scheduling system tracks their full assignment picture rather than only what is visible in a single program context.
Compliance Visibility Across a Large, Dispersed Organization
An Arc affiliate operating ten group homes across three counties and two day program sites has compliance monitoring challenges that a single-site organization does not. Documentation currency, credential renewals, incident reporting timelines, and ISP review dates all require active monitoring across a staff population and client caseload that no supervisor can see in full from any single location.
Vertex Case Manager’s compliance reminder system surfaces documentation deadlines and overdue records at the organizational level, giving compliance staff visibility across the full operation rather than requiring site-by-site reporting from local program managers. When an ISP review is approaching for a client in a group home in one county, the compliance reminder surfaces in the same system view that tracks documentation currency for day program clients in another county.
For executive directors of multi-site Arc affiliates, this organizational-level visibility is what makes proactive compliance management possible rather than reactive crisis response when an audit or quality review reveals gaps that accumulated unnoticed across dispersed sites.
The Financial Picture of Both Programs in One System
Arc affiliates that operate residential and day programs simultaneously have a financial reporting challenge that reflects the complexity of their operations. Revenue from residential billing, day program billing, supported employment billing where applicable, and any production or vocational program revenue all need to be consolidated into a financial picture that leadership and boards can use to manage the organization.
When billing and financial management operate in an integrated system, that consolidated picture is available in real time rather than requiring a manual assembly of reports from multiple platforms. Vertex Financial Manager, built on Microsoft Dynamics 365 Business Central, provides the general ledger and financial management foundation that Arc affiliates with significant revenue complexity need alongside the IDD-specific billing and case management tools.
For Arc affiliates that report financial results to their state Arc organization, to the national Arc, or to county funders alongside their Medicaid payers, the ability to generate structured financial and outcome reports from a single integrated data set reduces the reporting burden that multiple disconnected systems would otherwise create.
What the Integration Looks Like in Daily Practice
The clearest way to understand what integration means for a multi-site Arc affiliate running both residential and day programs is to trace what happens when a client transitions from a residential setting to a day program and back.
A client in an Arc group home wakes up on a Tuesday. The residential DSP who supported them overnight has documented the shift in Vertex, including any health events or behavioral observations that occurred. When that client arrives at the Arc day program an hour later, the program staff who greet them have access to the same case record. They can see the overnight notes. They can see the active goals the client is working toward. They can see any recent health documentation that is relevant to how they support that person during the day program session. The notes the day program staff write during the day become part of the same longitudinal record that the residential team will see when the client returns to the group home that evening.
This continuity of information is not a feature demonstration. It is the operational reality that integrated software creates for multi-site Arc affiliates that have built their technology infrastructure around it. Connect with the Vertex Systems team to discuss how the platform supports organizations operating residential and day programs at your scale and site count.
