LensReading which lens this session carries.
Every coverage statement

Function coverage

Sales

The platform observes 50.0% of the 4,820 items a week in scope here, reconstructs 25.0%, and estimates that 1,206 happen where it cannot read them.

The method behind this statement

Source system count · owned by Chief Revenue 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

Field negotiation held in email and in the account team’s own spreadsheets before anything reaches the quote system.

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

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

Order taken by phone in the fieldRecalled · pending
IN-0013 · Beatriz Salgado · Sales · field orders
Trade claim agreed in a customer meetingStructured claim · accepted
IN-0014 · Rafael Duarte · Sales · trade claims

Gaps raised against this function

1 gap in a chain that something must have filled.

Quote issued → Order bookedConfirmed by a filing · strong

Field orders are taken verbally and keyed the following day under the representative’s own login.

SP-0003 · 55 instances · median gap 19.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