KEEP PERFECT KNIT3D KNITTED BAGS BY QUANZHOU JUNYUAN BAGS Get a quote

Knitted Bag Inspection Report Format: The Twelve Fields a Buyer Can Check Against, and the Four That Decide a Dispute

What belongs in a bag inspection report? Twelve fields, and the defect count is only the last of them: standard and edition, lot definition, inspection level, sample size, accept and reject numbers, defect classification version, measurement results, packing check, photograph set, seal and carton numbers, inspector identity, and the conclusion with the remedy. A report missing the first five is a tally, not a finding, because nobody can check the accept number against a plan that was never written on the page.

printed inspection report laid open on a table with the lot definition and sample size rows highlighted in yellow marker
Lot definition and sample size highlighted. These two rows decide whether the accept number on the page means anything.

One Shipment, Two Reports: What Went Wrong

A European buyer took delivery of 6,000 knitted totes in three colourways and found shade variation on the black. The inspection report on file said pass, AQL 2.5, six defects found. It looked complete and it was worth very little, because it did not say what the lot was, what level was used, or which colourway the six defects came from.

When the buyer asked for the sample size, the answer turned out to be 80 pieces. That is the correct sample for a lot of 501 to 1,200 at general inspection level II, and the report was therefore technically right about a lot that was never defined as the one that shipped. Three colourways of 2,000 had been treated as one lot of 6,000, which at level II takes a sample of 200 with 10 accepted and 11 rejected.

Nothing dishonest happened. The inspector did the job that was specified, on a lot that was defined by what was packed rather than by what was knitted. The lesson the buyer drew was not about the inspector: it was that a report which does not show its own inputs cannot be checked, and an unchecked report is worth the same as no report, because the first thing either of them produces is an argument.

The Twelve Fields Every Report Must Carry

The list below is the minimum a buyer should accept, in the order it should appear on the page. The ordering is not decoration: it follows the sequence in which a reader checks the conclusion, and a report that puts the conclusion first and the inputs last encourages exactly the reading that produced the case above.

The twelve fields in the order a reader checks them. The first five are the ones most often missing, and they are the ones that make the rest of the report checkable.
FieldWhat it must stateWhy it is checked
1. Standard and editionISO 2859-1 and the edition yearAccept numbers differ between editions and a plan cannot be verified against the wrong one
2. Lot definitionStyle, colourway, production run, quantitySample size follows from the lot; per-container definition silently cuts the sample
3. Inspection levelGeneral inspection level I, II or IIILevel I roughly halves the sample and level III roughly doubles it at the same AQL
4. Sample sizePieces drawn, and cartons openedThe number the accept and reject figures are read against
5. Accept and rejectBoth numbers, per defect classOne number alone leaves the reader to infer the other and to guess the class
6. Classification versionCatalogue identifier and dateA trigger changed mid-programme invalidates the inspection that preceded it
7. Measurement resultsDimensions against the stated toleranceA dimensional fault is invisible to an attribute count without a written limit
8. Packing checkCarton count, weights, markings, barcode scanMost destination problems arrive at the pallet, not on the bag
9. Photograph setMinimum eight images, referenced to piecesA defect without a photograph cannot be reviewed by anyone who was not there
10. Seal and carton numbersContainer and seal number, carton numberingTies the report to a physical shipment rather than to a production run
11. Inspector identityName, company, date, time on siteEstablishes who is answerable for the finding and when it was made
12. Conclusion and remedyPass, fail or hold, plus what happens nextA report that ends at the count leaves the commercially important sentence unwritten

Twelve fields sounds like a lot of paperwork and in practice it is one template. Once the template exists the marginal cost per inspection is a few minutes, and the saving is measured in the disputes that never start because both sides are reading the same inputs.

Field Order and Why It Is Not Arbitrary

Reports are read backwards. A buyer opens the last page for the conclusion, and when the conclusion is unwelcome, works upwards looking for the field that explains it. Putting the inputs first means that upward search lands on the lot definition and the inspection level, which are the two fields that actually explain most surprising results.

The order also matches the order in which the decisions were supposed to be made. Lot, level, sample, accept number, then findings. A report whose fields appear in that order implicitly documents a planning process, and a report whose fields are scattered documents an inspection that was improvised around whatever was on the floor that morning.

One practical consequence: ask for the report within 24 hours of the inspection while the goods are still on the floor. A report written a week later from photographs and memory is a different document, and the fields most likely to be reconstructed loosely are exactly the first five.

Photographs: The Evidence Standard

A defect without a photograph is an assertion. The workable standard is eight images minimum: one overview of the inspection set-up, one of the carton and its marking, one of the reference sample beside the production sample, and at least one per defect class found, each with the piece number visible and a scale in frame.

