Operations that run when you're not watching.

Managed Services is ongoing operational support for an HCM platform: RJR consultants extending your internal team's capacity to handle the platform-substantive work that keeps the system running well over time. The scope typically includes payroll cycle support, configuration changes as policies and organizational structure evolve, integration monitoring and remediation when upstream systems shift, exception handling for edge cases, and platform expertise on demand for issues your internal team doesn't have the bandwidth or specialization to address.

Unlike implementation or optimization, which run against defined backlogs with explicit endpoints, Managed Services is continuous, typically structured as a defined-hours-per-month engagement with a dedicated consultant or small team familiar with your environment. The work happens within established service-level expectations: response times for issues, resolution targets for different severity levels, and regular reporting on what was handled and what's pending.

RJR runs Managed Services with consultants who carry the same UKG and ADP certifications as our implementation teams. The consistency matters because Managed Services work depends on understanding how your platform was configured and why, extending the implementation team's knowledge into the operational phase rather than starting from a learning curve every time something needs attention.

The honest answer depends on what your team actually needs. Hiring an internal HCM analyst makes sense when the work is consistent enough to justify a dedicated full-time role, the platform-specific expertise required can be developed over time, and your organization can absorb the recruiting timeline plus 6-12 months of ramp before the role is fully productive. Managed Services makes more sense when the work fluctuates, the expertise needed is platform-specialized in ways that take years rather than months to develop, or the bandwidth needs span multiple specialties that no single hire would cover.

The practical signal: if you'd be hiring one HCM analyst to handle UKG configuration plus ADP payroll integration plus reporting plus integration monitoring, you're hiring for a role that doesn't really exist. Each of those specialties has its own learning curve. Managed Services gives you access to consultants who are already specialized (payroll-focused, integration-focused, configuration-focused) without needing to find a unicorn or build the expertise internally over years.

Some clients run both: an internal analyst handling day-to-day operational work, plus Managed Services for the platform-substantive expertise that requires depth the internal role doesn't develop. The split works well when scope is clear about what the internal team owns versus what RJR handles. RJR adjusts engagement scope as internal capability builds, so the partner role can shrink as internal expertise expands.

A Managed Services engagement starts with onboarding, typically 2-4 weeks where RJR consultants familiarize themselves with your platform configuration, integration architecture, operational patterns, and team coordination expectations. Onboarding timeline depends on platform complexity and how well-documented the existing environment is; environments with strong documentation onboard faster than ones where the implementation history needs to be reconstructed.

From there, the engagement runs against a defined-hours-per-month commitment with a dedicated consultant or small team. Typical work patterns include scheduled work (payroll cycle support, monthly reporting cadences, quarterly configuration reviews) and on-demand work where issues come in through an established intake channel and get triaged against severity and effort. Communication rhythm usually includes weekly check-ins with your team, monthly engagement reviews to surface patterns and discuss upcoming priorities, and ad-hoc availability for issues that need fast response.

RJR engagements typically run on quarterly contract cycles with annual renewal patterns, allowing both sides to recalibrate scope based on what the work actually looks like over time. Some clients hold steady at the same engagement size for years; others ramp up during implementations or M&A integration periods, then ramp down as steady-state stabilizes. The engagement scope flexes within reason. Large scope changes mid-quarter are unusual, but adjustments at quarter boundaries are normal practice.

System Optimization and Managed Services serve different operational needs even though they overlap in surface activities. System Optimization is project-shaped work against a prioritized backlog of platform improvements: closing configuration gaps, building missing integrations, remediating accumulated issues from the original implementation. It runs in defined waves with explicit start and stop points; the deliverable is improvements to the platform.

Managed Services is continuous operational support: RJR consultants embedded as extension of your team to handle day-to-day platform work that keeps the system running well over time. It runs as ongoing engagement without explicit endpoint; the deliverable is operational reliability and bandwidth coverage rather than discrete improvements.

The practical signal: Optimization addresses what's wrong or missing on the platform. Managed Services addresses what needs to keep happening on the platform: payroll cycles run cleanly, configuration changes get made when policies shift, integrations stay healthy as upstream systems evolve, exception handling continues without operational disruption. Some clients run both simultaneously: Managed Services as the steady-state foundation, with Optimization as periodic improvement engagements when accumulated debt warrants focused attention. The combination works because the engagement types complement rather than duplicate each other.

Yes, with some structural patterns worth understanding. Managed Services engagements scale primarily at quarterly boundaries. RJR adjusts hours-per-month commitments based on what the prior quarter's work actually looked like and what's anticipated for the upcoming quarter. Typical patterns include scaling up during implementation projects or M&A integration when platform-substantive work spikes, scaling down as steady-state stabilizes after major changes, and seasonal adjustments where year-end and open enrollment periods carry higher operational load.

