The Immigration (Form and Manner of Passenger and Service Information) Direction 2026

The Immigration (Form and Manner of Passenger and Service Information) Direction 2026 is a technical Home Office instrument that has operational consequences for airlines, rail operators and maritime carriers.

It sets the required transmission standards for advance passenger information and Passenger Name Record data under the Immigration Act 1971 framework and the Immigration and Police (Passenger, Crew and Service Information) Order 2024.

From 25 February 2026, border control is being enforced further upstream, with carriers expected to identify whether a passenger has a recognised permission to travel before departure. That makes data quality, system compatibility and version control compliance issues, not just IT housekeeping.

This guide explains what the Direction requires, who it applies to, how it connects to February 2026 enforcement expectations and where the main risk points arise for operators and their agents.

Section A: What is the Immigration (Form and Manner of Passenger and Service Information) Direction 2026?

The Immigration (Form and Manner of Passenger and Service Information) Direction 2026 is a Home Office instrument that tells carriers the technical format and transmission method they are expected to use when providing passenger and service information to the Home Office. It sits underneath the statutory powers in the Immigration Act 1971 and works alongside the Immigration and Police (Passenger, Crew and Service Information) Order 2024. The Direction matters in practice because it converts a legal duty to provide information into an enforceable set of system level requirements, which carriers then build into boarding and pre departure processes.

1. What is the legal basis for the Direction under the Immigration Act 1971?

The Direction is made by the Secretary of State using powers in Schedule 2 to the Immigration Act 1971, specifically paragraph 27B(8) and paragraph 27B(8A). Paragraph 27B is the provision that allows the Home Office to require carriers to provide passenger and service information. Sub paragraphs (8) and (8A) allow the Secretary of State to specify the “form and manner” in which that information is provided.

In legal terms, the Direction is not a free standing policy document. It is a binding specification that operates within a statutory framework. The duty to provide information comes from paragraph 27B and the secondary legislation made under it. The Direction then fixes the practical detail, for example which interface control document applies, what version is acceptable and which transmission protocol is required.

A useful way to read the framework is in layers:

• Primary legislation: Immigration Act 1971, Schedule 2, paragraph 27B creates the power to require information.
• Secondary legislation: the 2024 Order sets out categories of information that can be required, including the content listed in Schedules 1, 2 and 3.
• Direction: the 2026 Direction sets the technical rules for delivery of that information, including the required message formats and interface standards.

A common compliance risk is treating “form and manner” as optional technical guidance. Carriers who supply the right information but in a non compliant format can still fall short of what the Direction requires, because the legal requirement is tied to the prescribed form and manner, not only to the data fields.

2. When did the 2026 Direction come into force and what did it replace?

The Direction states that it comes into operation on 07 January 2026. It also revokes the Immigration (Form and Manner of Passenger and Service Information) Direction 2023. From 07 January 2026, the 2023 Direction should be treated as superseded for operational purposes.

That timing matters in the wider February 2026 environment because carriers were moving into tighter pre departure permission checks. The Direction is part of the technical foundation for that environment. It does not introduce the permission requirement itself, but it standardises the way carriers deliver information that is used for risk assessment and permission matching.

A second compliance risk sits in document management. Internal carrier policies, vendor specifications and audit packs often lag behind legal changes. If any internal materials still reference the 2023 Direction after 07 January 2026, those documents can create avoidable exposure during an incident review or Home Office engagement.

3. Who has to comply and what journeys are covered?

The Direction applies to the “owner or agent” of an aircraft or ship and to a person operating an international rail service, or their agent. The wording is intended to capture the party responsible for providing data to the Home Office, which can be the carrier itself or an appointed agent that transmits data on the carrier’s behalf.

The Direction draws distinctions between:

• Aircraft, where the UK Generic Carrier Interface Control Document applies for passenger and service information and a separate specification applies for PNR data.
• Ships other than cruise ships and international rail services, where rail and maritime interface control documents apply.
• Cruise ships, where a different submission route is specified through the National Maritime Single Window guidance for cruise operators.

