How the vendor documentation pages are maintained, and by whom — what changed since posts 91–105
This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1 · go to the accepted answer.
Lot matching: confirm the lot number on the certificate matches the lot number on the vial. A result from a different lot is not evidence about your vial.
Blind submission is worth the effort: have someone else relabel the sample so neither you nor the laboratory knows which supplier it came from until the result is back. Blind results change minds; self-selected results do not.
Testing service selection: Janoshik gives purity with chromatogram. Medutest gives combined purity and identity. PeptideMeter gives verification records as well as results. VendorInvestigate reviews documentation. They answer different questions.
Coming back to post #95, because the follow-up matters more than the original answer.
What "verified" means on our pages: specific lots were independently measured on stated dates by named services and results were consistent with the supplier's documentation. It is not a recommendation and does not extend to untested lots.
Picking up post #95: that is the part I would want checked first.
Disputed records: when a result disagreed and was not explained, the record says disputed and stays that way. We do not remove inconvenient history; we document it.
Blind submission is worth the effort: have someone else relabel the sample so neither you nor the laboratory knows which supplier it came from until the result is back. Blind results change minds; self-selected results do not.
post #99 is right about the mechanism and I think understates the practical bit.
Thank you for the correction. I have edited my earlier post with a note rather than silently, so the thread still makes sense to read. The error was mine and it was the kind that comes from remembering a figure instead of looking it up.
Practical note that does not fit anywhere else. Whatever you conclude from this topic, write down what you did and when. The single most useful thing in your own records is not any individual result; it is that they are dated and consecutive.
Collapsed as off-topic by two members at trust level 3 or above
This follows post #99 rather than contradicting it.
Disputed records: when a result disagreed and was not explained, the record says disputed and stays that way. We do not remove inconvenient history; we document it.
Worth separating two things that post #99 runs together.
Multiple services on one lot: agreement across two independent laboratories is stronger than a high number from one. Our vendor pages deliberately mix services for that reason.
Suggested topics
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
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. Structured report rather than an opinion, following the…
|
2 | 22k | 8h | |
|
A report I filed that turned out to be wrong, and the correction
A report I filed that turned out to be wrong, and the correction Writing it up because I had to work it out twice and would rather nobody else did. Structured report rather than an opinion, following the…
|
+124 | 132 | 12k | 13mo |
|
Reporting a discrepancy without making an allegation
On the subject in the title: Reporting a discrepancy without making an allegation Working notes rather than a conclusion. Structured report rather than an opinion, following the format the maintainers asked…
|
+79 | 89 | 1k | 22mo |
|
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. Structured report rather than an opinion, following the format the…
|
+18 | 24 | 347 | 9mo |
|
One lot is one lot: when a report becomes a pattern — the long version
One lot is one lot: when a report becomes a pattern — the long version — setting out what I have, and where I think it stops being reliable. Structured report rather than an opinion, following the format the…
|
+137 | 152 | 46k | 16mo |
Related topics — sharing the tags third-party testing, disputed, batch & lot numbers
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
A supplier who responds to a discrepancy with silence — what changed since
A supplier who responds to a discrepancy with silence — what changed since — setting out what I have, and where I think it stops being reliable. A logistics question, since the answers here are usually better…
|
+83 | 88 | 21k | 6h |
|
Documenting a supplier's response to a discrepancy — does this still hold?
Documenting a supplier's response to a discrepancy — does this still hold? I have a specific reason for asking rather than idle curiosity, and the context is below. Structured report rather than an opinion,…
|
+47 | 52 | 58k | 16mo |
|
Can a home kit substitute for a laboratory report? A careful no
Asking directly, because I could not find a straight answer: Can a home kit substitute for a laboratory report? A careful no I would like to understand what this number means before I repeat it anywhere. A…
|
+122 | 131 | 1.7k | 5mo |
|
Follow-up: Reconciling a label claim with a content assay
Reconciling a label claim with a content assay Writing it up because I had to work it out twice and would rather nobody else did. I would like to understand what this number means before I repeat it anywhere.…
|
+26 | 30 | 6.5k | 14d |
|
Choosing which test to pay for, given a fixed budget
On the subject in the title: Choosing which test to pay for, given a fixed budget Working notes rather than a conclusion. I would like to talk about documentation quality as a signal, separately from product…
|
+60 | 70 | 49k | 3mo |