Resolution matters less than framing, but 1600 by 1200 pixels is a reasonable floor and a scale in frame is non-negotiable. A close-up of a 3 mm stitch run with no scale is unfalsifiable in both directions, and an image taken at arm's length under a bench lamp will not show a shade difference that is visible at 1 m under retail lighting.

For shade specifically, photograph the assembled bag next to the approved reference under the lighting the product will be sold under. A swatch comparison is not evidence of a structural shade difference between a knitted body and a knitted handle, and a buyer who has only swatch photographs will lose that argument even when the complaint is valid.

Defect Tally Versus Defect Finding

A tally says six defects. A finding says three minor thread ends over 10 mm on the inner face and three major dropped stitch runs over 3 mm on the outer face of the black colourway, on pieces 41, 88 and 173 of a sample of 200, against a catalogue version 2, at AQL 2.5. Both describe the same inspection and only the second one can be acted on.

The difference shows up at the remedy stage. A tally supports a conversation about whether six is acceptable. A finding supports a rework instruction, because it names the fault, the position, the trigger and the pieces, and a floor that receives that can sort the lot against a criterion rather than re-inspecting everything in the hope of satisfying an unstated one.

Where a buyer wants trend data rather than a single release decision, a finding also feeds it. Six defects across four lots, classified and positioned, tells a buyer whether a fault is drifting; six defects per lot with no classification tells a buyer nothing except that the number is stable. The report format is what makes the difference.

close-up photograph of a dropped stitch run on a black knitted panel with a millimetre ruler placed beside it
Piece 41, outer face, ruler in frame. A defect photograph without a scale cannot be reviewed by anyone who was not in the room.

Who Signs, and When the Report Becomes Binding

The report should be signed by the inspector with a name and a company, dated and timed, and it should state whether a representative of the producing partner was present. Presence matters because an inspection attended and countersigned is far harder to contest later, and a contested report is worth roughly what an unsigned one is worth.

Binding status is a separate question from signature. Most programmes make the report binding for the release decision on the lot inspected and nothing more, which is the right scope: it does not govern subsequent lots, it does not waive latent defects, and it does not settle anything about performance characteristics that were not measured at goods-in.

The exclusion of latent defects is the sentence buyers should read twice. Passing an attribute inspection says the lot looked right on that day under those lights, and it says nothing about pilling after a month, handle elongation after repeated 5 kg loads, or dimensional movement after the knit relaxes. Those are laboratory questions with their own ISO methods.

Reading a Report You Did Not Commission

Buyers frequently receive a report produced by the producing partner or by an agent, and the reading discipline is different because the document was not written to be checked. Four things separate a report that can be relied on from one that was written to close a file.

01

Can you recompute the sample?

Take the lot size and the stated level, look up the sample, and see whether it matches. If the report does not state both, you cannot, and the accept number is unverifiable.

02

Are both numbers present?

Accept and reject should appear together. A report showing only an accept number has removed the reader's ability to see how close the result came to failing.

03

Is the sample traceable?

Cartons opened and piece numbers referenced. A sample drawn from the top of five cartons is a different sample from one drawn across the pallet, and only the numbering shows which.

04

Does it name the failures?

A pass with zero findings on a first lot of a new programme is a signal to check the method, not a cause for celebration. Look at the level and the carton count first.

05

Is performance excluded?

The report should say what it did not test. Silence on abrasion, wash fastness and load means those were not measured, and the pass does not cover them.

06

Is the remedy written?

A fail that does not state segregation, rework and who pays for re-inspection converts a finding into an open-ended conversation at the worst possible moment.

Turning the Report into a Decision

A report should end with one of three words: pass, hold or fail. Hold is underused, and it is the right outcome when a result is borderline, when a measurement is missing, or when a performance test is outstanding. Holding a lot costs a day and preserves every option; releasing it converts a question into a destination problem.

Where the outcome is fail, the report should carry the remedy in the same document: segregate the lot, state the rework instruction, name who re-inspects and who pays, and set the date. Four sentences, and the difference between a rejection that resolves and a rejection that occupies a month.

What to demand on the page

  • ISO 2859-1 with edition, lot defined per style and colourway, general inspection level II, sample size and cartons opened, accept and reject per class, catalogue version, measurement results against tolerance, eight photographs with piece numbers, container and seal number, inspector name and date, and pass / hold / fail with the remedy.
inspector photographing carton markings and a numbered seal on a loaded pallet of knitted bag cartons
Container and seal number recorded against the carton count. This field is what ties the report to a physical shipment.

Get the inspection report template for a knit bag order

Send the bag type, quantity per colourway and whether inspection happens at goods-in or during packing. We will return the twelve-field report template with the accept and reject numbers behind AQL 2.5 already filled in, and quote FOB Xiamen at 100 pcs per style and colourway with 7 working days sampling and 30 days bulk. Start on the contact page.