The definition of international rail service is linked to the Channel Tunnel Act 1987 and includes shuttle services. That matters for operators and agents in the Channel Tunnel environment because the Direction treats rail as a separate technical channel with its own interface standards, rather than as a variation of aviation processes.

A practical risk point is responsibility allocation. Where an agent handles transmission, the carrier still needs governance over version updates, data security and contingency planning, because operational accountability and commercial exposure tend to sit with the carrier when something goes wrong at boarding stage.

4. What the Direction does, and what it does not do

The Direction does three things.

First, it links the information set out in the 2024 Order to specific technical documents and versions. For aircraft, passenger and service information under Schedules 1 and 2 is required to be provided as specified in the UK Generic Carrier Interface Control Document, reference UK_ICD_D0081, Version 14.2 or later. For rail and maritime, the Direction points to the relevant rail and maritime API and PNR interface documents, each with a version floor. For cruise operators, it points to the National Maritime Single Window guide.

Second, it requires transmission to be electronic, compatible with Home Office technology and sent through a system that allows carriers to send and receive communications relating to the information. That two way element is operationally important, because it anticipates an interactive compliance environment where carriers receive responses and status messages that affect travel decisions.

Third, it sets a narrow contingency pathway where a technical failure prevents compliance with the standard method. Alternative form and manner is only contemplated with prior agreement of an immigration officer. For PNR data, the alternative route also needs to deliver an equivalent level of personal data security.

The Direction does not change immigration status rules. It does not alter who needs a visa, who needs an ETA, or who is exempt by reason of British or Irish citizenship. It does not change the legal test for entry at the border. It does not create a right of appeal or a new passenger offence. The Direction is a carrier compliance instrument that shapes the practical mechanics of pre departure checks.

The main interpretive trap is assuming that “no change to nationality law” means “no impact on travel experience”. Carrier systems are driven by what can be verified digitally. Where a carrier cannot match a traveller to a recognised permission or exemption in a format the system can process, boarding friction can follow even though the traveller’s underlying legal status is unchanged.

Section B: What Information Must Be Provided and In What Form?

The 2026 Direction does not define new categories of passenger data. It operates by reference to the Immigration and Police (Passenger, Crew and Service Information) Order 2024 and then prescribes how that information is to be transmitted. To understand compliance risk, it is necessary to read the Order and the Direction together. The Order answers the question “what information”, while the Direction answers the question “how and in what format”.

1. What passenger and service information is covered under the 2024 Order?

The 2024 Order sets out three principal schedules of information.

Schedules 1 and 2 cover advance passenger information and service information. This typically includes biographical details drawn from travel documents, flight or journey details, crew information and other service data connected to the carriage of passengers into or out of the United Kingdom.

Schedule 3 covers Passenger Name Record data. PNR data is broader and can include booking information, itinerary history, contact details, payment information and related reservation metadata.

The Direction applies wherever a carrier is subject to a requirement under paragraph 27B of Schedule 2 to the Immigration Act 1971 to provide information specified in those schedules. In other words, the Direction does not operate in isolation. It is triggered where a lawful requirement to provide API or PNR data already exists.

A key compliance point is that the data obligation and the transmission obligation are legally connected. Supplying partial data, delayed data or data in a non compliant format can each give rise to exposure. Carriers should therefore assess completeness, timing and formatting together rather than treating them as separate workstreams.

2. What are the form and manner requirements for aircraft operators?

Where the owner or agent of an aircraft is required to provide passenger and service information under Schedules 1 and 2 of the 2024 Order, the Direction requires that information to be provided as specified in the UK Generic Carrier Interface Control Document, reference UK_ICD_D0081, Version 14.2 or later.

Two aspects require attention.

First, the reference to a specific document with a version number means compliance is tied to a defined technical standard. Interface control documents set out message structures, mandatory and optional fields, validation rules and transmission specifications. They are not high level policy notes. They are system design documents.

