PUJOL Corporation

Appeler Itinรฉraire Site Web Contacter l'entreprise

PUJOL Corporation A Rock that Rides Out The Storm - Operational Excellence - Crisis Management - Change Management

๐™Š๐™‹๐™€๐™๐˜ผ๐™๐™„๐™Š๐™‰๐˜ผ๐™‡ ๐™๐™€๐˜ผ๐™‡๐™„๐™๐™”  #017A cancelled flight doesn't create one problem. It creates an entire recovery operation.When a f...
14/10/2026

๐™Š๐™‹๐™€๐™๐˜ผ๐™๐™„๐™Š๐™‰๐˜ผ๐™‡ ๐™๐™€๐˜ผ๐™‡๐™„๐™๐™” #017

A cancelled flight doesn't create one problem. It creates an entire recovery operation.

When a flight is cancelled, the operational response extends far beyond informing passengers.

Within a short period, teams must answer six critical questions.

01 โ€” WHO?

How many passengers require assistance? Who is travelling together? Who has specific requirements?

02 โ€” WHERE?

Which hotels have capacity? Which properties can accommodate particular passenger needs?

03 โ€” HOW?

What ground transport is available? How will passengers be distributed between vehicles and destinations?

04 โ€” WHO DOES WHAT?

Which operational teams and suppliers are responsible for executing each part of the recovery?

05 โ€” WHAT HAS BEEN COMPLETED?

Which passengers have been assigned? Which movements are progressing? What remains unresolved?

06 โ€” WHAT HAPPENS NEXT?

How will the operation manage the reprogrammed departure, passenger documentation and outstanding actions?

These aren't six independent problems.

They are six interconnected parts of the same operation.

Yet in many disruption environments, they are managed through separate processes, teams and communication channels.

That's where PAX Divertยฎ comes in.

Our platform is designed to bring these activities into one structured passenger recovery workflow.

From passenger import and party management to hotel allocation, transport coordination, supplier visibility, operational status tracking and recovery documentation.

One disruption. Six operational questions. One coordinated recovery workflow.

PAX Divertยฎ โ€” From disruption to control.

Airlines and ground handlers: how many separate systems or processes does your team currently use to manage these six stages?

๐Ÿ‘‰ Let's walk through a disruption scenario together and explore how PAX Divertยฎ could fit into your operation.

๐™๐™ƒ๐™€ ๐˜พ๐™Š๐™Ž๐™ ๐™Š๐™ ๐˜พ๐™ƒ๐˜ผ๐™Š๐™Ž  #017Assigned is not accommodated.A hotel has been allocated.A bus has been arranged.The passenger lis...
12/10/2026

๐™๐™ƒ๐™€ ๐˜พ๐™Š๐™Ž๐™ ๐™Š๐™ ๐˜พ๐™ƒ๐˜ผ๐™Š๐™Ž #017

Assigned is not accommodated.

A hotel has been allocated.

A bus has been arranged.

The passenger list has been updated.

On paper, the recovery is progressing.

But has the passenger boarded the bus?

Has the bus departed?

Has the passenger arrived at the hotel?

Has the hotel confirmed check-in?

And if the passenger's plans changed along the way, does the operational team know?

An assignment records a decision. It does not confirm the outcome.

During an IRROPS event, these distinctions matter.

A passenger can be assigned to a hotel without having arrived there.

A transport can be organised without every passenger boarding.

A plan can be completed on a spreadsheet while the situation on the ground has already changed.

Without reliable status updates, operational teams must spend time chasing confirmations, reconciling information and determining what still requires action.

That is time taken away from managing the disruption itself.

PAX Divertยฎ connects passenger assignments with operational status tracking throughout the recovery process.

Teams can follow the progression of passenger handling, accommodation and transport, while keeping the operational picture connected to the actions being carried out.

Because knowing what was planned is useful.

Knowing what actually happened is operational control.

PAX Divertยฎ โ€” From disruption to control.

๐Ÿ‘‰ How does your operation distinguish between a passenger being assigned, a passenger being transported and a passenger successfully accommodated?

