2.2 Activity Durations, Productivity, and Work Calendars
Key Takeaways
Duration estimates should trace to quantity, production rate, crew, method, workfront, calendar, and risk assumptions.
Adding resources reduces duration only when work is divisible and the workfront, supervision, equipment, and workflow can support the larger crew.
Calendars define working time and can differ by trade, shift, location, season, or operating restriction.
Anticipated weather treatment must follow the contract or specification and use a documented, project-appropriate basis; no single calendar method is universally required.
Multiple calendars and relationship lags can make date and float interpretation non-intuitive, so reviewers should trace dates in actual working time.
2.2 Activity Durations, Productivity, and Work Calendars
An activity duration is a forecast of working time under a stated execution basis. AACE RP 32R-04 concerns determining activity durations. A reviewable estimate connects the duration to scope quantity, production rate, crew composition, shifts, method, access, learning, congestion, and calendar.
Quantity and production
A basic relationship is:
If production is expressed through labor-hours:
Suppose 1,200 cubic yards require 0.40 labor-hours per cubic yard. Total effort is 480 labor-hours. A six-person crew working eight hours per day supplies 48 labor-hours per day, producing a ten-working-day arithmetic duration. The estimate is credible only if the rate already reflects placement method, equipment, workfront, curing interfaces, inspection, and crew balance.
Resource-duration judgment
The fixed-work equation can illustrate a scenario, but actual production rarely scales perfectly. Doubling one craft may create waiting, congestion, supervision limits, equipment shortages, or unequal crew balance. Some work cannot be divided, and some durations are controlled by physical processes, reviews, transport, or calendar windows rather than labor effort. State whether duration is resource-driven, quantity-driven, fixed by an external process, or based on expert judgment.
Calendars
A calendar defines working and nonworking time: workweek, shifts, holidays, planned outages, seasonal restrictions, or other allowed windows. Different activities may use different calendars. Procurement expediting may use a five-day office calendar, fabrication a six-day shop calendar, and commissioning a continuous operating calendar.
Relationship lag also needs a calendar basis. A seven-day cure stated in calendar days differs from seven working days on a five-day calendar. Document which calendar controls a lag or model the waiting period as an activity when responsibility and status matter.
Anticipated weather
Weather treatment is project-specific. The contract or schedule specification may require anticipated adverse-weather days in calendars, explicit allowance activities, productivity adjustments, risk analysis, or another method. Use a relevant historical source and period, adjusted for location, season, work type, and threshold. A generic “ten-year average” is not automatically correct for every project, and assigning the same weather calendar to indoor and outdoor work can be misleading.
Keep normal anticipated conditions distinct from exceptional events as the governing documents define them. Document the source, analysis period, monthly allocation, affected work, and any double-counting controls. If duration rates already include normal weather loss, adding the same loss again as nonworking days will overstate the allowance.
Multi-calendar effects
When a path crosses calendars, elapsed calendar time and working-day float can appear to change at the interface. Software may report float using activity or relationship-calendar rules that vary by product and configuration. Review the actual dates and working periods rather than assuming one float number has identical meaning across all activities.
For a zero-based calculation, a duration of six working days starting at time zero finishes at time six. For inclusive day numbering, an activity starting on Day 1 and lasting six working days finishes on Day 6. State the convention before doing hand calculations.
Duration-review checklist
- Trace quantity and productivity to an estimate, record, or responsible expert.
- Confirm crew and equipment are available when scheduled.
- Check workfront, access, supervision, safety, and congestion.
- Verify calendars, shifts, holidays, weather, and restrictions.
- Separate working duration from waiting, review, cure, or delivery time where useful.
- Compare production assumptions with actual trends during updates.
- Re-estimate remaining duration from current conditions rather than mechanically subtracting elapsed time.
A good duration is not merely mathematically neat. It is an explainable forecast of how long the defined work will take under the planned method and calendar.
Applied review: reconcile original and remaining duration
Original duration records the planned working time at baseline. Remaining duration is a current forecast from the data date. Do not calculate remaining duration solely as original duration minus elapsed time when actual production, quantity, access, method, or crew has changed. Re-estimate the remaining scope using the best current information and explain the variance.
Check units before applying a rate: labor-hours per unit, units per crew-day, calendar days, and working days are not interchangeable. If two calendars interact, inspect the actual dates around weekends, holidays, shifts, and lag periods. A one-line formula is useful only after its quantity, capacity, calendar, and feasibility assumptions are consistent.
A task requires 480 labor-hours. Six workers each provide eight hours per working day. What is the arithmetic duration before other feasibility adjustments?
6 days
8 days
12 days
10 days
What is the most defensible way to model anticipated weather?
Follow the governing requirements and use a documented, location-, season-, and work-specific allowance without double-counting.
Always insert exactly ten NOAA-based nonworking days into every calendar.
Add an undisclosed percentage to every activity duration.
Ignore normal weather because all weather is force majeure.
Why can float appear discontinuous where a path crosses different calendars?
Every calendar change creates a new contractual milestone.
The working-time basis used to express dates and float changes across the interface.
The critical path stops at every weekend.
Multiple calendars automatically delete predecessor logic.
Sections you finish are checked off in the contents.