Chemical firm Syngenta to quit Grangemouth, putting 400 jobs at risk
Summarised from 3 outlets · 4 reports · Updated 2 Oct, 19:01 · Archive
Syngenta announced plans to cease operations at its Grangemouth site, putting almost 400 jobs at risk.
Syngenta announced plans to cease operations at its Grangemouth chemical plant in Scotland, putting almost 400 jobs at risk. The company said its Grangemouth operation was no longer 'competitive' due to increasing competition from overseas.
The potential job losses would affect hundreds of workers at the major Scottish chemical site. The announcement came after previous job losses at the Grangemouth facility.
In response to the news, the SNP demanded the UK Government urgently deliver £200 million of promised investment for Grangemouth. The party called on the government to act quickly to protect jobs and support the site's future.
How it is being reported
- SNP demand promised £200m for Grangemouth as hundreds of jobs at riskTHE SNP have demanded the UK Government urgently deliver £200 million of promised investment for Grangemouth after almost 400 more jobs were put at risk.The National · 2 Oct, 14:56
- Hundreds of jobs under threat at Grangemouth chemical plantSyngenta said its Grangemouth operation was no longer 'competitive' due to increasing competition from overseas.BBC Scotland · 1 Oct, 16:54
- Hundreds of jobs at risk as major Scottish chemical site faces closureHUNDREDS of jobs are at risk after a major chemical firm announced plans to cease operations at its Grangemouth site.The National · 1 Oct, 15:12
- Hundreds of Scots jobs at risk as chemical manufacturer announces plans to quit countryHundreds more jobs could be lost in Grangemouth next year as a result of Syngenta's plan, which could cost almost 400 jobs.Daily Record · 1 Oct, 14:58
In this story: Syngenta · Grangemouth · Scotland · SNP · UK Government
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)