The task needs two days of work, so it is booked for Tuesday and Wednesday. The person doing it is available for half-days, an input arrives Thursday and the reviewer works next Monday. Effort and elapsed duration answer different questions, and a delivery promise needs both.
Effort is the work required from people. Elapsed duration is the time between the relevant start and finish, including the sequence and waiting conditions you have defined. APM's scheduling guidance places activities in a logical timetable; the practical bridge below makes those conditions visible.
Photo by Moritz Kindler on Unsplash.
Ask what the two-day estimate contains
Clarify whether the estimate covers preparation, production, checking, correction and acceptance. Identify the roles involved rather than assuming the work belongs to one interchangeable pool of hours.
Separate time actively spent from time waiting for an input or decision. Do not treat waiting as free if people must monitor, chase or recover it. Those activities consume effort even when the main task cannot progress.
Build an effort-to-duration bridge
For a significant task, write:
Accepted output and its start condition.
Effort by role, including review and correction.
Available work windows for each role.
Required predecessor inputs.
Planned response or approval windows.
Earliest credible finish under those conditions.
Assumptions still awaiting confirmation.
This is not a second detailed project plan. It explains the conversion behind one estimate that affects a commitment.
A hypothetical two-week span
A service team needs twelve hours to prepare a new reporting pack and four hours for review and correction. The preparer has four protected hours on three separate days. Source material becomes available after the first planned window, so preparation shifts to later slots.
The reviewer can then assess the result only at the next agreed review window. The total hands-on effort remains sixteen hours in this simplified example, but the accepted finish can span parts of two working weeks.
The answer is not to label every task two weeks. It is to show which condition creates the duration and which feasible change would alter it. Earlier source acceptance or a different authorised review slot might help; pretending the preparer is full-time does not.
Challenge hidden availability assumptions
Ask whether someone is available for attendance, preparation and follow-up. A free meeting slot may not provide the capacity to read a complex deliverable beforehand. Confirm the practical commitment with the owner.
Where a task can be interrupted, record any restart or coordination effort. Where it cannot, identify the continuous window needed. Avoid dividing a duration by headcount unless the work can actually be shared without another controlling constraint.
Report both measures honestly
Effort supports workload and cost discussions. Duration supports sequence and delivery expectations. When a date moves, explain whether more work was discovered, availability changed or waiting increased. Each cause suggests a different response.
Use the small-team project plan to connect the estimate to the whole sequence. For the connected task, read How to Resolve a Resource Conflict Between Project Work and Daily Operations. If two-day tasks repeatedly occupy two weeks without explanation, discuss your project requirements.
