The certificate should say what is actually covered.
Scope wording should match the organization's real activities, sites, services, and buyer-facing use.
Process
Management System Certification Process
AQX reviews the applicant, scope, operating context, evidence readiness, and buyer requirement before a management system certificate route is confirmed.
1. Inquiry and requirement review
AQX reviews the exact buyer, tender, platform, or internal requirement and confirms the likely route before payment.
2. Scope and organization definition
The holder, country, sites, activities, exclusions, standard, and intended use are mapped into a supportable certificate scope.
3. Evidence readiness check
Policies, procedures, records, screenshots, training, risk registers, licenses, and operational evidence are checked for sufficiency.
4. Review, correction, and decision
AQX may request corrections. Issuance depends on the reviewed file, scope fit, status checks, and final decision controls.
5. Certificate record and verification
Eligible records may be shown in the public verification system with holder, standard, scope, dates, status, and limitations.
6. Maintenance, change, and renewal
Material changes, complaints, misuse, expiry, renewal, suspension, or withdrawal are handled through documented governance steps.
The file should support the claimed management system.
Evidence may include policies, procedures, records, responsibilities, monitoring, corrective action, and management review.
The public record should support buyer checks.
Verification helps buyers compare holder, scope, dates, route, status, and limitations before reliance.
Before applying
Send the standard and the business context together.
A management system certificate request is easier to review when AQX can see the standard, the buyer wording, the company activities, and the evidence available.
Useful preparation
- Legal name, address, country, and sites.
- Requested standard and scope wording.
- Documents and records already available.
- Buyer wording, deadline, and acceptance requirement.
Commercial fit check
Use this page to decide whether the request is worth pursuing.
Every support page should move the visitor from vague interest to a clear buying decision: what the buyer wants, what the organization can prove, and whether the route is worth budget.
Buyer intent
Translate the ask into a usable brief.
Clauses, portal text, tender wording, country context, and deadline details turn an unclear request into something AQX can actually review.
Scope control
Keep the claim tied to real operations.
The route only makes sense when the activities, sites, services, and legal entity match what the buyer is asking for.
Evidence quality
Show proof, not just intention.
Useful files include records, policies, procedures, monitoring, training, and prior assessments that support the claim being made.
Commercial decision
Stop before payment if the fit is unclear.
If the requirement still looks ambiguous or misaligned, AQX should review it before the applicant spends on the wrong path.