In breve

Multi-site plant restructuring fails on order rather than on intent. Each reduction, transfer and capacity increase carries an owner, a business case and a milestone plan. The order between them carries none of those things. Shared engineers, customer approvals and national consultation calendars are finite. Three programmes drawing on the same ones in one quarter will compete. That competition sits on no project report, and it stays nobody's line item until a customer notices.

Three sites change in the same quarter, and every plan assumes it is alone

A group approves a headcount reduction at one plant. At a second site it approves a closure and a transfer of the work. At a third it approves the extra volume that will receive it. Each decision is sound, with a sponsor, an approved saving and a date. Nothing in that structure asks whether one company can execute all three at once.

The volume of this activity makes overlap normal rather than exceptional. CLEPA reported 18,900 European automotive supplier job cuts announced in the first half of 2026. That is 35 per cent below the second half of 2025, against 4,840 jobs created. Those figures are announcements, not realised reductions. Each becomes a multi-site plant restructuring programme somewhere in a network.

Strategy& took a similar view in its Automotive Supplier Study 2026. It says that capacity adjustments and debt reduction “must move forward much faster to free up capital for future investments”.

Speed at group level and speed at site level are different quantities. Multi-site plant restructuring exposes that difference within the first quarter. A board can approve three changes in one meeting. The group executes them through the same engineers and the same quality teams. It also needs the few people who know how a line behaves.

Why multi-site plant restructuring is harder across borders

Each site reports through a different country team. Each change runs as its own programme, under its own legal and industrial relations track. A group COO reading the portfolio view sees three projects of similar size. The site view shows three employer obligations, three sets of employee representatives and three sets of customers to inform. None of those tracks compresses to suit a group timetable.

CEE network capacity changes run on separate legal clocks

Collective redundancy procedure takes its shape from Council Directive 98/59/EC on collective redundancies. The duties that bite are national. Czechia applies the Labour Code (Act No. 262/2006 Coll.) and notifies the Labour Office, the Úřad práce. Slovakia applies section 73 of its Labour Code (Act No. 311/2001 Coll.). Poland works to the Act of 13 March 2003 on collective redundancies. Hungary applies the Labour Code (Act I of 2012) and Romania the Labour Code (Law No. 53/2003).

Where a change qualifies as a transfer of an undertaking, Directive 2001/23/EC on transfers of undertakings adds its own information duty. Once member states transpose Directive (EU) 2025/2450 amending the European Works Council Directive 2009/38/EC, transnational matters carry a further consultation step. German sending sites add the Betriebsrat and, in automotive, IG Metall. CEE network capacity changes therefore start from different triggers in each country, and a group calendar cannot align them.

Parallel plant transfers put group resources in competition

Customer approval runs on a clock of its own. IATF 16949 sets out control of changes at clause 8.5.6.1, including customer notification and approval where a manufacturing location changes. The AIAG PPAP manual treats production from a different plant as a submission trigger.

In a group running parallel plant transfers, several submissions reach the same customer quality team in the same weeks. That team then sets the pace. The same competition applies to launch engineers, supplier quality engineers and the maintenance teams who move equipment. CE Interim's account of tooling transfer during a plant closure in Hungary sets out the two-clock problem at one site. A network multiplies it.

How to recognise that the order has no owner

The first signals are not financial. They show up in resourcing conversations, and in the distance between what each plant reports and what the group believes is happening.

• The group asks a receiving site to launch transferred work in the quarter it reduces its own headcount.
• Two plants book the same launch engineers for the same weeks, then settle it between themselves.
• Every project reports to plan, yet nobody at group level can say which change completes first.
• Several moves go to customers separately, with no view of the combined queue.
• A sending site schedules its buffer stock build after notices go out rather than before.

Any one of these is ordinary in a busy network. Together they show that the sequence exists only as the sum of individual plans, which means nobody has decided it.

Multi-site restructuring coordination needs one person who can make a site wait

Multi-site restructuring coordination requires one person with authority over the order of execution. That includes authority to tell a plant director an approved date has moved. In a multi-site plant restructuring that authority comes from the group, because no site will delay its own programme. Before any scheduling, the mandate holder settles, in order:

1. Which changes draw on the same engineering, quality and maintenance resource, and in which weeks.
2. Where several approvals reach the same customer at the same time.
3. What notification and consultation duties apply in each country, and which of them gate a stop date.
4. Whether a sending site must finish its buffer stock build before notices go out.
5. Which receiving sites can take work now, and which must wait behind their own change.

