Member Portal Join Now Resources
AutoID™ Programme

How AutoID™ Works

AutoID™ follows a structured flow: define scope, collect evidence, apply integrity checks, issue a unique reference, and maintain a lifecycle-aware status over time — without making market access decisions.

Quick Steps
  1. Application scope and jurisdiction profile are declared
  2. Applicant, identity and evidence sources are verified
  3. Assessment, review and decision are recorded
  4. The authorised record projection is published
  5. Sources, changes, alerts and history are maintained
AutoID™ is a technical identity and trust layer — not homologation.
Scope & Coverage Framework & Principles

A Workflow Designed for Clarity and Traceability

AutoID™ is designed to explain identity in a consistent way: what is covered, what evidence supports it, and how the record evolves through updates and lifecycle events.

The AutoID™ Flow (Overview)

AutoID™ works through a structured process that keeps scope explicit, evidence referenced, and status versioned. The exact technical details may evolve, but the workflow remains stable.

1) Define Application & Scope

Define what is being identified: a vehicle variant, battery system, ADAS module, software component, facility scope or manufacturer profile.

2) Verify Identity & Authenticate Evidence

Gather supporting inputs: documentation references, declarations, traceability markers, test links or other evidence aligned to the declared scope.

3) Assess, Review & Decide

Assess every applicable control against authenticated evidence, record findings, complete independent technical review and obtain a reasoned decision from an authorised decision maker.

4) Publish & Maintain Lifecycle

Issue a unique AutoID™ reference with a published summary, then track lifecycle events: updates, changes, recalls, and superseded versions over time.

AutoID™ does not decide market access. It documents identity and traceability through declared scope and structured evidence.

Step 1 — Declare Scope

Scope is the foundation. AutoID™ begins by declaring what exactly is being identified, at what level, and under which intended boundaries.

Vehicle Variant
Model / configuration scope, not vague “brand” references.
Energy Systems
Battery packs or energy modules where traceability matters.
ADAS & Software
Software-defined modules with versioned lifecycle logic.
Facilities / Profiles
Production or organisational scope where relevant.
Declared scope makes records comparable and reduces ambiguity.

Step 2 — Structure Evidence

Evidence is not a marketing brochure. AutoID™ relies on structured references aligned to the declared scope, allowing the ecosystem to understand what supports the record.

Documentation References
Technical documents linked to scope fields.
Declarations
Structured statements designed for comparison and traceability.
Traceability Markers
References that connect identity to change history.
Supporting Records
Scope-aligned inputs that strengthen technical understanding.
Evidence is always linked to scope; this is what makes the record meaningful.

Step 3 — Assessment, Independent Review & Decision

Assessment examines identity, configuration, jurisdiction mapping and evidence against every applicable control. Independent review and an authorised decision remain separate from regulatory authority decisions.

Applicability & Scope
Every applicable requirement is tied to the exact object, configuration and jurisdiction profile.
Evidence Authentication
Issuer, integrity, relevance, technical sufficiency and configuration applicability are checked.
Independent Review
A competent reviewer who did not perform the assessment checks the complete case and finding closure.
Authorised Decision
A separate decision maker records the exact result, scope, limitations and route to challenge.
A positive scoped result requires every applicable control closed as conforming or justified not applicable, with no unresolved finding affecting the claim.

Step 4 — Publish the Authorised Record & Track Lifecycle

After the applicable controls are closed and an authorised independent decision is recorded, the approved public projection may be published. Restricted evidence and private vehicle-level data remain access-controlled.

AutoID™ Reference
AID-M-123e4567-e89b-42d3-a456-426614174000
Example model identifier using the First Edition class-code and UUID syntax.
Status Layers
Identity / Assessment / Legal Source / Currency
Kept separate to prevent misleading conclusions.
AutoID™ is designed to represent change without confusion: records can be updated and superseded while keeping history traceable.

Separate Status Layers

AUTOID deliberately keeps identity, assessment, external legal-source status and evidence currency separate. A single green label cannot replace these distinctions.

Status layerControlled valuesMeaning
Identitydraft, verified, disputed, suspended, retiredWhether the object identity and authority to maintain it have been checked.
Scoped assessmentnot_assessed, in_review, verified, refused, suspended, withdrawn, supersededThe outcome for an exact assessed scope, configuration and profile.
External legal sourcenot_checked, reported_valid, reported_restricted, reported_expired, reported_withdrawnThe separately sourced authority status at the recorded check time.
Currency & safetycurrent, review_due, stale; alert none_reported, open or resolvedEvidence freshness and safety information, shown independently of identity.
“Verified” identity does not by itself assert technical conformity, legal conformity or market permission.

Process and Implementation Documents

Open the controlled First Edition documents for complete requirements, procedures and working records.

Operations and Implementation Manual
The 18 operating procedures for applications, assessment, decisions, publication and continuing assurance.
27 pagesOpen PDF
Vehicle Identity and Homologation Evidence Standard
The 120 mandatory controls, defined claims, object boundaries and lifecycle rules.
33 pagesOpen PDF
Assessment Checklist and Operational Forms
Interactive checklist with 120 control records and forms F01-F08.
54 pagesOpen PDF
Registry Data and Interface Specification
Identifier syntax, state logic, data contracts, security boundaries and implementation acceptance.
15 pagesOpen PDF

Next: Scope & Coverage

Explore what can receive an AutoID™, what is intentionally out of scope, and how scope keeps the framework comparable.

Scope & Coverage Framework & Principles

IAF’s Global Member Network

From regional OEMs to global tech pioneers, IAF unites a diverse community committed to shaping tomorrow’s mobility.

  • Active global outreach across key mobility regions
  • Strategic onboarding of founding corporate & expert members
  • Monthly roundtables, knowledge-sharing & draft consultations
  • Early-stage collaborations with research & policy networks

…and many more benefits designed to amplify your impact in the evolving mobility ecosystem.

Join the Federation
Explore Network

Join Us in Shaping the Future of Global Mobility

Be part of a powerful movement driving safer, smarter, and more sustainable transportation systems worldwide. Connect with leaders, influence policies, and co-create the automotive innovations of tomorrow with the International Automotive Federation.

Become a Member Explore Membership