GRS Audit Trail: Which Documents Should a Buyer Request, and from Whom?

A recycled content claim fails in one of two ways. Either the claim was never true, which is rare and usually obvious, or the chain behind it has a gap, which is common and almost never obvious until someone asks. The gap is usually in the middle: a converter that bought certified yarn, made fabric, and sold it on without the paperwork that lets the next party claim. The bag at the end of that chain looks identical to one with a complete file.

This page is a request list. It sets out the nine documents, who holds each one, how far back the chain has to go, what has to reconcile between them, and what to do when one link will not produce what you asked for. It is written to be sent: the tables below are the request, and the order is the order in which the answers arrive.

What Is the Minimum Document Set for a Recycled Claim?

Nine documents, and all nine are quick to ask for at the right moment and slow to chase later. The first two come from outside your direct control: the scope certificate of the site that produced the certified input, and the transaction certificate for the lot you bought. The next four are commercial and internal: the purchase order, the commercial invoice, the packing list, and the goods-in record tying the delivered quantity to the certificate quantity.

The last three are the ones buyers forget, and they are the ones an auditor asks for first: the production record showing which lot of fabric went into which production order, the component breakdown that converts a fabric-level figure into an article-level one, and the approved copy with its sign-off date. Without the production record there is no link between the certificate and the finished goods; without the breakdown there is no link between the certificate and the printed number.

Who Holds Each Document, and How Far Back Does the Chain Go?

The chain runs back to the point at which the recycled material entered it as a certified input, and no further. A recycled polyester chain typically starts at a filament or chip producer, runs through a spinner or a weaver, then to a dyehouse or a coater, then to the assembly unit, then to the brand. Each party that takes certified input and sells certified output has to hold a scope certificate and issue or receive a transaction certificate at each step.

How far back should a buyer go? As far as the claim requires, which in practice means to the last certified party before the goods became a component of the bag. A buyer does not normally need the records of the bottle collection stage, but does need the certificate that covers the fabric lot, and the right to ask for one step further back if the first one looks thin. Ask for the chain map at enquiry: a one-page list of parties and steps is worth more than any single certificate.

What Must the Transaction Certificate Reconcile Against?

Three commercial documents, every time. The quantity on the certificate against the quantity on the commercial invoice and the packing list; the product description against the fabric actually used, stated in the language of the specification rather than of the standard; and the dates against the shipment. Where any of the three fails, the certificate does not cover the goods, whatever it says on its face.

Reconciliation is easier if it is done once per lot and recorded on a single line: certificate number, invoice number, quantity, and the initials of the person who checked. That line is the audit trail for the lot. Where a programme runs many lots, a spreadsheet with one row per lot is the whole system, and it is enough.

Which Internal Records Prove the Chain Inside the Assembly Unit?

The assembly unit is where the chain is most often broken, because cutting and sewing is where one certified input becomes part of a multi-component article. Three records close it. The fabric issue record, showing which roll or lot was issued to which production order. The cutting record, showing how many units were cut from that issue. And the finished-goods record, showing how many units of that order were packed and shipped.

Together they answer the question an auditor actually asks: could the number of units you claim for have been made from the quantity of certified fabric you hold a certificate for. If the fabric issued supports 480 units and the claim covers 500, the answer is no, and the remedy is to claim on 480 and sell 20 without the claim. This is arithmetic, not negotiation.

How Do You Verify Volume Reconciliation Without Visiting?

Ask for the reconciliation in a form you can check: opening stock of certified input, purchases in the period, issues to production, sales out, and closing stock, all in the same unit, for the same period. It is a stock ledger and it is what the standard requires the site to keep. A site that runs certified input will have it; a site that does not will send a certificate instead, and the difference is diagnostic.

Then sanity-check the ledger against the physical reality you can observe: how much fabric a unit consumes, how many units were shipped, and whether the certified fraction sold matches the certified fraction bought. A ledger that balances but implies a fabric consumption well below the marker efficiency for the pattern is a ledger that has been made to balance.

What Does a Complete File Contain at Shipment?

One folder per production lot, with the nine documents in a fixed order, and a cover sheet with four lines: the lot reference, the quantity, the printed claim, and the name of the person who closed the file. That is it. The cover sheet is what makes the folder usable eighteen months later, when the person who assembled it has moved on and the question comes from a customer rather than from an auditor.

Add one discipline that costs nothing: name the folder after the lot, not after the date or the customer. A customer will ask about a shipment, and a shipment is a lot. Folders named after dates are unsearchable the moment two customers share a production week.

Lot reference

The production order number used on the fabric issue record

Quantity shipped

Units, reconciled against the certificate quantity

Claim printed

The exact sentence, as approved, with its sign-off date

File closed by

Named person, date, and the register entry for the check

Which Documents Are Time-Sensitive and Which Are Not?

Two are time-sensitive in a way that catches buyers out. The transaction certificate has to be requested for the lot, which means before or at shipment, because the issuing party needs the actual quantity and the actual dates; asking for it three months later produces a reconstruction. And the production record has to be captured while the order is running, because once the line has moved on, the roll numbers are gone.

The scope certificate is time-sensitive in a different way: it expires, so it has to be re-checked at every reorder rather than filed once. The remaining documents — invoices, packing lists, the component breakdown, the approved copy — are stable once created, and they only need revisiting when a component or a wording changes. Sorting the nine documents by their clock is the fastest way to see which two need a diary entry and which seven need a folder.

What Do You Do When One Link Will Not Produce a Document?

First, find out which of three things is happening. The party may not hold a scope certificate, in which case it cannot issue a transaction certificate and the chain stops there; the goods can still be sold, but not with a claim that depends on that step. The party may hold a certificate but be unwilling to share commercial records, in which case a narrow request — a redacted ledger, or a statement of the certified quantity bought and sold in the period — usually resolves it. Or the document may simply not exist yet, which is a scheduling problem rather than a compliance one.

Second, decide on the claim rather than on the document. Where a link cannot be evidenced, reduce the claim to the part of the product that can be. A shell-fabric claim supported by a complete chain is worth more commercially than a product claim supported by a chain with one missing link, because the first one survives a question and the second one does not.

How Should the File Be Stored and Indexed?

Indexed by lot, stored once, accessible to two people. The storage medium matters far less than the index and the second named person. Most claim failures in practice are retrieval failures: the document exists, but the person who can find it has left, and the answer to the customer is delayed long enough to become a problem in itself.

Keep a register with one row per lot and five columns: lot reference, certificate number, quantity, claim printed, and file closed by. The register is the audit trail for the programme, and it is the first thing to hand over when a customer asks how the claim is controlled. A register with gaps is honest evidence of a programme in progress; a register that does not exist is evidence of nothing at all.

How Long Should the File Be Kept?

Long enough to answer a question about the oldest product still in the market, plus the period your own contracts or the applicable rules require. For most bag programmes that means several years from the last shipment of the lot, and longer where a customer contract says so. Where two requirements conflict, keep to the longer, because the cost of storage is trivial next to the cost of an unanswered question.

One practical note: keep the calculation, not only the certificates. Certificates are re-issuable; a calculation made at the time, showing how the printed number was derived from the certificate, is not. It is the document that turns a folder of certificates into a substantiated claim.

Frequently Asked Questions

People Also Ask