๐™๐™ƒ๐™€ ๐˜พ๐™Š๐™Ž๐™ ๐™Š๐™ ๐˜พ๐™ƒ๐˜ผ๐™Š๐™Ž  #016A room isn't passenger recovery. Neither is a bus.During a disruption, resources matter.You need ...
06/10/2026

๐™๐™ƒ๐™€ ๐˜พ๐™Š๐™Ž๐™ ๐™Š๐™ ๐˜พ๐™ƒ๐˜ผ๐™Š๐™Ž #016

A room isn't passenger recovery. Neither is a bus.

During a disruption, resources matter.

You need rooms.

You need transport.

You need people.

But securing resources doesn't mean the recovery operation is under control.

Because between โ€œ50 rooms availableโ€ and โ€œ50 passengers accommodatedโ€, an entire operation still has to happen.

Which passengers go where?

Who needs to remain together?

Who has specific requirements?

Which transport serves which hotel?

Who has actually boarded?

Has the vehicle departed?

Has the passenger arrived?

Has the hotel checked them in?

What happens when the plan changes?

And who still requires action?

This is where passenger recovery becomes more than procurement.

Resources have to become coordinated operational outcomes.

PAX Divertยฎ is designed to manage that transition.

Supplier capacity is captured.

Passenger lists are imported and structured into parties.

Operational requirements are identified.

Accommodation and transport are assigned according to predefined rules.

Suppliers can see the passengers assigned to them and update their status as the recovery progresses.

Passenger documentation and Letters of Guarantee are generated.

And operational teams maintain visibility over what has been planned, assigned and actually completed.

All within the same recovery workflow.

Because the objective isn't to find a hotel.

It isn't to find a bus.

It's to recover the passenger.

That's the difference between having resources available and having the operation under control.

PAX Divertยฎ โ€” From disruption to control.

๐Ÿ‘‰ Managing passenger recovery during IRROPS? Let's talk about how your operation handles it today.

๏ปฟ

๐™๐™ƒ๐™€ ๐˜พ๐™Š๐™Ž๐™ ๐™Š๐™ ๐˜พ๐™ƒ๐˜ผ๐™Š๐™Ž  #015One disruption. Too many tools.A flight is cancelled.And suddenly, passenger recovery starts happ...
28/09/2026

๐™๐™ƒ๐™€ ๐˜พ๐™Š๐™Ž๐™ ๐™Š๐™ ๐˜พ๐™ƒ๐˜ผ๐™Š๐™Ž #015

One disruption. Too many tools.

A flight is cancelled.

And suddenly, passenger recovery starts happening everywhere.

The passenger list is in a spreadsheet.

Hotel availability is being confirmed by phone or email.

Transport is being arranged separately.

Passenger requirements are being passed between teams.

Assignments are being updated manually.

Suppliers are waiting for instructions.

Letters of Guarantee still need to be issued.

And somewhere in the middle of all of this, someone is trying to maintain an accurate picture of the recovery.

None of these tools are necessarily failing.

They simply weren't designed to operate as one recovery system.

That's where operational friction appears.

Information has to be copied.

Updates have to be relayed.

Decisions have to be reconciled.

And every additional handoff creates another opportunity for the operational picture to fall behind reality.

PAX Divertยฎ takes a different approach.

One disruption.

One operational environment.

One recovery workflow.

Create the disrupted flight.

Alert stakeholders and suppliers.

Receive available capacity.

Import passengers and structure passenger parties.

Account for specific requirements.

Assign accommodation and transport according to operational rules.

Generate passenger documentation.

Allow suppliers to follow and update the passengers assigned to them.

Generate Letters of Guarantee.

Manage the reprogrammed departure.

And maintain the operational history throughout.

That's what PAX Divertยฎ was built to do.

Not add another tool to the disruption.

Connect the operation that already exists around it.

๐Ÿ‘‰ Managing passenger recovery during IRROPS? Let's talk.

