The stage duration editor labels itself 'in working days (Mon–Fri)' and converts what is typed into the calendar span that many working days actually cover from that stage's start. The stage quick-edit does the same, and additionally rolls a start dropped on a non-working day to the next working day.
Also called: how long is this stage · set stage duration · 5 day stage
- 1Entered value → calendarSpanFor(task.startDay, workDays, workingDaysFor(project)) → stored as the task's duration
- 2The label states the crew's pattern so the conversion isn't a surprise
- 3In the quick-edit popover, a start date picked on a Saturday is rolled forward by nextWorkingDay() before the span is computed
Builders think in working days: framing is five days means five days of crew on site, not five squares on a calendar. Entering it any other way meant doing weekend arithmetic in your head on every stage of every job, and getting it wrong on some of them. Durations are entered in working days, and picking a Saturday as a start rolls forward to the next working day and says so on the field, instead of quietly booking a crew onto a weekend.
- 'Days' meaning two different things to the builder and the software
- Stages starting on days nobody works
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →