1:1
Traceable conversion
Governed origin exists and the work can be followed to a current or final state. This is the TR numerator.
Revenue lands on plan. Utilization looks healthy. The dashboard is green. None of that proves the operating model converted strategy into governed value. It proves outcomes were reported.
Reported is not the same as proven.
A baseline is only as defensible as the work population underneath it. Where detected work cannot be reconciled to a governed origin, the plan is priced on what the model admitted while capacity is consumed by that plus everything it never saw.
The hatched band is the part no one budgeted. Until it is reconciled it should be read as exposure-at-risk — some of it resolves into lineage noise, and the rest is drawing capacity the forecast never priced.
The ratio is worth most before the forecast is banked. Afterward it stops being a baseline input and becomes an explanation.
Before an opex, performance-improvement or automation case is promised, the ratio says how much of the work behind it the model can actually follow.
A high ratio would not have guaranteed the forecast. It would have made the forecast’s exposure legible before it was banked.
Finance, delivery, process and governance analysis each read their own observed population. The ratio says whether that population is complete enough to trust.
The pressure on the 2026 agenda is cost, automation and return — all of it priced against work populations most operating models have never reconciled. Banking learned the same principle through failure: after the financial crisis, the Basel Committee made risk-data aggregation a control issue, not a data-quality nicety. Transformation work has rarely been held to that standard.
of business transformations fail to achieve their original ambitions.
of finance organizations have implemented or plan to implement AI. Seven percent report a high or very high impact from it.
of North American CFOs name digital transformation of finance their top priority for 2026.
of firms achieved 100% or more of their annual margin target — alongside billable utilization at a survey low.
Automation does not create the traceability problem. It raises the cost of scaling an operating condition leadership cannot explain.
Value-producing work should be followable from governed origin to current or final state, proof, and correction.
This does not mean traceability proves causation or value realization. It means traceability creates the operating condition required to test and defend a transformation claim. Leaders cannot prove the operating model changed if they cannot follow the work the model is supposed to govern.
Not reported. Not completed. Not counted. Followable.
The unit rule: every detected unit of value-producing work should reconcile to a governed Get record, or an explainable lineage back to one.
The work entered through a governed origin and can be followed to a current or final state.
The work was detected downstream, but no governed origin can be found.
Traceability Ratio™ = exposure-weighted 1:1 work states ÷ total detected work exposure (1:1 + unresolved 0:1)
In plain language: the share of detected work exposure that reconciles to a governed origin.
Exposure-weighted.
Unit count, within comparable work classes.
A board should not read a $5 million engagement and a $5,000 request as equal units.
The asymmetry is deliberate. The ratio starts with what happened and reads backward, so its denominator is detected work exposure. Unresolved 0:1 is treated as additive until reconciled: it may be bypass work, lineage failure, duplicates, late admission, or a parent-child split. Until the enterprise knows which, the exposure is at risk.
To qualify as 1:1, an origin must:
exist at or before commitment or first material execution — or, for approved exceptions, be reconciled within the defined window;
enter through an approved channel or approved exception path;
carry an accountable owner;
identify the work class or commitment;
include a unique work ID or approved parent-child lineage;
attach at least a basic economic or risk exposure reference.
Thin-but-real admission can count. Backfilled administrative cover cannot.
A retrofitted record is not traceability — it is cleanup theater.
The ratio begins with the observed population: of what the enterprise later detected, how much can be followed back to governed origin. Reverse the reconciliation and a different question appears — of what the enterprise governed and admitted, how much ever produced a qualifying downstream state? That second read does not change the ratio. It exposes an operating condition the ratio was never designed to count.
Governed origin exists and the work can be followed to a current or final state. This is the TR numerator.
Governed origin exists, but no qualifying downstream state exists within the applicable read. Outside the TR denominator.
Work exists downstream but the model cannot reconcile it to governed entry. The potential hidden factory.
No work unit exists in either ledger. At the capability level, persistent zero admission and zero throughput may still matter if capacity remains supplied.
The 1:0 cell is not automatically failure. Work can be legitimately waiting, future-dated, paused, canceled or explicitly deferred. The meaningful residual is what remains after approved timing, aging and disposition rules are applied. When budget, capacity, obligation or strategic dependency remains attached to that residual, the operating model is carrying a commitment that has not converted.
The 0:0 condition needs another level of analysis. There is no orphan work item to detect, because neither ledger contains one. What can remain is the operating surface itself — specialist capacity, licenses, vendor commitments, platforms, management structure or facilities that carry cost while meaningful demand and throughput approach zero. The issue is not inactivity alone. It is inactivity the enterprise cannot explain or economically justify.
Neither residual is automatically failure, and neither belongs inside the ratio.
Of the work exposure the enterprise later detects, how much reconciles to a governed origin?
It does not measure whether the work performed well.
It is not a project-status score, a data-quality score, or a leakage score.
It does not replace finance, delivery, project governance, process mining, or capacity economics. It tells leaders whether those instruments are reading a complete enough work population to be trusted.
The prior questionOf the exposure-bearing work the enterprise later detects, how much entered the operating model in the first place?
Why leaders may be defending a number their operating model cannot trace.
The technical paper behind this instrument. It defines traceability as a proof principle, specifies the Traceability Ratio™ as the metric produced by applying it to detected work, and sets out the origin–flow state read in full. Written for executives, boards and value-creation leaders accountable for converting transformation investment into governed execution and measurable enterprise value.
Traceability Ratio™ is an instrument of the ZBTOS system. ETEGY runs the read inside a mandate. ZBTOS teaches your people to run it themselves.