Test Method, Result, Specification, and LOQ Terms Explained

Separate method, observation, and decision fields

A test method describes the procedure used to produce information from a sample. A result reports the laboratory's observation or calculated value under that procedure. A specification states an acceptance criterion selected for the report or product system. A conformity statement compares a result with that criterion under stated decision rules. These fields are connected, but none is a synonym for another. A summary should retain each one instead of reducing the row to a number and a colored pass icon.

Start by copying the row as printed, including analyte name, method identifier, result, unit, reporting basis, specification, qualifier, and status. Then capture footnotes and legends because laboratories often define abbreviations there. If a specification column is blank, do not infer a limit from another certificate or from general knowledge. If a status is absent, do not calculate one for publication unless the project has a documented, authoritative specification and a reviewed decision rule within its scope.

Read method identifiers at the level disclosed

A method identifier may point to a published standard, compendial procedure, regulator manual, or laboratory-developed procedure. It may include a revision, year, modification note, or preparation step. Transcribe that detail. A technique such as chromatography, spectrometry, or plate count identifies only part of a procedure. Sample preparation, calibration, controls, calculations, and reporting conventions can differ even when two laboratories name the same broad instrument class.

The notation modified does not explain which step changed or how the change was validated. Record the notation and ask the issuer for the controlled method description when that detail is important to the document review. Do not silently replace an internal method code with a public method that appears similar. A method's presence on a laboratory accreditation scope can support a scope check, but the exact site, matrix, field, and method wording still need to be compared. Familiar method names should not be treated as universally interchangeable.

Keep results attached to units and reporting bases

A result becomes meaningful as a report field only with its unit and basis. Milligrams per serving, milligrams per capsule, milligrams per kilogram, percent by mass, colony-forming units per gram, and a response in a prepared extract describe different quantities. Copy inequality signs and scientific notation exactly. Preserve significant figures as reported; adding decimal places during transcription suggests precision the laboratory did not state. A blank, zero, not tested, and not detected entry are different evidence states.

Conversions require the inputs that connect one basis to another. Converting a concentration to an amount per package may require sample mass, dilution, serving size, density, or recovery information that a summary certificate does not provide. When those inputs are missing, keep the original unit and mark the desired conversion unavailable. If a report uses a dry-weight or as-received basis, preserve that wording. A comparison table should not align unlike bases in one numeric column merely because the analyte names match.

Distinguish LOD, LOQ, and reporting limits

The limit of detection, commonly LOD, generally concerns the point at which a method can distinguish a signal under defined conditions. The limit of quantitation, commonly LOQ, concerns the level at which a value can be quantitatively reported under defined performance criteria. Laboratories can also use method detection limits, practical quantitation limits, reporting limits, or contract limits with definitions set by their procedures. Read the report legend or method documentation rather than assuming every acronym has an identical operational definition.

A notation such as less than LOQ means the reported condition is below the stated quantitation boundary; it should not be replaced with zero. Not detected also does not mean absolute absence. The certificate may show the applicable numerical limit and unit, or it may require a linked method or appendix. Record what is disclosed. Do not use a detection or quantitation limit as a health threshold, and do not classify a package from that field without the report's own specification and scope.

Understand specifications and conformity wording

A specification can be a range, minimum, maximum, identity requirement, descriptive criterion, or other documented acceptance condition. The certificate may name its source, such as a client specification or compendial reference, or it may state only the value. Keep source and value separate. A laboratory's reported conforms status should be attributed to that report and criterion, not rewritten as an independent MIHEN judgment or as a claim that the entire product meets every possible requirement.

Measurement uncertainty and decision rules can affect conformity statements near a boundary. Some reports disclose uncertainty, guard bands, or the rule used to decide conformity; others do not. Preserve these notes and avoid recalculating status from a rounded display number. If a result seems inconsistent with a printed status, mark the document for issuer clarification. Do not correct the certificate from the outside. A revised report or written explanation from the responsible issuer provides a traceable resolution.

Build a terminology record that remains auditable

For every summarized row, store the original text, report and page, method, result string, unit, basis, specification string, status, qualifier, and applicable footnote. Add a plain-language explanation in a separate field so readers can distinguish transcription from editorial context. Link to the issuer's legend or the cited method definition where available. Reviewers should be able to reconstruct the displayed summary without searching a screenshot for missing symbols.

Use evidence states such as reported value, below stated reporting limit, not detected as defined by issuer, not tested, missing field, and unresolved notation. These labels describe documents rather than health meaning. Avoid best, pure, clean, safe, dangerous, or effective conclusions based on a row. The final guide should remind readers that technical terms operate within a method, sample, unit, criterion, and date. Removing any of those parts can change what a laboratory statement actually communicates.

• Transcribe analyte, method, result, unit, basis, specification, and status separately.
• Keep revision numbers and modified-method notes with the method identifier.
• Preserve inequality signs, scientific notation, qualifiers, and significant figures.
• Do not treat blank, zero, not tested, and not detected as equivalent.
• Use the issuer's definitions for LOD, LOQ, and reporting-limit terms.
• Do not convert units without every required input and an auditable calculation.
• Attribute conformity wording to the certificate and its stated criterion.
• Link plain-language explanations back to the original row and footnotes.