LensReading which lens this session carries.
Every coverage statement

Function coverage

Procurement & Source-to-Pay

The platform observes 70.0% of the 8,940 items a week in scope here, reconstructs 20.0%, and estimates that 894 happen where it cannot read them.

The method behind this statement

Source system count · owned by Chief Procurement Officer · Function head

Observed is the count the source systems return.

Observed comes straight from what the connected systems return. The remainder is split between what the platform can reconstruct and what it is told exists.

What is happening in the unseen share

Off-contract buying settled on a corporate card and reconciled later.

Who has signed for it

Nobody. This figure rests on its method alone.

An attestation would not turn an estimate into a measurement.

Work filed here that the platform could not see

3 items have been filed by somebody who did the work off-platform.

Supplier agreed a price hold by phoneDeclared · accepted
IN-0001 · Diego Fuentes · Procurement · supplier management
Off-contract purchase on a corporate cardDeclared · accepted
IN-0006 · Kwame Boateng · Procurement · tail spend
Paper invoice received by the business unitDeclared · accepted
IN-0018 · Sofia Kalogeropoulou · Procurement · invoice intake

Gaps raised against this function

2 gaps in a chain that something must have filled.

Requisition approved → Purchase order issuedConfirmed by a filing · strong

A buyer is negotiating by email before raising the order, and that negotiation is not in any connected system.

SP-0001 · 189 instances · median gap 61.5 hours
Invoice received → Invoice matchedConfirmed by a filing · strong

Invoices are arriving at sites by post and being forwarded in batches.

SP-0002 · 158 instances · median gap 402.0 hours

What this statement is, and what it is not

Coverage can only ever be estimated from the outside.

A coverage statement is disputable by design.

Compare against every other statement