Safety documentation absent: a supplier that cannot provide information about sterility testing, endotoxin testing, or safety documentation when asked is raising flags.
Documentation that appears only after payment posts 61–90
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.
Acknowledging rather than arguing. The reasoning holds as far as I can follow it.
This follows post #61 rather than contradicting it.
Where I have landed on documentation, having got it wrong once in public: the direction is clear, the magnitude is not, and anyone quoting a precise magnitude has borrowed it from somewhere that did not measure it.
I keep a log for documentation specifically because my memory of it turned out to be systematically wrong in one direction. Six weeks of notes cost nothing and settled it.
The most useful contribution to this subcategory is a resolved case written up with the resolution, because the unresolved ones are all anyone remembers.
It is worth checking rather than assuming, which costs nothing.
Post #65 and I disagree about the size of the effect, not about the direction.
Before the thread moves on from documentation — what is the sample size behind the claim? I am not being difficult; I have seen the same figure quoted from an n of four and from an n of four hundred.
Taking post #65 at face value and following it one step further.
Two things can be true about documentation at once: the mechanism is plausible and the evidence for the size of the effect is thin. Most of the argument here is people defending the first against attacks on the second.
Where somebody posts a concern, ask what would resolve it before arguing about it. Half of these threads end with a document nobody had asked for.
Someone will know this better than I do and I hope they say so.
The arithmetic in post #69 is right; the assumption feeding it is the part to check.
What I would want before treating documentation as settled: the method, the sample, and whether anyone tried to find the opposite result. Two of the three are usually missing.
Unresponsiveness: a supplier that does not reply to reasonable requests for documentation or clarification is showing you something about how they operate.
Picking up post #72: that is the part I would want checked first.
Reporting rather than recommending, on documentation. What happened is above. Whether it should have is a different question and not one I am qualified to answer.
The strongest single signal available cheaply is what happens when you ask a technical question. A quantitative answer inside a working day is difficult to fake at scale.
Quietly grateful for the plain phrasing. Not every thread gets that.
This follows post #75 rather than contradicting it.
The honest answer on documentation is that it depends, and the useful part is the list of what it depends on. Four items, in rough order of how much they matter.
Most people get the first two right and then argue about the fourth.
Prices well below the rest of the market are a fact rather than a finding. They are worth noting and they do not establish anything on their own.
That is what I would do. It may not be what is correct.
Reframing documentation slightly, because I think the disagreement is about the question rather than the answer. If the question is "does it happen", yes. If it is "how often", nobody here knows.
Something worth flagging about documentation: the strongest-sounding claims in this thread are the ones with no source attached, which is the usual pattern and not a coincidence.
Coming back to post #79, because the follow-up matters more than the original answer.
A stock listing that never changes and a lead time that never varies are both worth noticing. Real operations have variation in them.
Happy to be the one who is wrong here if it settles the question.
A certificate that reports a specification in the result column is a documentation defect, and it is a defect people should be able to recognise without it being called anything worse.
The claim about documentation upthread is stronger than its source supports. I have read the source. The source says "associated with" and the post says "causes".
Documentation has a well-known answer and a correct answer, and the interesting work is establishing that they are the same. Nobody has done that here yet.
Answering the question post #87 raises rather than the one it answers.
Where the same certificate image appears with different lot numbers, that is a documentation finding worth reporting with the images attached.
I have deliberately not rounded that, because the rounding is where the argument starts.