Reporting an analytical method reproducibly means describing the measurement in enough detail that an independent researcher could repeat it and obtain comparable results. A method that cannot be reproduced from its description undermines the findings built on it, however careful the original work. This article sets out what belongs in an analytical methods report: the instrument and its settings, calibration and reference materials, validation, and the reporting guidelines and protocol repositories that structure good practice. It is guidance on documentation, applicable across techniques.
Why the methods section carries the weight
Every measurement technique converts a property of a sample into a signal through a chain of physical steps, each governed by parameters the operator chooses. Whether the instrument is an MRI scanner, a mass spectrometer or a thermal cycler running a PCR, the result depends on settings that another laboratory cannot guess. The methods section is where those choices are recorded. If it omits them, the experiment is effectively unrepeatable, and the published result becomes a claim rather than a verifiable observation.
What to record about the instrument and parameters
A reproducible report identifies the instrument precisely and lists the settings that affect the measurement. The level of detail should be enough that a competent reader could configure their own equipment to match.
| Category | Examples of what to report | |
|---|---|---|
| Instrument | Make, model and relevant configuration of the apparatus | |
| Acquisition settings | The technique-specific parameters that govern signal generation | |
| Sample preparation | How the sample was prepared, stored and presented to the instrument | |
| Data processing | Software, versions, transforms and any filtering applied to raw data | |
| Environment | Conditions such as temperature that materially affect the result |
Reporting the data-processing chain matters as much as the acquisition. Many techniques apply substantial mathematical transformation between raw signal and reported value, and an undocumented processing step can change results as much as a hardware setting. Naming software and versions makes the analysis traceable.
Calibration and reference materials
An instrument’s raw output is meaningful only against a known scale. Calibration ties the measurement to a reference, and reporting how and when calibration was performed lets others judge and reproduce the accuracy. Where certified reference materials exist, samples of known composition or known value, citing them anchors a method to a community-agreed standard and allows cross-laboratory comparison. A report should state what was used to calibrate, the reference materials employed, and how often calibration was checked over the course of the work.
Validation and uncertainty
Validation establishes that a method does what it claims under the conditions of use. Depending on the technique this may include assessing the limit of detection, the range over which response is reliable, repeatability between runs, and the method’s sensitivity to small changes in conditions. Reporting these characteristics, together with an honest statement of measurement uncertainty, tells readers how much weight a number can bear. A value quoted without any indication of its uncertainty invites overinterpretation and is difficult to reproduce meaningfully.
Reporting guidelines and protocol repositories
Researchers rarely have to design a reporting structure from scratch. Many fields maintain community reporting guidelines that enumerate the minimum information a methods section should contain for a given type of study, reducing the risk of leaving out a critical parameter. Alongside these, protocol repositories such as protocols.io let authors publish a step-by-step procedure as a citable object, with a persistent identifier, separate from the constraints of a paper’s word limit. Linking a manuscript to a deposited protocol gives readers the full operational detail and a stable reference. Using a recognised guideline and depositing the detailed protocol together address the two failure modes of methods reporting: omission and lack of granularity.
Consistent terminology supports all of this; the CASRAI dictionary standardises the vocabulary used to describe research outputs and processes, and our reproducibility coverage explores related practices. Practical author-facing guidance is collected in our guidance for authors.
Frequently asked questions
How much detail is enough?
The working test is whether a competent independent researcher could repeat the measurement from the description alone and expect comparable results. If any parameter that materially affects the outcome would have to be guessed, the report is incomplete. Depositing a full protocol alongside the paper is a reliable way to reach that bar.
Why report data processing as well as acquisition?
Many techniques transform raw signal substantially before producing a reported value, through Fourier transforms, baseline corrections, filtering or thresholding. An undocumented processing step can alter results as much as a hardware change, so software, versions and transforms should be recorded as part of the method.
What role do reference materials play?
Certified reference materials provide a known value against which an instrument can be calibrated and across which laboratories can compare. Citing them anchors a method to a shared standard, which is central to making measurements comparable and reproducible across sites.
Where do reporting guidelines and protocols.io fit?
Reporting guidelines define the minimum information a methods section should contain, guarding against omission. Protocol repositories such as protocols.io let authors publish granular, citable, versioned procedures that exceed a paper’s space limits. Used together they cover both completeness and detail, as discussed across our research lifecycle coverage.
