Stability tests and sample retains
Use stability tests, samples, and retain workflows to support release decisions with evidence instead of memory.
Updated March 22, 20261 min read
Overview
/stability-tests and /samples support release evidence that should stay close to batch and GMP work.
These surfaces are useful when you need to confirm that what is being released is the same thing that was tested, reviewed, and retained.
Recommended workflow
- Create or review the relevant stability test plan in
/stability-tests. - Link the work back to the product and batch context being evaluated.
- Use
/samplesto track retained material or shipped evaluation samples. - Keep release decisions tied to the evidence, not to a separate spreadsheet or email thread.
What to watch
- sample identity should stay tied to batch identity
- retain material should be easy to trace later
- stability observations should be reviewable before label or GMP release is considered final
Related routes
/stability-tests/samples/gmp
Next docs
Need a quick answer?
Use Help for troubleshooting and account questions. Stay in Docs for setup, workflows, and technical reference.