Recommended Practice 1701d (Passenger Services Conference, IATA), formally designated PSC(31)1701d, is the industry recommended practice that defines the specifications and standards for Self-Service Electronic Document Check (also referred to as Self Service Document Check). It forms part of the RP 1701 series covering the End to End Passenger Process and appears in the Passenger Services Conference Resolutions Manual (PSCRM) alongside related practices such as 1701a (Passenger Data Harmonization), 1701f (Self-Service Baggage Check-In), and later One ID practices (1701o Contactless Travel and 1701p Digitalization of Admissibility).
Its purpose is to enable passengers to provide travel-document data without the assistance of an airline agent and to support automated verification that the passenger holds the correct documents to satisfy the requirements of departure, destination, or transit countries. The practice also facilitates the collection or verification of data needed for Advance Passenger Information (API) programmes.
Origin, Status, and Relationship to Other Standards
RP 1701d was developed under the broader RP 1701 framework, which established a modular “Passenger Process Toolbox” approach to standardising both self-service and assisted process steps across the end-to-end journey. The practice was adopted to give airlines a consistent technical and process foundation when deploying document-capture and document-check applications in dedicated (airline-specific) or common-use environments.
It remains a Type B recommended practice of indefinite duration. Subsequent industry work on digital identity, verifiable credentials, and contactless travel (One ID RPs 1701o and 1701p) builds directly on the capability for early, automated document checking that RP 1701d first formalised. Modern commercial implementations (for example IATA Timatic Doc Scan) operationalise the same principles—passenger self-capture or upload of documents, automated verification against entry requirements, and return of validated data to the airline’s departure-control system—within web, mobile, kiosk, and agent-assisted channels.
Purpose and Scope
Airlines need to obtain and verify passenger data from travel documents for three primary reasons:
- Verify that the passenger is who they present themselves to be.
- Verify that the passenger has the correct travel documents to be admitted to (or transit) the country or countries on the itinerary.
- Collect or verify previously obtained passenger data for transmission to government authorities (API / iAPI).
RP 1701d focuses on the second objective and enables the third. Its scope covers the specification and standards for Travel Document Self-Service Data Capture and Document Check Applications. It applies when Members offer Self-Service Document Check capability in a dedicated or common-use environment for individual airline processes.
The practice is technology-agnostic with respect to the physical or digital capture device (kiosk, web check-in, mobile app, or later digital-wallet solutions) provided the functional and data standards are observed.
Technical Structure and Key Provisions
Recommendation
When Members offer Self-Service Document Check capability in a dedicated or common environment for individual airline processes, the specification and standards described in the Recommended Practice shall be applied.
Core Process Elements
The standard process for Self-Service Document Check comprises three elements:
- Document Data Registration
- Self-Service Data Capture
- Document Check
It is recommended that the last two processes (Self-Service Data Capture and Document Check) are followed for self-service document check.
Functional Intent
The purpose is to enable passengers to provide travel-document data without the assistance of an airline agent. The captured data should be used to automatically check that the passenger holds the correct travel documents required for the departure, destination, or transit countries on the itinerary.
Data obtained through the process support both the airline’s own compliance obligations and the subsequent transmission of accurate API data to governments.
Implementation in Airline Operations
Airlines implement RP 1701d principles through:
- Integration of document-capture capability into existing self-service channels (web check-in, mobile app, CUSS kiosks, self-bag-drop units).
- Use of optical character recognition (OCR), machine-readable zone (MRZ) reading, and image capture to extract biographic and document data.
- Real-time or near-real-time validation of the extracted data against entry-requirement databases (classically Timatic or equivalent rules engines).
- Return of validated data and an “OK to travel” / “document compliant” status into the airline’s Departure Control System (DCS) and reservation record.
- Fallback to agent-assisted capture (same verification engine, different user interface) for passengers who cannot or prefer not to use pure self-service.
- Support for both live image capture and file upload (PDF or image) so that passengers can complete the process from home.
Modern commercial services such as Timatic Doc Scan illustrate the operational realisation of these principles: the passenger begins check-in in the airline app or website; the system determines whether additional documents are required; the passenger is prompted to capture or upload them; the documents are verified against current entry rules; and an immediate compliance result is returned, enabling remote check-in to continue.
Relationship to Later Digital and Contactless Standards
RP 1701d provides the foundational self-service document-check capability upon which later One ID practices build. RP 1701p (Digitalization of Admissibility) advances the concept so that the passenger can digitally demonstrate possession of all required documents and authorisations (passport, visa, digital travel authorisation, health certificates, etc.) without necessarily disclosing the full underlying data. RP 1701o (Contactless Travel) then leverages biometric identity verification so that repeated physical presentation of documents at airport touchpoints can be eliminated. Accurate, standardised early document checking remains a prerequisite for these higher-maturity solutions.
Benefits for Passengers, Airlines, and Governments
- Passengers: Ability to complete document verification in advance of arrival at the airport; reduced queue time and stress at check-in; clearer guidance when additional documents are required; support for both tech-comfortable and assisted scenarios.
- Airlines: Lower risk of fines for carriage of inadequately documented passengers; reduced manual document-handling workload at the airport; higher data quality for API submissions; smoother remote check-in completion rates; consistent process across dedicated and common-use environments.
- Governments: Higher-quality, more complete API data received earlier in the process; fewer inadequately documented passengers arriving at the border; improved facilitation for compliant travellers.
Auditability and Continuous Improvement
Effectiveness can be measured through:
- Percentage of passengers completing document check via self-service channels.
- Document-compliance “OK to travel” rates and reduction in last-minute document issues at the gate.
- API data accuracy and rejection statistics.
- Reduction in carrier fines or refused-boarding incidents related to document deficiencies.
- Consistency of implementation against the functional standards of RP 1701d across channels and stations.
Conclusion
Recommended Practice 1701d – Self-Service Electronic Document Check established the industry baseline for passenger-driven capture and automated verification of travel documents. By defining a clear process (data capture followed by document check) and requiring consistent application of the associated specifications in both dedicated and common-use environments, the practice enables earlier, more accurate compliance checking, supports high-quality API data, and reduces reliance on agent-mediated document handling. It remains a foundational element of the modern self-service and digital-identity passenger journey and continues to underpin later One ID standards for digitalisation of admissibility and contactless travel.
Sources include the published text of RP 1701d (PSC(31)1701d) as reflected in Passenger Services Conference materials, the RP 1701 End to End Passenger Process framework, IATA Timatic Doc Scan documentation, and related One ID Recommended Practices 1701o and 1701p. Full proprietary specifications reside in the IATA Passenger Services Conference Resolutions Manual.
