What is cycle time?
By Ledgerium Research TeamUpdated July 2026How we research this
Cycle time is the total elapsed time it takes for a process to run from its starting point to its finish — the sum of both the time actively spent working on it and the time it spends waiting between steps. It's usually measured directly from timestamped records of when each step started and ended, not estimated.
Key takeaways
- Cycle time is the full elapsed time from the start of a process to its finish, including both active work and idle wait time between steps.
- Cycle time is different from active work time: a process can have low active effort but a long cycle time if it spends most of its elapsed time waiting.
- Accurate cycle time needs a timestamp for when each step actually started and ended — estimates based on memory tend to understate wait time significantly.
- Breaking cycle time down by step usually reveals that a small number of steps or handoffs account for most of the total elapsed time.
Definition: Cycle time
Cycle time is the total elapsed time between the start of a process instance and its completion, measured end to end and including every phase in between — both the time actively spent performing steps and the time the process instance spends waiting, whether that is an item sitting in a queue, waiting for approval, or idle between handoffs. It is distinct from active work time, which counts only the effort directly applied to the task.
What counts toward cycle time
Cycle time covers the entire span from when a process instance begins to when it finishes, not just the parts where someone is actively working on it. That means it includes time spent waiting for an approval, sitting in a queue behind other work, or being idle between one handoff and the next. Because wait time is so often the larger share of the total, a process can look efficient when measured only by active effort and still have a long cycle time overall.
How cycle time is measured
Cycle time is measured by recording the timestamp at which a process instance starts and the timestamp at which it ends, then taking the difference; breaking it down further means capturing a timestamp at the start and end of each individual step, so the total can be attributed across the steps and handoffs that make it up. The reliability of the measurement depends entirely on the timestamps being accurate and complete — cycle times estimated from memory or from a rough sense of 'usually a few days' tend to significantly understate how much time is actually spent waiting.
Why cycle time matters
Cycle time is one of the clearest signals of where a process is actually losing time, because breaking it down by step routinely shows that the total is dominated by one or two slow handoffs rather than being spread evenly across the whole process. That makes it a natural starting point for improvement work: instead of guessing where a process is slow, a step-by-step cycle-time breakdown points directly at the handoff or approval step that is responsible for most of the delay.
How Ledgerium captures this
Ledgerium computes cycle time by timestamping the start and end of every step in a recorded workflow run and summing the elapsed time across the full sequence, so the figure comes directly from real execution rather than a manual estimate.
1. Install the extension
Add the Ledgerium recorder to Chrome. No screenshots and no keystrokes are ever captured.
2. Record the real workflow
Perform the process once. Ledgerium captures the structured steps, timing, and system context.
3. Get the output
Receive an SOP, a process map, and a workflow intelligence report generated from the real work.
Worth knowing
Ledgerium measures cycle time from the timestamps in a recorded workflow, so the figure reflects the runs that were actually recorded; it does not retroactively estimate cycle time for work that happened before recording began.
Sources
- Ledgerium AI — Product overview — verified 2026-07-18
- Ledgerium AI — Methodology (how we research this) — verified 2026-07-18
Frequently asked questions
- No. Cycle time includes the full elapsed time, including waiting and idle periods between steps. Active work time only counts the time someone is directly working on the task, which is usually a small fraction of total cycle time.
- It depends entirely on the process — there's no universal target. The more useful question is usually how a process's current cycle time compares to its own history, and which specific steps account for most of it.
- The first step is usually identifying which steps or handoffs account for most of the elapsed time, since cycle time is rarely spread evenly across a process — a small number of slow handoffs is a common finding.
- You need a timestamp for when each step actually starts and ends. Manual estimates tend to understate cycle time because people notice active work far more easily than idle wait time.
See this in a real workflow recording
Record a workflow once and get a structured SOP, a process map, and an intelligence report generated from real work, not memory.
Free plan includes 5 documented workflows per month. No screenshots ever captured.