Mid-quarter adjustments are less common but not impossible. Significant unforeseen changes (new acquisitions, regulatory shifts requiring rapid platform updates, sudden integration partner changes) can warrant scope adjustment outside the normal cadence. The structural reason quarterly boundaries work better is consultant allocation. RJR commits dedicated capacity to your engagement, and reallocating that capacity mid-quarter affects both your work and the work of other clients sharing those consultants.

The flexibility worth being honest about: scope can scale meaningfully (50% up or down at quarterly boundaries is normal) but consultant identity is more stable than scope. The dedicated consultant or team familiar with your environment tends to remain consistent through scope changes. New consultants get added when scope grows substantially, but existing relationships get preserved when scope shrinks. The continuity matters because re-onboarding new consultants every quarter would consume the engagement bandwidth that's supposed to deliver value.

Managed Services typically handles platform-substantive issues: payroll exceptions requiring configuration analysis, integration failures needing root-cause investigation and remediation, configuration changes when policies or organizational structure shifts, reporting development when business needs new visibility, and platform-specific troubleshooting where the issue is rooted in the HCM system itself.

Issues that typically escalate back to the client side include: business policy decisions that aren't yet defined (RJR can configure to a stated policy, but doesn't define the policy itself), data privacy or compliance escalations requiring legal or HR leadership input, vendor relationship issues with third parties (integration partners, benefits providers, payroll processing vendors) where contract or commercial decisions are involved, and strategic platform decisions like module adoption, vendor changes, or major architecture shifts.

The boundary depends partly on engagement scope and partly on what your internal team has authority over. Some clients delegate broader authority to Managed Services for configuration changes within established parameters. RJR can implement policy changes that fit existing patterns; others require explicit approval workflows for any configuration change. RJR adjusts to your governance preferences. Both patterns work, but they affect engagement velocity differently. Engagements with broader delegated authority move faster on routine work; engagements with tighter approval requirements move slower but maintain stronger client-side oversight.

The handoff is structured as a defined transition rather than a hard cutover. During hypercare's two-pay-period engagement, RJR's implementation team is already operating in support mode: handling production issues, refining configuration based on what surfaces, coordinating with your operations team on emerging needs. Managed Services onboarding overlaps with the final hypercare weeks, so the consultant team that will handle ongoing engagement gets context directly from the implementation team rather than reconstructing it after handoff.

Practical handoff includes knowledge transfer sessions where implementation team documents configuration decisions and operational quirks, access provisioning so Managed Services consultants have what they need to do the work, runbook development for standard operational procedures, and explicit scope agreement on what Managed Services handles versus what escalates back to your team. The transition typically completes 2-4 weeks after hypercare ends (with implementation team availability tapering through that window) so that operational responsibility transfers cleanly without ambiguity about who owns what.

The continuity matters because most operational issues that surface in the first six months post-go-live are rooted in implementation-era decisions: why a particular configuration was chosen, what trade-offs were accepted, what edge cases were left for later iteration. Managed Services consultants who understand that history can address issues at the root rather than the symptom. RJR's standard practice is to pull at least one Managed Services consultant into the implementation team's later phases so the transition is genuine knowledge continuity rather than a cold handoff.

Success in Managed Services is measured at operational reliability and team bandwidth, not at completion of discrete deliverables. The signals are concrete: payroll cycles run cleanly without operational disruption, integration health stays within tolerance with issues caught and remediated before downstream impact, configuration changes get made on schedule when policies shift, exception handling continues without backlog accumulation, and your internal team's capacity is freed for higher-value work rather than consumed by platform-substantive issues they're not equipped to solve.

The harder-to-quantify signal is what Managed Services makes possible elsewhere: internal HR or operations leaders can focus on strategic work rather than firefighting platform issues, business decisions can be made faster because configuration changes are reliably executable rather than blocked by capacity constraints, and the organization treats the HCM platform as reliable infrastructure rather than ongoing operational risk. That confidence shift typically takes 3-6 months of consistent engagement to develop: the period when your internal team learns what RJR handles cleanly and stops mentally tracking issues that have become RJR's responsibility.

RJR runs Managed Services engagements with measurable service-level expectations and quarterly reviews against operational metrics. Each engagement tracks issue resolution velocity, configuration change throughput, integration uptime, and engagement satisfaction from your internal team. The honest read on success is that Managed Services done well becomes invisible operationally (you stop thinking about it because the work just keeps happening), which is exactly what good operational support should produce.