Quality control

Tasks that require QC are checked by another builder before the order moves on.

Assigning QC

Set a QC builder from the QC By column in Tasks, or in the task detail. Only leads and self-QC certified builders appear.

Tasks not requiring QC show N/A and cannot have a QC builder set.

QC is often assigned late

In practice QC is frequently recorded when the check happens rather than planned in advance — the person doing it is stamped onto the task. Both work; assigning ahead simply makes QC visible in capacity planning.

Self-QC

A builder checking their own work is only allowed when they have can self-QC set. Otherwise it is rejected, so QC stays independent by default.

Passing and failing

Passing finishes the task: it becomes Completed. Failing stops it — the task shows as Stopped: QC Failed, goes back into the queue for rework, and flags the order.

Fail the same task three times and it becomes Stopped: Escalated instead. That follows the task’s own history rather than who recorded the verdict, so a task cannot avoid escalation by being failed in bulk.

Task statuses

A task has two things you can read: where it has got to, and whether QC has run. They are separate, because a task can be finished building while its check is still outstanding.

Status	Means
Unassigned	Nobody is on it yet — or, if it needs QC, no QC person has been named
Assigned	Fully crewed and ready to work
In Progress	Being worked on, or built and now waiting for its QC check
Stopped	Halted until somebody acts. Shown with the reason: Blocked, QC Failed or Escalated
Completed	Finished, QC included

Only Completed counts as done. It drops out of the unscheduled and capacity views; everything else is still outstanding work.

A task waiting on QC still says “In Progress”

QC is the last step of the task, so until it passes, the task has not finished. A task whose build is done and whose check is outstanding sits in In Progress and appears in the QC builder’s queue. This is why there is no separate “QC Pending” status.

Unassigned means not fully crewed

A task needing QC is Unassigned until both a builder and a QC person are named — one alone is not enough for anyone to finish it. This is why assigning a builder to a QC task does not always move it to Assigned, and why the count of unassigned work is often higher than expected. That is the real figure; it was previously hidden behind a status that only checked for a builder.