IAF technical ecosystem
Standards vs Recognition
A standard describes what should be demonstrated. An assessment examines the evidence. Recognition records a decision about a defined organisation or capability. These are connected steps, but they are not interchangeable.
Two related questions, different answers. IAF's technical portfolio helps organisations define requirements and build reviewable evidence across vehicles, components, digital systems, infrastructure and operations. A recognition pathway examines whether an applicant meets the criteria of a specified programme and scope. Publishing or using a standard does not by itself create an approval, certificate, rating, registry listing or permission to use an IAF mark.
The distinction
Three functions that should not be confused
The middle step matters: a technical document is not an assessment result, and an assessment result is not necessarily organisational recognition.
On a small screen, scroll the table horizontally to compare all three columns.
Terminology matters. This page describes the federation's IAF recognition pathways. It does not claim that an IAF publication or recognition is statutory accreditation, type approval, homologation or a substitute for an independent accreditation scheme. Applicable legal and regulatory requirements remain separate.
How the connection works
From a selected standard to a defensible decision
The same technical framework can support product evaluation, an internal control programme or a recognition application. The outcome depends on the edition, declared scope, evidence quality and the rules of the particular assessment route.
01 / SELECTChoose the relevant documentCheck its title, edition, publication status and applicable clauses.
02 / DEFINEFix the scopeIdentify the organisation, site, vehicle, version, service or activity.
03 / DEMONSTRATEGenerate evidenceUse controlled records, competent methods and stated limitations.
04 / DECIDEApply the programme rulesReview findings and issue only the outcome the route permits.
What makes the evidence transferable?
Traceable identityRecords identify the item, version, site, date and responsible party being assessed.
Declared applicabilityIncluded requirements, exclusions and reasons are explicit, not assumed.
Method and competenceTest or audit methods, equipment and reviewer competence are documented.
Bounded conclusionFindings state uncertainties, deviations, unresolved issues and decision limits.
Explore the portfolio
Where the 12 frameworks fit
IAF's portfolio spans more than four original topic areas. The groups below are a navigation aid, not a claim that every document has the same status or that every framework is required for every applicant. Open each overview for its scope and full technical PDF.
The standards portal displays the current document status and provides the complete PDF for each framework.
A working draft is not an issued recognition scheme.Several technical texts remain in draft or development. Their publication makes requirements available for review; it does not announce that every linked assessment, label or certification service is already operational.
Choose the route
Start with the outcome you actually need
On a small screen, scroll horizontally for the complete route comparison.
Common questions
What can you claim?
Does using an IAF standard mean our organisation is recognised?
No. A standard can guide controls and evidence, but recognition requires a separate applicable programme, assessment and decision for a defined scope.
Does an organisational recognition cover every product we make?
No. Recognition is limited to its stated organisation, activities and conditions. Product or system conformity needs its own defined criteria and evidence.
Can a draft PDF be cited as an approval or certification?
No. Cite the document and edition accurately as a technical reference. Any formal outcome or mark requires a separate authorised process.
Can I use an IAF quality mark after a favourable internal review?
No. Mark use is governed by the applicable scheme and explicit authorisation. See the quality marks guidance.
Your next step
Build evidence. Select the right pathway. Help improve the framework.
Explore the full technical documents, discuss a scope-specific recognition route, or contribute a precise, evidence-backed comment to the standards programme.