The State of ITOps in 2026, Seen From a Charter Desk

The State of ITOps in 2026, Seen From a Charter Desk

Anyone who has watched a charter coordinator at work knows the choreography: a client changes the departure time, a ground car must be re-timed, catering needs a new window, and every party must hear about it in the right order. Behind that choreography sits a stack of booking systems, messaging tools and payment services that someone must keep alive. That quiet backstage job has a name, ITOps, and 2026 has been an eventful year for it. Here is a plain-spoken look at where the field stands, drawing on a status entry in the Ops Atlas on ITOps, with a few stories from the world of premium travel to make it concrete.

A field with a long memory

The roots go back further than most people expect. The Atlas timeline starts with the British government’s central computing agency published the first ITIL guidance in 1989, and that library eventually grew to some thirty volumes. An international service management standard followed in 2005, built on an earlier British one. A lifecycle-based edition arrived in 2007, ownership changed hands through the 2010s, and in 2019 a fourth edition swapped the lifecycle for a set of practices. Then, in January 2026, the current owner, PeopleCert, announced a fifth version, described in the announcement as AI-native by design and due to arrive in phases. The fourth edition stays available meanwhile.

For a charter operator that sounds remote, but the lesson is familiar: standards evolve slowly, while customers expect instant service. The practical consequence is that teams should not wait for any new edition before fixing their own basics.

Trend one: practices over process maps

The shift in 2019 from a lifecycle to practices matters because it mirrors how good charter teams work. Nobody runs a trip as a straight line from enquiry to landing; the work is a bundle of capabilities, such as pricing, crew coordination, ground handling and aftercare, each with its own owner. The Atlas counts 34 practices in the current edition, 22 on the product and service side and 12 on general management, but it also stresses that the core operational set is small: a service desk, incident handling, service requests, problem investigation, change enablement, monitoring, configuration records and service levels.

Trend two: change is being rethought

The most interesting debate concerns how changes get approved. The research programme behind a well-known set of software delivery studies found no evidence that approval by an outside board lowers failed-change rates. It recommends peer review instead, with the board becoming more of a designer of the process than a gate. Yet in Europe a regulation that shares the same acronym, in force since January 2025, still expects independent approval and a post-implementation sign-off of emergency changes for firms in its scope. So the picture in 2026 is split: evidence nudges teams toward lighter review, while law may hold firms to specific controls.

Think of how a premium operator handles a last-minute route amendment. Routine tweaks, such as a seat-layout preference, are pre-agreed. An unusual change gets a second pair of eyes. An emergency diversion happens immediately and is reviewed later. That three-lane thinking is exactly what the Atlas describes as standard, normal and emergency changes. For another view of how those preferences are managed on the client side, see what luxury travellers expect charter providers to anticipate.

Trend three: predictive risk scoring, with caveats

One of the newest data points in the Atlas is an unreviewed preprint from August 2026 produced by a bank’s research team. A learned model flagged 63% of the changes that later led to major incidents, compared with roughly a fifth for the bank’s own questionnaire. The precision was 0.55 across 203 changes. Excited commentary followed, but the Atlas adds the arithmetic that tempers it: in a stream of 10,000 changes where one per cent fail, only about six per cent of raised flags would point to a real problem.

The charter parallel is a weather-risk tool that warns of delays. If it cries wolf too often, dispatchers stop looking. The sensible reading is that models can sharpen where humans look first, not that they replace the look.

Trend four: the tooling map keeps shifting

The Atlas snapshot for October 2026 names two commercial service platforms and two open-source ones, one of which shipped a new release in September. It also records that Opsgenie, the paging product from Atlassian, is due to be switched off in early April 2027. For any team that depends on a single paging tool, that date is a gentle reminder to keep the escalation process independent of the product that carries it.

Our experience in travel is the same. Booking platforms are replaced every few years, yet the discipline of confirming a passenger manifest, double-checking a handover and logging every exception endures regardless of software.

Trend five: regulation is climbing the agenda

Two European measures show up repeatedly in the entry. One is the digital resilience law already mentioned. The other, a network and information security directive, imposes staged reporting after a serious incident, beginning with a heads-up inside one day and ending with a written wrap-up roughly thirty days on. Whether or not your business falls into scope, customers increasingly ask how you would behave in a disruption. A written answer, with named owners and clock times, reassures high-value clients more than any brochure promise.

That matters in the premium segment, where expectations about discretion and responsiveness are high. A short incident plan, rehearsed twice a year, is cheaper than a lost client. If your passengers also use ground transfers, take a look at the reasons travellers book private cars to and from the airport, because that leg depends on timely systems too.

Trend six: the front desk is where trust is won

It is easy to focus on dashboards and forget that the service desk is the human face of the function. In charter work, the person who answers a late-night message from a client is the operator’s brand for that moment. The same holds in technology: a clear acknowledgement, an honest estimate and a follow-up when the work is done matter as much as the fix. The Atlas places the desk and the knowledge articles kept in the ticketing tool inside the core scope for exactly this reason. Teams that write down how they solved yesterday’s problem find that tomorrow’s version is resolved by whoever happens to be on shift, not only by the one veteran who remembers.

What has not changed

The anti-patterns the Atlas lists in 2026 would have been recognisable in 1999:

  • Heavy process forced on a small team with one service.
  • Identical treatment for every change.
  • New rules piled on after each failure.
  • Records of everything, when only decision-relevant facts are needed.
  • Service clocks whose pause rules nobody understands.
  • Monitoring that can fail silently.
  • Private spreadsheets in place of the shared record.

Every one of them has a charter-desk equivalent, and every one is cheaper to avoid than to repair.

A short story to close the loop

Imagine a small charter operator, entirely fictional, whose crew-paging tool silently stopped delivering messages one Friday evening. Nothing looked wrong on screens; no alarms rang because the alarm itself was the thing that had failed. The problem surfaced when a client called to ask why nobody had confirmed the Saturday morning departure. The fix that followed was modest: a scheduled test message every hour, a second channel as a back-up, and a Monday review that traced the cause to an expired credential. No new approval layer was added. That is what a mature response looks like in practice, and it is the quiet spirit of the discipline described in the Atlas.

For the human side of the same industry, from arrival procedures to passenger conduct, our guide to etiquette for first-time helicopter passengers is a pleasant companion read.

Where it goes next

Expect more automation in how work is routed, more pressure from regulators and a steady stream of tool changes. The teams that cope will be the ones that kept their records honest, their clocks understood and their alerting tested. Fashion in frameworks will keep moving; the habit of knowing what you run, who owns it and how you would learn it had failed will not go out of date.