Active time and elapsed time in operations
An item may take four days from accepted intake to confirmed completion while receiving only a few short periods of evidenced work. That difference can reveal where elapsed time accumulates, but it is not a direct measure of employee effort. Unknown states, parallel work, and delayed updates can change the ratio.
The GAO process-reengineering framework pairs cycle-time reduction with activity analysis and performance measures. A small-team study can borrow that separation by measuring total elapsed time and evidenced activity as related but different quantities.
Define states before timing them
Freeze the intake and completion events. Then define observable states such as active handling, waiting for internal review, waiting for external input, scheduled hold, blocked, completed, and unknown. A status label counts only when its entry and exit evidence meet the stated rule.
Preserve event time, record time, source, editor, and correction history. The NIST log-management guide describes consistent timestamps as part of usable event records. A workflow export with precise display times can still be unreliable when users record different events.
Do not infer continuous activity from one open status. Use bounded intervals supported by an action record, version change, communication event, or system transition. Label gaps as unknown rather than assigning them to active or waiting time.
Reconcile the elapsed timeline
For each item, elapsed time runs from the frozen intake event to completion or the study boundary. Partition that interval into mutually understood state segments. Preserve overlaps when two people or systems work at the same time, and avoid adding overlapping minutes as though they were elapsed clock time.
Report active, waiting, unknown, and overlap duration in the same unit. If a flow-efficiency ratio is used, place state coverage and unknown time beside it. A high ratio based on poorly observed states is not stronger evidence than a lower ratio based on complete records.
Use medians and distributions across comparable work classes. The NIST run-sequence guidance supports examining ordered behavior, while its histogram guidance supports looking beyond a single average. Retain open items separately because their elapsed duration is still accumulating.
Interpret time composition without blame
Waiting may be required by a control, customer decision, appointment date, or contractual cooling period. Active time may include necessary review and correction. The study identifies where time is recorded, not whether each interval is waste or whether one person worked quickly.
Compare state patterns before and after a process change only when definitions, coverage, and work mix remain comparable. If event capture changed, report the measurement break instead of presenting the ratio movement as operational improvement.
An operations coordinator can maintain state definitions, reconcile timelines, and publish coverage. Process owners decide which waits are required and which experiments are safe. Our operations support services can maintain this evidence, and the Research index contains related flow studies.
Sources and limits
- GAO process-reengineering framework, for activity analysis, cycle time, and performance measures.
- NIST process characterization, for defined inputs, outputs, and process behavior.
- NIST log management guide, for timestamped event records and clock consistency.
- NIST timestamp data quality, for event time, latency, and clock deviation.
- NIST run sequence plot, for ordered process observations.
- NIST histogram guidance, for duration distributions.
- NIST uncertainty guidance, for stating measurement uncertainty.
- GAO data reliability guide, for accuracy, completeness, and applicability.
- Census data management standard, for reproducible processing and retained versions.
- NIST Research Data Framework, for provenance and change records.
These sources support a state and duration measurement design. They do not define universal active states, prove waste, or measure individual productivity. This article is operational research guidance, not employment, audit, timekeeping, or service-level advice.