Course contents
Practitioner · Course 3: Physical and Chemical Testing · Lesson 5 of 5

Building a complete testing tracker for an order's required tests

Level: PractitionerTime: 40 minutesOrder used: A and B (the T-shirt and the jeans)Tool: Testing tracker
For a merchandiser, production manager, or quality controller at a garment factory who must set up and maintain one complete testing tracker covering every test an order needs. Lessons 3.1 to 3.4 are useful background but not required. Figures are teaching figures.
FactoryDelta Garments
Order shapeHybrid: a confirmed export order and a domestic standing-stock run
Reference ordersOrder A's 180 GSM knit and Order B's 12 oz denim
Business modelHybrid (MTO and MTS lines, domestic)
Testing labAn independent testing lab
ToolTesting tracker (this course's workbook)
02Opening

This page explains how to build one complete testing tracker that covers every test an order needs, from booking through to a recorded pass or fail

This page is for a merchandiser, production manager, or quality controller at a garment factory who must set up and maintain one working tracker covering every test an order's tech pack requires. Lessons 3.1 to 3.4 taught the test categories, how results are rated, how to read a report, and what to do when a test fails. This lesson brings all of that into one tool: a single testing tracker listing every test line an order needs, the standard each is tested against, the sample stage, the required result, the actual result, the date, the pass/fail outcome, and the action taken if it failed. This is chiefly an information-flow skill: keeping every test's status visible in one place, across a factory floor that can be running an export order and a domestic standing-stock run on the same line at the same time. Without one tracker covering every line, a factory can lose track of which tests are booked, which have returned, and which still need action, especially where more than one order runs through the floor together.

03Before you start

You need: the test categories from Lesson 3.1, the rating scales from Lesson 3.2, the report-reading method from Lesson 3.3, and the four failure options from Lesson 3.4.

By the end of this lesson you can:

  • list the columns a complete testing tracker needs for every test line;
  • populate a tracker row for a new test from a tech pack's testing requirement;
  • update a tracker row once a test lab report returns an actual result;
  • record the correct action taken for any failed test line;
  • use one tracker to manage tests across more than one order running on the same floor.

Not covered here: the test categories, rating scales, report-reading method, and failure options this tracker relies on (Lessons 3.1 to 3.4, already covered).

04Key terms

Words you will meet in this lesson

TermMeaning
Testing trackerA single working document listing every test line an order needs, its standard, sample stage, required result, actual result, date, outcome, and action if failed.
Test lab reportAn independent testing lab's written, measured record of a test's method, result, and pass/fail outcome against a named standard.
Required resultThe specific rating or percentage a standard states a test must meet or better.
Actual resultThe rating or percentage an independent testing lab actually measures for that fabric or garment.
Sample stageThe point in production, fabric, cut panel, or finished garment, at which a test's sample is taken.
Independent testing labA third-party laboratory, not owned by the factory or the buyer, that performs these tests and issues a report both sides can rely on.
05Teaching
The rule

A complete testing tracker has one row per test line and eight fixed columns, and it is complete only when every row an order's tech pack requires actually exists in it

A testing tracker is a single working document, not a set of separate notes or emails, listing every test line an order needs. Each row holds eight fixed pieces of information: the test name, the test standard or method, the sample stage the test needs, the required result from the buyer's tech pack, the actual result once the independent testing lab reports it, the date tested, the pass/fail outcome, and the action taken if it failed. A tracker is complete for an order only when every test line that order's own tech pack names has its own row, whether or not the test has returned a result yet; a missing row is not the same as a test that has not started, because a missing row means nobody is tracking whether it has started at all.

One tracker row = one test lineTest nameStandardSamplestageRequiredresultActualresultDatetestedOutcomeActionif failed
A testing tracker holds eight fixed columns per test line, from booking to action taken.* A tracker missing even one row an order's tech pack requires is not tracking that order's full testing requirement.
What you meet in real life

The same eight columns apply to every order, but how many rows are active at once, and how they are grouped, differs when more than one order shares a floor

What can differThe shapes you meetWhy it matters
One order vs. more than one order on the same floorDelta Garments' hybrid line, running a confirmed export order and a domestic standing-stock run together, needs each order's own rows kept clearly separated by order, even inside one shared tracker file.Mixing rows from two orders without a clear order label risks reading Order A's passed shrinkage test as if it also covers a domestic style's own fabric.
Export order vs. domestic standing-stock orderAn export order's rows are usually closed out once, at shipment; a domestic Make to Stock brand's rows repeat on every new production run of the same standing style, since each run is its own fabric lot.Reusing an old passed result for a new production run, instead of adding a new row, risks missing a real change in a later fabric lot.
A test line still pending vs. a test line with a resultSome rows will show a booked test with no actual result yet, because the lab has not reported back; other rows will show a complete pass or fail.A tracker with blank actual-result cells for tests booked weeks ago flags a lab response that needs following up before the order can proceed.
A failed row vs. a passed rowA passed row needs no further action column entry beyond "none required"; a failed row must show which of Lesson 3.4's four options was chosen.A failed row with a blank action column is an unresolved decision, not a completed one, even though the fail itself has already been recorded.
Socks, terry, and home-textile product familiesA hosiery, terry, or bedding order's tracker uses the same eight columns, with that product's own test names and standards in the test-name column.The tracker's structure does not change by product family; only which named tests appear in it does.
The case we follow

Delta Garments' hybrid line runs Order A's export shipment alongside a domestic standing-stock run, and both need their own complete rows in the same tracker

Delta Garments is running a hybrid line: Order A, the confirmed 15,000-piece export order for Northline Apparel, and a separate domestic standing-stock run of a similar T-shirt style for a local brand, on the same floor at the same time. Mona, the merchandiser, keeps one testing tracker file, with Order A's six test lines from Lesson 3.1 in their own clearly labelled rows, and the domestic run's own test lines in separate rows below them, each labelled with its own order name. When the independent testing lab returns Order A's colour fastness and shrinkage results, Mona updates only Order A's own rows; the domestic run's rows stay exactly as they were until its own lab results return separately.

The worked number

Order A's six rows and the domestic run's four rows sit in the same tracker file, each set independently complete

Order A (export): 6 test lines from Lesson 3.1, all rows populated, 5 passed, 1 pending retest
Domestic standing-stock run: 4 test lines (colour fastness, shrinkage, restricted substances, seam strength), 3 passed, 1 not yet booked
Total rows in the shared tracker file: 6 + 4 = 10 rows, tracked as two separate, order-labelled groups

Ten rows sit in one file, but each order's set of rows is judged complete on its own: Order A's set is complete with six rows even though one still needs a retest, while the domestic run's set is incomplete until its fourth test line is actually booked, regardless of how many of Order A's own rows have already passed.

The method

A five-step method for setting up and maintaining one testing tracker across one or more orders

1. List everytest line fromthe tech pack2. Add one rowper line, labelledwith its order3. Fill inrequired resultand sample stage4. Update asreports returnwith actual result5. Record theaction for anyfailed row
Building and maintaining a testing tracker is a fixed five-step method, whether one order or several share the floor.* Skipping step 2's order label, on a floor running more than one order, is how one order's result gets mistakenly read against another's fabric.
  1. List every test line from each order's own tech pack testing requirement, using Lesson 3.1's method.
  2. Add one row per test line, labelled clearly with which order it belongs to.
  3. Fill in the required result and sample stage for each row from the tech pack, before any test is even run.
  4. Update each row's actual result, date, and outcome as the independent testing lab's reports return, comparing per Lesson 3.2 and Lesson 3.3.
  5. Record the action taken for any failed row, using one of Lesson 3.4's four options, and confirm goods do not move until that column is filled.
The trap

A common mistake is reusing one order's passed test result as if it also covers a different order's fabric on the same floor

A common mistake, on a floor running more than one order at once, is treating a test result that passed for one order as if it also covers a second, similar-looking order, because both use a similar fabric. A colour fastness or shrinkage result belongs to the specific fabric lot it was actually measured on, not to a general style or fabric type; Order A's passed shrinkage result says nothing about a domestic standing-stock run's own, separately sourced fabric, even where both are a similar single jersey. A tracker with clearly separated, order-labelled rows exists precisely to stop this mistake; a shared, unlabelled list of test results invites it.

06In plain words

Once you know what tests an order needs, how results are rated, how to read a report, and what to do if a test fails, the last step is keeping all of that in one place. A testing tracker is a single list with one row for every test an order needs. Each row holds the test's name, what standard it is tested against, what stage of production the sample comes from, what result the buyer needs, what result the lab actually measured, the date, whether it passed, and what was done if it failed. If a factory is running more than one order on the same floor at once, each order's rows need their own clear label, so nobody reads one order's passed result as if it also applies to a different order's fabric. A tracker is only complete once every row a tech pack actually requires exists in it, whether or not that test has come back yet.

07Quick check
  • A testing tracker has one row per test line, with eight fixed pieces of information.
  • The eight columns are: test name, standard, sample stage, required result, actual result, date, outcome, and action if failed.
  • A tracker is complete for an order only when every test line its tech pack names has its own row.
  • On a floor running more than one order, every row needs a clear order label.
  • A passed result belongs to the specific fabric lot it was measured on, never to a similar-looking order.
  • A failed row is only resolved once its action column names one of the four options from Lesson 3.4.
  • A blank actual-result cell on an old booking flags a lab response that needs following up.
  • The same tracker file can hold rows for an export order and a domestic order at the same time, kept separate.
08Workplace scenario

A new colleague at Delta Garments almost records the domestic run's shrinkage test as passed, using Order A's own already-passed result

Delta Garments' hybrid line is running Order A alongside a domestic standing-stock run, and a new colleague is updating the shared testing tracker for the first time.

  • Order A's shrinkage test passed last week, and its row is marked "Pass" with the actual result recorded.
  • The domestic run's own shrinkage test has not yet been booked with the independent testing lab.
  • Both fabrics are a similar single jersey construction, and the new colleague assumes the results should be the same.
  • The new colleague is about to mark the domestic run's shrinkage row as "Pass," copying Order A's own actual result.

The tracker's two rows, exactly as they stand before this update:

Testing tracker, Order A row. "Shrinkage: actual 2.1%, required maximum 3%. Pass." Testing tracker, domestic run row. "Shrinkage: actual [blank], required maximum 4%. Not yet booked."

Should the domestic run's row be marked "Pass" using Order A's own actual result? Decide before you open the decision.

Show decision

No. The domestic run's fabric is a separate lot from a different order, and its own shrinkage row must show its own actual result from its own booked test, not Order A's number.

The two facts that decide this are the tracker's own separate rows, each labelled to its own order, and the rule that a passed result belongs only to the specific fabric lot it was measured on. The new colleague should book the domestic run's own shrinkage test with the independent testing lab and leave its row as "Not yet booked" until that lab's own actual result returns.

09What it costs

The cost of copying one order's result into another order's row, against booking and waiting for each order's own separate result

This lesson's cost is framed by what a copied result risks, rather than one fixed figure, since the tracker itself has no cost beyond the normal cost of the tests it records. If the domestic run's own fabric actually shrinks more than Order A's fabric, and its row was wrongly marked "Pass" from a copied result, the standing-stock style can reach Cedar & Co.'s style of shops shrinking out of size after a customer's first wash, a defect discovered only after full production and delivery cost has already been spent, and repeating on every future run of the same style until someone notices the tracker was never actually testing that fabric. Booking and waiting for the domestic run's own separate test costs only the lab's normal fee and the wait for its own result, a cost far smaller than a defect repeating across an unknown number of future runs.

10Working template

Testing tracker: the finished tool, covering every test line for every order on the floor, ready to use

This course's testing tracker is the tool this whole course has built toward: one row per test line, eight fixed columns, and a clear order label on every row, whether the floor is running one order or several at once. [Download the tracker](templates/T09-C03-testing-tracker.xlsx).

OrderTest nameSample stageRequired resultActual resultResultAction if failed
Order A (export)Colour fastness to washingFabricGrade 4 minimumGrade 4PassNone required
Order A (export)Shrinkage testFabric3% maximum2.1%PassNone required
Domestic runShrinkage testFabric4% maximumNot yet bookedRetest pendingBook with lab

Download the Testing tracker (Excel)

11Check yourself

1. What are the eight fixed pieces of information a complete testing tracker row holds?

2. Order A's colour fastness test has already passed. A new, unrelated order using a different fabric needs its own colour fastness result. Can the new order's row be marked "Pass" using Order A's own result?

3. A tracker shows a failed shrinkage row with the actual result, required result, and date all filled in, but the action-if-failed column is blank. Is this row complete?

12Glossary
ENARFRTRMeaning
Testing trackerمتتبع الاختباراتSuivi des essaisTest takip listesiA single working document listing every test line an order needs, its standard, sample stage, required result, actual result, date, outcome, and action if failed.
Test lab reportتقرير المختبرRapport du laboratoire d'essaiTest laboratuvarı raporuAn independent testing lab's written, measured record of a test's method, result and pass/fail outcome against a named standard.
Required resultالنتيجة المطلوبةRésultat requisİstenen sonuçThe specific rating or percentage a standard states a test must meet or better.
Actual resultالنتيجة الفعليةRésultat réelGerçek sonuçThe rating or percentage an independent testing lab actually measures for that fabric or garment.
Sample stageمرحلة العينةStade de l'échantillonNumune aşamasıThe point in production, fabric, cut panel, or finished garment, at which a test's sample is taken.
Independent testing labمختبر اختبار مستقلLaboratoire d'essai indépendantBağımsız test laboratuvarıA third-party laboratory, not owned by the factory or the buyer, that performs these tests and issues a report both sides can rely on.
13Next

Course 3 complete — physical and chemical testing is now covered

You can now name an order's required tests, read a rated result, read a complete test lab report against the buyer's own standard, decide among the four options once a test fails, and keep every test tracked in one working tool. The next course in Track 9 continues the quality and compliance sequence. Back to the course map

14Ladder

RecognizeName the eight fixed columns a complete testing tracker row holds.
ConnectMatch each test line from an order's tech pack to its own labelled row in the tracker.
CompareContrast a tracker running one order against one running more than one order on the same floor.
DecideKeep every order's rows separately complete, and close every failed row with a recorded action.