Toray — Service request ledger

A specification review starts when the reinforcement, the laminate job, and the missing evidence are written as separate lines.

Ask a material question
  1. Brief
  2. Sample
  3. Approval
  4. Order context

Service request ledger

Prepare the request
Request Include
Sample discussion Grade family, cloth or tow form, and the laminate use
Specification question Fiber family, GSM or linear density, width, sizing or resin state
Availability question The exact textile reference and the quantity under discussion
Order context Destination and the timing you need to plan around

Define the reinforcement before the grade nickname

Public search often arrives as toray carbon fiber, toray t700 carbon fiber, toray t300 fiber, or toray t800 carbon fiber. Those phrases point at fiber families. They do not describe a woven cloth, a multiaxial fabric, a tow supply, or a prepreg. Write the physical form before the nickname. If you already hold a swatch, say whether it is dry, bindered, or resin-filmed, and note the face you measured. Name weave construction and whether warp and weft match. A later reader should be able to tell a fiber datasheet from a fabric specification without guessing.

Review the sample against one decision

Put the dated reference beside the proposed construction and record the property that actually matters: drape over the tool, tow alignment, areal weight, usable width, or surface after the process you use. Handfeel language from apparel cloth is a weak proxy for reinforcement. If the question is wet-out or resin content, say so, and do not substitute a tensile headline from a different specimen. A sample enquiry records the comparison you want. It does not establish that a swatch is in stock or that bulk cloth will match the swatch.

Approve the fields you checked

Keep the approval note attached to the same construction. Fiber composition, weave construction, GSM in g/m², usable width in cm, and finish or resin state should travel together. If a width was measured inside the selvedge, write that limit down. If a modulus figure came from impregnated strand rather than from the cloth, leave that method on the note. Tensile strength and tear strength need their own method names; seam slippage from an apparel test is not a default for a reinforcement splice. Approval of a shade is rarely the point for carbon reinforcement; approval of architecture and process state is.

Confirm quantity without inventing a supply date

Quantity, destination, and requested timing describe the commercial frame of the question. They do not, by themselves, confirm supply, a minimum, or a date. For roll cloth, ask which identification sits on the package and whether a roll inspection note exists for that roll. For tow or yarn, ask whether the format is a spool, a carton, or another package, and keep linear density in dtex or denier. A 3K label means 3,000 filaments and is not a yarn count. A buyer may write 200 g/m² as a cloth target; that target is not a listed construction. Colorfastness, pilling, and dimensional stability stay off the ledger unless the surface specification asks for them. Unknown stock stays unknown until a current answer covers that reference. A stock question and a custom-development question use different checkpoints: one asks for the batch you can verify, the other asks for a sample review before any bulk step.

Separate the request before it is sent

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.

What to put in the inquiry
RequestIncludeKeep separate
Sample discussionReference, colour direction and intended useA screen image is not the approval standard
Specification questionComposition, construction, GSM, usable width and finishAn unknown value stays blank
Availability questionMaterial reference and the quantity under discussionA catalogue page is not a delivery promise
Order contextDestination and the decision that still needs an answerDo not merge it into the sample record

Prepare the next handoff

Send the reinforcement reference and the order frame as two distinct notes.