Introduction
Backup care networks were built for a workforce that no longer exists. The assumption underneath them is geographic concentration: employees clustered within commuting distance of a few offices, in major metros where caregiver supply is dense enough for a vendor to guarantee coverage. Buy the network, cover the population.
Distributed work removed the concentration and left the assumption in place. Your headcount is now spread across hundreds of postcodes and dozens of countries, and a meaningful share of it sits in places where a provider network has no depth. The care benefit did not change. The workforce underneath it did, and coverage quietly became a function of where an employee happens to live.
This is a piece for HR leaders and CHROs about that mismatch: what specifically breaks, why it shows up as an equity problem before it shows up as a utilization problem, and what a care benefit has to look like when employees are dispersed by design.
Key Takeaways
- Provider-network backup care depends on caregiver density, which falls away sharply outside major metros and disappears in small markets.
- Distributed work also shifted care demand into hours and days professional supply does not cover well.
- Uneven coverage across locations is a visible equity problem, and it lands hardest on employees furthest from headquarters.
- My Choice Care removes the dependence on local agency supply by letting employees nominate a trusted caregiver whom Helpr vets and pays directly at a $12-20 per hour average subsidy.
- One program can cover employees in 150+ countries, with active utilization in 50+ today, under a single set of eligibility rules and one utilization report.
What Actually Breaks When the Workforce Disperses
Four things, and they compound.
Network density collapses outside metros. A backup care vendor's coverage map looks strong because it is drawn around the cities where caregiver supply exists. Move thirty miles out and available caregivers thin dramatically. Move to a small market and there may be none. The vendor has not misrepresented anything, since this is simply how agency supply distributes, but the practical consequence for a distributed employer is that a single national contract delivers very different benefits to different employees.
Small markets never justify a contract. If you have nine employees in one country and fourteen in another, no local vendor wants that business and no procurement team wants to run the RFP. Those employees end up with either nothing or an informal reimbursement arrangement that most of them will never use, because a reimbursement process for an unvetted caregiver is more friction than it is worth.
Care demand moved into uncovered hours. Distributed teams work across time zones. An employee taking a 7am call for a colleague in another region, or covering an evening handover, needs care at hours when professional availability is at its thinnest. Backup care built around a standard working day covers the hours the employee was already able to manage.
The vendor stack multiplies. The usual response to patchy coverage is to add another vendor for the next region, which produces a familiar end state: several contracts, several eligibility definitions, several invoicing streams, several renewal dates, and a benefits team spending a meaningful part of the year reconciling them. Coverage still has holes, they are just harder to see.
Why This Reaches a CHRO Before It Reaches a Report
The reason this escalates is not cost. It is visibility.
An employee in a small market who is told the care benefit does not really work where they live draws a conclusion about how the organization regards employees outside headquarters. That conclusion travels, and it travels faster in a distributed company where employees compare notes in shared channels rather than in a canteen.
Utilization reporting tends to obscure the problem rather than reveal it. Aggregate uptake looks acceptable because the metro population uses the benefit normally. The employees who cannot use it register as non-users, which is indistinguishable in a report from employees who did not need care. The signal only appears when uptake is broken out by location, and by that point the equity perception has already formed.
The framing that matters for a CHRO is straightforward: a care policy that names a country and does not function there is a policy problem, not a supply problem.
The Mechanism That Fixes It
Coverage that follows the employee cannot depend on the employer having a local caregiver network everywhere, because no employer will. It has to depend on a mechanism that works without one.
My Choice Care is that mechanism. The employee nominates someone they already trust, most often a family member, a neighbour, a friend, or the caregiver the household already uses. Helpr screens and onboards that individual, then pays them directly through the platform against the employer's allocation at a $12-20 per hour average subsidy.
Read that in the context of a distributed workforce and the significance is obvious. Coverage stops being a function of agency density and becomes a function of policy. An employee in a town with no professional caregiver supply is not an exception to be handled by an HR business partner. They nominate someone local, Helpr vets and pays that person, and the benefit works the same way it works at headquarters.
It also solves the hours problem. Nominated caregivers are available at 5am and on a rotating roster in a way that agency dispatch generally is not, because they are already part of the family's life.
Where professional coverage is the right answer, Helpr Network Care provides pre-vetted caregivers at $45-50 per hour with a four-hour minimum and a 97% fulfillment rate on requested bookings, under continuous background checks. Most distributed employers fund both routes and let the employee choose per situation, which is what produces coverage that is genuinely uniform rather than nominally uniform.
What a Distributed Care Program Looks Like
Four properties, each of which addresses one of the failures above.
One contract, global scope. Employees in 150+ countries under a single agreement, with active utilization in 50+ today. Eligibility and allocation rules are set once at the program level rather than negotiated per market.
Identical rules everywhere. The same eligibility definition applies to a team of 900 in one country and a team of nine in another. This is the property that makes the program defensible when employees compare their experiences.
Funding sized for local reality. Care Funds are employer-funded care dollars, typically designed around 80-100 hours per employee per year and weighted where regional care costs or supply justify it. Weighting the allocation is legitimate. Leaving a market uncovered is not.
Navigation included. Distributed employees face care searches in markets your HR team has no visibility into. Care Finder assigns a dedicated care consultant who provides 1:1 support: sourcing options in the employee's actual local market, verifying licensing and references, and staying with the case through the decision. Relocation is a particularly common trigger, because an employee moving city or country restarts their entire care arrangement from nothing.
One reporting view. Utilization, spend, and care type by country and population, consolidated rather than assembled from vendor statements. This is what lets you see the location-level gaps early, and it is what makes the 4.93x return on care benefit spend evidenceable instead of asserted.
Where to Start
If your workforce has dispersed and your care benefit has not been revisited since, the diagnostic is a single query: uptake by location, next to headcount by location.
Locations with headcount and near-zero uptake are the ones to look at. Some of those employees did not need care. Others tried, found nothing available, and stopped. Aggregate reporting cannot tell you which, and the distinction is the whole question.
Frequently Asked Questions
Why does backup care work less well for remote employees?
Because provider-network coverage depends on local caregiver density, which is concentrated in major metros. Remote employees are frequently outside those areas, so the same national contract delivers strong coverage to some employees and very little to others. The gap is a supply distribution artefact rather than a vendor failing, but the employee experience is identical to having no benefit.
How do we cover employees in countries where we have only a handful of people?
Through My Choice Care, which does not require a local provider network. The employee nominates a caregiver they already trust, Helpr screens and onboards that person, and pays them directly at a $12-20 per hour average subsidy. This is what makes coverage across 150+ countries workable without a contract in every market.
Is it better to run separate regional care vendors?
Rarely. Multiple vendors produce multiple eligibility definitions, invoicing streams, and renewal dates, and they still leave your smallest markets uncovered because no vendor wants a nine-person contract. One program with globally consistent rules and locally weighted allocations is simpler to administer and easier to defend.
How do we identify coverage gaps in our current program?
Break utilization out by location and compare it against headcount. Locations with employees and almost no uptake are where the benefit is likely failing rather than unneeded. Aggregate uptake figures hide this, because concentrated metro usage keeps the overall number looking reasonable.
Do remote employees need care support at unusual hours?
Frequently, yes. Distributed teams work across time zones, so care is needed for early handovers, evening calls, and shifts that fall outside conventional agency availability. Employee-nominated caregivers cover those hours more reliably than professional dispatch, which is another reason to fund both routes.
How does care navigation work when HR has no local knowledge?
Care Finder assigns the employee a dedicated care consultant who works the case 1:1, sourcing and verifying options in the employee's own market. Local knowledge is applied per case rather than published centrally, which is why the model scales across a distributed workforce where a provider directory does not.
