Workflow Cycle Time vs Hands-On Time: What Is the Difference?

Define the start and finish first

Cycle time requires a consistent trigger and completion event. For a proposal, the trigger might be an accepted request and completion the submitted document. For monthly reporting, it might begin when required data is available and end when the approved report reaches the client. Changing these definitions between periods makes the metric unreliable.

Hands-on time is the sum of active work inside that boundary: research, entry, drafting, checking, correction and communication. It can be estimated through samples or measured with workflow events where available.

Calculate the two metrics

Flow efficiency can reveal a waiting problem, but use it carefully. Calendar hours include nights and weekends unless the business defines working-time cycle measures. Publish the convention beside the result.

What hands-on time tells you

Active time supports capacity planning and directional labour cost. If monthly volume rises, the team can estimate additional effort. Breaking active time by stage also shows whether research, drafting, formatting or review consumes the most capacity.

Reducing hands-on time can release capacity, but only if the saved time is real, adopted and usable elsewhere. A faster task inside a blocked workflow may not improve delivery.

What cycle time tells you

Cycle time exposes queues, approval delay, missing inputs and handoff friction. A process can require little labour and still feel slow to a client. Measure median and variation rather than only the average; a few extreme cases can distort the mean.

When cycle time is the target, record where each item waits. Otherwise the team may speed up the wrong active stage.

Illustrative time map

Illustrative example—not a client result. A report takes 72 elapsed hours from request to delivery. Research uses two active hours, drafting 1.5 hours and final sending 0.5 hours: four hands-on hours total. The remaining 68 hours are queue and approval time.

Draft automation might remove one hour of active work but leave the three-day delivery unchanged. Clarifying approval ownership could reduce cycle time without changing production labour. The correct intervention depends on the target.

Use one primary metric and guardrails

If the business problem is late delivery, cycle time or on-time completion may be primary while hands-on time and rework act as guardrails. If the problem is capacity, hands-on hours or cost per output may be primary while cycle time and quality remain guardrails.

The Workflow Cost Calculator estimates active labour and visible cost. Pair it with timestamps when elapsed delay matters.