A vague question such as “How long does this peptide last?” leaves the respondent to guess the material, physical state and conditions. A focused clarification request starts with the exact information gap and the sample to which it applies.
Give the respondent an unambiguous starting point
Use the product identifier, labelled form and lot where available. Include the title or version of the handling document that prompted the question, since a response about another version may not resolve the discrepancy.
Sigma-Aldrich’s customer-support forms illustrate the value of this specificity: product-document requests ask for item and lot details, while technical questions allow product information and relevant attachments. These are examples of information routing, not Novum service commitments.Sigma-Aldrich — Customer Support (opens in a new tab)
A concise request should state whether the question concerns the supplied unopened material or a laboratory preparation. Those states should not be left for the recipient to infer from the product name.
Attach only the relevant records needed to explain the question, following the laboratory’s information-sharing rules. A large unsorted collection can obscure the one discrepancy that needs an answer.
Ask one answerable handling question
| Broad question | More useful question |
|---|---|
| How should this be stored? | Which dated handling document applies to product P7, lot L4, in its supplied form? |
| Is the sample still fine? | Does available evidence address the recorded conditions in event E12 for this material and container? |
| Which instructions are right? | Document A and label B state different conditions; which applies to this lot, and can the discrepancy be explained? |
These examples request clarification rather than asserting an acceptable condition or usable period. The answer may be that the available evidence does not address the proposed situation.
If several issues exist, separate them into numbered questions. A response to the storage label should not be mistaken for an answer about a prepared solution or an unrecorded transport event.
Describe the known event without filling its gaps
For an event-specific question, provide the documented times, conditions, container state and source of those observations. Distinguish measured information from estimates or assumptions.
For example, a parcel’s delivery timestamp does not establish its earlier temperature history. Say which part of the history is available and which part is unknown instead of constructing an apparently complete timeline.
Ask what evidence supports the reply and which material state it covers. A statement based on another formulation can be useful context while still failing to resolve the exact question.
Record what the answer resolves
Keep the request and response linked to the sample or document record, including their dates and any attachments. Summarise the answer’s scope in plain language so a later reader can see what was established.
If the reply is general, identify the remaining specific question. If a revised document is supplied, retain its relationship to the earlier version rather than losing the history of the conflict.
The laboratory’s responsible decision-maker should assess the implications for planned work using the available evidence. A polite or confident response does not substitute for that assessment.
The request has done its job when the material, uncertainty and answer can be understood together. A clear record of an unresolved limit is still a useful outcome when evidence is unavailable.
Sources and further detail
- Sigma-Aldrich — Customer Support (opens in a new tab)
Manufacturer support form checked for product, lot and attachment fields. Used only as an example of technical enquiry context; no request was sent and no service or response-time promise is inferred.
Sources checked 20 September 2026. Worked records are original hypothetical examples, not Novum operating procedures or actual customer events. This article has not undergone independent scientific peer review.