Frequently Asked Questions

What fields does a bag inspection report need?

Twelve: standard and edition, lot definition, inspection level, sample size, accept and reject per class, classification version, measurement results, packing check, photograph set, seal and carton numbers, inspector identity, and a conclusion with the remedy. The defect count is one line inside field nine.

Why is the lot definition on the report so important?

Because the sample size follows from it. Three colourways of 2,000 pieces are three lots taking three samples of 200 at level II, while one combined lot of 6,000 takes a single sample of 200. The second reading inspects a third of the pieces and is perfectly legal if the buyer did not define the lot.

Should a report show the accept number or the reject number?

Both, per defect class. They sit one apart and there is no middle outcome in a single sampling plan, so showing only the accept number removes the reader's ability to see how close the result came to failing and to judge whether the plan was the one that was agreed.

How quickly should an inspection report be issued?

Within 24 hours while the goods are still on the floor. A report reconstructed a week later from photographs and memory is a different document, and the fields most likely to be reconstructed loosely are the lot definition, the inspection level and the carton count.

How many photographs should an inspection report include?

Eight minimum: the inspection set-up, the carton and its marking, the approved reference beside the production sample, and one per defect class found. Each needs the piece number visible and a scale in frame, at a floor of roughly 1600 by 1200 pixels.

Why should a shade complaint be photographed on the assembled bag?

A knitted body and a knitted handle from one dye lot can read as two colours because the structures reflect light differently. A swatch comparison will not show that, so photograph the assembled bag beside the approved reference under the lighting the product will actually be sold under.

What is the difference between a defect tally and a defect finding?

A tally says six defects. A finding says three minor thread ends on the inner face and three major dropped stitch runs on the outer face of one colourway, on named pieces, against a stated trigger and catalogue version. Only the second supports a rework instruction or a trend analysis.

Is a passed inspection report binding on later lots?

No. It is binding for the release decision on the lot inspected and nothing more. It does not govern subsequent lots, it does not waive latent defects, and it does not settle performance characteristics such as abrasion life or handle elongation that were never measured at goods-in.

What does a passed inspection not cover?

Everything measured in a laboratory rather than counted at a table: pilling after a month of use, abrasion life in Martindale cycles, wash fastness, handle elongation under repeated load, and dimensional movement once the knitted panel relaxes. Each has its own ISO method and its own specimen.

Should the inspector's name appear on the report?

Yes, with company, date and time on site, plus whether a representative of the producing partner was present. A report attended and countersigned is materially harder to contest later, and a contested report is worth about as much as an unsigned one.

What does a hold outcome mean on an inspection report?

That the lot is not released and not rejected: the result is borderline, a measurement is missing, or a performance test is outstanding. Holding costs a day and preserves every option, while releasing converts an open question into a problem at destination.

What should the remedy section say after a failure?

Four sentences: segregate the lot, state the rework instruction, name who re-inspects and who carries the re-inspection cost, and set the date. Without those, a rejection opens an unconstrained conversation at the point where the buyer has the least time available.

How can a buyer check a report they did not commission?

Recompute the sample from the lot size and the stated level and see whether it matches, check that accept and reject both appear, check that cartons and piece numbers are traceable, and check whether the report states what it did not test. A zero-finding pass on a first lot is a reason to check the method.

Where should inspection happen, at goods-in or during packing?

Both is the useful answer and packing is the one usually skipped. Goods-in catches the product; packing catches the carton count, the weight, the marking and the barcode, which is where most destination problems actually originate. State both in the order acknowledgement.

People Also Ask

What should a bag inspection report include?

Twelve fields led by the standard, the lot definition, the inspection level and the sample size, then the accept and reject numbers, measurements, packing check, photographs, seal and carton numbers, the inspector, and a conclusion with a remedy.

How do I verify an AQL inspection report?

Recompute the sample size from the stated lot size and inspection level. If the report omits either, the accept number cannot be checked and the report is a tally rather than a finding.

Why is my inspection report showing only an accept number?

Because the reject number was omitted. They sit one apart, so showing only the accept figure hides how close the lot came to failing and makes the plan impossible to verify against the standard.

Do inspection reports cover pilling and abrasion?

No. Those are laboratory tests on separate specimens with their own ISO methods. An attribute report states what was counted at goods-in and should say explicitly what it did not measure.

What happens after a bag lot fails inspection?

The report should state the remedy immediately: segregate, rework instruction, who re-inspects, who pays, and by when. Four sentences convert a rejection into a process rather than a negotiation.

Sources and further reading

Every figure on this page is either our own programme data or attributed below. Open the originals before you write them into a specification.