JoinOS
Operations / 02

Why a job doesn't have one status

A job can contain sections at completely different operational stages — and teams need that section-level truth.

Operations/Operating System/6 min/JoinOS

A job can look “in progress” while one section is manufacturing, another is waiting on procurement, and another is still held on drawings.


That is not confusion. That is how architectural joinery actually runs. Individual work areas move through the lifecycle at different times.

Job container · Section state · Different stages

One job. Many states.

Take Harbour House. The job exists as one quoted project and operational container. Inside it, kitchen, pantry, laundry, ensuite and walk-in robe each carry their own drawing, procurement, manufacturing and installation state.

Management may need the job-level picture.
Operational teams need section-level truth.

A single status cannot serve both — and when everything is compressed into one label, the detail that tells people what to do next disappears.

Operational principle

This is why JoinOS tracks state at the section level rather than reducing the job to one generic status.

How JoinOS handles itExplore the Platform
Continue reading

Next entries in the sequence.

Next in index: Approved isn't the same as communicated