Back to BlogWhy Global Contingent Workforce Expansion Is Not a Copy-and-Paste Rollout
Global contingent workforce expansion often looks straightforward on paper: choose the countries, map the suppliers, configure the VMS, train hiring managers and go live. In reality, the process is rarely that clean, because every market brings its own combination of legal, operational and cultural complexity.
That was one of the strongest messages to emerge from my conversation with Brenda Monaghan, EMEA Program Manager for Contingent Labor at Medtronic, at CWS Europe 2026.
Brenda offered a candid account of what global expansion really involves. Not the polished version that fits neatly onto a strategy slide, but the operational reality of navigating different laws, systems, suppliers, finance processes, cultural expectations and stakeholder relationships in every market.
This is the first article in a four-part series exploring the hidden complexity of global contingent workforce expansion. We begin with one of the most important lessons from our discussion: a global programme cannot simply be copied from one country and pasted into another.
One global strategy, many local realities
The appeal of a global contingent workforce programme is consistency. Organisations want one operating model, one governance framework, one set of controls and, where possible, one complete view of their non-employee workforce.
That ambition makes sense, but consistency does not mean every market can operate in exactly the same way.
Every country brings its own employment and labour laws, tax and payroll requirements, supplier relationships, invoicing rules, technology platforms, cultural expectations and stakeholder dynamics. Even within a single country, different sites may operate in completely different ways.
This is where many expansion programmes begin to struggle. The organisation starts with a global process and assumes each country can be fitted into it. In practice, local realities do not always cooperate.
The most successful programmes take a different approach. They begin by understanding how each market operates, then design the rollout around what can be standardised and what must remain local.
Eight countries in 18 months
Medtronic has been expanding its global contingent workforce programme for several years. In the 18 months Brenda discussed at CWS Europe 2026, the organisation added eight new countries and delivered £3.6 million in savings, largely through internal rate renegotiation and bringing in the right partners at the right time.
That is a significant achievement, but Brenda was clear about the level of ambition involved. Eight countries in 18 months is already a demanding pace. Some organisations are attempting to roll out programmes across 20 or 30 countries in a single year, which creates a very different level of pressure.
The drive to expand quickly is understandable. Executive teams want greater workforce visibility, stronger compliance, better data and tighter cost control. But speed without discovery creates problems that often take much longer to fix later.
A country should not be viewed as another box to tick on the rollout plan. Each one is a separate implementation with its own risks, relationships and operating conditions.
France: one country, five different rollouts
France provides a useful example of why country-level planning is sometimes not enough.
Medtronic’s French operations include four manufacturing sites and one commercial site. On paper, that looks like one national rollout. Operationally, it is closer to five.
The sites use different finance systems, and some are not operating on SAP. Each also has its own supplier relationships, including six direct labour suppliers across the four manufacturing locations and approximately 15 indirect suppliers.
The local stakeholder environment varies too. Manufacturing sites may involve HR, finance, procurement, site leadership, union representatives and works councils, all of whom have different priorities, concerns and levels of influence.
A process that works at the commercial site may not work in a manufacturing environment, while a supplier arrangement that makes sense at one location may not be suitable at another. This is why discovery needs to happen below the country level.
Programme teams need to understand how each site currently engages workers, which suppliers are involved, what systems are used and who needs to be part of the change. Without that detail, a rollout may look complete in the central project plan while remaining fragmented on the ground.
Italy: when the standard process does not fit
Italy presented a different kind of challenge.
Brenda’s team spent around six months trying to solve local invoicing complexity within the VMS. Italian invoicing requirements included strict deadlines and a large number of line-item payment types, and the team attempted to configure the standard system workflow to accommodate them.
Eventually, it became clear that the process could not be forced into the existing model. The local invoicing process needed to happen first, with the information then reconciled back into the system.
The lesson was not that the technology had failed. It was that the local operating reality had to come before system configuration.
A VMS can centralise workflows, approvals, supplier activity and reporting, but it cannot make every country operate in the same way. Had the invoicing requirements been fully understood at the start, the team may have avoided months of additional work.
That is the value of local expertise during the discovery stage. It helps organisations distinguish between a process that can be standardised and one that needs to be adapted.
India: relationships can be stronger than process
India revealed another form of complexity.
Medtronic introduced a vendor-neutral programme with clear rules, training and process documentation. Suppliers were not supposed to contact hiring managers directly.
The process was communicated and the expectations were clear, yet suppliers continued meeting hiring managers on site.
This was not necessarily an act of resistance or bad intent. It was simply how those relationships had always worked.
The new programme was asking people to change behaviours that had developed over years, and that takes more than a new set of rules.
This is an important reminder that rollout success cannot be measured only by whether the technology is live or whether training has been completed. A programme may be technically implemented while the old operating model continues around it.
Local habits, relationships and informal ways of working need to be considered alongside formal processes. Otherwise, suppliers and hiring managers may continue doing what feels familiar, even when the new framework says otherwise.
Czechia: timing is part of programme design
In Czechia, the rollout was progressing well until the team scheduled training during Easter week with relatively short notice.
The escalation that followed was not about the VMS, compliance model or supplier strategy. It was about timing and cultural expectations.
The local team felt the schedule had not respected an important period in their calendar. From a central programme perspective, the training may have seemed like a routine project milestone, but locally it sent a different message.
This is the kind of issue that is easy to overlook in a global rollout. A date that looks available in the project plan may be inappropriate in the local market, while a communication style that feels direct and efficient in one region may feel abrupt in another.
Cultural sensitivity is not an optional extra. It affects participation, trust and the willingness of local teams to support the programme.
Why EMEA is often underestimated
The complexity becomes particularly visible when US-headquartered organisations expand into EMEA.
From a distance, EMEA can sometimes appear to be one region with broadly similar operating conditions. It is not. It is a collection of markets with different labour laws, consultation requirements, cultural expectations and stakeholder structures.
In countries such as France, Germany and the Netherlands, works councils may have formal consultation rights when operational changes are introduced. Manufacturing environments may also involve active union relationships and established local engagement processes.
These are not minor administrative details. They can affect the scope, timing and design of the rollout.
The challenge for regional programme leaders is often translating that complexity into language that global headquarters can act on. Saying “it is different here” is unlikely to change the project plan. Explaining the specific legal obligations, consultation requirements, risks and realistic timelines is much more effective.
I have seen this first-hand. While supporting a large US-headquartered aviation company with a rollout across Poland, the Netherlands and Sweden, our team spent significant time engaging works councils and local stakeholders across manufacturing sites and regional offices. That included conversations with finance directors, local CEOs and union leaders.
Some of those discussions were uncomfortable, but without them the programme would not have succeeded.
The extra consultation was not a delay to the rollout. It was part of the rollout.
Discovery is not a delay
When organisations are under pressure to expand, discovery can feel like the stage that slows everything down. In reality, it is often the stage that prevents the real delays.
Before entering a new market, programme teams need to understand how workers are currently engaged, which suppliers are being used, which finance, HR and procurement systems are involved, how invoicing and payment work locally, what labour and tax requirements apply, which stakeholders need to be consulted and what behaviours already exist.
This work should happen before configuration and go-live, not after problems begin to surface.
The goal is not to create a completely different programme in every country. That would defeat the purpose of global governance. The goal is to identify where consistency is possible and where local variation is necessary.
At CXC, we have seen repeatedly that the strongest programmes are not the ones that force every country into the same model. They are the ones that create a clear global framework and then apply it with enough local understanding to make it work.
The danger of measuring success by go-live
A programme can go live on time and still fail.
The system may be active, but suppliers may continue contacting hiring managers directly. The policy may be published, but managers may keep using old engagement routes. The VMS may be configured, but the local finance process may still happen outside it. Training may be complete, but local stakeholders may feel excluded or ignored.
Go-live is an important milestone, but it is not the final measure of success.
A successful expansion is one where the programme is understood, adopted and operated correctly in the local market. That requires follow-up after launch.
Programme teams need to look for workarounds, missed processes and behaviours that training has not changed. They need to continue engaging local stakeholders and adjust the model where local requirements demand it.
Global consistency does not mean local uniformity
Global contingent workforce expansion works best when organisations stop treating standardisation and localisation as opposites.
A strong programme needs both.
Global governance provides visibility, clear ownership, consistent controls, supplier oversight, workforce reporting and defined engagement routes. Local adaptation makes those controls workable by accounting for the laws, systems, stakeholders and behaviours that exist in each market.
The global model should set the direction. The local operating model should determine how that direction is applied.
That is how organisations create programmes that scale without losing trust, compliance or control.
Five questions to ask before entering a new country
Before adding another country to the rollout plan, programme leaders should be able to answer five questions.
First, how is work currently being engaged? This means mapping the worker types, engagement routes and local processes that already exist.
Second, which suppliers and systems are involved? Programme teams need to understand supplier relationships, finance systems, payroll processes and current technology.
Third, what must happen locally? Country-specific invoicing, tax, employment and consultation requirements should be identified before configuration begins.
Fourth, who needs to support the change? Depending on the market, this may include HR, finance, procurement, legal, site leadership, hiring managers, suppliers, unions and works councils.
Finally, which parts of the global process need to be adapted? Organisations should not wait until go-live to discover that a workflow, training plan or system configuration does not fit the local market.
Expansion is possible, but it is not simple
Medtronic’s experience shows that global contingent workforce expansion can deliver measurable results. Eight countries were added in 18 months, with £3.6 million in savings.
But those results were not achieved by applying the same template everywhere.
They came from navigating different systems, supplier landscapes, invoicing requirements, stakeholder relationships and cultural expectations.
The central lesson from my conversation with Brenda at CWS Europe 2026 is clear: global expansion does not fail because the overall strategy is wrong. It often fails because the local reality was not understood before the rollout began.
Organisations that invest in proper discovery tend to build programmes that last. Those that skip it often find themselves returning to the same countries, fixing issues that could have been addressed from the start.
Coming next in the series
In part two, I explore why change management, compliance and local expertise determine whether a global contingent workforce programme succeeds in practice, not just on paper.
CXC has supported global contingent workforce programmes for more than 30 years, across over 100 countries. We’ll help you understand what needs to be standardised, what needs to stay local and what needs to be addressed before go-live.
