Overview
Software changes constantly. Without a controlled process, a small update can quietly invalidate a certificate.
We review your change control procedures and assess individual changes, deciding whether they need retesting and how much, so you can release with confidence and keep your approvals valid.
What we test
- Classification of changes by impact on certified components
- Review of release notes, diffs and critical files
- Targeted regression testing where required
- Version control and build reproducibility
- Your internal change management procedures
What you submit
- Change request and release notes
- Code diffs or build comparison
- Updated critical file hashes
- Reference to the existing certificate
What you receive
- Change assessment report
- Updated certificate or confirmation of continued approval
- Findings report, where retesting is needed
Timeline and pricing
Both depend on the scope of the product and the number of markets. We agree a fixed quote and a timeline at scoping, before any work starts, and you can follow progress throughout.