Where authority sits in a multi-site plant restructuring

Sequencing authority belongs above the sites and below the board. In most groups that means the group COO, supported by a Chief Restructuring Officer where the programme carries financing conditions. The test is simple: can this person move a plant's date without escalating, and will the plant comply? Where the answer is no, the group has coordination in name and not in fact.

La dimensione transfrontaliera nella pratica

A sequencer working only from headquarters sees plans, and one working only from a site sees that site. The role needs both. It means reading a German social plan negotiation, a Czech notification duty and a Romanian consultation step as one schedule. CE Interim, part of Valtus Alliance, works on multi-site plant restructuring across borders. The binding constraint is rarely capability at one plant, and almost always bandwidth across several.

What the documented transfers show

Eurofound's European Restructuring Monitor records Lear's announcement of 11 August 2026 that production at Gründau in Hessen would end. The closure affects about 180 production and logistics jobs, against a foreseen end date of 30 June 2027. The remaining production capacity moves to Slovakia, Serbia and Tunisia. One closure becomes three receiving operations in three countries, only one inside the European Union. Eurofound also records that the works council and IG Metall oppose the decision.

The pattern repeats across the region. Eurofound records Prodotti Inteva announcing on 16 May 2026 that its plant at Rychnov u Jablonce nad Nisou would close. Production moves to Romania, and the group keeps two other Czech plants. In Bulgaria, Eurofound records SE Bordnetze closing its Mezdra plant and cutting about 100 jobs at Karnobat. That site continued with reduced capacity, and production moved to Moldova and Romania. That is one group running a closure, a reduction and two receiving countries at once.

Eurofound's reading of the sector is that the reshaping is geographically uneven. A group's own sites are therefore not all moving the same way. Someone has to decide the order between them rather than inherit it. CE Interim's note on the Bosch plant closures follows the same movement of work into Central and Eastern Europe from the German side.

Domande frequenti

Who should sequence a multi-site plant restructuring?

One named person with group authority, usually the group COO or an executive reporting to them. Site leadership cannot hold it, because each plant director answers for a date that sequencing may have to move. A single functional owner cannot hold it either, because the conflicts cross engineering, quality, HR and logistics. The role needs authority over order, not depth in one function.

What actually collides when changes run in parallel?

Shared and finite resources collide first: launch engineers, supplier quality engineers, maintenance teams and customer approval capacity. Consultation calendars collide differently, because national rules set their length. Capital collides last, when transition costs at two sites land in the same reporting period. In a group running parallel plant transfers, the receiving sites usually feel all three.

Can a group programme office do this?

In a multi-site plant restructuring, a programme office often sees the collisions first. What it usually lacks is authority to resolve them, because it reports progress rather than directs sites. Where it holds real decision rights over dates, and the group enforces them, it can hold the sequence. Otherwise it keeps a record of a problem nobody can act on.

What authority does sequencing need?

It needs authority to change an approved date, and to hold a transfer until a receiving site is ready. Shared engineering and quality resource must move between plants on the same authority. The role also needs sight of each country's notification position, because a stop date the legal process cannot support is not a date. Without the first of those powers, multi-site restructuring coordination stays advisory, and advisory coordination loses to a plant director defending a committed milestone.

What happens when two sites have the same deadline?

One of them moves, by decision or by discovery. Deciding means choosing which site waits, telling the customer early and adjusting the saving profile. Discovery means finding out when a launch slips or the plant misses a delivery. The customer then sets the order. No published evidence shows how groups commonly sequence CEE network capacity changes, so common practice cannot settle it.

The decision in front of the group

Once the group has taken the footprint decisions, multi-site plant restructuring stops being a question of whether to restructure, sell or close a particular site. It becomes a question of order. Either the group executes those decisions in a sequence it has chosen, or in one imposed from outside. Customer approval queues, national consultation duties and the readiness of the receiving plant will otherwise set it. Choosing the sequence now is a planning decision, taken while dates remain internal. Discovering it later arrives as a missed delivery, with the saving profile already committed to a lender or a board.

The practical test is whether anyone in the group can tell a plant director to wait, and has the hours to use it. Where the executives who could hold it already run the changes they would have to sequence, those two jobs compete for the same hours. Some groups bring in an interim programme director to hold the sequencing mandate for the length of the programme. Where the bandwidth exists internally, the mandate should stay inside the group. Either way the order of execution gets set, by the group or by its customers and their calendars.