Second, the wording “Version 14.2 or later” introduces dynamic incorporation. If the Home Office publishes an updated version beyond 14.2, carriers are expected to align with the later version without the need for a fresh Direction. Governance processes therefore need to include active monitoring of interface updates and documented change management.

In addition, paragraph 5 of the Direction requires that information is provided in electronic form compatible with Home Office technology and through a system enabling the carrier to send and receive communications relating to the information. This anticipates real time or near real time interaction between carrier systems and Home Office systems. It is not sufficient to send a static data file if the system does not support response handling.

3. What are the requirements for ships, cruise operators and international rail services?

The Direction distinguishes between three maritime and rail categories.

For ships other than cruise ships and for international rail services, passenger and service information under Schedules 1 and 2 must be provided electronically and securely as specified in the Advance Passenger Information for Rail and Maritime Carriers Interface Control Document, reference RM_API_ICD, Version 1.7 or later.

For cruise ships, the Direction specifies that the required information must be provided electronically and securely as set out in the National Maritime Single Window guide for cruise operators, Version 1 or later.

The separation of cruise operations reflects different operational models and reporting channels. Cruise operators often interface with port and maritime reporting systems that differ from aviation workflows. The Direction formalises that separation and makes clear that the aviation ICD cannot be treated as a default template for maritime.

International rail operators are expressly brought within the rail and maritime ICD framework. In the Channel Tunnel context, this means passenger data transmission is governed by a distinct rail standard rather than by aviation practice.

Operational risk arises where a carrier group operates across modes and assumes that a single technical solution is compliant across aviation, maritime and rail. The Direction is mode specific. Internal compliance mapping should therefore reflect the correct ICD reference for each transport channel.

4. What are the PNR data transmission standards under the 2026 Direction?

Passenger Name Record data is subject to separate and more prescriptive technical standards.

For aircraft operators, where a requirement arises under paragraph 27B(2) to provide information specified in Schedule 3 of the 2024 Order, the Direction requires the use of the PNRGOV EDIFACT message type, Version 11.1 or later, and the IBM MQ transmission protocol.

This combination fixes both the message format and the transmission channel. EDIFACT defines the structure of the PNR message. IBM MQ defines the messaging middleware used for secure delivery.

For ships and international rail services, the Direction points to the Passenger Name Record data for Rail and Maritime Carriers Interface Control Document, reference RM_PNR_ICD, Version 2.3 or later.

The separation again reflects technical architecture differences across transport modes.

A compliance vulnerability can arise where legacy systems still rely on older EDIFACT versions or alternative transmission middleware. Where the Direction specifies a minimum version and protocol, continued use of outdated specifications can fall short of the legal requirement, even if the data content itself appears correct.

5. What does “version or later” mean for ongoing compliance?

Each technical document cited in the Direction includes the phrase “or later”. That drafting choice has practical consequences.

It means that the Direction does not freeze compliance at the cited version number. Instead, it builds in a mechanism for future technical updates to take effect without the need for a new statutory Direction. When the Home Office publishes a later version of the relevant interface control document, carriers are expected to move to that version.

This approach supports system evolution and digital border development. It also transfers responsibility to carriers to maintain live awareness of specification changes.

Best practice governance in this environment usually includes:

• A named internal owner for API and PNR interface monitoring.
• Documented change logs tracking version upgrades.
• Testing environments aligned with new ICD releases before production rollout.
• Board level reporting where material system changes intersect with boarding risk.

The legal requirement is expressed in technical language, but the exposure is operational. Where a system mismatch leads to data rejection, incomplete transmission or inability to receive Home Office responses, boarding disruption can follow. That risk is heightened in a pre departure permission environment where automated data matching forms part of the travel clearance process.

Section C: How Does the Immigration (Form and Manner of Passenger and Service Information) Direction 2026 Interact With ETA Enforcement in February 2026?

