No requirements base
Features emerge on demand — what was actually tested against?
FEATURE · QUALITY ASSURANCE
We build review software.
So we review ourselves.
A system meant to make GxP work reviewable must work reviewably itself. That is why we develop traqx requirements-driven, test automated and manually — and measure correctness at single-value level: 99% across a test suite of more than 13,000 pages.
Book your personal live demo
View all features →
No obligation · personal · straight in the calendar
WHAT YOU GET
Your supplier works the way your auditors expect it from you.
- Requirements firstFunctions are specified before implementation — development against defined requirements, not on demand.
- Tested automated and manuallyEvery version runs through automated tests; manual checks cover what automation does not see.
- 99% at single-value levelAcross our test suite of more than 13,000 pages, single-value checks reach 99% correctness — measured, not claimed.
THE PROBLEM
AI vendors that promise quality — and do not measure it.
Where supplier assessments of AI tools regularly fail.
Demo instead of test data
What you see is the fair-weather case; real test coverage stays a claim.
"Accuracy" without a measure
Percentages without a defined measurement level are marketing, not a quality statement.
Responsibility blurs
Who validates what? Without a clear boundary, the supplier becomes an audit risk.
THE SOLUTION
Measurable quality with a clear responsibility boundary.
Four principles of our own quality assurance.
- 01Specification before code.
Requirements are defined before implementation starts.
- 02Test at single-value level.
More than 13,000 pages of test suite; 99% correctness as the measured state.
- 03Automated plus manual.
Continuous automated tests, complemented by manual checks.
- 04Name the boundary.
Your use-case validation stays yours — we supply the documents for it.
HOW IT WORKS
Requirement, test, evidence — our own medicine.
01 · SPECIFICATIONFirst the requirement, then the code
New functions start as a defined requirement. That keeps traceable what a function is supposed to do — and what it is tested against. It is the same discipline your CSV practice demands from system suppliers.
02 · TESTSA test suite of more than 13,000 pages
Automated tests check the system continuously at single-value level — does every value land in the right place in the right document? 99% correctness is the measured state; manual tests complement the automation.
03 · BOUNDARYHonest about what this means — and what not
Our self-validation eases your supplier assessment but does not replace it: validating the configured application for your intended use remains your responsibility. traqx gives you the documents for it — DPA, T&C and fact sheet are open under /terms/.
FAQ
Common questions about this feature
What does "99% at single-value level" mean?
Our test suite covers more than 13,000 pages of test material. At single-value level — does every individual value land correctly in its place — traqx reaches 99% correctness. The remaining share is exactly why every output goes through human review.
Does that make traqx "validated" for our use?
No — and we deliberately do not claim that. Our self-validation and test discipline ease your supplier assessment; validating the configured application for your intended use remains your responsibility.
Which documents do we get for the supplier assessment?
DPA, T&C and the fact sheet are openly published under /terms/ — with version state and PDF download. Further evidence for your assessment is discussed in the live demo.
ON YOUR OWN CASE
Audit us before you trust us.
In the personal live demo we also show you how we test traqx ourselves — and which documents carry your supplier assessment.
Book your personal live demo
No obligation · personal · straight in the calendar
More features: All features →