Designing a Global Labour Relations Operating Model for Workforce Change
Every multinational labour relations team faces the same fundamental tension: the centre wants one consolidated view, and local teams need processes that reflect local law, local stakeholders, and local timelines. Neither side is wrong. The job of a good operating model is to let both exist without one undermining the other.
If you have worked on a cross-border restructuring, you have probably lived through what happens when the operating model is not clear. The central programme team builds a tracker in a spreadsheet or a generic project tool. They define stages — something like "Announce, Consult, Implement, Close." They ask each country to report against those stages weekly. And within a few weeks, the reporting starts to break down. Germany is stuck in a stage called "Consult" that could last months because the works council has co-determination rights that require genuine negotiation, not just notification. France has entered a prescribed information-and-response cycle with the CSE that does not map neatly to any of the central stages. The UK team is running a statutory collective consultation with its own timeline triggers. And the central team is looking at a dashboard full of amber statuses with no way to tell which ones represent genuine risk and which ones are simply following the local process as designed.
This article sets out a framework for designing an operating model that actually works across jurisdictions — one that gives central leadership the consolidated reporting they need while preserving the local fidelity that keeps consultation processes legally sound and practically effective.
The four layers of a labour relations operating model
A useful way to think about the operating model is in four layers. Each one answers a different question, and each one needs to work independently before the whole thing holds together.
Governance: who decides what. This is the layer most organisations start with, and it is the one that causes the most friction when it is unclear. Governance answers questions like: who approves the consultation strategy for a given country? Who decides whether to escalate a stalled works council negotiation? Who owns the relationship with external legal counsel? Does the central LR team have decision authority, or are they advisory? In many organisations, these questions are answered differently depending on who you ask — the central programme lead, the HRBP, the in-country ER lead, and external counsel may all believe they hold the decision. The operating model needs to make this explicit.
Process: how work flows. This layer defines the actual steps that happen in each jurisdiction when a workforce change is proposed. It covers the consultation workflow — from initial assessment through to closure — and it needs to be specific enough to be useful. A process layer that says "consult with employee representatives" is not a process. A process layer that says "identify the relevant representative body, confirm the information package required, submit the proposal, track the response window, log questions and responses, obtain the formal opinion or agreement, and document the outcome" is a process. Critically, the process layer must be configurable by jurisdiction. The steps in Germany will not match the steps in the UK, and neither will match the Netherlands or France.
Data: what gets recorded. This is the layer most organisations underinvest in, and it is the one that determines whether reporting is possible or fictional. If local teams are not recording the right information in a structured way — representative body composition, consultation status, document submissions, response dates, agreement terms — then no amount of reporting sophistication will produce useful output. The data layer defines the minimum information set that every country programme must capture, and it defines the format so that data can roll up globally without manual reconciliation.
Reporting: what leaders see. This is the output layer, and it only works if the other three are in place. Reporting answers questions for the executive team, for the programme steering committee, and for regional leads. It needs to show both status and rationale — not just "where are we" but "why are we there, and what needs to happen next." We will come back to reporting architecture in more detail below.
Why one-size-fits-all governance breaks down
The instinct to standardise is understandable. If you are running a restructuring across fifteen countries, you want one set of stage gates, one set of templates, one reporting cadence. It is tidier, it is easier to build, and it looks cleaner in a steering committee pack. But it breaks down because the legal frameworks are genuinely different — not just in detail, but in structure.
Germany's co-determination framework under the Betriebsverfassungsgesetz (BetrVG) gives works councils real blocking power on certain matters. This is not a consultation right in the sense that many Anglo-Saxon practitioners understand it — it is a consent right on specific topics, including working time arrangements and social plans. A restructuring that affects these areas cannot simply proceed after a notification period. It requires negotiation, and the works council can legitimately withhold agreement.
France's CSE (Comité Social et Économique) creates a different kind of structure. Consultation follows prescribed information stages with defined response windows. The employer must provide specific documentation, the CSE must be given time to review and respond, and the process has a rhythm that is set by regulation rather than by programme convenience.
The Netherlands operates under the WOR (Wet op de Ondernemingsraden), which grants works councils both advice rights and consent rights depending on the subject matter. The UK has its own statutory framework for collective redundancy consultation under TULRCA, with specific triggers based on the number of proposed dismissals and prescribed minimum consultation periods. The Nordic countries tend to work through collective agreements and trade union channels rather than works councils, creating yet another structural pattern.
None of these are wrong. They are different legal traditions with different expectations about the role of employee representatives in organisational decision-making. An operating model that tries to flatten these differences into a single set of stages will either be so generic as to be useless, or so specific to one jurisdiction that it misrepresents the others.
The control-tower model
The approach that works best in practice is what is sometimes called a control-tower model. The idea is straightforward: the centre defines the frame, and local teams execute within it.
In concrete terms, this means the central team owns a specific set of things. They own the reporting framework — the common language and structure that every country reports into. They own the escalation rules — the criteria for when a local issue becomes a central decision. They own the minimum evidence standards — the baseline set of information that every country programme must capture. And they own the decision gates — the points at which central sign-off is required before the programme moves forward.
Everything else sits with the local team. The local team owns the consultation strategy for their jurisdiction. They own the relationship with the representative body. They own the sequencing and timing of consultation steps. They own the documentation package. And they own the local legal assessment of what is required and what is advisable.
This separation matters because it prevents two failure modes. The first failure mode is over-centralisation: the central team tries to run the consultation process directly, makes mistakes because they do not understand local requirements, and damages the relationship with local employee representatives. The second failure mode is under-centralisation: each country runs its own process with no common structure, and the central team has no way to aggregate status, compare progress, or identify where problems are emerging.
The control-tower model avoids both by being explicit about the boundary. The centre controls the frame. Local teams control the content within the frame.
How the key functions interact
A labour relations operating model does not exist in isolation. It sits within a wider ecosystem of functions that all have a role in workforce change, and the model needs to define how they interact.
HR Business Partners are typically the first point of contact for business leaders planning a workforce change. They understand the business rationale and the people impact. But in many organisations, HRBPs do not have deep expertise in consultation process or labour law. The operating model needs to define the handoff point — the moment at which the HRBP brings in the LR specialist or the ER team.
Labour relations specialists own the consultation process design and the relationship with employee representatives. In a well-functioning model, they are involved early — before the business has committed to a timeline that may not be achievable given local consultation requirements. One of the most common operating model failures is late involvement of LR: the business announces an implementation date, the HRBP agrees to it, and the LR team is then asked to compress a consultation process into a timeline that does not work.
Legal teams — whether in-house or external — provide jurisdictional legal advice. The operating model needs to be clear about when legal review is required (always, or only in specific circumstances), who instructs external counsel (the LR team, the HRBP, or the central programme team), and how legal advice is captured and tracked so it is not lost in email chains.
Shared services teams often handle the administrative execution of workforce changes — issuing letters, updating systems, processing terminations. The operating model needs to define the trigger for shared services involvement. If they start processing changes before consultation is complete, the organisation has a compliance problem. The handoff from LR to shared services should be gated by a clear sign-off that consultation obligations have been met.
When these interactions are not defined, you get the problems that most multinational ER teams will recognise: duplication of effort (two teams doing the same assessment), gaps (no one owning a critical step), conflicting advice (legal counsel saying one thing, the HRBP saying another, the central team saying a third), and no single source of truth for programme status.
The centre of excellence model and its limitations
Many organisations try to solve the operating model problem by establishing a labour relations centre of excellence (CoE). The idea is that a small central team holds deep expertise and provides guidance, templates, and oversight to local teams across the organisation.
This model has real strengths. It concentrates expertise, it creates consistency in approach, and it gives local teams a place to go when they need specialist input. For organisations that are just building a labour relations function, a CoE is often a sensible starting point.
But the CoE model has limitations that become visible at scale. A small central team cannot be deeply involved in every country programme simultaneously. They end up being either a bottleneck (everything waits for CoE review) or a rubber stamp (they review too quickly to add real value). The CoE also tends to default to advisory rather than operational — they write the playbook, but they do not run the play. This works when local teams are strong, but creates risk when local capability is uneven.
The control-tower model described above is, in some ways, an evolution of the CoE. It keeps the central expertise and the common framework, but it is more explicit about decision rights and more structured about how central and local teams interact. The CoE provides knowledge. The control tower provides governance.
Reporting architecture: status and rationale
Most executive reporting on workforce change programmes focuses on status. Each country gets a RAG rating, maybe a percentage complete, maybe a projected completion date. This information is useful but fundamentally limited. A red status tells you there is a problem. It does not tell you what the problem is, whether it is within the programme's control, or what needs to happen to resolve it.
A well-designed reporting architecture captures both layers. The status layer provides the rollup that executives need: where is each country in its consultation process, what is the overall programme timeline, where are the risks. The rationale layer provides the explanation: why is Germany behind (the works council has requested additional financial information before proceeding with social plan negotiations), why is the UK on track (statutory consultation period is running and no complications have emerged), why is France at risk (the CSE has appointed an expert, which will extend the consultation timeline).
The rationale layer is what transforms reporting from a status update into an actionable decision tool. Without it, every steering committee meeting becomes a round of "can someone explain what is happening in Germany?" followed by someone pulling up an email chain.
This dual-layer reporting only works if the data layer of the operating model is properly designed. If local teams are capturing consultation steps, representative body interactions, document submissions, and response timelines in a structured system, then the rationale layer can be generated from the data. If they are tracking all of this in emails, local spreadsheets, and slide decks, then the rationale layer requires manual narrative reconstruction every reporting cycle — which means it is always late, always incomplete, and always dependent on whoever assembles the pack.
What happens when the operating model is not clear
It is worth being explicit about the failure modes, because they are common and they are expensive.
Duplication. Multiple teams assess the same question independently. The HRBP asks external counsel for a legal opinion on consultation requirements. The central LR team commissions the same opinion from a different firm. The local ER lead has already obtained advice internally. Three pieces of work, three invoices, three potentially different answers.
Gaps. No one owns a critical step. The most common gap is the handoff between consultation completion and implementation. Everyone assumed someone else was confirming that consultation was finished before shared services began processing changes.
Conflicting advice. Without clear governance, different functions give the business different answers. Legal says the consultation must run for 45 days. The programme team says the timeline only allows for 30. The HRBP tries to split the difference. The result is a process that satisfies no one and may not satisfy the law.
No single view. The central team cannot produce a reliable picture of programme status because data is scattered across countries, formats, and systems. Every reporting cycle is a scramble to collect, reconcile, and assemble information from local teams who are all tracking things differently.
All of these are operating model failures, not people failures. The individuals involved are usually competent and well-intentioned. The problem is that the model does not make clear who does what, in what sequence, using what tools, and reporting to whom.
Why generic project tools fail
When organisations do not have a purpose-built platform, they default to whatever project management or collaboration tool is already available. Spreadsheets, generic workflow tools, project management applications. These tools can be made to work for a while, but they fail in predictable ways.
First, they have no concept of labour relations data structures. A generic project tool does not know what a works council is, what a consultation timeline looks like, what a social plan contains, or how representative body composition should be tracked. You end up building these structures by hand, and they are fragile — dependent on whoever set them up and difficult to maintain as the programme evolves.
Second, they cannot handle jurisdiction-specific workflow variation within a common reporting frame. You either standardise the workflow (which misrepresents some countries) or you let each country build its own (which makes rollup reporting impossible without manual reconciliation).
Third, they provide no data freshness monitoring. In a multinational labour relations programme, information goes stale quickly. Representative body members change, agreements expire, consultation statuses shift. Without active monitoring of data freshness — knowing not just what the data says, but when it was last confirmed — reporting reliability degrades over time.
A purpose-built platform for multinational labour relations addresses these gaps structurally. Landscape reporting shows the full labour relations footprint across every jurisdiction, with interactive views so leadership can see the shape of the organisation's employee representation at a glance. Configurable consultation workflows allow each jurisdiction to follow its own process while feeding into common reporting. FreshScore monitoring (a 0-100 measure of data freshness) flags when representative body data, agreement records, or consultation statuses need to be reviewed and confirmed. Change Advisory Gateway workflows coordinate multi-country assessments so a single restructuring initiative can be tracked through parallel consultation processes in different markets. Agreement databases with version control and expiry tracking manage collective agreements and social plans as living documents rather than archived files. And reporting pulls directly from live workflow data, so the rationale layer is generated from the system rather than assembled manually.
Getting started: sequencing the operating model design
If you are building or redesigning a labour relations operating model, the sequencing matters. Start with governance. Get decision rights clear before you design processes, because processes without clear ownership will not stick. Then design the data layer — define what information needs to be captured across every jurisdiction and in what format. Then build the process layer, making it configurable by jurisdiction but consistent enough in structure to support common reporting. Finally, design the reporting layer to serve the audiences who need it: steering committees, regional leads, country teams, and executive sponsors.
Resist the temptation to start with the tool. Organisations frequently begin by selecting a platform and then try to build the operating model around whatever the tool supports. This produces an operating model shaped by software constraints rather than by programme needs. Define the model first, then select a platform that supports it.
That said, the platform choice matters. A platform that natively supports configurable workflows, structured consultation tracking, landscape reporting, data freshness monitoring, and dual-layer status-and-rationale reporting will make the operating model dramatically easier to sustain. A platform that requires you to build all of this by hand will impose ongoing maintenance costs that erode the model over time.
Graylark LRM provides the control-tower architecture described here — central reporting with configurable workflows that adapt to local regulatory requirements across jurisdictions. Its landscape reporting, FreshScore monitoring, and Change Advisory Gateway are designed specifically for the way multinational labour relations operating models need to work.
See how Graylark LRM supports global operating models