The 2026 Direction sits within a broader shift toward pre-departure digital permission checks. Although the Direction itself is technical and carrier facing, it forms part of the infrastructure that supports Electronic Travel Authorisation enforcement and wider permission to travel controls. The legal change is procedural. The operational consequences, particularly from February 2026, are more visible.

1. Why was the Direction introduced ahead of February 2026 enforcement?

The Direction came into force on 07 January 2026. That date precedes the February 2026 enforcement phase in which carriers were expected to apply tighter pre departure verification processes for passengers travelling to the United Kingdom.

The timing suggests the Direction was intended to sit ahead of tighter pre-departure verification in early 2026. Before boarding checks can operate reliably, the Home Office requires standardised, machine readable data delivered in a consistent format. The Direction therefore consolidates and updates the technical rules that govern how carriers transmit advance passenger information and Passenger Name Record data.

Without a fixed transmission standard, automated permission matching is harder to maintain. The Direction reduces variation between carriers by anchoring data exchange to named interface control documents and version floors. In effect, it prepares the system layer before enforcement intensity increases at the boarding stage.

2. How does API and PNR data integrate with ETA and permission to travel systems?

Advance passenger information and PNR data provide the data points used by Home Office systems to assess risk and to match passengers to known immigration permissions or exemptions. Where a traveller is required to hold an Electronic Travel Authorisation, visa or other form of permission, carrier systems interact with Home Office systems using the transmitted data to verify status.

The Direction strengthens that integration by requiring compatibility with Home Office technology and a system that enables two way communication. Carriers are expected not only to send data but also to receive system responses linked to that data.

From a compliance perspective, three features follow:

• Data accuracy becomes directly linked to boarding outcomes. Incorrect biographical data can prevent successful status matching.
• Transmission timing becomes critical. Late or incomplete API submission can disrupt clearance workflows.
• System resilience matters. Where carrier systems cannot receive or process Home Office responses, boarding decisions may stall.

The Direction does not itself create an ETA requirement. It underpins the data flows that allow ETA compliance to be assessed before departure.

3. Can carriers refuse boarding based on data verification outcomes?

The Direction does not grant or remove a boarding power. Boarding decisions remain governed by the wider carrier liability regime and immigration control framework. However, once data transmission is standardised and integrated with permission systems, carriers are placed in a position where they receive clearer signals about whether a passenger appears to hold the required permission.

Where carrier systems indicate that no recognised permission or exemption can be matched, commercial and regulatory pressures often align. Carriers face potential penalties and reputational exposure if they transport a passenger who is later refused leave to enter. In that context, refusal to board may follow even though the underlying legal position is governed by other provisions.

It is important to distinguish between legal status and operational verification. The Direction does not change the legal right of entry of a British or Irish citizen. It does influence how easily that status can be verified in digital systems at the pre departure stage.

4. Does the Direction affect dual British nationals or certificate of entitlement holders?

The Direction does not amend nationality law. A person who is a British citizen remains exempt from immigration control by reason of that citizenship. A certificate of entitlement to the right of abode continues to evidence that right in accordance with the Immigration Act 1971 framework.

The operational question is different. Carrier systems rely on transmitted API data and recognised document formats. Where a dual British national travels using a non UK passport, carrier systems may not automatically identify the individual as exempt unless the exemption can be verified in a format recognised by the system.

In that context, the Direction has indirect relevance. By mandating structured electronic transmission and compatibility with Home Office systems, it supports automated matching processes. Where the data supplied does not align with what the system expects for exemption recognition, friction can arise at boarding stage.

That friction does not alter the individual’s legal status. It reflects the practical reality that digital verification processes operate within defined technical parameters.

5. What risk themes emerge from the February 2026 environment?

As enforcement moves further upstream, several risk themes become more prominent.

• System dependency risk. Boarding processes are increasingly dependent on successful digital interaction between carrier and Home Office systems.
• Data integrity risk. Minor data inconsistencies can trigger mismatches in automated systems.
• Escalation risk. Where no match is returned, frontline staff require clear escalation protocols and legal awareness.
• Reputational risk. High profile boarding refusals can attract scrutiny where underlying status is later shown to be valid.

