Course contents
Practitioner · Course 3: Socks and Hosiery · Lesson 3 of 5

Hosiery-specific quality faults and how to inspect for them

Level: PractitionerTime: 45 minutesOrder used: C (the socks, Suez Hosiery)Tool: Sock order file, Quality Fault Log sheet
This lesson is for a quality checker, merchandiser or new entrant who inspects knitted socks and logs faults in the Quality Fault Log sheet. It follows T06-C03-L02. It follows Suez Hosiery's own finishing line, inspecting Order C, a real cast order like Order A's T-shirt or Order B's jeans. Figures are Order C's own teaching examples.
OrderOrder C, Suez Hosiery (export batch)
ProductKnitted sock, circular-knit tube
Fault familiesKnitting-stage and packing-stage
Severity levelsMinor, Major, Critical
ActionsAccept, Rework, Reject
Reused fromCourse 3, lessons 1 and 2
02Opening

This page explains how to name and log four sock-specific quality faults correctly, for anyone who inspects finished knitted socks

This page explains how to name and log four sock-specific quality faults correctly, for anyone who inspects finished knitted socks: a quality checker, a merchandiser reviewing an inspection report, or a new entrant learning the trade. This lesson teaches a decision skill: once a fault is found, the inspector must name it correctly, judge its severity, and decide the action, since the wrong name sends the fix to the wrong stage of production.

A knitted sock can carry faults a cut-and-sew garment never shows, because a sock is knitted whole on a circular knitting machine and closed by linking, not cut from flat fabric and sewn along several seams. An inspector who has only checked cut-and-sew garments before can meet these for the first time and not know what to call them.

Without a named fault type, an inspection report only says something looks wrong, not what is wrong or which stage should fix it. A sock logged as a "quality issue" gives a quality team no way to tell a knitting fault apart from a linking fault or a packing-stage sorting mistake, so the batch waits while the wrong team explains a fault it did not cause.

03Before you start

What you need, and what this lesson does not cover

You need: T06-C03-L02 (sock anatomy, knitting zones and finishing steps), and it helps to know T03-C05-L02's structural-defect concept, though this lesson restates what it reuses.

By the end of this lesson you can:

  • name the four sock-specific quality faults: a dropped stitch or hole, uneven ribbing tension at the cuff, poor toe linking, and a mismatched pair;
  • explain why each fault comes from the circular-knitting or linking process, or from the packing stage, rather than from cutting and sewing flat fabric;
  • assign a severity (Minor, Major or Critical) and an action (Accept, Rework or Reject) to a logged fault;
  • trace a specific fault back to the production stage most likely responsible for it;
  • question a vague fault label before it is logged, and ask for the specific fault type instead.

Not covered here: what makes hosiery different from cut-and-sew garments (lesson T06-C03-L01); sock anatomy, knitting zones and finishing steps (lesson T06-C03-L02); costing a hosiery order (lesson T06-C03-L04); building a complete hosiery order file (lesson T06-C03-L05).

04Key terms

Words you will meet in this lesson

TermMeaning
Structural defectA fabric fault from the weaving or knitting process itself, such as a broken yarn or dropped stitch.
Hole/tearA fabric defect where the material is torn or punctured through.
Laddering (run)A knitwear fault where a single dropped stitch unravels vertically down a column of loops.
WeltA reinforced, more tightly knitted band at the top of a sock's cuff that resists laddering and holds the sock's opening in shape.
Dye lotOne batch of fabric or yarn dyed together in the same vat, which can differ slightly in shade from another batch of the same colour.
ReworkFixing a fault in goods already made, instead of scrapping them or accepting them as they are.
05Teaching
The rule

A knitted sock carries four fault types a cut-and-sew garment never shows, because they come from the circular-knitting, linking and pairing process

A knitted sock carries four fault types that do not exist on a cut-and-sew garment, because they come specifically from the circular-knitting and linking process, or from the packing stage that follows it. A dropped stitch or hole comes from a broken or skipped needle during knitting, most often visible on the foot or leg. Uneven ribbing tension at the cuff or welt comes from inconsistent machine tension and changes the cuff's grip. Poor toe linking is a bulky or loose seam left by linking done with too coarse a stitch or a skipped stitch. A mismatched pair is two socks from different dye lots, yarn batches or knitting runs packed together as one pair. Each logged fault gets a severity of Minor, Major or Critical, and an action of Accept, Rework or Reject.

Uneven ribbing: cuffDropped stitch/hole:foot areaPoor toe linking:bulky seamMismatched pair: differentshade between the two socks
A pair of socks can carry four sock-specific faults in four different locations. Each fault has its own cause and its own likely production stage, so each must be named and logged separately, not grouped under one vague label.
What you meet in real life

The four sock-specific fault variants an inspector actually meets, and how each is judged

