The problem: spec changes made outside of control
When a spec changes by email or a spreadsheet edit, there's no clear record of who approved it or which batches it applies to.
A batch misses its gloss range, and the team decides the spec should change. If the update is made directly in a document or spreadsheet, there's no clear record of who approved it, why, or from which batch it applies.
What this demo shows
- A batch misses its gloss range.
- Quality Engineering opens and approves a change request.
- Quality Management gives the second approval.
- The next batch is tested against the new spec.
Why it matters
Specs define what passes. Changing them through a controlled request, with the failing batch and proposed revision linked, keeps the reasoning attached.
Two-stage approval and a full event log show who approved the change and when, and the next batch is tested against the new spec automatically.
See it with your own data
This video is part of QMS. To see how it would work with your own formulations and records, request a demo. Our team replies within 30 minutes during business hours.
Read the transcript
Uncountable keeps your specs, test results, and approvals in one platform. Batch B2291 just finished QC. Its gloss reads 78.4, below the release range. So, Uncountable shows it in red. Quality engineering opens a change request. It links the failing batch, the current spec, and rev 15, which raises the gloss lower limit to 85.
Quality engineering approves, and the request moves on. Quality management gives the second approval, and the change is released. Rev 15 changes only the gloss range. pH and viscosity stay the same. The next batch, B2312, is tested against rev 15. Every result is in range. And the event log keeps every edit, approval, and phase move with who did it and when.
Every spec change, approved and on record.
