An honest declaration on reporting a discrepancy: I have a prior here and it is strong enough that you should weight what I say downward. Stating it rather than hiding it.
Reporting a discrepancy without making an allegation posts 61–90
This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1.
Coming back to post #62, because the follow-up matters more than the original answer.
Photograph the vial and the label before opening. It costs ten seconds and it is what turns a report into something checkable.
Taking post #64 at face value and following it one step further.
An update on my earlier reporting a discrepancy post: the pattern held for another six weeks and then stopped, which I did not predict and cannot explain.
Reports of ordinary results are more valuable than reports of remarkable ones, precisely because only the remarkable ones get posted elsewhere.
Written quickly, so the reasoning may be tighter than the wording.
I read post #66 twice before replying, because I had assumed the opposite.
If the supplier was asked about a discrepancy, include what they said verbatim rather than summarised. The wording of a response is informative.
I have written this out at length because the short version keeps being misread.
Do not adjust a reported figure. Post what the laboratory said and put your interpretation in a separate sentence.
It took me longer than it should have to see that.
Post #66 put the caveat in the right place and I want to underline it.
On reporting a discrepancy the community has more anecdote than the confidence in this thread implies, and I include my own contribution in that.
Adding what did not work for me on reporting a discrepancy, since the failures never get written up and they are half the useful information.
Dosing and purity: a vial that is 99% pure might contain 80% of its label claim if the other mass is water, counter-ion, and excipient. Purity and content are different. Both matter for different reasons.
The short answer was in the first line; everything after is the working.
The claim about reporting a discrepancy upthread is stronger than its source supports. I have read the source. The source says "associated with" and the post says "causes".
The documentation on reporting a discrepancy is better than this thread and I say that as someone who has posted in the thread.
Collapsed as off-topic by two members at trust level 3 or above
Nothing to add on the substance. Thank you for taking the question at face value.
Everything in post #73 holds. The case it does not cover is the one I have.
Do not adjust a reported figure. Post what the laboratory said and put your interpretation in a separate sentence.
I keep a log of this specifically because memory is unreliable about it.
Reports of ordinary results are more valuable than reports of remarkable ones, precisely because only the remarkable ones get posted elsewhere.
Worth saying I have only my own numbers here, and n is small.
Photograph the vial and the label before opening. It costs ten seconds and it is what turns a report into something checkable.
One more caveat and then I will stop qualifying: the sample selected itself.
Collapsed as off-topic by two members at trust level 3 or above
On post #80 — agreed on the reasoning, with one qualification.
A methods point on reporting a discrepancy rather than a substantive one: if the comparison is not like for like, the difference you are measuring is the difference in method.
Selective submission and selective reporting are the two easiest ways for a result to be shaped, and blinding addresses the first while a commitment to post addresses the second.
Quietly grateful for the plain phrasing. Not every thread gets that.
The version of reporting a discrepancy that circulates here is a simplification of a simplification. It is not wrong, but it has lost the conditions under which it holds, and those conditions are where the interesting cases live.
I have no financial interest in anything named in this thread and I want to say so before I comment on reporting a discrepancy, because it is the sort of subject where it matters.
Collapsed as off-topic by two members at trust level 3 or above
Practical answer on reporting a discrepancy, since the theoretical one is upthread: do the simplest check first, write down the result, and only then decide whether the complicated explanation is needed. It usually is not.
If the supplier was asked about a discrepancy, include what they said verbatim rather than summarised. The wording of a response is informative.
This topic was referenced in
- The report format the maintainers ask for, and why each field is thereSourcing › Vendor reports · 4 replies
- The report format the maintainers ask for, and why each field is there — what changed sinceSourcing › Vendor reports · 35 replies
Suggested topics
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
What "verified" means on our vendor pages, stated narrowly
What "verified" means on our vendor pages, stated narrowly — that is the question, and I have not found it answered plainly anywhere I have looked. A question about how a record should be read rather than…
|
+27 | 31 | 27k | 7mo |
|
Reconciling a supplier certificate with an independent result
Reconciling a supplier certificate with an independent result — setting out what I have, and where I think it stops being reliable. Reconciling a supplier certificate: setting out the arithmetic in full,…
|
+18 | 24 | 347 | 9mo |
|
Revisiting: The report format the maintainers ask for, and why each field is there
Posting this under the heading it deserves: Revisiting: The report format the maintainers ask for, and why each field is there Everything below is what sits behind that. Structured report rather than an…
|
+100 | 108 | 57k | 1d |
|
Second pass at: What "verified" means on our vendor pages, stated narrowly
Second pass at: What "verified" means on our vendor pages, stated narrowly — setting out what I have, and where I think it stops being reliable. A question about how a record should be read rather than about…
|
+94 | 102 | 20k | 3mo |
|
Coming back to: Why our vendor pages link the storefront and mark it sponsored
Why our vendor pages link the storefront and mark it sponsored I have a specific reason for asking rather than idle curiosity, and the context is below. Reading back through what has been written here about…
|
2 | 22k | 8h |
Related topics — sharing the tags batch & lot numbers, disputed, documentation quality
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
About the Red flags category
Patterns that reliably precede a problem. Documented, dated, and free of accusation without evidence. This post is a community wiki: any member at trust level 3 or above can edit it, and every edit is…
|
4 | 57k | 17mo | |
|
"Greater than or equal to 99%" as a specification rather than a result
"Greater than or equal to 99%" as a specification rather than a result Writing it up because I had to work it out twice and would rather nobody else did. Setting out an integration problem with the actual…
|
+132 | 146 | 47k | 5mo |
|
Identical chromatograms across two different lots
Identical chromatograms across two different lots Writing it up because I had to work it out twice and would rather nobody else did. Collecting what is known about identical chromatograms in one place,…
|
+80 | 87 | 58k | 18mo |
|
Purity assay versus content assay: two different numbers
On the subject in the title: Purity assay versus content assay: two different numbers Working notes rather than a conclusion. Asking about purity assay versus content assay directly, because I have read four…
|
+6 | 10 | 24k | 25d |
|
A comparison of home results against a laboratory result on the same vial
Posting this under the heading it deserves: A comparison of home results against a laboratory result on the same vial Everything below is what sits behind that. Comparison of home results against: setting out…
|
+61 | 65 | 35k | 8mo |