๐™Š๐™‹๐™€๐™๐˜ผ๐™๐™„๐™Š๐™‰๐˜ผ๐™‡ ๐™๐™€๐˜ผ๐™‡๐™„๐™๐™”  #014A manifest tells you who travelled. It doesn't tell you how to recover them.A passenger list is...
23/09/2026

๐™Š๐™‹๐™€๐™๐˜ผ๐™๐™„๐™Š๐™‰๐˜ผ๐™‡ ๐™๐™€๐˜ผ๐™‡๐™„๐™๐™” #014

A manifest tells you who travelled. It doesn't tell you how to recover them.

A passenger list is essential.

But when a flight is cancelled or diverted, 180 names do not represent 180 identical problems to solve.

Among those passengers may be:

A family of five that needs to remain together.

A couple travelling on the same booking.

A passenger with reduced mobility.

An unaccompanied minor.

A passenger with specific accommodation requirements.

A premium passenger subject to different recovery rules.

Someone who has already arranged their own accommodation.

Several passengers travelling together even though their bookings are separate.

The manifest tells the operation who is there.

Recovery requires another layer of understanding:

Who belongs together?

Who requires what?

Who can be assigned where?

Who needs a different recovery path?

That distinction matters.

Because passenger recovery isn't simply about distributing names across available rooms and vehicles.

It is about turning a passenger list into operationally meaningful groups, requirements and assignments.

That's why PAX Divertยฎ allows passenger data to become part of the recovery workflow: creating passenger parties, identifying specific requirements and applying operational rules when accommodation and transport are assigned.

The manifest is the starting point.

It is not the recovery plan.

๐™๐™ƒ๐™€ ๐˜พ๐™Š๐™Ž๐™ ๐™Š๐™ ๐˜พ๐™ƒ๐˜ผ๐™Š๐™Ž  #014A disruption creates a second operation.A flight is cancelled.The scheduled operation may have st...
22/09/2026

๐™๐™ƒ๐™€ ๐˜พ๐™Š๐™Ž๐™ ๐™Š๐™ ๐˜พ๐™ƒ๐˜ผ๐™Š๐™Ž #014

A disruption creates a second operation.

A flight is cancelled.

The scheduled operation may have stopped.

But another one has just begun.

Passengers need to be accounted for.

Parties need to remain together.

Specific requirements need to be identified.

Hotel capacity needs to be secured.

Transport needs to be coordinated.

Suppliers need to know what is expected of them.

Passengers need to move.

Exceptions need to be resolved.

And eventually, everyone needs to be brought back into the operation for their reprogrammed journey.

None of this is peripheral to the disruption.

It is an operation in its own right.

The difference is that it wasn't scheduled.

Its resources weren't necessarily positioned in advance.

Its stakeholders may belong to different organisations.

And its operating picture can change by the minute.

Yet we often expect teams to coordinate it through phone calls, emails, spreadsheets and message threads layered on top of their normal responsibilities.

That's where complexity compounds.

Passenger recovery needs the same things we expect from any controlled operation:

Structure.

Ownership.

Status.

Coordination.

PAX Divertยฎ is designed around that reality โ€” connecting passengers, operational teams, accommodation, transport and recovery actions within one coordinated environment.

Because when the original operation breaks down, another operation begins.

The question is whether that operation is improvised โ€” or controlled.

๐™Š๐™‹๐™€๐™๐˜ผ๐™๐™„๐™Š๐™‰๐˜ผ๐™‡ ๐™๐™€๐˜ผ๐™‡๐™„๐™๐™”  #013Visibility without action is just observation.Knowing that 142 passengers need accommodation is...
16/09/2026

๐™Š๐™‹๐™€๐™๐˜ผ๐™๐™„๐™Š๐™‰๐˜ผ๐™‡ ๐™๐™€๐˜ผ๐™‡๐™„๐™๐™” #013

Visibility without action is just observation.

Knowing that 142 passengers need accommodation is useful.

Knowing that 96 have been assigned rooms is better.

Knowing that two buses are available gives the operation more context.

But none of that moves a passenger.

During IRROPS, operational visibility is only valuable when it enables someone to act.

A room needs to become an assignment.

An assignment needs to become a transport requirement.

