Output adherence
Objective. Define output adherence as the top adherence layer, show how delivered work is compared with the output standard, and keep it distinct from schedule and work adherence.
A dictionary entry. Output adherence measures whether the work actually delivered during scheduled time met the expected output standard - the layer that tells you whether the activity produced enough, which schedule and work adherence do not.
See it in the demo
What it is
Output adherence answers the question the other two adherence layers cannot: was enough actually produced? It compares the work delivered against the expected output for the scheduled time, at the agreed standard. Schedule adherence (MET-14) confirms the person was on plan; work adherence (MET-15) confirms the time went to intended work; output adherence confirms whether that effort met the output standard. It is the point where adherence meets the Work Output view of delivered, standard-valued work.
How it is calculated
At app-logic level: delivered output for the period is compared with the expected output derived from the standard (see standard handle time, MET-08, and attainment, MET-09) for the scheduled productive time, usually as a percentage or ratio. Included: completed, counted work valued at the standard. Excluded or adjusted: uncompleted or unverified work, and work types that are not counted. The standards, the counting rules and the completion definition are configurable - confirm with product. Because it depends on standards and completion definitions, output adherence is only as trustworthy as those definitions and the coverage of counted work.
How to read it and the common misread
Read output adherence as the test of whether scheduled, intended effort turned into enough delivered work. Low output adherence alongside good schedule and work adherence points to standards, complexity, quality or process friction - not necessarily effort. The target is the customer's own standard and baseline. The common misread is the RTA rule stated positively: assuming that because someone was schedule-adherent and active, the output was fine. It need not be. A second misread is reading output adherence without checking the standard and completion definition behind it, or treating a projection of expected output as an achieved result.
Where it appears
In Real-Time Adherence as the top layer of the layered adherence view, and conceptually connected to Work Output, where delivered work, standards, attainment and quality live. Read it together with schedule and work adherence, never alone. Demo figures are seeded illustrations.
Interpretation check
Output adherence is the only adherence layer that tests whether enough was actually produced. Being schedule-adherent and active does not guarantee the output standard was met.
Practical task
In the RTA demo, read all three adherence layers for one agent together and write a two-sentence summary that no single layer could support, then note the standard and completion definition you would confirm with product before quoting output adherence to a customer.
Self-check
What does output adherence measure that schedule and work adherence do not?
Whether the work actually delivered met the expected output standard for the scheduled time - the adequacy of the result, not just following the plan or doing the intended activity.
An agent is schedule-adherent, work-adherent, but low on output adherence. What does that suggest?
That effort and plan were right but delivery fell short of standard - look to standards, complexity, quality or process friction rather than assuming low effort.
Why is output adherence only as trustworthy as its standards?
It is derived from the output standard and the completion/counting definitions. If those are wrong or coverage is incomplete, the adherence figure is unreliable - confirm them with product.
What is the difference between expected output and achieved output here?
Expected output is a projection from the standard; achieved output is delivered, counted work. Presenting a projection as an achieved result is a misread.
Verified vs demo. The demo shows output adherence on seeded standards and output. A customer's output adherence depends on their standards, completion definitions and counted-work coverage, which must be validated in their instance.