Enter Project Data
Use the responsive input grid below. It shows three columns on large screens, two on medium screens, and one on small screens.
Example Data Table
This sample shows how the calculator can be used for a project delivery review.
| Project | Start | End | Deliverables | Active | Waiting | Rework | Approval | Interruptions | Planned Breaks | Cycle Hours | Hours per Item |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Website Redesign Sprint | 2026-03-10 09:00 | 2026-03-17 17:00 | 8 | 34 | 10 | 6 | 5 | 4 | 3 | 62 | 7.75 |
| Client Onboarding Setup | 2026-03-01 10:00 | 2026-03-05 16:00 | 5 | 18 | 4 | 2 | 3 | 1 | 0 | 28 | 5.60 |
| Reporting Automation | 2026-02-15 08:30 | 2026-02-24 18:00 | 6 | 40 | 12 | 8 | 6 | 5 | 2 | 73 | 12.17 |
Formula Used
Component Cycle Time = Active Work + Waiting + Rework + Approval Delay + Interruptions + Planned Breaks
Cycle Time per Deliverable = Component Cycle Time ÷ Completed Deliverables
Flow Efficiency (%) = (Active Work ÷ Component Cycle Time) × 100
Delay Ratio (%) = ((Waiting + Approval Delay + Interruptions + Planned Breaks) ÷ Component Cycle Time) × 100
Rework Ratio (%) = (Rework ÷ Component Cycle Time) × 100
Estimated Business Days = Elapsed Calendar Days × (Working Days per Week ÷ 7)
Throughput per Business Day = Completed Deliverables ÷ Estimated Business Days
Coverage Ratio (%) = (Component Cycle Time ÷ Total Elapsed Time) × 100
These formulas help compare real elapsed duration, tracked work patterns, waste, and output pace in one place.
How to Use This Calculator
Enter the project name, start date-time, and end date-time first. Add the number of completed deliverables and then fill in each time category.
Use active work for direct execution time. Use waiting for queues, handoffs, or blocked periods. Add rework, approvals, interruptions, and planned breaks separately.
Provide team size, working hours per day, and working days per week so the tool can estimate business-day throughput and average team load.
Optionally enter a target cycle time in workdays. After submission, the results, graph, and export buttons appear above the form.
Use CSV or PDF export to keep a project record, compare sprints, or share timing analysis with stakeholders.
FAQs
1. What does project cycle time mean?
Project cycle time is the total duration needed to move work from project start to completion. It helps teams understand speed, predict delivery, and detect waste across the process.
2. Why separate active work from waiting time?
Separating them shows whether slow delivery comes from execution effort or from delays like approvals, queues, or blocked dependencies. That makes improvement work more targeted and measurable.
3. What is flow efficiency?
Flow efficiency measures how much tracked cycle time is truly productive work. Higher percentages usually mean smoother delivery and fewer hours lost to waiting, handoffs, or interruptions.
4. How should I enter rework hours?
Enter hours spent correcting, redoing, or revising previously completed work. Tracking rework separately helps reveal quality issues, unclear requirements, or review problems that expand cycle time.
5. What does the coverage ratio show?
Coverage ratio compares all logged time components with total elapsed project time. A low value suggests missing categories. A value above one hundred percent usually indicates parallel or overlapping effort.
6. Can I use this for agile sprints?
Yes. It works well for sprints, onboarding flows, internal projects, client delivery, and operational initiatives. It is especially useful when teams want faster handoffs and steadier throughput.
7. Why does the calculator ask for team size?
Team size lets the tool estimate average tracked hours per person. That helps you compare workload balance, resource demand, and the likely effort pressure behind each project cycle.
8. What should I do if my target is missed?
Check delay ratio, rework ratio, and the graph first. Then reduce bottlenecks, tighten reviews, limit interruptions, or clarify requirements before adding more capacity or extending deadlines.