Published November 2, 2026

Question and scope

This protocol asks how capacity variance can be described from the operating record, using one defined population and one observation window. The the operations director owns the decision.

Population and unit of analysis

The unit is one capacity observation, from opening event through recorded close. Keep linked revisions separate and record the source date and owner.

Definitions and measures

Define the opening event, closing event, pause rule, and missing-evidence rule before collecting capacity variance data. Report eligible count, sample, exceptions, and unresolved items.

Evidence standard

Record the source, observation time, field supported, reviewer, and decision owner. Keep restricted operational data in the approved system. Example: Averages can hide one overloaded queue; demand, waiting, and rework need separate definitions.

Sampling and collection

Sample routine, exception, and reopened records. Preserve the original observation when a definition changes and label the new rule for later cases.

Analysis and reporting

Report observation separately from interpretation. Show the oldest open item and missing fields, not only the completion rate. Name the next decision and its owner.

Limits and sources of error

The cited public sources frame operating records, privacy, security, and internal-control practice in general terms; they do not provide a local result or a management conclusion for a specific team.

Review cadence

Review the result on a fixed date and end with one process change, one owner, and one check date. A repeated defect should change the template before it changes coaching.

Sources