Project plans often fail because work effort and calendar time are treated as the same thing. Total work time is the sum of the effort required by the tasks. Calendar time also includes waiting, approvals, meetings, dependencies, weekends and other scheduling limits. Separating these concepts gives you a more useful estimate before setting a deadline.
What total work time means
Total work time is the combined duration of the tasks that make up the work. If research takes 90 minutes, drafting takes 2 hours and review takes 30 minutes, the total effort is 4 hours. That does not mean the project will finish four hours after it starts.
Start with a task list
- List the tasks needed for the deliverable.
- Estimate the effort for each task.
- Use consistent units such as hours and minutes.
- Add the task durations.
- Check dependencies before turning effort into a schedule.
Use Tervilo's Time Calculator
The Tervilo Time Calculator adds or subtracts durations in days, hours, minutes and seconds. It is useful when a project estimate contains mixed units and you want to avoid manual carry errors.
Example: four task durations
Suppose research takes 1 hour 25 minutes, drafting takes 2 hours 40 minutes, review takes 45 minutes, and revisions take 1 hour 10 minutes. The total is 6 hours of effort. The project still needs a schedule that accounts for availability and waiting.
Do not add waiting time to effort by accident
If a two-hour task must wait one business day for approval, the work effort is still two hours. The elapsed project window is longer. Record the waiting period separately so the estimate stays understandable.
Decimal hours and clock minutes are different
45 minutes equals 0.75 decimal hours, not 0.45. Thirty minutes equals 0.5 hours. This distinction matters when totals move between a time calculator, spreadsheet and timesheet.
Example with mixed units
2 hours 30 minutes is 150 minutes. Add 95 minutes and 80 minutes and the total is 325 minutes, or 5 hours 25 minutes. Using one unit during the calculation makes the arithmetic easier to check.
Parallel work changes elapsed time
Two people can work at the same time. Eight hours of combined team effort might fit inside a five-hour calendar window if some tasks run in parallel. Parallel execution changes schedule length, not the amount of effort represented by the tasks.
Estimate recurring work from real data
For repeated projects, compare estimates with actual completion time. Break large activities into smaller tasks and record real durations. This produces better estimates than relying on memory or an optimistic single number.
Include meetings and setup when appropriate
A project may require meetings, handoffs, testing, administration and setup. Decide whether your figure represents production effort only or the total working time required from the team, and label the estimate accordingly.
Example: team workload
One person may have 6 hours of research and writing while another has 2 hours of design. Total team effort is 8 hours, but individual workloads are 6 and 2 hours. The project schedule depends on when those people are available and which tasks depend on each other.
Turn effort into a realistic schedule
Once effort is known, place it against actual working hours and availability. A person with only four available work hours per day cannot complete a six-hour task in one working day simply because the effort totals six hours.
Document the assumptions
Record task duration, owner, dependencies, expected availability and any recurring overhead. When an assumption changes, you can update the affected part of the plan instead of rebuilding everything from memory.
Common mistakes
- Adding waiting time to work effort.
- Mixing decimal hours with clock minutes.
- Ignoring meetings or setup when total working time is required.
- Assuming parallel work eliminates effort.
- Turning total effort directly into a deadline without checking availability.
When a simple total is not enough
Large projects need resource planning and dependency management. A total effort number is a useful baseline, but it does not by itself show the critical path or whether the available team can meet the deadline.
Quick verification checklist
- □ All tasks are listed.
- □ Durations use consistent units.
- □ Waiting time is separate.
- □ Parallel tasks are identified.
- □ Availability is checked.
- □ Assumptions are documented.
Quick answer
Add the effort required for each task using consistent units, then keep waiting time, dependencies and working-calendar limits separate. Use Tervilo's Time Calculator for mixed durations and convert the total effort into a real schedule only after checking availability.