Define the requested material
Describe the target sequence or identity using an agreed notation. Include terminal groups, any specified modifications and the supplied form or counterion requirement where relevant. Do not rely on a short project nickname to communicate all of these details.
State quantity and acceptance requirements separately
- Required amount and the basis on which it is specified.
- Requested analytical requirements and any method-specific conditions.
- Required files, such as identity and chromatographic records where applicable.
- Packaging, labelling and delivery constraints.
- Which requirements are fixed and which may be discussed.
Request confirmation of feasibility and document scope. Listing a requirement in an RFQ does not mean a supplier has accepted it.
Keep confidential details out of public channels
The initial contact can describe the project at a high level. Agree an appropriate information-exchange method before sending a confidential sequence, proprietary attachment or customer dataset. Do not publish those materials as an example for another buyer.
Create a versioned brief
Give the brief a version and date. If the sequence, modification, amount or analytical requirement changes, mark the difference and request a revised review. Keep the accepted version with the quotation so technical and purchasing teams refer to the same request.