LensReading which lens this session carries.

End-to-end outcomes · one chain

OI-HTP-0072 — Hire to productive

One hire followed from an offer is accepted and a hire event is created to the joiner is paid correctly for a full period, across every function and tower it touched.

Hire to productive — all chains
State
Open
The week ended before the chain could reasonably finish.
Chain cycle
6.2 d
Wall clock, first stage start to last stage end
Of which waiting
38.6 h
26% of the chain was queue, not work
Cost to serve
$109.37
10 touches over 2 stages
A person intervened
2×
At 2 stages, marked below
Match confidence
0.62
Cohort

What this chain is, and how sure we are it is one chain

Identity, counterparty and the correlation key

The unit
Beatriz Salgado
Japan · Asia Pacific · JPY
Started Tue, Aug 11, 20:58, and has not ended inside the observation window.
How the stages were joined
Cohort · 0.62
The chain crosses a boundary and no usable party join exists on either side.
A chain is only as sure as its weakest join, so the figure above is the minimum across the 1 joins below, not their average.
How much of the service ran
2 / 3
2 functions · 2 towers
1 of the 3 stages were never found; the chain stops after first pay run. That is the chain as observed, not proof the work did not happen elsewhere.

The chain, stage by stage

2 stages · 38.6 h waiting · 4.6 d in work

01Hire recorded a person intervened
CG-H2R-009179Hire eventhcmHRH2RSanjay Raghunathan
The chain starts here.
In work
2.8 d
Touches
5
Handling
manual
Join
Origin
On the document
$0
Handoff wait before this stage: 38.6 h — nothing was being done to the hire for that time.
02Access granted a person intervened
CG-IT-012768Access requestitsmITITSYasmin Chaudhry
Both sides of this step name a party, and the two namespaces barely meet …
In work
43.0 h
Touches
5
Handling
manual
Join
Cohort 0.62
On the document
$0
The amounts in the right-hand column are what each document carried, and they are deliberately not added up — the same money is written down once at each of the 2 stages this hire passed through. This service carries no monetary value at all — it is internal work — so no value figure is shown for it anywhere.

Where a person intervened

2 of 2 stages were not touchless

Hire recorded
manual
Sanjay Raghunathan · HR · Hire-to-Retire · 5 touches over 2.8 d
Access granted
manual
Yasmin Chaudhry · IT · IT Service · 5 touches over 43.0 h
Across the 133 complete chains of this service the median is 1, so this one sits above the middle. A stage counts here when its handling is assisted or manual; touchless stages are excluded.

What the time and the money went on

The chain decomposed

Waiting
38.6 h
26% of elapsed time
In work
4.6 d
74% of elapsed time
Waiting and work are an exhaustive split of the 6.2 d this chain took — every hour is in one bucket or the other. The longest single wait was 38.6 h before access granted.
Cost to serve, $109.37
10 touches at 11 minutes of loaded time each$106.33
2 stages of inference and system cost$3.04
Cost to serve is modeled from the touches the ledger recorded, not billed from a timesheet.
No stage on this chain raised an exception.

The same chain for the whole week, as a distribution

133 complete hire to productive chains, 10–16 August 2026

this chain sits at the 98th percentile
5
10
8
32
29
22
9
14
2
2
2.3 dten equal bands of chain cycle time6.7 d
Median chain
4.3 d
p25 3.8 d · p75 4.7 d
Slowest tenth
5.4 d
worst seen 6.7 d
Median waiting
3.4 d
76% of the median chain is queue
Median cost
$15.19
p90 $47.09
The mean of 4.3 d sits above the median of 4.3 d, which is why the distribution is drawn rather than reported as an average: the gap between the median and the slowest tenth is 28.3 h, and it is that tail, not the average, that customers of this service actually feel. This chain is not complete, so it is not in the 133 above. The commitment is 720 hours; no chain started early enough in a one-week window to be judged against it.
The ledger behind these chains is one week, 10 to 16 August 2026, which is 168 hours. A chain that had not finished when the week ended is open, not late: the week simply stopped watching it. A chain whose commitment falls after the end of the week could never have been seen to miss, so its service level reads not measurable rather than holding. Nothing on these pages should be read as a monthly or annual attainment. This chain had not finished when the window closed, so its cycle time is a floor, not a duration — it is right-censored, and it is not counted as a breach anywhere on this platform.