What a stability-indicating method is and how you demonstrate one — one year on

Robustness testing deliberately varies the parameters most likely to drift — organic percentage, pH, temperature, flow — and shows the result does not. It is the part of validation that predicts whether a method will transfer.

Happy to be corrected if someone holds better data than mine.

Thank you — that answers what I came here to find out.

Picking up post #14: that is the part I would want checked first.

The limit of quantitation determines what the impurity table can honestly contain. Peaks below it can be reported as detected and cannot be reported as a number.

On post #17 — agreed on the reasoning, with one qualification.

Range and working range are different things and a certificate rarely distinguishes them. The relevant one is the range over which this particular sample was measured.

System suitability is the ongoing evidence that a validated method is still performing. Validation is done once; suitability is done every run, and it is the one that appears on a certificate.

For what it is worth, the same held on the two occasions I checked.

Robustness: the method gives consistent results when minor parameters vary. Tested by deliberately varying pH, temperature, flow rate, and mobile phase composition within reasonable ranges and demonstrating that results stay within acceptance.

Adding the caveat now so it does not have to be extracted later.

If someone has run stability-indicating method properly I would rather read that than my own reconstruction of it. Posting mine only because the thread has gone quiet.

On post #21 — agreed on the reasoning, with one qualification.

A method transferred between laboratories needs a demonstration that it performs equivalently, not just a document describing it. Transfer is where a great many between-laboratory disagreements originate.

Picking up post #21: that is the part I would want checked first.

A method that reports the same number for every lot is worth a second look. Real processes vary, and a total absence of variation is a statement about the measurement rather than the process.

The limit of quantitation determines what the impurity table can honestly contain. Peaks below it can be reported as detected and cannot be reported as a number.

Specificity is the first question: does the method separate the analyte from everything reasonably expected to be present? A method that has not been challenged with its own degradation products has not answered it.

Reporting the observation and leaving the explanation open deliberately.

Reporting a result to more decimal places than the method's precision supports is a small dishonesty that appears everywhere. A method with a two per cent relative standard deviation does not support a figure quoted to a hundredth.

A qualification I should have led with rather than closed on.

Adding the measurement that post #25 says would settle it.

The most useful single question about a method: what would it fail to detect? Every method has an answer and few documents state it.

The rule of thumb is fine; the edge cases are where it earns its keep.

Where I part company with post #25, and it is a narrow parting.

Transfer between laboratories: a method can be transferred from one lab to another, but the receiving lab needs to demonstrate that they can achieve the same performance. This requires comparative testing and sometimes small method refinements.

Documented validation is what separates a number from an opinion expressed numerically. That is the whole reason to ask for the procedure identifier rather than the method name.