A peptide purity percentage is not a complete quality verdict.
Identity, purity and strength answer different questions in the regulatory documents discussed here. A useful assessment starts with the stated purpose of each procedure and the evidence supporting that purpose.
The practical approach is to separate the claims before judging the report. Identify what each method was intended to establish. Then examine whether its supporting documentation addresses that purpose rather than treating one result as an answer to every analytical question.
Read the Framework
The ICH Q2(R2) guideline distinguishes identity, assay or potency, purity and impurities as analytical purposes. Its scope includes new or revised procedures used for release and stability testing of commercial drug substances and products. That scope covers chemical and biological or biotechnological materials.
FDA’s IND chemistry, manufacturing, and controls guidance similarly separates identification, quality, purity and strength. It says sufficient information should support those assurances throughout an investigation. The information needed varies with the investigation phase, proposed formulation and duration.
The evidence type here is official regulatory guidance. An experimental study model is not applicable to these recommendations. These documents provide an analytical and documentation framework rather than original findings from cell experiments or animal and human studies.
Their drug-development scope also matters. Applying their distinctions to a research-use-only peptide report is a way to organize a review. It is not a declaration that the material meets regulatory requirements.
Separate the Questions
What supports identity?
FDA’s IND guidance calls for evidence supporting the structure and identity of the active pharmaceutical ingredient. It lists nuclear magnetic resonance, infrared and UV spectra as examples of identity evidence.
These are examples within regulatory guidance, not a peptide-specific experimental comparison of the methods. When reading a report, locate the identity claim and the evidence attached to it. Keep that question separate from the reported purity result.
The useful question is: Which documented evidence supports the stated identity? A method name should remain connected to the analytical purpose it is being used to support.
What supports purity?
The same FDA guidance cites high performance liquid chromatograms as an example of evidence supporting purity level and impurities. ICH Q2(R2) also names purity and impurities among the purposes addressed by analytical procedures.
For a document review, retain that specific scope. Read the chromatographic result alongside the stated method and acceptable limits. Do not silently expand a purity finding into an identity or strength conclusion.
CaliLean’s discussion of separating different analytical claims provides related context for keeping these questions distinct.
Where does strength fit?
FDA expects acceptable limits and analytical methods addressing strength in IND documentation. ICH Q2(R2) separately includes assay or potency among analytical purposes.
Preserve the terminology used in the underlying record. A strength claim should stay attached to its stated method and limits rather than being replaced by the word “purity.” Likewise, a report describing an assay should explain which analytical purpose that assay serves.
This makes the review more precise without assuming that differently named measurements are interchangeable.
What about quality?
FDA lists quality alongside identification, purity and strength. Its framework asks for sufficient supporting information rather than presenting a single test result as a universal quality measure.
The practical implication is to review the set of documented assurances. Ask which questions have supporting evidence and which remain unanswered. A summary should preserve those distinctions instead of compressing the record into a single favorable number.
Ask About Validation
ICH Q2(R2) provides guidance on deriving and evaluating validation tests for individual analytical procedures. It names accuracy, precision and specificity among the relevant concepts. Detection limit, quantitation limit, linearity and range are also included.
Which characteristics matter depends on the procedure’s purpose. The appropriate starting point is therefore the intended analytical question, not a generic demand that every method carry the same list of validation terms.
A useful review asks:
- What is the procedure intended to establish?
- Which validation characteristics were evaluated for that purpose?
- Where does the documentation connect that evaluation to the reported claim?
Treat “validated” as the beginning of an inquiry rather than its conclusion. Look for an explanation of what was evaluated and why that evaluation supports the procedure’s stated use.
This is a reading framework, not a new validation protocol. It adds no laboratory thresholds or acceptance criteria beyond those documented for the procedure. For related discussion, CaliLean’s guide to examining method-validation evidence focuses on assessing analytical claims.
Follow the Claim
A purpose-based review can follow a short sequence grounded in the distinctions used by ICH and FDA:
- Name the claim. Record whether the result concerns identity, purity, impurities or another stated purpose. Preserve the report’s terminology for strength, assay or potency.
- Locate the supporting method. Connect each claim to the procedure described in the record. FDA’s examples illustrate why an identity method and a purity method should not be treated as interchangeable labels.
- Find the supporting evaluation. Examine the validation information relevant to that procedure’s purpose using the ICH framework. Keep any phase-specific submission context visible.
- Read the stated limits. FDA calls for acceptable limits and analytical methods in IND documentation. Keep those limits connected to the claim they address.
The output is a claim-by-claim account of the evidence. It should make clear what the documentation supports without adding analytical conclusions that the record does not establish.
Read Phase Carefully
FDA’s IND page includes a specific clarification for first-in-human Phase 1 investigations: analytical method validation data are not expected in that setting.
That statement concerns phase-appropriate submission expectations. It should not be generalized to every IND phase or interpreted as a waiver of sound analytical controls. Read it alongside FDA’s broader statement that sufficient information must support identification, quality, purity and strength throughout the investigation.
For the reader, the useful distinction is between the information expected in a particular submission context and a general statement about a method’s performance. Before using the clarification to interpret a record, retain its first-in-human Phase 1 scope.
Keep Certificates Bounded
FDA’s IND guidance suggests submitting certificates of analysis. That establishes a place for certificates within the documentation record, not a basis for treating them as complete quality verdicts.
A certificate of analysis applies to the stated batch or sample and the reported tests and methods. It does not establish clinical safety, efficacy or suitability for human use.
Read the certificate as a record of specific analytical claims. Identify the material covered and connect each reported result to its method and stated scope. CaliLean’s guide to reading laboratory documentation offers a related framework for reviewing those records.
Keep Conclusions Proportional
The most defensible finding from these official documents is straightforward: analytical purpose determines how a result should be assessed. Identity, purity and strength deserve separate attention. Validation evidence should be evaluated in relation to the procedure’s intended purpose and regulatory context.
For peptide research documentation, that means replacing a single-number verdict with a traceable account of claims and supporting methods. An unanswered question should remain visible rather than being filled by a neighboring result.
A useful report leaves a clear record of the question behind the measurement.
How CaliLean helps
After the analytical questions are clear, the work shifts to bringing product information and research records together through CaliLean’s scientific education and laboratory documentation. For laboratory professionals facing fragmented information, its evidence reviews connect peptide research with traceable sources while maintaining a research-use-only boundary and a clear distinction from consumer health claims.
Sources
Introducing / CaliLean Field Notes
A little more
perspective.
An editorial letter for curious minds. Thoughtful reading, questions worth keeping and the sources behind them.
Explore Field Notes Join the list for the first edition
