About Accreditations ISO 9001
What ISO 9001 means for AI systems.
Requirements, reviews, test evidence and handover are written down, so someone outside the project can check the work.
Why the process matters more on AI work.
Conventional software either does what the specification says or it does not, and a test suite settles the argument in an afternoon. A system built around a model can answer the same input differently on a different day, so "it works" stops being one observation and becomes a question about what was measured, on which data, against what threshold, and who accepted the result.
Under ISO 9001 each of those is written down, with a named person against the acceptance. That is what a documented quality system is worth on an AI build, and it is the first thing to go when nobody is asking for it.
What gets written down, and who reads it.
The four points on a build where the standard requires a record, and what each record is for.
What you asked for
Requirements are documented and agreed before build work starts, and every later change is made against that document rather than against somebody’s memory of a meeting.
What we built
Changes go through review before they merge, and the review is recorded against the change, so why something is the way it is outlives the person who wrote it.
What we tested
Test evidence is kept, including what the system was run against and what everyone had agreed an acceptable result would be.
What you were handed
Handover carries the documentation the system needs in order to be run and changed by somebody who was not on the build.
Acceptance is the hard part on an AI build.
A model that is right most of the time can still be wrong in the way that matters most to you, so what counts as an acceptable result is agreed before the build rather than argued about after it. That agreement goes into the scope, with the name of the person who signs it off.
Where the standard stops.
ISO 9001 certifies a management system, so what it tells you is how work is controlled and reviewed here. It is not a quality mark on any particular piece of software, and it does not promise that a model will behave. What it gives you is a documented trail, and a certification body outside this company checking that the trail is real.
Who checks it.
Assessed by a body outside this company.
The certificate is issued by Alcumus ISOQAR, a certification body accredited by UKAS, so the assessment against the standard is theirs rather than ours. Your procurement team can confirm the result without taking our word for any of it.
Check it yourself.
Every accreditation below is listed on a public register and can be verified independently.
- Standard
- ISO 9001:2015
- Certificate number
- 24112
- Certifying body
- Alcumus ISOQAR
- Accreditation
- UKAS
- First certified
- November 2024
Enter certificate number 24112 in the Alcumus ISOQAR certificate checker to confirm the certificate is current. Scope statements and renewal dates go to your compliance team on request, along with the certifying body’s own record.
Where this connects.
Every mark we hold
ISO 27001, ISO 9001 and Cyber Essentials are certifications we hold. We operate in compliance with UK GDPR, and we design toward the EU AI Act. The register says which is which.
See the accreditations registerThe information security side
ISO 27001:2022 sits under the same certificate number and covers how client data is classified, reached, moved and recovered.
What ISO 27001 coversAI governance and compliance
The service where these controls become your own policy, from classifying use-case risk to writing the charter your team works to.
Explore AI governance