supplier · GB-COH00395826
Balfour Beatty PLC
as a supplier
7 recorded awards from 5 buyers , between 30 Apr 2016 and 25 Aug 2022.
“Exclusive” means this organisation was the only one awarded under that procurement; the rest were shared with other suppliers, typically on a framework.
No median is shown because every award here carries a framework ceiling rather than a settled price. A ceiling is the most that could be spent across every supplier on the agreement, so averaging them would overstate this organisation’s work, often by an order of magnitude. The individual values are listed below as published.
sells to
| buyer | awards |
|---|---|
| Rotherham Metropolitan Borough Council | 2 |
| Southampton City Council | 2 |
| Derby City Council | 1 |
| King's Lynn and West Norfolk Borough Council | 1 |
| Transport for London | 1 |
contracts won
| contract | buyer | value | awarded |
|---|---|---|---|
| TD1972 - TCF Derby Road - NEC4 ECSC Option A Contract for Enabling Works - Balfour Beatty | Derby City Council | £192,526 | 25 Aug 2022 |
| College Road Roundabout NPIF | Rotherham Metropolitan Borough Council | £3,800,000 | 30 Aug 2018 |
| A630 Parkway Widening Scheme | Rotherham Metropolitan Borough Council | £3,400,000 | 30 Aug 2018 |
| TfL Property Partnerships Framework shared | Transport for London | £5 | 30 Apr 2016 |
| Hunstanton Coastal Defence Project Design & Consultation | King's Lynn and West Norfolk Borough Council | · | 14 Apr 2026 |
| Highways Services | Southampton City Council | · | 13 Oct 2025 |
| Highways Services | Southampton City Council | · | 13 Oct 2025 |
every contract won by Balfour Beatty PLC →
as published
This page combines 2 separate records from the source data. Every one is listed below exactly as the publisher filed it, so you can check the grouping yourself.
| name as published | identifier | postcode | records |
|---|---|---|---|
| Balfour Beatty plc | GB-COH 00395826 | E14 5HU | 6 |
| Balfour Beatty PLC | · | · | 1 |
why these were combined
- identical name · balfour beatty plc 1
Matching uses organisation identifiers where publishers provide them, falling back to name and address. Records are never combined on address alone, because one shared-service postcode carries 244 different organisations. how this works