Outcomes & measurement

What the pilot will prove — measured, not asserted.

This is a measurement framework, not a results page: we have no customer results to show yet, and we will not invent any. Here is exactly what a pilot tracks, how it is counted, and what the desk shows you. The desk itself is a control layer for unresolved work between your existing systems — these measures are how it proves it belongs there.

The framework

Seven measures, counted honestly

Agreed in week 0 of a pilot. Each one has a definition, so there is no arguing about the numbers in week 4.

01

% of requests with an owner

The single most telling number in an operation. If open requests routinely lack an owner, work is being decided by whoever noticed it first.

02

Submission-to-acknowledgement time

How long before someone takes responsibility. Measured against the response targets agreed for each urgency level.

03

Age of open requests

How long the oldest open request has been waiting — and the shape of the whole queue, not just the average.

04

% past target response time

Requests that missed their first-response target, counted honestly — including the ones nobody looked at.

05

Duplicates

The same issue reported twice because the first report vanished. A direct measure of intake failure.

06

Volume by category and location

Where the work actually comes from — the raw material for staffing and prevention decisions.

07

Escalations

How many requests escalated, how fast they were acknowledged, and whether safety escalations ever waited.

Illustrated

What the desk shows

Sample views built from fictional data — the same measures your pilot would track, with your real numbers once you are running.

What the desk measures

The measures a pilot tracks — your real numbers appear here once you are running.

Requests with an owner

94%

of open requests

Median time to first acknowledgement

3.2 h

last 30 days

Requests past response target

6

open right now

Safety escalations acknowledged

12 / 12

last 30 days

Recurring issues flagged

4

this month

Vendor commitments missed

2

last 30 days

Illustrative workflow using sample data. No customer data shown.

Open requests by age

How long the open queue has been waiting, stacked by status.

Open requests by age (sample data)0–1 daysNew: 2Escalated: 242–3 daysNew: 1Assigned: 2In progress: 364–7 daysNew: 1Assigned: 2In progress: 2Needs review: 168–14 daysNew: 2Needs review: 1315+ daysNew: 11
NewAssignedIn progressNeeds reviewEscalated

Illustrative workflow using sample data. No customer data shown.

Later

From measures to case studies

Once pilots complete with customer approval, this page becomes real case studies: named customers, documented before-and-after, approved evidence. Until then, it stays a framework — because invented results would poison the trust a pilot is meant to build.

See a sample evidence pack →

Next step

Agree the measures for your operation.

Tell us what “working” means for your team, and we will build the pilot's success criteria around it.