Organisation · Contracts Finder · London Borough of Merton

London Borough of Merton

Identity
organisation:contracts_finder:London Borough of Merton — the Contracts Finder key, used as-is. No identity here is invented.
Graph built
5 September 2026

Names in the records

Each spelling a register uses for this entity, and the method that tied it here. A name is never the identity; a similar name is never a match.

As publishedRegisterTied byConfidenceRows
London Borough of MertonContracts Finderexact name within one register1.04

What the records establish

  • London Borough of Merton: 4 records of "awarded the contract" between 11 June 2026 and 11 August 2026, £6,494,968 in total where a figure is published.
All 4 recorded relationships. Kind: FACT — every row is a register's own record; nothing on this page is computed.
RelationshipWithDateAmountDetailRecord
awarded the contractCANNIZARO TOILET BLOCK REFURBISHMENT11 August 2026£35,000Construction workpublic_contracts
awarded the contractLaptop Refresh11 August 2026£2,019,968Portable computerspublic_contracts
awarded the contractTransformation Programme7 August 2026£4,000,000Technical analysis or consultancy servicespublic_contracts
awarded the contractWifi Additional Requirement11 June 2026£440,000IT services: consulting, software development, Internet and supportpublic_contracts

What this does not establish

The records above establish that London Borough of Merton and each entity named appear together in an official register, in the relationship that register records, on the date it records. They do not establish why any donation was made, why any contract was awarded, whether any one record was known to the people behind another, or that any record caused another. No causal inference is made on this page, and nothing here is a finding of any kind against anyone. A reported donation is a lawful, reported transaction; a contract award is a published notice; a seat is a seat.

The same name elsewhere in the records

A register spells another entry exactly as it spells this one. The graph keeps them apart because no register says they are the same, and a shared name is not evidence that they are.

Derived from: public_contracts. Each row above names the table and key it came from and links the official record where one exists. How the graph is built is described at the evidence graph.