Three levels of working-week setting. The company default lives on the organization and is required (so resolution always terminates). Crews and individual projects can each override it; null means inherit, never 'works no days'.
Also called: per crew working days · this job works weekends · override working days
- 1resolveWorkingDays(project, crew, org) returns the first non-empty pattern, falling back to Mon-Fri
- 2The picker shows what the inherited pattern actually is, so 'inherit' has a visible consequence instead of something you have to go look up
- 3The company setting is saved through its own route (organizations is deliberately not /api/db-writable) with an optimistic-then-rollback save so the UI never claims a setting the scheduler won't use
- 4The last remaining day cannot be toggled off — a crew that works no days can't be scheduled at all
Most crews work Monday to Friday, the concrete sub works Saturdays, and the occasional rush job runs seven days — one company-wide setting could not say that, so somebody was hand-correcting dates on every job that was an exception. The working week is set for the company, overridden for a crew, and overridden again on the one job that runs weekends. A week left unset means inherit, which is deliberately not the same as a week with no days in it: a crew that genuinely never works is a real thing to say, and it must not be confused with one nobody has configured yet.
- A single company-wide working week that doesn't match every sub
- Confusing 'not configured' with 'works no days'
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 →