Two clocks are running
When a task starts, one clock measures labour and another measures the calendar. Active time counts periods when someone is actually working. Elapsed time includes waits, queues, overnight periods, weekends, approvals, drying, shipping and other gaps.
Mixing the two causes planning mistakes. A maintenance action may need 90 minutes of technician effort but occupy a four-hour service window. A document may need 30 minutes of editing but remain in review for two business days. Both statements can be true.
Why the distinction matters
Labour capacity is usually planned from active time. Customer promises, project milestones and appointment windows are usually experienced as elapsed time. If a team reports only one of these, managers and customers can draw the wrong conclusion about workload or responsiveness.
The distinction also changes the effect of added staff. Two people may shorten a divisible work package, but neither can compress a fixed external wait. Parallel work helps only where tasks are genuinely independent and resources are available.
A simple recording method
For recurring processes, track at least four fields: start time, finish time, active effort and reason for major waiting periods. That small dataset often reveals whether the biggest opportunity is faster work, better scheduling, fewer queues or faster decisions.
On this site, calculators intentionally show active and waiting components separately whenever possible. That makes the assumptions visible rather than hiding everything inside one final duration.