Crews.working_days (migration 212) is an array of weekday numbers or null. Null means follow the company default, not 'works no days'. A job can override the crew, and the picker shows what it is inheriting.
Also called: crew works Saturdays · working days · why does a 5 day stage end Wednesday · schedule skips weekends
- 1The crew card renders a WorkingDaysPicker showing the company default as the inherit option.
- 2setCrewWorkingDays is its own function rather than a field on updateCrew, because the patch is spread straight into the row.
- 3The schedule counts stage durations in these days and shades non-working columns.
- 4The project modal offers the same picker, inheriting from the crew then the company.
A crew that pours on Saturdays and a crew that does not will never finish the same stage on the same date, and a schedule that assumes a uniform week promises customers dates nobody is going to hit. Each crew carries the days it actually works and every stage duration is counted in those days, so a sub who works weekends gets dates that match reality instead of a plan nobody follows. The setting used to save silently and do nothing, which is the kind of failure discovered a month later by a crew standing in a field on a Saturday.
- One company-wide working week applied to crews that do not keep it.
- Silently failing settings writes on a scheduling field.
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 →