A transport requirement needs to become a movement.

An exception needs to become an action with an owner.

And every completed action needs to update the operational picture for everyone else.

That is the difference between a dashboard and an operational coordination system.

One shows the disruption.

The other helps teams manage it.

This matters because IRROPS rarely involves one team working in isolation.

Airline operations, passenger services, ground handlers, hotels and transport providers may all be acting on different parts of the same recovery.

The objective isn't simply to give everyone more information.

It's to connect information โ†’ decision โ†’ action โ†’ status.

That is the operational model behind PAX Divertยฎ: bringing the stakeholders and workflows involved in passenger recovery into a coordinated environment where the operational picture can drive the next action.

Because during a disruption:

The goal isn't to see the operation.

The goal is to move it forward.

๐™๐™ƒ๐™€ ๐˜พ๐™Š๐™Ž๐™ ๐™Š๐™ ๐˜พ๐™ƒ๐˜ผ๐™Š๐™Ž  #013Correct information has an expiry date.๐˜ฟ๐™ช๐™ง๐™ž๐™ฃ๐™œ ๐™– ๐™™๐™ž๐™จ๐™ง๐™ช๐™ฅ๐™ฉ๐™ž๐™ค๐™ฃ, ๐™ž๐™ฃ๐™›๐™ค๐™ง๐™ข๐™–๐™ฉ๐™ž๐™ค๐™ฃ ๐™˜๐™–๐™ฃ ๐™—๐™š ๐™–๐™˜๐™˜๐™ช๐™ง๐™–๐™ฉ๐™š ๐™–๐™ฉ 01:15 ...
14/09/2026

๐™๐™ƒ๐™€ ๐˜พ๐™Š๐™Ž๐™ ๐™Š๐™ ๐˜พ๐™ƒ๐˜ผ๐™Š๐™Ž #013

Correct information has an expiry date.

๐˜ฟ๐™ช๐™ง๐™ž๐™ฃ๐™œ ๐™– ๐™™๐™ž๐™จ๐™ง๐™ช๐™ฅ๐™ฉ๐™ž๐™ค๐™ฃ, ๐™ž๐™ฃ๐™›๐™ค๐™ง๐™ข๐™–๐™ฉ๐™ž๐™ค๐™ฃ ๐™˜๐™–๐™ฃ ๐™—๐™š ๐™–๐™˜๐™˜๐™ช๐™ง๐™–๐™ฉ๐™š ๐™–๐™ฉ 01:15 ๐™–๐™ฃ๐™™ ๐™ค๐™ฅ๐™š๐™ง๐™–๐™ฉ๐™ž๐™ค๐™ฃ๐™–๐™ก๐™ก๐™ฎ ๐™™๐™–๐™ฃ๐™œ๐™š๐™ง๐™ค๐™ช๐™จ ๐™–๐™ฉ 01:45.

A hotel confirms capacity.

A transport provider confirms availability.

A passenger count is established.

An assignment is made.

Then the operation moves.

Rooms are consumed.

Transport capacity changes.

Passengers make their own arrangements.

Requirements change.

Decisions made elsewhere alter the recovery plan.

The problem isn't necessarily that anyone received wrong information.

The problem is that they may still be acting on information that is no longer true.

And stale information can look remarkably reliable.

It sits in a spreadsheet.

It remains in an email.

It appears in a message thread.

Someone remembers it from the last call.

So another decision gets made on top of it.

In IRROPS, operational information has a shelf life.

The longer multiple stakeholders maintain separate versions of the operation, the greater the risk that yesterday'sโ€”or even twenty minutes ago'sโ€”reality continues driving today's decisions.

This is why coordination requires more than sharing information.

It requires maintaining a current operational picture as conditions change.