What can differThe shapes you meetWhy it matters
Dropped stitch or holeA visible gap or hole in the knit, most often on the foot or leg, typically Major or Critical since it affects durability and appearanceTraces back to a broken or skipped needle on the circular knitting machine, not to linking or packing
Uneven ribbing tension at the cuffLoose or tight ribbing that changes the cuff's grip, sometimes corrected by rework such as re-knitting or re-boarding, typically Minor to MajorTraces back to inconsistent knitting-machine tension settings, not to a packing-stage mistake
Poor toe linkingA bulky, loose or misaligned toe seam, uncomfortable inside a shoe, typically Major since it is a common cause of customer returnsTraces back to a linking machine's stitch setting or a skipped stitch, a separate process from knitting
Mismatched pairTwo socks of different shade or size packed as one pair, typically Major since it reaches the customer as a visibly wrong productTraces back to a packing-stage sorting mistake, not to either sock's own knitting or linking
Export order or domestic order such as a local brand's own Make to Stock batchThe same four fault types and the same naming discipline apply whether the batch ships to an export buyer or to a domestic retailerShows the naming rule holds regardless of business model or which market the finished socks ship to
The case we follow

An inspector on Suez Hosiery's own finishing line checks a batch of Order C against the four fault types before it is cleared for packing

An inspector on Suez Hosiery's finishing line checks a batch of finished Order C socks, returned from boarding, against the four sock-specific fault types before the batch is cleared for pairing and packing. Order C, ribbed crew socks in a cotton/polyester/elastane blend, 24,000 pairs, is this academy's real, fixed sock order, the same way Order A's T-shirt or Order B's jeans are. The inspector's task is not to decide whether a sock "looks fine"; it is to check each sock against the four named fault types, one at a time, and log any it finds with a specific name, a location, a severity and an action.

Boardingreturns finished socksInspectorchecks the four fault typesPairing and packingreceives the cleared batch
The inspector stands between boarding's finished socks and the pairing and packing stage. Every sock is checked against the same four named fault types before the batch moves on.
The worked number

No new order quantity: one Order C inspection batch, with four example fault instances logged

This lesson needs no calculation. It uses one batch from Order C, Suez Hosiery's own fixed sock order, and demonstrates recording individual fault instances in the Quality Fault Log's exampleRow, exactly as shown in the workbook.

Fault typeLocationSeverityAction
Dropped stitch/holeFoot, mid-sole areaMajorReject
Uneven ribbing tension at cuffCuff/top bandMinorRework
Poor toe linking (bulky seam)Toe closureMajorReject
Mismatched pair (shade or size)Pairing and packing stageMajorReject
The method

How to inspect and log a sock-specific fault correctly

  1. Identify which of the four sock-specific fault categories applies, not a generic "bad quality" label.
  2. Record the exact location found, such as the cuff, the foot, the toe, or the pairing stage.
  3. Assign a severity based on visibility and functional impact: Minor, Major or Critical.
  4. Decide and record the action: Accept, Rework or Reject.
  5. Note enough context in the notes column that the fault's likely cause, a knitting-machine setting, a linking-machine setting, or a packing-stage mix-up, can be traced.
The trap

Logging a knitting-stage fault and a packing-stage fault under the same vague label

A common mistake is logging a knitting-stage fault, such as a dropped stitch or uneven ribbing, under the same vague label as a packing-stage fault, such as a mismatched pair. The two fault families have completely different causes and different corrective teams: a knitting-machine adjustment does not fix a packing-line sorting mistake, and treating them as one undifferentiated "quality issue" sends the correction to the wrong stage of production. A vague label cannot distinguish between the two, so it sends the corrective conversation to whichever team happens to be asked first, not to the team that actually caused the fault, and the batch waits longer than it should.

06In plain words

A knitted sock can go wrong in ways a cut-and-sew garment cannot, because it is knitted whole on a machine and closed by joining stitches at the toe, rather than cut and sewn from flat fabric. A needle can break or skip during knitting, leaving a gap or a hole. The ribbed band at the top can come out too loose or too tight. The seam that closes the toe can end up bulky or badly joined, uncomfortable inside a shoe. Two socks of different shades or sizes can end up packed together as one pair. Each of these is its own separate problem with its own separate cause, so it needs its own separate name when it is written down. Writing "quality issue" instead of naming exactly what went wrong sends the fix to the wrong team and wastes time everyone would rather spend fixing the real cause.

07Quick check
  • A dropped stitch or hole is typically Major or Critical, since it affects both durability and appearance.
  • Uneven ribbing tension is typically Minor to Major, and can sometimes be corrected by rework.
  • Poor toe linking is typically Major, since a bad toe seam is a common cause of customer returns.
  • A mismatched pair is typically Major, since it reaches the customer as a visibly wrong product.
  • A fault logged under a vague label instead of its specific type cannot be traced to the right stage.
08Workplace scenario

An inspector on Suez Hosiery's finishing line finds a pair where one sock is a slightly different shade of grey than its partner and logs it as "quality issue"

