Span and duration both describe how long something takes, yet they answer different questions. Knowing when to use each keeps schedules realistic and stakeholders calm.
Duration measures calendar time from start to finish, including nights, weekends, and holidays. Span measures only the working time within that calendar window. Swap the two and your project plan quietly slips.
Core Definitions
Duration is the elapsed clock time between two calendar moments. It counts every hour, whether anyone is working or not.
Span is the net working time required to complete an activity. It ignores non-working periods and focuses only when effort is actively applied.
A task with a three-day duration can have a one-day span if the team only works eight hours across those three days.
Everyday Examples
Painting a room may take two calendar days because the paint must dry overnight. The actual brush-in-hand span is four hours.
Software code review can last five business days in duration while the reviewer spends only six hours of focused span.
Shipping a package might show five days in transit, yet the courier’s handling span is a few minutes at each depot.
Why the Mix-Up Happens
People hear “it takes three days” and picture three full workdays. They forget that weekends, approvals, and queues inflate duration while leaving span untouched.
Project tools often display bars that stretch across weekends, reinforcing the duration view. Stakeholders then expect deliverables sooner than the span allows.
Language Traps
Saying “this task is three days of work” is ambiguous. Clarify whether you mean three calendar days or three workdays of effort.
Replace vague phrases with “duration of three calendar days” or “span of twenty-four hours of effort” to remove doubt.
Planning Accuracy
Build schedules by placing duration on the calendar and span inside the resource sheet. This dual view prevents overallocation.
If a designer has sixteen hours of span but only four hours free each day, the task needs four working days of duration even though the effort feels like “two days.”
Buffer Placement
Add buffers to duration, not span. A task with eight hours of span can still receive a one-day buffer in duration to absorb reviews.
Buffers attached to span artificially inflate effort estimates and hide true availability.
Resource Leveling
Duration sets the calendar window; span sets the hourly demand. Match the two to keep people from triple-booking.
A developer allocated to two simultaneous tasks each with eight-hour spans can look free for two days until you notice the durations overlap.
Part-Time Staff
Part-time workers stretch duration without changing span. A sixteen-hour span task becomes four days for a half-time employee.
Ignore this twist and the project appears delayed even though effort is on track.
Critical Path Differences
Critical path calculations rely on duration, not span. A short-span task with long duration can still gate the entire project if nothing else runs parallel.
Conversely, a high-span task squeezed into non-working hours may sit off the critical path and fool planners into thinking there is float.
Parallel Streams
Two tasks with identical twenty-hour spans can finish weeks apart if one has a five-day duration and the other twenty due to resource limits.
Visualize both dimensions to decide where to add parallel tracks.
Agile Velocity
Story points estimate span; sprint calendars show duration. A team finishing forty story points in a two-week sprint converts span into a duration boundary.
Confuse the two and managers push for more story points without extending the calendar, crushing quality.
Release Planning
Map feature span onto release duration by checking team capacity each sprint. A hundred hours of span needs three sprints if capacity is forty hours per sprint.
Skip the check and the release train leaves with half the cargo.
Manufacturing Lead Time
Factory lead time is duration; machine cycle time is span. A part can spend five days moving through stations while touching machines for only thirty minutes.
Optimize span inside each station, then compress duration by removing queue time between them.
Batching Effects
Large batches inflate duration because pieces wait. Reduce batch size and duration shrinks even though the span per unit stays constant.
Teams celebrate faster delivery without working harder.
Service Windows
Maintenance windows quote duration to customers; internal crews track span to estimate staffing. A four-hour overnight window may contain ninety minutes of wrench time.
Track both to avoid overstaffing or breaching the contract.
SLA Language
Service-level agreements often promise resolution within a duration such as “two business days.” Engineers log span to keep the promise realistic.
Hide the distinction and support tickets miss their SLA even though engineers stayed busy.
Event Management
Conference organizers sell duration to attendees; crews schedule span for setup. A three-day festival can compress build span into two nights if crews work after hours.
Advertise only duration and attendees never notice the midnight rigging span.
Breakdown Timing
Strike after an event often has tight duration but high span. Venues charge for every extra hour, so crews parallelize teardown to fit both constraints.
Personal Productivity
People block calendar duration for deep work, then fill it with shallow tasks. Measure actual span of focus to reveal wasted windows.
A two-hour calendar block with thirty minutes of real span signals distraction.
Time-Boxing Tweaks
Shrink duration first when life gets busy. A report still needs four hours of span, but splitting it into four mornings keeps evenings free.
Software Settings
Project tools let you toggle between fixed-duration and fixed-span modes. Pick fixed-duration when deadlines are immovable; pick fixed-span when effort is capped.
Switching modes mid-project scrambles forecasts unless you re-baseline.
Auto-Schedule Pitfalls
Auto-schedulers often default to duration and spread span evenly. Override the even split to reflect real availability and prevent phantom overtimes.
Client Communications
Tell clients duration to set expectations; tell your team span to assign workload. Never swap the audiences.
A client told “forty hours of work” imagines a week of calendar days, not the month it may actually take.
Change Requests
Scope creep adds span first. Translate the new span into revised duration before you promise a new delivery date.
Risk Registers
Risks usually extend duration more than span. A key reviewer out sick for three days inflates duration while span waits untouched.
Log the risk against the calendar, not the effort estimate.
Mitigation Moves
Buffer span with backup skills; buffer duration with flexible milestones. Each buffer type guards a different dimension.
Financial Implications
Contractors often bill by span; penalties hinge on duration. A delayed project can trigger liquidated damages even if the contractor logged only the planned span.
Separate the two in contracts to avoid surprise losses.
Milestone Payments
Link payments to span completion inside a duration ceiling. This rewards effort while protecting schedule.
Remote Work Nuance
Time-zone spreads stretch duration while span stays constant. A hand-off that once took an hour now waits overnight.
Overlap hours become the new constraint, not the amount of work.
Async Collaboration
Async teams should track span in shared logs and duration in shared calendars. The dual view keeps hand-offs smooth.
Checklist for Planners
State both numbers in every task line. Review resource calendars weekly to keep duration honest.
Highlight any task where span exceeds daily capacity; it is a future bottleneck.