What typically becomes difficult
Affected travellers must be narrowed down by area and time.
Current journey changes alter the affected population.
Communications, responses and event context need to be connected.
Solution · Duty of Care
Identify relevant travellers and supply Security processes with precision.
Identify potentially affected travellers and inform them appropriately through TD care. NP4 connects existing travel and location data with incident context and your communication rules. TD doc can add centrally managed security content; TD hub can supply data to external providers. Both additions are optional.
Situation
When a general traveller list is not enough
When an event occurs, location, timeframe, itinerary and available contact details need to align. External risk intelligence alone does not provide the actual company context. Comparing it with available travel and location data helps identify potentially affected travellers and inform them appropriately.
NP4
NP4's role
NP4 combines available trip data and permitted contact details, narrows down potentially affected travellers by area and time, and supports communication under your rules. The process uses TD pool and TD care; TD doc and TD hub can add centrally maintained content or defined handovers to external systems where needed.
Riskline can be connected as an optional source for risk levels, Real-Time Alerts and security content.
Optional Riskline integrationResponsibility boundary: NP4 does not replace risk intelligence, medical or security assistance, and does not assume the organisation’s duty-of-care responsibility.
Approach
From a clear scope to dependable operations.
Provide travel data
Bring location information and authorised contact data together for your security process. Coverage depends on the existing sources.
Identify potentially affected travellers
Use TD care to match incidents against the relevant area, time period and available travel information.
Communicate according to defined rules
TD care informs the selected group by email, SMS and, when enabled, push notification. TD doc can add advisories, country reports and branded content.
Optionally supply external systems
TD hub can supply required information to external risk, assistance or security providers and other target systems. Scope and delivery method follow each recipient’s needs.
Relevant proof
Published customer examples from related use cases.
From Travel Management to a travel-data foundation used across enterprise functions.
GEA uses the NP4 Travel Data Suite to collect and consolidate global booking data, analyse it and connect downstream systems.
Explore customer project →FAQ
Enterprise questions
Is Riskline mandatory?
No. TD doc maintains and delivers Advisories and Country Reports without Riskline. The optional integration is designed for companies that automate their own travel-security processes: it synchronises country risk levels, feeds Real-Time Alerts into TD care and automatically creates new security content in TD doc, updates existing content and deletes outdated content. Additional Riskline APIs can be connected within the agreed scope.
Which traveller and contact data is used?
That is defined for each customer based on purpose, permissions and the privacy concept.
Does NP4 replace an assistance or travel security provider?
No. TD care makes location and risk information operationally usable, TD doc handles agreed automated security communications and TD hub can transfer defined data to external providers.
Relevant products
Core products
Combine travel data available from connected sources so that agreed travel and stay information can support your security processes.
View product
Match available travel and stay data with event and risk information. Narrow down potentially affected travellers and support communication with that group.
View productOptional by process
Trip Logging can provide an additional capture path for journeys outside automatically connected booking channels. Completeness and freshness depend on the available sources and on trips actually being recorded.
Explore Trip LoggingDiscuss the scenario using your actual landscape.
Let us review your current landscape, objectives and relevant data and process requirements.