The facts in front of the inspector:

  • A pair of finished socks reaches the pairing and packing stage together.
  • One sock in the pair is a slightly different shade of grey than its partner.
  • Neither sock shows a hole, a ribbing problem, or a toe-seam problem on its own.
  • The inspector writes "quality issue" in the Quality Fault Log, without naming which of the four fault types applies.

The document the inspector reads, the Quality Fault Log entry as submitted:

Quality Fault Log, submitted entry: Fault type: quality issue. Location: pairing stage. Severity: not recorded. Action: not recorded.

Is "quality issue" specific enough to log correctly? Decide before you open the answer.

Show decision

No. "Quality issue" does not distinguish a mismatched pair, a packing-stage sorting fault, from a knitting-stage fault such as a dropped stitch or uneven ribbing.

Two facts, together, decide this. First, neither sock shows a hole, a ribbing problem, or a toe-seam problem of its own, which rules out the three knitting-and-linking-stage fault types. Second, the only difference found is a shade difference between the two socks once they are paired together, which is exactly how a mismatched pair shows itself.

Since the problem here is two socks of different shades packed together, this is specifically a mismatched-pair fault, and the log should say so, so the corrective action goes to the pairing and packing stage, not to the knitting machines.

09What it costs

What a vaguely logged sock fault risks for the next batch, not only for the one it is found in

This lesson's cost is framed qualitatively, since no separate cost figure for a mislabelled sock fault is fixed elsewhere in this academy. A vaguely logged fault sends the correction to the wrong stage of production, delaying the batch's release toward whatever delivery date it is held against.

If "quality issue" is first sent to the knitting-machine team, and only later, after no cause is found there, sent on to the packing team, the batch loses days it does not need to lose. Worse, if the real cause, here a packing-stage sorting mistake, is never identified, the same fault risks recurring in the next batch, since nothing at the packing stage was corrected. Naming the fault specifically, as a mismatched pair, the first time it is logged, sends the question straight to the pairing and packing stage and avoids both the delay and the risk of repeating the mistake.

10Working template

Sock order file, Quality Fault Log sheet: the fault type, location, severity and action columns this lesson fills

Copy this table into the Quality Fault Log sheet. Fill each row with the specific fault type, not a general description.

Fault typeLocationSeverityActionNotes
Dropped stitch / holeTrace to a broken or skipped needle during circular knitting
Uneven ribbing tension at cuffTrace to inconsistent knitting-machine tension settings
Poor toe linking (bulky seam)Trace to the linking machine's stitch setting
Mismatched pair (shade or size)Trace to a packing-stage sorting mistake

Download the full working sheet from the link on this course's page.

Download the Sock order file, Quality Fault Log sheet (Excel)

11Check yourself

1. What causes a dropped stitch or hole in a knitted sock?

2. Why is a mismatched pair considered a packing-stage fault rather than a knitting-stage fault?

3. A checker at a different, 8,000-pair sock batch finds a toe seam that feels bulky when the sock is turned right-side out. What fault type should be logged?

12Glossary
ENARFRTRMeaning
Structural defectعيب إنشائيDéfaut de structureYapısal kusurA fabric fault from the weaving or knitting process itself, such as a broken yarn or dropped stitch.
Hole/tearثقب/تمزقTrou/déchirureDelik/yırtıkA fabric defect where the material is torn or punctured through.
Laddering (run)نزول العين (السلّم)Maille filée (échelle)Kaçık ilmek (merdiven)A knitwear fault where a single dropped stitch unravels vertically down a column of loops, most visible and most likely on finer-gauge knits.
Weltالويلت (حافة الجورب المقواة)Bordure renforcée (welt)Konç lastiği (welt)A reinforced, more tightly knitted band at the top of a sock's cuff that resists laddering and holds the sock's opening in shape.
Dye lotدفعة الصباغةLot de teintureBoya partisiOne batch of fabric dyed together in the same vat, which can differ slightly in shade or hand-feel from another batch of the same colour.
Reworkإعادة التشغيل (تصليح العيب)RetoucheYeniden işleme (tamir)Fixing a fault in goods already made, instead of scrapping them or accepting them as they are.
13Next

Lesson 6.3.4: Costing a hosiery order from yarn to finished pair

You now know how to name and log the four sock-specific quality faults correctly, and why a vague label sends the fix to the wrong stage of production. The next lesson costs Order C, Suez Hosiery's own sock order, using the same live-formula method already fixed for denim, from yarn to finished pair. Back to the course map

14Ladder

RecognizeName the four sock-specific quality faults and where each one shows up on the sock.
ConnectSee how each fault traces back to the circular-knitting process, the linking process, or the packing stage.
CompareTell a specifically named fault, such as a mismatched pair, from a vague label, such as "quality issue."
DecideJudge which production stage a logged fault should be traced back to, and what severity and action it deserves.