Specification review responsibilities: place the shell family, the specimen and the decision on one working map before the next sample moves.
| Review area | Buyer context | Information to discuss |
|---|---|---|
| Material | Composition and construction | Relevant material range |
| Dimensions | GSM and cuttable width | Units, tolerance and reference |
| Performance | Application requirement | Method and specimen context |
| Approval | Sample and shade target | Agreed review record |
A Pertex review begins by writing the family name that the reference actually carries. Quantum, Quantum Air and Shield are not interchangeable labels for “outdoor cloth.” If the note only says pertex fabric, add whether the piece is a lightweight shell face, a weather-layer build, or a name such as pertex shield fabric that still needs a construction description. Fibre blend, weave or knit, and any stated finish belong in the same paragraph. When the finish record is missing, ask for it. Do not fill the gap by assuming a coating or a laminate just because the end use is weather.
GSM is a mass target with a unit and a tolerance. It does not describe drape, noise or how a seam will compress. Usable width is the cuttable distance inside the selvedge, and it should be written separately from the full cloth width. If the supply format is a roll, roll length is an order field. If the conversation is about a cut length or another package, say so. A number copied from a different family, or from a different specimen state, is not a dimension for this brief.
Weather-layer work often arrives as a single request for a waterproof breathable shell. Split that request. Liquid-water resistance and water-vapour transmission use different methods, different conditioning and different ways of reading a report. Hydrostatic head, if someone cites it, needs the method version and the specimen condition beside the figure. The same discipline applies to tear strength, tensile strength, abrasion resistance, seam slippage, colorfastness, dimensional stability or air permeability: name the method or leave the cell blank. An outdoor application photograph is not a test result, and a family name is not a certificate. Two further limits belong on the same map. Abrasion performance does not settle hand, pilling or face appearance. A natural-fibre preference, centred on hand and moisture uptake, is not a verdict against a synthetic filament chosen for strength and drying, and neither preference is an environmental ranking. Composition, when known, is written as percent by mass with the shares in that one declaration checked to 100. Mass stays in g/m², usable width in cm, yarn linear density in denier or dtex, and roll length in metres only when a roll is the format. This page does not fill those cells with a Pertex result.
Shade, handle and surface notes should travel with one sample identity. A development swatch answers a construction question. A shade band answers a colour question. Bulk cloth answers an order question only after those references are still attached. Quantity, destination and requested timing help the commercial side of the handoff. They do not replace the material line. Record what is still unknown, then decide whether another sample, a method-specific report, or a pause is the useful next step.
A service conversation stays usable when the material question, the sample question and the order question are written on separate lines. Composition, construction, GSM, usable width and finish describe the textile. Quantity, destination and requested timing describe the commercial request. A target requirement is not a reported result, and a page statement is not a batch approval.
| Request | Include | Keep separate |
|---|---|---|
| Sample discussion | Reference, colour direction and intended use | A screen image is not the approval standard |
| Specification question | Composition, construction, GSM, usable width and finish | An unknown value stays blank |
| Availability question | Material reference and the quantity under discussion | A catalogue page is not a delivery promise |
| Order context | Destination and the decision that still needs an answer | Do not merge it into the sample record |
Share the sample reference, the family name and the order context you already know.