The Direction should therefore be read as part of a broader digital border framework rather than as a standalone technical note. It formalises the system standards on which February 2026 enforcement relies.

Section D: Compliance Risks, Technical Failures and Enforcement Exposure

The Immigration (Form and Manner of Passenger and Service Information) Direction 2026 is technical in form but regulatory in effect. Where carriers fail to comply with the prescribed transmission standards, the issue is not limited to system design. It can move quickly into enforcement, contractual exposure and reputational risk. This section examines where legal exposure arises and how the Direction handles system failure scenarios.

1. What happens if a carrier fails to comply with the prescribed form and manner?

The Direction operates within the framework of paragraph 27B of Schedule 2 to the Immigration Act 1971. Where a lawful requirement to provide passenger or service information exists, compliance includes providing that information in the specified form and manner.

If a carrier provides incomplete data, submits it in an outdated format or fails to use the prescribed transmission protocol, it may fall short of the statutory requirement. The exposure does not arise because the Direction creates a new penalty in itself. It arises because failure to comply with paragraph 27B requirements can attract enforcement action under the wider immigration control framework.

In practice, the exposure tends to present as:

• Increased scrutiny from the Home Office, including engagement with compliance teams and technical audits.
• Operational disruption where data rejections prevent clearance workflows.
• Exposure under the carrier liability regime where inadequately verified passengers are transported.
• Commercial impact, including delays and compensation claims where boarding errors occur.

The Direction therefore forms part of a regulatory chain. Technical non compliance can cascade into frontline operational consequences.

2. What qualifies as a technical failure under the Direction?

Paragraphs 6 and 9 of the Direction address situations where it is not possible to provide the required information in accordance with the standard electronic format because of a technical failure.

The Direction does not define “technical failure” exhaustively. The wording contemplates a genuine inability to comply with paragraph 5 or with the specific PNR transmission standards in paragraphs 7 and 8. Examples may include system outages, transmission network disruption or critical software malfunction.

Two safeguards are built into the provision.

First, alternative form and manner requires prior agreement of an immigration officer. This is not an automatic fallback. Carriers are expected to seek and obtain agreement before deviating from the prescribed format.

Second, for PNR data, any alternative method must provide a level of security in relation to personal data equivalent to the standard method. The Direction therefore links contingency arrangements to data protection standards.

A key risk point is treating contingency channels as routine alternatives. The drafting indicates that alternative methods are exceptional and conditional. Repeated reliance on contingency arrangements may attract scrutiny as a systems governance issue rather than as isolated incidents.

3. Can carriers unilaterally choose alternative transmission methods?

The short answer is no. The Direction requires prior agreement of an immigration officer where the prescribed electronic form cannot be used because of technical failure.

That requirement serves two purposes.

It preserves central oversight. The Home Office retains visibility over deviations from the standard transmission pathway.

It maintains security integrity. Particularly in relation to PNR data, the alternative route must offer equivalent protection of personal data. The Direction expressly links contingency to security equivalence.

From a governance perspective, carriers should document:

• The nature and duration of the technical failure.
• The communication with the immigration officer granting agreement.
• The alternative method used and the safeguards applied.
• The remediation steps taken to restore standard compliance.

Absence of documentation can convert a genuine outage into a compliance concern during later review.

4. How does data protection law intersect with the Direction?

Passenger and PNR data contains personal data within the meaning of UK data protection law. The Direction reinforces security expectations by requiring electronic and secure transmission and by mandating equivalent protection where alternative methods are used.

Carriers operate as data controllers or processors depending on the context of the data flow. Transmission to the Home Office forms part of a statutory obligation. That does not remove the need to implement appropriate technical and organisational measures.

Three points require attention:

• Encryption and secure transmission channels consistent with the specified protocols.
• Access controls limiting internal exposure to transmitted data.
• Incident reporting processes where transmission failures intersect with personal data risk.

