The stale-spreadsheet problem every charter desk quietly lives with

Forty-one seconds: that's how long it takes villiersOS's compliance agent to run a live eligibility check against an operator's Air Operator Certificate, insurance certificate and safety rating before that operator's aircraft is even allowed to generate a quote. Most charter desks don't have anything close to that. They have a spreadsheet.

The spreadsheet is usually rebuilt once a year, often around renewal season for the broker's own professional indemnity cover, and it lists every approved operator alongside their AOC number, insurance expiry date and IS-BAO or ARGUS rating. It's a reasonable document on the day it's saved. The problem is what happens in the eleven months that follow.

An operator's Part-CAT or Part-135 certificate can be suspended after an incident. A hull and liability policy can lapse because a renewal payment was late by three days. An ARGUS Gold rating can be downgraded to nothing after a failed audit. None of that waits for the broker's annual review cycle, and none of it shows up on a spreadsheet until someone remembers to open the file and check.

The practical effect is that a broker quoting a Bombardier Global 6000 for a London to Nice sector next Tuesday is often working from data that describes the operator's status as of some point last year, not the operator's status right now. That sector typically prices between £18,000 and £24,000 one-way at current market rates, which is a meaningful sum to put behind an operator whose certificate nobody has actually checked since last spring.

This is the specific failure that charter operator compliance software is built to close, and it is worth being precise about what "closing it" actually means operationally, not just as a compliance slogan.

What the compliance agent actually checks: AOC status, insurance certificates, IS-BAO/ARGUS/Wyvern ratings, aircraft age

AOC status is the first gate, and it's narrower than it sounds: a certificate can be current in general and still invalid for the specific aircraft type or route being quoted, whether that's an EASA Part-CAT certificate for an Embraer Legacy 650 based in LSGG Geneva or an FAA Part 135 certificate for a Gulfstream G450 operating out of the United States.

The second check is insurance cover: verifying that hull and liability insurance is active, not just present in a file, and that liability limits meet the threshold Villiers sets for the aircraft category, typically $50 million for a midsize jet and higher for long-range types such as the Bombardier Global 7500.

The third is safety rating: confirming standing with the recognised third-party audit bodies, IS-BAO stage 2 or 3, ARGUS Gold or Platinum, or Wyvern Wingman, and flagging any operator whose most recent audit has lapsed past its renewal window rather than simply expired outright.

The fourth is aircraft age: cross-checking the specific tail against Villiers' age policy, which excludes most aircraft manufactured more than 25 years ago from premium client quotes regardless of the operator's rating, because an operator's certification says nothing about a 27-year-old airframe's maintenance history on its own.

None of these four checks is unusual in isolation. Any competent ops team asks all four questions. What's unusual is that villiersOS asks them at the moment a quote is requested, against live data, rather than against whatever answer was true when the spreadsheet was last updated.

Continuous revalidation vs the annual audit: why checking at quote-time instead of once a year changes the risk profile

An annual audit and a quote-time check are answering two different questions, and the difference matters more than it sounds. The annual audit asks whether an operator was eligible in principle. The quote-time check asks whether this specific operator, on this specific aircraft, is eligible right now.

Insurance renewal dates don't cluster neatly around a broker's audit calendar. Across Villiers' approved operator base, roughly a third of insurance policies renew in months that fall outside the broker's own annual review window, which means an annual audit can miss a lapse for up to eleven months before the next scheduled check catches it. A compliance agent that runs at quote-time doesn't have an eleven-month blind spot, because it doesn't have a fixed check date at all: every quote request is itself the check.

The same logic applies to safety ratings. IS-BAO stage 2 audits typically run on a 24-month cycle and ARGUS ratings are reviewed annually, but both organisations can suspend or downgrade a rating mid-cycle following an incident report or a failed spot inspection. An annual spreadsheet review inherits whatever rating was true on the day it was compiled. A quote-time check inherits whatever rating is true on the day of the flight.

The risk profile shift is straightforward: continuous revalidation converts operator compliance from a periodic snapshot into something closer to an always-current state. For a broker dispatching several hundred flights a year across dozens of operators, that's the difference between discovering an insurance lapse when a claim is filed and discovering it before the quote is ever sent.

Inside a failure: what happens when an operator drops out of eligibility between one request and the next

A client requests a quote for four passengers on a Cessna Citation Longitude between EGLF Farnborough and LFMD Cannes, and the operator holding that aircraft has an insurance certificate that lapsed nine days earlier because a renewal payment cleared late. That's the moment the mechanics actually matter, not the check itself.

The compliance agent flags the operator ineligible before the quote generation step runs, not after. The aircraft simply doesn't appear as an option in the quote the broker sees, which means no team member has to manually catch the lapse, and no client is ever shown a price built on an aircraft that shouldn't have been available.

The system then does two things in the same pass. It logs the ineligibility with a timestamped reason, in this case "insurance certificate lapsed", to an internal task queue that a human broker reviews, and it re-runs the same route request against the next eligible operator holding a comparable aircraft, so the client still receives a quote within the same response window rather than a delay or a dead end.

If the operator's certificate is restored, whether that's a renewed insurance policy or a reinstated AOC, the agent picks that up on the next check and the operator becomes eligible again automatically. Nobody has to remember to re-add them to a list, because there was never a static list to update in the first place.

The point of building it this way is that the failure is invisible to the client and cheap for the broker. Nobody has to manually intercept the operator, and nobody has to explain after the fact why an aircraft with a lapsed certificate was ever quoted. The mechanism that would have taken a human reviewer, at minimum, a phone call and twenty minutes to sort out on the old spreadsheet model runs in the same 41 seconds as the original check.

Why this layer, not the 90-second quote, is the part that makes agent-model dispatch defensible

Villiers can quote a charter request in under 90 seconds because the compliance layer sits underneath the quote engine, not alongside it as a separate manual step. That ordering is the entire business case. Speed without a live eligibility check is just a faster way to make the same mistake a slow desk could make; speed built on top of a continuous compliance check is a genuinely different product.

The margin argument is direct. A broker running manual operator vetting typically spends the equivalent of half a day of an operations coordinator's time per month reconciling insurance and rating data across a network of thirty to fifty operators. Automating that check doesn't just save the hours, it removes the specific error mode, a stale approval, that manual review is most prone to missing precisely because it only happens once.

The throughput argument follows from the same mechanics described above: an operator failing eligibility mid-request doesn't stall the pipeline, because the agent reroutes to the next eligible operator in the same pass rather than escalating to a human first. That's what makes it possible to scale quote volume without scaling the compliance headcount at the same rate.

The adjacent-sector case is where this gets interesting for anyone thinking about agent-model software beyond aviation. The architecture underneath charter operator compliance software, a live eligibility check that gates a transaction before it's allowed to proceed, generalises to any high-value, trust-dependent booking category where the seller's credentials can change faster than a periodic audit catches them. The same architecture could run against a yacht charter operator's flag-state certification and P&I insurance, a luxury property letting agent's landlord licensing and buildings cover, or a high-value vehicle rental firm's fleet insurance and roadworthiness certification. None of those sectors are ones villiersOS operates in today, but the underlying pattern, verify eligibility at the point of transaction rather than on an annual calendar, isn't specific to jets.

That's the part worth taking seriously about charter operator compliance software as a category: the quote speed is the visible feature, but the defensible one is the layer nobody sees, running a check in under a minute that used to take a spreadsheet, a memory, and a bit of luck.