Human-centred by design
Controls, information and physical interaction should remain clear for diverse drivers and passengers.
IAF Standards Programme
IAF Smart Mobility
Connected mobility and human experience requirements
A human-centred framework for making connected journeys understandable, usable and dependable across vehicles, infrastructure and mobility services—even when digital dependencies are impaired.
First Edition · Draft for Technical Review · 13 September 2026
Read the Full Working Draft
26 clauses · Annexes A-F · 6 assessment modules
At a glance
Mobility That Still Works for People
The standard evaluates the experience delivered by the complete mobility chain—not simply whether equipment is present. It connects human needs, city readiness, cooperative communication, journey services, energy interaction and automation within one evidence-based assessment.
Connected, not dependent
Baseline protection should not require a compatible phone, account, wearable or connected vehicle.
Ready for real conditions
Claims are assessed against declared roads, cities, networks, infrastructure and service dependencies.
Supported by evidence
Test results, limits, assumptions and change records stay connected to the assessed capability.
Assessment architecture
Six Modules, Selected by the Claimed Capability
A common core always applies. The relevant modules are cumulative and follow what the product or service actually provides or claims.
Controls, information and accessibility
Applies where a human interface or passenger environment is within scope.
Meaning, timing, trust and interoperability
Applies when V2X or another cooperative capability is supplied or claimed.
Roads, roadside data and urban dependencies
Applies when city readiness or infrastructure integration is claimed.
Planning, booking, handovers and shared access
Applies to connected journeys and shared-mobility services.
Charging access, payment and continuity
Applies when charging or another energy-service interaction is provided.
Responsibility, assistance and fallback
Applies when a function performs a driving task or uses remote assistance.
Framework structure
The 26 Clauses in Six Clear Groups
The full document contains the technical requirements and annexes. This table provides a concise map from scope and governance to assessment, public claims and adoption.
| Clauses | Group | What it covers |
|---|---|---|
| 01-04 | Foundation and Scope | Purpose, application rules, terminology, assessment objects and module selection. |
| 05-06 | Governance and Dependencies | Accountability, operating conditions, external dependencies and service contracts. |
| 07-11 | Human Experience | Inclusive design, controls, displays, driver state, passenger experience and ergonomics. |
| 12-17 | Connected Mobility | V2X, cooperative functions, city integration, journeys, charging and adaptive interfaces. |
| 18-22 | Continuity and Evidence | Degraded operation, personal control, software change, validation and incident response. |
| 23-26 | Decision and Adoption | Conformity decisions, public claims, assessment records, improvement and maintenance. |
Need the technical detail? The working draft includes required test scenarios, proposed acceptance criteria, the mandatory evidence register and the capability-record structure.
Key ideas
What Readers Should Take Away
Essential access cannot be digital-only
People without a compatible phone, account or payment card must still be considered where the service affects access or protection.
Equipment presence is not the final outcome
The assessment follows information and action through vehicles, infrastructure, networks and service providers.
External suppliers remain within the boundary
Ownership by another party does not remove a dependency when it can affect the claimed mobility outcome.
Undemonstrated is not the same as not applicable
Missing evidence, unverified assumptions and operating limits must be visible in the assessment record.
Updates require experience regression testing
Software, service and dependency changes should be checked for effects on usability, safety, accessibility and continuity.
Using the document
From a Declared Mobility Scope to a Traceable Decision
Development status: This proposed First Edition is published for technical review and pilot validation. Formal adoption and the release conditions described in Annex E are required before operational use.
01Declare the assessment object, modules and operating domain
02Map human needs, dependencies and service contracts
03Validate applicable scenarios against the proposed criteria
04Record evidence, limitations, decisions and change triggers
Continue with the full technical document
Review all 26 clauses and Annexes A-F, including the required scenarios, measures and evidence records.