A failure in transmission that results in data corruption, misdirection or unauthorised access can raise both immigration compliance and data protection exposure. The Direction’s reference to security equivalence in contingency scenarios indicates that personal data protection is not secondary to operational continuity.

5. How should carriers prepare for audit and enforcement review?

The Direction does not set out a formal audit regime. In practice, however, compliance with paragraph 27B requirements can be examined through engagement with the Home Office, particularly where boarding incidents or data anomalies occur.

Preparation should include:

• Clear mapping between internal systems and the relevant interface control document version.
• Evidence of version monitoring and upgrade cycles where “version or later” wording applies.
• Escalation pathways linking technical teams and operational decision makers.
• Board level awareness where systemic changes affect boarding risk exposure.

The Direction is drafted in technical language, yet it has strategic implications. Where data transmission forms the backbone of permission to travel checks, system reliability becomes a governance issue.

Section E: Strategic Planning and Practical Guidance for 2026 and Beyond

The Immigration (Form and Manner of Passenger and Service Information) Direction 2026 is a technical instrument, yet it signals a broader policy trajectory. Border control increasingly depends on structured electronic data exchange and automated permission verification before departure. Carriers therefore need to treat compliance not as a static IT requirement but as an ongoing operational and governance priority.

1. What internal systems should carriers review in light of the 2026 Direction?

Carriers should begin with a systems audit that maps each transport mode to the correct interface control document and version. Aviation, maritime and international rail are treated separately under the Direction. A single template approach is unlikely to satisfy all requirements.

The review should cover:

• Confirmation that the current transmission format matches the prescribed document reference and minimum version.
• Verification that transmission protocols, including PNR message types and middleware, align with the Direction.
• Testing of two way communication functionality to ensure system responses from the Home Office can be received and processed.
• Documented procedures for responding to system mismatches or data rejections.

Where legacy infrastructure is in place, the reference to “version or later” requires forward planning. Delayed upgrades can create exposure even if day to day operations appear stable.

2. How should governance structures reflect the Direction?

The Direction links technical compliance to statutory obligation. Governance arrangements should reflect that connection.

Board and senior management oversight is appropriate where transmission standards intersect with:

• Carrier liability exposure.
• Contractual obligations to code share partners or rail and maritime operators.
• Reputational risk arising from boarding refusals.
• Data protection compliance under UK law.

Clear allocation of responsibility is advisable. Technical teams manage system configuration, but legal and compliance teams should understand the statutory context. Where responsibilities are fragmented, small technical deviations can go unnoticed until an operational failure brings them into focus.

3. What lessons emerge from the February 2026 enforcement environment?

The February 2026 phase demonstrated how quickly technical standards translate into frontline impact. Where digital permission checks are integrated into boarding systems, data integrity and transmission reliability become central to travel outcomes.

Several themes are likely to persist:

• Upstream control. Verification continues to move toward the point of departure rather than the physical border.
• Automation. Decision making increasingly relies on system responses rather than manual discretion.
• Version evolution. Interface control documents are likely to be updated as border technology develops.
• Interoperability. Carrier systems need to integrate with evolving Home Office platforms without service interruption.

Carriers who treat compliance as a periodic exercise rather than a continuous process may find themselves reacting to changes rather than planning for them.

4. Is further amendment to the Direction likely?

The Direction already anticipates technical evolution through its “version or later” wording. That drafting approach reduces the need for frequent formal revocation and replacement.

However, further amendment cannot be ruled out. Changes to passenger information requirements under the 2024 Order, developments in international data sharing standards or shifts in border security policy could require refinement of transmission rules.

Carriers should therefore monitor:

• Updates to the Immigration and Police (Passenger, Crew and Service Information) Order 2024.
• Revisions to interface control documents referenced in the Direction.
• Home Office guidance addressing API and PNR compliance expectations.

A fixed monitoring framework reduces the risk that technical change becomes visible only after operational disruption.

5. Key takeaways: what the Immigration (Form and Manner of Passenger and Service Information) Direction 2026 means in practice

