Topic summary

Revisiting: The report format the maintainers ask for, and why each field is there

Sourcing › Vendor reports batch & lot numbers Janoshik Analytical documentation quality third-party testing disputed

This is a generated summary. It shows the 9 most-liked posts from a topic of 109, in their original order, with the accepted answer included where one exists. It is a reading aid and it will miss nuance — the full topic is the record.

n.kirchnerTL27 Jan 2026#8

BDraganov, post #5: Confirming post #4 from a second method, which matters more than confirming it from a second person. Comparing your result to somebody else's on a different lot is not a comparison of suppliers. Lot is the unit and it should be in every report. Go to post

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.

That distinction has done more work for me than anything else in this category.

29 likes in reply to #5 7mo

b.nwosuTL224 Jan 2026 · edited#14

Confirming post #12 from a second method, which matters more than confirming it from a second person.

A difference inside method repeatability is not a disagreement. Saying so in your own report prevents somebody else reading it as one.

32 likes 6mo

d.bramleyTL3Regular3 Mar 2026#30

The cost of a submission is worth stating. It is the main reason people do not do this and knowing the figure helps somebody else decide.

32 likes 5mo

d.nilsenTL218 Mar 2026#37

h.kimani, post #6: I had written a reply contradicting post #2 and deleted it. Here is what survived. Where you have no independent result, a documentation report is still worth filing: what the certificate contained, what it omitted, and how fast a request was answered. Go to post

I read post #36 twice before replying, because I had assumed the opposite.

The variance between people here is larger than the effect being discussed.

32 likes in reply to #6 4mo

h.vargaTL219 May 2026#69

ma.balogun, post #33: Do not adjust a reported figure. Post what the laboratory said and put your interpretation in a separate sentence. Go to post

Structured report format: compound, lot, independent testing service, method as reported, result, and the certificate figure for the same lot. One lot is one lot. It becomes a pattern at three or four, and it becomes a disputed record when asked and not explained.

That is my reading. Someone else read the same page differently and was reasonable.

33 likes in reply to #33 2mo

me.eriksenTL230 May 2026#75

Somebody will have a better source than mine, and I hope they post it.

31 likes 2mo

s.grigorescuTL2Member13 Jun 2026 · edited#83

m.duarte, post #11: Post #9 describes the usual case. This is about the unusual one. Do not adjust a reported figure. Post what the laboratory said and put your interpretation in a separate sentence. Go to post

Reports of ordinary results are more valuable than reports of remarkable ones, precisely because only the remarkable ones get posted elsewhere.

Not the whole picture, but the part of it I can speak to.

30 likes in reply to #11 1mo

c.amankwahTL225 Jun 2026 · edited#90

Quietly grateful for the plain phrasing. Not every thread gets that.

29 likes 1mo

e.piresTL217 Jul 2026#103

figure_review, post #85: Building on post #84 rather than restating it. The maintainers will ask for missing fields rather than rejecting a report. Filling them in afterwards is normal and nobody minds. Go to post

Photograph the vial and the label before opening. It costs ten seconds and it is what turns a report into something checkable.

On balance I think that is right, and I would not bet much on it.

32 likes in reply to #85 11d

Read the full topic (109 posts)

This topic was referenced in

How the vendor documentation pages are maintained, and by whom — what changed sinceSourcing › Vendor reports · 104 replies
[2026 update] Comparing documentation quality across the directory, tabulatedSourcing › Vendor reports · 3 replies

Suggested topics

Topic	Participants	Replies	Views	Activity
Filing a first vendor report: a worked example Sourcing › Vendor reports third-party testing batch & lot numbers Janoshik Analytical documentation quality Filing a first vendor report: a worked example Writing it up because I had to work it out twice and would rather nobody else did. Working notes on filing a first vendor rather than a conclusion. I would…	+1	5	12k	15mo
One lot is one lot: when a report becomes a pattern Sourcing › Vendor reports documentation quality certificate of analysis batch & lot numbers disputed Solved Posting this under the heading it deserves: One lot is one lot: when a report becomes a pattern Everything below is what sits behind that. Structured report rather than an opinion, following the format the…		2	19k	14mo
Second pass at: What "verified" means on our vendor pages, stated narrowly Sourcing › Vendor reports Janoshik Analytical documentation quality third-party testing batch & lot numbers Solved 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
Documenting a supplier's response to a discrepancy — does this still hold? Sourcing › Vendor reports certificate of analysis third-party testing batch & lot numbers 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 question about turnaround and…	+47	52	58k	16mo
What "verified" means on our vendor pages, stated narrowly Sourcing › Vendor reports batch & lot numbers disputed documentation quality third-party testing 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

Related topics — sharing the tags batch & lot numbers, Janoshik Analytical, documentation quality

Topic	Participants	Replies	Views	Activity
Revisiting: Patterns that reliably precede a problem, documented Sourcing › Red flags underdosing moderation mislabelling documentation quality Posting this under the heading it deserves: Revisiting: Patterns that reliably precede a problem, documented Everything below is what sits behind that. Patterns, from the point of view of someone who has read…	+16	20	36k	2mo
A comparison of home results against a laboratory result on the same vial — does this still hold? Analytics › Home & field testing ELISA third-party testing LOD & LOQ documentation quality Solved A comparison of home results against a laboratory result on the same vial — does this still hold? I have a specific reason for asking rather than idle curiosity, and the context is below. Comparison of home…	+2	6	15k	11h
Follow-up: Reporting a discrepancy without making an allegation Sourcing › Vendor reports certificate of analysis disputed third-party testing Janoshik Analytical Reporting a discrepancy without making an allegation Writing it up because I had to work it out twice and would rather nobody else did. A follow-up question about Reporting a discrepancy that I did not know…		2	24k	19mo
Coming back to: When a red flag was a misunderstanding, and the retraction Sourcing › Red flags mislabelling moderation documentation quality When a red flag was a misunderstanding, and the retraction I have a specific reason for asking rather than idle curiosity, and the context is below. Red flag — I have the observation and I do not trust my…	+6	10	257	21h
Revisiting: Filing a first vendor report: a worked example Sourcing › Vendor reports batch & lot numbers documentation quality third-party testing disputed On the subject in the title: Revisiting: Filing a first vendor report: a worked example Working notes rather than a conclusion. A question about Filing a first vendor that I think has a definite answer,…		2	60k	11mo