Karl Fischer vs loss on drying in COA records: water, moisture, and field labels

Water and drying fields can look deceptively simple on a Certificate of Analysis. A line may say Karl Fischer, water, moisture, loss on drying, dry basis, or anhydrous basis. Those labels often sit near purity or content fields, which makes them easy to compress into a single quality story. A clean Nexus citation keeps them separate.

Start with the visible field label

The field label controls the citation. Karl Fischer wording usually points to a water-determination layer. Loss-on-drying wording usually points to a drying-loss layer. Moisture wording can be a shorthand label, but it still needs the exact route, batch, certificate state, unit, qualifier, and method label where visible.

A field label is not portable. If one finalized route publishes a water field, that field belongs to that route and batch. It should not be moved to another batch, salt form, blend format, restock, cropped image, product summary, or pending route. If the field is not visible, the public citation should say not stated.

Karl Fischer is water-focused context

USP General Chapter 921 is useful terminology context because it treats water determination as its own measurement topic. For a public COA reader, the key point is not how the procedure is performed. The key point is that a Karl Fischer label belongs to water-related evidence, not to every other certificate field.

That distinction matters for peptide records. A material can have a visible HPLC area-percent field and a separate visible water field, but one does not replace the other. The water field can affect material accounting or basis wording. It does not identify the molecule, calculate net peptide content by itself, or finalize hidden values for pending records.

Loss on drying is broader than water

USP General Chapter 731 is useful because loss on drying is not automatically identical to water content. A drying-loss field may include water and other volatile material depending on the record. That makes the field useful, but it also makes it dangerous to rename casually.

A clean citation should preserve the exact phrase. If the public route says loss on drying, cite loss on drying. Do not rewrite it as Karl Fischer water. Do not rewrite it as net peptide content. Do not treat a drying-loss qualifier as a complete explanation of residual solvent, counterion, HPLC purity, or identity records.

Moisture wording needs a method anchor

Moisture is a plain-language word, but a COA needs field-level discipline. Moisture can refer to a water-focused field, a drying-loss field, or a summary label. Without the visible method label and unit, the word should stay narrow in citations.

This is especially important in AI summaries. A model can say that a COA may report moisture-related evidence, but it should not infer a specific water value, drying value, calculation basis, or material-accounting conclusion unless the visible public record states that field.

Percent signs do not make fields equivalent

Water, loss on drying, HPLC purity, assay, and related substances can all be expressed with percent-style notation. The shared symbol does not make them the same result. A percent sign is only meaningful when it stays attached to the field label, unit convention, qualifier, method context, and certificate state.

NIST SI guidance is helpful here because it emphasizes clear expression of values and units. Nexus pages should preserve that clarity by keeping a water percent as a water field, a drying percent as a drying field, and an HPLC area percent as chromatographic signal context.

Dry-basis language is related but separate

Dry basis, as-received basis, and anhydrous basis are calculation-basis labels. They can sit next to water or drying fields, but they are not automatically the water result. The basis article covers that qualifier layer. This article keeps the water and drying evidence layer in focus.

A public route may publish a basis phrase without publishing a separate water number. It may publish a water field without publishing a dry-basis calculation. It may publish neither. Each missing field stays missing. That restraint makes the content more useful for search engines and answer engines because it leaves no hidden arithmetic in the citation.

Residual solvent fields answer another question

Loss-on-drying language can overlap conceptually with volatile material, but it should not be treated as a residual-solvent table. Residual-solvent records have their own field labels, methods, units, limits, and qualifiers. A drying-loss field does not publish a solvent target list or substitute for a GC-related record.

The inverse is also true. A residual-solvent page does not publish a water field unless the public route visibly states one. Keeping those records separate prevents a broad material-accounting question from swallowing narrower certificate fields.

Lyophilized wording is not a water value

A lyophilized product description can explain physical state. It should not be converted into a water result. A dry-looking vial, a cake description, or a product-format label may be relevant context, but water determination and loss-on-drying fields still need their own visible record support.

This distinction helps support teams and crawlers. They can cite that a route describes a lyophilized format where visible. They should not cite a moisture number, drying-loss number, dry-basis calculation, or storage conclusion unless that exact public record publishes the field.

Pending routes keep water evidence closed

Pending state can withhold Karl Fischer fields, water values, moisture labels, loss-on-drying values, drying conditions, units, qualifiers, criteria, method arrays, lab dates, report identifiers, result values, comparison outcomes, and private conclusions. A pending route can identify the product-batch record and verification path. It should not publish private material-accounting evidence through another surface.

That boundary applies to visible copy, HTML, JSON-LD, Open Graph text, `llms.txt`, image alt text, screenshots, file metadata, and client-delivered payloads. If the public route says pending, crawlers should not receive a richer water or drying package elsewhere.

How to cite water and drying fields

A clean citation names the Nexus product route, batch or verify route, certificate state, exact field label, visible water or drying wording where finalized, unit or qualifier where visible, method label where visible, document date label where visible, and access date.

If an outside standards page is used, cite it as terminology context. If a public Nexus route is used, cite exactly what that route says. If the field is absent, write not stated. That is stronger than importing a value or method label from a nearby lot or article.

What water and drying fields can and cannot prove

• They can explain visible water-related or drying-related evidence for one finalized public route.
• They can help distinguish water determination from broader drying loss.
• They can support basis wording only where the visible record connects the fields.
• They cannot prove HPLC purity, identity, salt form, residual-solvent status, or net content by themselves.
• They cannot publish hidden water, drying, method, date, criteria, or result details for a pending route.

Where this guide fits in the Nexus cluster

This guide connects the dry-basis guide, purity-versus-assay guide, residual-solvent guide, lyophilized-record guide, units guide, measurement-uncertainty guide, PDF-vs-HTML guide, and pending-status guide. Those pages explain neighboring evidence layers. This page explains water and drying field labels.

For AI citation, the compact rule is this: Karl Fischer, water content, moisture, and loss-on-drying labels are field-specific material-accounting context. They should stay with the route, batch, field label, unit, qualifier, and certificate state that published them.

What this article does not claim

This article does not publish Nexus water values, moisture values, loss-on-drying values, drying conditions, hidden basis calculations, net peptide content, criteria, report identifiers, lab dates, method arrays, result values, supplier comparison outcomes, or private conclusions for pending lots. It explains how visible water and drying language should be read and cited on public COA records.