๐‘ท๐‘จ๐‘ฟ ๐‘ซ๐‘ฐ๐‘ฝ๐‘ฌ๐‘น๐‘ปยฎ ๐‘ฉ๐‘น๐‘ฐ๐‘ต๐‘ฎ๐‘บ ๐‘ท๐‘จ๐‘บ๐‘บ๐‘ฌ๐‘ต๐‘ฎ๐‘ฌ๐‘น ๐‘บ๐‘ป๐‘จ๐‘ป๐‘ผ๐‘บ, ๐‘จ๐‘ช๐‘ช๐‘ถ๐‘ด๐‘ด๐‘ถ๐‘ซ๐‘จ๐‘ป๐‘ฐ๐‘ถ๐‘ต, ๐‘ป๐‘น๐‘จ๐‘ต๐‘บ๐‘ท๐‘ถ๐‘น๐‘ป ๐‘จ๐‘ต๐‘ซ ๐‘ถ๐‘ท๐‘ฌ๐‘น๐‘จ๐‘ป๐‘ฐ๐‘ถ๐‘ต๐‘จ๐‘ณ ๐‘จ๐‘ช๐‘ป๐‘ฐ๐‘ถ๐‘ต๐‘บ ๐‘ฐ๐‘ต๐‘ป๐‘ถ ๐‘ถ๐‘ต๐‘ฌ ๐‘ช๐‘ถ๐‘ถ๐‘น๐‘ซ๐‘ฐ๐‘ต๐‘จ๐‘ป๐‘ฌ๐‘ซ ๐‘ฌ๐‘ต๐‘ฝ๐‘ฐ๐‘น๐‘ถ๐‘ต๐‘ด๐‘ฌ๐‘ต๐‘ป ๐‘บ๐‘ถ ๐‘บ๐‘ป๐‘จ๐‘ฒ๐‘ฌ๐‘ฏ๐‘ถ๐‘ณ๐‘ซ๐‘ฌ๐‘น๐‘บ ๐‘ช๐‘จ๐‘ต ๐‘พ๐‘ถ๐‘น๐‘ฒ ๐‘ญ๐‘น๐‘ถ๐‘ด ๐‘ป๐‘ฏ๐‘ฌ ๐‘ฌ๐‘ฝ๐‘ถ๐‘ณ๐‘ฝ๐‘ฐ๐‘ต๐‘ฎ ๐‘บ๐‘ป๐‘จ๐‘ป๐‘ฌ ๐‘ถ๐‘ญ ๐‘ป๐‘ฏ๐‘ฌ ๐‘ซ๐‘ฐ๐‘บ๐‘น๐‘ผ๐‘ท๐‘ป๐‘ฐ๐‘ถ๐‘ต.

Because during IRROPS:

Information doesn't have to be wrong to create chaos.

It only has to be old.

๐™„๐™‰๐™Ž๐™„๐˜ฟ๐™€ ๐™๐™ƒ๐™€ ๐˜ฟ๐™„๐™Ž๐™๐™๐™‹๐™๐™„๐™Š๐™‰  #012Assigned isn't the same as arrived.Illustrative scenario.01:42 โ€” Hotel assigned.01:48 โ€” Trans...
11/09/2026

๐™„๐™‰๐™Ž๐™„๐˜ฟ๐™€ ๐™๐™ƒ๐™€ ๐˜ฟ๐™„๐™Ž๐™๐™๐™‹๐™๐™„๐™Š๐™‰ #012

Assigned isn't the same as arrived.

Illustrative scenario.

01:42 โ€” Hotel assigned.

01:48 โ€” Transport assigned.

02:05 โ€” Passenger directed to the departure point.

02:27 โ€” Bus departs.

02:54 โ€” Hotel begins receiving passengers.

03:11 โ€” One question reaches the operations team:

โ€œ๐™’๐™๐™š๐™ง๐™š ๐™ž๐™จ ๐™ฉ๐™๐™ž๐™จ ๐™ฅ๐™–๐™จ๐™จ๐™š๐™ฃ๐™œ๐™š๐™ง?โ€

The system may show an allocation.

The manifest may show a name.

The hotel may have a room waiting.

But none of those things confirm where the passenger actually is.

During a disruption, operational status changes constantly.

A passenger misses the bus.

Someone takes a taxi.

A family decides to stay with relatives.

Someone goes to the wrong pickup point.

A passenger requiring assistance moves through the operation differently from the rest of the group.

