Estimated vs Executed

Estimated vs Executed allows teams to measure how accurately work is being planned and completed. It compares the hours estimated for each task with the actual hours worked, helping teams identify where estimations are realistic, optimistic, or conservative.

Measuring Time

The feature provides two modes of measurement:

Invested Hours – Team members manually log the time spent on tasks (e.g., “worked 3 hours on this task”). This is the default option.
Worked Active Time – The system automatically tracks time based on real activity such as task updates, removing the need for manual input.

Calculation

For each task:

Percentage = (Executed Hours / Estimated Hours) × 100

Example: If a task was estimated at 10 hours but required 12, the result is 120% — indicating it took 20% longer than planned.

The overall percentage aggregates all valid estimated and executed hours (excluding incomplete data) to show the team’s global accuracy rate.

Visualization

In the Team Activity Table, each team member sees a global percentage (e.g., 95%) and can click to open a detailed modal. The modal contains:

WIP tab: ongoing tasks.
Done tab: completed tasks. Each tab displays a summary percentage and a detailed table listing task names, estimated hours, executed hours, and individual percentages.

This metric can also be found in the Project Investment section.

Insights

Around 100% → accurate estimation.
>100% → underestimation; tasks took longer.
<100% → overestimation; tasks were easier or faster.
200%+ → likely issues such as poor estimation, blockers, or rework.

Value

By tracking Estimated vs Executed, teams can continuously improve estimation accuracy, balance workloads, and enhance delivery predictability. The metric supports data-driven planning and accountability across the organization.