Overview
Most certification delays come from findings that could have been caught earlier. A short quality assurance pass before formal submission removes them.
We test your product informally against the standard it will be certified to and give you a list of issues to fix, without the formal reporting. QA work is kept separate from the formal evaluation team.
What we test
- Functional testing against the target standard
- Rules, help screens and player information
- Common causes of certification findings
- Readiness of the submission package
What you submit
- Pre-release build
- Draft documentation
What you receive
- Informal issues list
- Readiness assessment for formal submission
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.