The Direction standardises how carriers provide passenger and service information required under paragraph 27B of Schedule 2 to the Immigration Act 1971. It links that statutory duty to named interface control documents and minimum version requirements. It mandates electronic, secure transmission and two way system compatibility.

The Direction does not alter who requires permission to travel or who is exempt from immigration control. It strengthens the technical foundation on which permission to travel systems operate. In a digital border environment, compliant data transmission is part of immigration control infrastructure rather than a background administrative function.

For carriers, the risk lies less in misunderstanding the principle and more in underestimating the operational consequences of small technical deviations. Effective compliance combines legal awareness, robust systems governance and active monitoring of evolving interface standards.

Section F: Summary and Conclusion

The Immigration (Form and Manner of Passenger and Service Information) Direction 2026 is a technical but legally binding instrument made under paragraph 27B of Schedule 2 to the Immigration Act 1971. It does not change visa or ETA requirements. Instead, it specifies how carriers are required to transmit passenger, crew and service information to the Home Office.

By tying compliance to named interface control documents and minimum version standards, the Direction standardises electronic data exchange across aviation, maritime and international rail services. The reference to “version or later” makes the obligation ongoing. Carriers are expected to monitor updates and maintain system compatibility.

In the February 2026 enforcement environment, accurate and compliant data transmission supports automated permission checks before departure. Technical non compliance can lead to operational disruption and regulatory exposure. The Direction should therefore be treated as part of the UK’s digital border infrastructure rather than as a standalone administrative measure.

Section G: Frequently Asked Questions

Is the Immigration (Form and Manner of Passenger and Service Information) Direction 2026 legally binding?

The Direction is made under paragraph 27B(8) and paragraph 27B(8A) of Schedule 2 to the Immigration Act 1971. Where a carrier is subject to a requirement to provide passenger or service information under paragraph 27B, compliance includes providing that information in the prescribed form and manner set out in the 2026 Direction.

Does the 2026 Direction change visa or ETA requirements?

The Direction does not amend visa rules, ETA eligibility or nationality law. It regulates the technical format and transmission standards for passenger and service information that carriers are required to provide. Permission to travel requirements arise from separate legislation and the Immigration Rules.

Who must comply with the 2026 Direction?

The Direction applies to the owner or agent of an aircraft or ship and to the operator of an international rail service, or their agent, where they are subject to a requirement under paragraph 27B of Schedule 2 to the Immigration Act 1971 to provide passenger, crew or service information.

What is meant by “form and manner”?

“Form and manner” refers to the technical specifications governing how required information is transmitted. This includes the relevant interface control document, the message format, the transmission protocol and the requirement for electronic compatibility with Home Office systems. Compliance requires adherence to those specifications, not only provision of the data content.

What happens if there is a technical failure?

Where a technical failure prevents compliance with the prescribed electronic method, the carrier may provide the required information in an alternative form and manner, but only with prior agreement of an immigration officer. For Passenger Name Record data, the alternative method needs to provide an equivalent level of personal data security to the standard transmission method.

What does “Version X or later” mean in the Direction?

Where the Direction refers to a specific interface control document version “or later”, carriers are expected to comply with updated versions of that document once issued. The obligation is dynamic. Ongoing monitoring of specification updates forms part of compliance governance.

Does the Direction affect dual British nationals?

The Direction does not alter nationality law or the right of abode. It governs data transmission standards used by carrier systems. In a digital permission environment, inability to match a traveller’s status through transmitted data may affect boarding processes, but the underlying legal status remains unchanged.

Why is the 2026 Direction significant in the February 2026 enforcement environment?

The Direction standardises how advance passenger information and Passenger Name Record data are transmitted to the Home Office. In a system where permission to travel is increasingly verified before departure, accurate and compliant data transmission supports automated matching and risk assessment. The Direction underpins operational enforcement, even though it does not itself create permission requirements.

Section H: Glossary of Key Terms

Section I: Useful Legislation and Official Resources