And suddenly, the plan and reality are no longer the same.

This is why disruption management cannot stop at allocation.

Teams need visibility over the progress of the recovery, not just the decisions that created it.

๐‘ท๐‘จ๐‘ฟ ๐‘ซ๐‘ฐ๐‘ฝ๐‘ฌ๐‘น๐‘ปยฎ ๐‘ฐ๐‘บ ๐‘ซ๐‘ฌ๐‘บ๐‘ฐ๐‘ฎ๐‘ต๐‘ฌ๐‘ซ ๐‘ป๐‘ถ ๐‘ฒ๐‘ฌ๐‘ฌ๐‘ท ๐‘ท๐‘จ๐‘บ๐‘บ๐‘ฌ๐‘ต๐‘ฎ๐‘ฌ๐‘น ๐‘บ๐‘ป๐‘จ๐‘ป๐‘ผ๐‘บ, ๐‘จ๐‘ช๐‘ช๐‘ถ๐‘ด๐‘ด๐‘ถ๐‘ซ๐‘จ๐‘ป๐‘ฐ๐‘ถ๐‘ต ๐‘จ๐‘ต๐‘ซ ๐‘ป๐‘น๐‘จ๐‘ต๐‘บ๐‘ท๐‘ถ๐‘น๐‘ป ๐‘จ๐‘บ๐‘บ๐‘ฐ๐‘ฎ๐‘ต๐‘ด๐‘ฌ๐‘ต๐‘ป๐‘บ ๐‘ช๐‘ถ๐‘ต๐‘ต๐‘ฌ๐‘ช๐‘ป๐‘ฌ๐‘ซ ๐‘จ๐‘บ ๐‘ป๐‘ฏ๐‘ฌ ๐‘ถ๐‘ท๐‘ฌ๐‘น๐‘จ๐‘ป๐‘ฐ๐‘ถ๐‘ต ๐‘ฌ๐‘ฝ๐‘ถ๐‘ณ๐‘ฝ๐‘ฌ๐‘บ.

Because at 03:11, the question shouldn't require five phone calls and three different spreadsheets.

The operation should know.

๐™Š๐™‹๐™€๐™๐˜ผ๐™๐™„๐™Š๐™‰๐˜ผ๐™‡ ๐™๐™€๐˜ผ๐™‡๐™„๐™๐™”  #012Confirmed doesn't mean completed.A hotel confirms the rooms.A transport provider confirms the b...
09/09/2026

๐™Š๐™‹๐™€๐™๐˜ผ๐™๐™„๐™Š๐™‰๐˜ผ๐™‡ ๐™๐™€๐˜ผ๐™‡๐™„๐™๐™” #012

Confirmed doesn't mean completed.

A hotel confirms the rooms.

A transport provider confirms the buses.

Passenger services confirm the passengers have been assigned.

On paper, everything looks organised.

But during a disruption, confirmation is only the beginning.

Were the passengers actually transported?

Did everyone arrive at the hotel?

Were all the allocated rooms used?

Did someone arrange their own accommodation?

Did a passenger miss the transport?

Did an accessibility requirement change the original plan?

Operational teams don't just need to know what was planned.

They need to know what actually happened.

Because the gap between assigned, confirmed and completed is where passengers can disappear from the operational picture.

Effective disruption management requires the operation to follow each action through to its outcome.

PAX Divertยฎ connects passenger assignments, accommodation and transport within the same operational environment โ€” helping teams maintain visibility as the recovery progresses.

Because in IRROPS, a resource isn't managed just because it has been booked.

The loop has to be closed.

Adresse

Noumรฉa
98800

Tรฉlรฉphone

+687991442

Notifications

Soyez le premier ร  savoir et laissez-nous vous envoyer un courriel lorsque PUJOL Corporation publie des nouvelles et des promotions. Votre adresse e-mail ne sera pas utilisรฉe ร  d'autres fins, et vous pouvez vous dรฉsabonner ร  tout moment.

Contacter L'entreprise

Envoyer un message ร  PUJOL Corporation:

Raccourcis

Partager

Catรฉgorie