Inspections

A QC Inspection is the document that captures one act of checking — at a specific stage, on a specific Production Batch, by a specific inspector. It's the atomic unit of quality data in GarmentFlow.

Every dashboard, every report, every alert reads from QC Inspection records. Get this right and the rest of the section works. Skip it (or post inspections sloppily) and your data tells lies.

Getting there

Awesome bar: Cmd/Ctrl + K → type qc inspection → pick QC Inspection List

Click path: Desk → GarmentFlow → Quality Control → QC Inspection card

From the App: Quality App → In-line or Final tab

The lifecycle

A QC Inspection moves through four statuses:

Draft — being set up. Inspector picks the batch, stage, lot size, sample size; nothing has been recorded yet.
In Progress — inspector is recording parameter readings and defects.
Completed — inspector has finished and submitted the inspection. From here, results are sealed.
On Hold — paused. Reason captured.

When the inspection completes, it lands on one of four Inspection Results:

Accepted — passes. Batch moves on.
Accepted with Deviation — passes with a noted exception. Useful when the brand allows a known minor variance to ship.
Rejected — fails. The batch goes back for rework or scrap.
Hold for Review — the inspector can't decide alone. A quality manager has to weigh in before stock moves.

The result is what drives downstream decisions: a Rejected inspection blocks the batch from finished goods; a Hold for Review pauses stock movement until the manager signs off.

The two flavors

The same doctype serves two very different workflows:

In-line quality checks — performed during production, at operation boundaries. Catches problems while there's still time to fix them.
Final quality checks — performed after production, before garments leave for boxing. The last-chance gate.

What distinguishes them at the document level is the Inspection Stage — a link to the operation being checked. An in-line check might point at Stitching or Wash; a final check points at the last operation in the batch (Packing or Finishing).

The Quality App has separate tabs for each, but the underlying records are all QC Inspections.

Anatomy of an inspection

Every QC Inspection carries five sections of data:

Inspection Details — date, time, stage, Production Batch, Production Unit. What is being inspected.
Context — lot size, sample size, inspector, shift. Who and how thoroughly.
Results — status, inspection result, defect rate, overall score. The outcome.
Parameter Readings and Defects Found — the data. Covered together on the Recording defects and readings page.
Quality Rating — a 5-star summary rating and free-text comments. The narrative.

Image: A completed QC Inspection on the Desk, showing Inspection Details, Context, Results, and the Parameter Readings table with several rows of pass/fail data.

Desk vs App — when to use which

Both interfaces post to the same QC Inspection records. Pick by who's doing the work:

Inspectors on the floor → almost always the App. Big touch targets, photo capture from the device, scan-to-pick the batch, defect entry by tap rather than by typing.
Quality managers reviewing or correcting → the Desk. The form view shows everything at once, including the audit trail and side-by-side parameter readings.
Bulk inspections from a fixed station → either. A tablet is faster on the floor; a laptop is faster at a desk-bound QC station.

The rule of thumb: capture from the App, analyze from the Desk.

What to do next

Go through In-line quality checks for the production-time workflow, then Final quality checks for the pre-boxing gate. Recording defects and readings covers the two output sections that drive every dashboard.