Yarn Specification Sheet: What Textile Buyers Should Include

Begin with Identity, Scope, and Revision

A specification sheet needs to identify what it describes. Start with a project reference, the yarn or sample identifier, and the intended application. Record the date and revision so the development team, buyer, and supplier can distinguish the current agreement from earlier working versions.

Also state whether the sheet describes an exploratory sample, a candidate for a machine trial, or a production-approved yarn. A preliminary target and an approved acceptance requirement should not look identical. Otherwise, an unconfirmed value can become an apparent commitment simply because it was copied into a later document.

Use a clear status for each uncertain field, such as “supplier confirmation requested” or “subject to trial.” These labels belong in the working specification, not in place of actual requirements once approval is needed. Update the sheet when a question is resolved and retain the link to the sample that supported the decision.

Core Fields for a Yarn Specification Sheet

The framework below separates the information requested from its confirmation status. Adapt the rows to the yarn being discussed; the table does not prescribe a universal product standard.

A supplier’s technical data sheet may provide several of these fields, but it serves a different purpose from a mutually agreed purchase specification. Preserve the supplier document as a source, then identify which requirements apply to your particular project and which points still need agreement.

Describe Components Before Summarizing the Assembly

Composite yarns need enough detail to show how their parts relate. For a covered yarn, separate the core from the covering yarn. For a plied construction, identify the components and the method used to combine them. A single compact code may be useful as a label, but it should not be the only technical description.

An illustrative example is a received marking of 70D/24F/2. The sheet can record that marking exactly, followed by unresolved questions: which component does 70D describe, does 24F refer to that same component, and what does /2 mean in the supplier’s notation? Do not enter 140D/48F as the final specification until the construction and final count basis have been confirmed.

This approach preserves useful source information without turning interpretation into fact. Once confirmed, add the supplier’s written construction description and the final yarn designation, keeping both connected to the sample identifier.

Select Performance Fields by Application

Not every yarn project needs every possible test. Choose fields that address the intended fabric, process risks, and buyer requirements. Too many unexplained numbers can be as unhelpful as too little information, especially when different reports use different methods.

Do not transfer a fabric-level target directly to the yarn without discussion. Fabric recovery, for example, depends on more than the supplied yarn. Specify the evaluation level so the parties know whether a requirement will be assessed on yarn, unfinished fabric, or finished fabric.

Distinguish Nominal Values, Tolerances, and Results

A nominal value identifies the intended grade or designation. A tolerance defines an agreed acceptable variation. A test result describes a particular measurement under particular conditions. These three items should occupy separate fields rather than being merged into one number.

For example, a nominal count of 70D does not by itself establish an acceptable measured range. That range must be agreed where needed, together with the method and measurement basis. There is no single tolerance that this article can responsibly apply to every material, structure, and application.

When test results are used for acceptance, record the method and edition, units, conditioning, sampling approach, and any agreed deviations or special handling. Stretch-sensitive yarns need particular attention to how length and tension are defined. ASTM’s skein-method scope illustrates why method applicability matters; citing a standard name alone is not enough to show that every yarn fits its conditions.

Keep Color and Package Requirements Specific

“Black” or “on cones” may be enough to begin a conversation, but neither is a complete approval requirement. Link color to an agreed reference and identify the stage at which it is evaluated. State whether the sample represents a proposed shade or an approved standard.

For packaging, distinguish net yarn mass from gross package mass and record the support and dimensions needed by the receiving operation. If a trial uses a different package from the proposed production package, document that difference so unwinding observations are interpreted correctly.

Keep coloration route separate from package form. A delivered cone does not prove package dyeing, and a hank does not prove hank dyeing. These details should be confirmed directly when relevant to the development or purchasing requirement.

Common Specification-Sheet Mistakes

Copying unverified shorthand into a final count field. Preserve the original code, but resolve its component and construction meaning before approval.

Listing a target without its evaluation basis. “High recovery” or “good colorfastness” needs an application-specific definition and agreed assessment conditions.

Treating every blank as permission to substitute. Mark open questions explicitly. A missing material grade or package detail should trigger clarification rather than an assumed agreement.

Review the Sheet Before Approval

– Confirm that the sheet identifies the exact candidate yarn and physical sample. – Check units, component relationships, and the meaning of all suffixes. – Separate required values from supplier proposals and unresolved questions. – Match acceptance criteria to methods, conditions, and sampling expectations. – Record the intended fabric and the stage of evaluation. – Resolve package compatibility and color-reference questions. – Record the agreed revision and retain the supporting trial observations.

Practical Questions

Can I use one template for different yarn types? Yes, as a framework. Remove irrelevant fields and add construction-specific ones so the completed sheet remains meaningful.

What if only a fabric sample is available? Start with the fabric’s identity, known information, intended use, and development objective. Mark yarn parameters as unconfirmed pending examination and discussion.

Does a signed specification replace a production trial? It records requirements, while a trial provides evidence about behavior in the intended process. Use each for its own purpose and connect the trial result to the approved specification revision.

Related Reading

• How to Read Yarn Specifications: Understanding 70D/24F/2
• Hank Yarn vs Cone Yarn: Understanding Yarn Packages
• How to Request a Yarn Sample for Fabric Development