The hidden operation beneath every flight
For most passengers, a flight begins at the gate. For an airline, however, some of the most consequential work takes place long before the doors close.
Outside the terminal window, often unnoticed, a complicated operation is unfolding.
Baggage must be identified, reconciled, sorted and loaded. Cargo has to be accepted, prepared and positioned correctly. Ground power may be connected. Potable water, catering, cleaning and lavatory services may be under way. Passenger stairs or boarding bridges have to be positioned. Aircraft doors and holds are opened and closed. Pushback equipment is prepared. Load-control information moves between operational teams. Dangerous goods, special loads and mobility equipment require particular handling. Staff move around an aircraft that may be surrounded simultaneously by belt loaders, dollies, tractors, buses, catering trucks, passenger stairs and other ground support equipment.
All this has to happen safely, often in less than an hour.
The ramp is therefore one of aviation’s most operationally dense environments. It combines human beings, heavy equipment, multimillion-dollar aircraft, strict departure schedules, multiple employers, different airline procedures, airport rules, regulatory requirements and frequently difficult weather conditions. IATA describes ground handling as integral to airline operations and notes that ramps are confined workplaces in which aircraft, ground support equipment and people are continually moving. IATA
That complexity explains why an apparently routine ground-handling error can have consequences that extend well beyond the apron.
Incorrect loading can affect aircraft weight and balance. Improperly restrained cargo can become a flight-safety hazard. A belt loader can strike a fuselage. Passenger stairs can damage an aircraft door. A baggage tractor can collide with equipment or personnel. Poor communication between load-control and ramp staff can introduce errors into the loading process. Inadequate training can turn a routine procedure into a safety event.
The financial consequences are also substantial. IATA currently estimates that, without preventive action, the annual cost of aircraft ground damage could approach $10 billion by 2035. Its recent ground-handling data continues to identify ground support equipment operations as one of the principal sources of aircraft ground damage.
Yet ground handling presents an unusual oversight problem.
An airline may serve scores or hundreds of airports. At each airport it might use a different Ground Handling Service Provider, or GHSP. The same handler may serve dozens of airlines, each arriving with its own manuals, audit schedules, operating variations, training requirements and oversight expectations.
For years, this created an inefficient pattern: airlines repeatedly auditing the same handler, while handlers repeatedly demonstrated essentially the same core safety controls to different customers.
The IATA Safety Audit for Ground Operations — ISAGO — was created to change that.
ISAGO’s proposition sounds straightforward: develop a credible, standardized, independent way of auditing ground handling operations so that airlines, handlers, airports and regulators can rely on a common baseline rather than continuously reinventing the same oversight process.
Nearly two decades after its creation, the program has become a substantial part of the international ground-operations safety architecture.
Its importance, however, is not simply that it produces an audit report.
ISAGO is increasingly about something more ambitious: reducing the operational differences between stations, aligning ground handlers with common industry manuals, strengthening Safety Management Systems, testing whether procedures actually work in the field, and creating a shared language through which airlines, airports, ground handlers and regulators can discuss ground-operational risk.
That evolution is central to understanding what ISAGO is today.
What exactly is ISAGO?
ISAGO stands for the IATA Safety Audit for Ground Operations.
IATA describes it as a global safety oversight program designed to improve the operational quality, consistency and safety performance of Ground Handling Service Providers. Its objectives include stronger management systems, standardized operational procedures, lower safety risk, reduced operational variation and fewer duplicate audits.
The key words are ground handling service providers.
ISAGO is not primarily an airline audit. IATA already has the IATA Operational Safety Audit, or IOSA, for airline operational management and control systems. ISAGO extends the concept of standardized safety oversight into the ground-handling environment.
The distinction matters because an aircraft’s safety chain does not begin when it leaves the ground.
The airline remains responsible for managing the safety of outsourced operations, but much of the work around an aircraft may be performed by contractors. ISAGO provides airlines with an independent source of information about whether those contractors have appropriate management systems and whether the procedures used at a station conform to applicable industry standards.
The program therefore sits at the intersection of four important functions: standardization, safety management, operational assurance and third-party oversight.
ISAGO does not simply ask whether a company possesses manuals. The modern audit methodology asks whether documented procedures conform to applicable standards and whether those procedures are actually implemented in everyday operations.
That difference between documentation and implementation is fundamental.
A beautifully written manual is of limited safety value if the people working beside the aircraft do something completely different.
Conversely, staff may have developed locally effective practices that are not properly documented, governed or consistently taught. That creates a different form of organizational risk.
The revamped ISAGO model deliberately examines both.
IATA’s March 2025 ISAGO Audit Handbook defines documentation assessment as auditor validation of a GHSP’s published gap analysis and operational documentation. Implementation assessment is the examination of operations through methods including direct observation, interviews and records review. IATA
That makes ISAGO less like a paperwork inspection and more like a test of whether a ground-handling organization functions as an integrated operational system.

Why aviation needed a ground-operations audit system
The origins of ISAGO lie in a problem that was already well understood by the mid-2000s.
Ground damage was expensive, operationally disruptive and potentially dangerous. At the same time, the industry’s oversight arrangements were fragmented.
IATA’s 2008 Annual Report records that work on what would become ISAGO began at the end of 2006. During 2007, the association developed an initial harmonized set of audit standards for ground handling companies and conducted 13 trial audits to test whether those standards could be audited effectively. Auditor training and preparation courses for ground handlers were developed in parallel. IATA
ISAGO was formally launched in February 2008.
The historical context was serious. IATA reported at the time that ground damage was costing aviation approximately $4 billion annually. Its 2009 annual reporting also noted that ground damage accounted for 17% of the previous year’s accidents involving western-built jet aircraft in the dataset then being discussed. The industry’s objective was therefore both financial and safety-related: reduce damage and injuries while removing unnecessary duplication from ground-service audits. IATA
The concept borrowed an important idea from IOSA.
Instead of every customer conducting completely separate assessments against different frameworks, the industry could create a globally recognized audit product based on common standards and standardized audit methods.
That principle was attractive to ground handlers for an obvious reason.
Imagine a handler serving 30 airlines at a major hub. Without some mechanism for audit recognition, the provider might face overlapping audits throughout the year. One airline could inspect passenger handling in January, another ramp operations in February, another training in March and yet another the same management system in April.
Each audit consumes employee hours. Managers must prepare documents and escort auditors. Training records are repeatedly extracted. Corrective-action teams answer similar questions. Operational personnel are interviewed repeatedly.
The problem is not that oversight is unnecessary.
It is that poorly coordinated oversight can become repetitive without becoming proportionately more effective.
ISAGO’s original promise was that one sufficiently robust audit could be accepted by multiple airlines.
That remains one of the program’s defining ideas.
From experiment to global program
ISAGO did not remain static after 2008.
Early implementation used what became known as an audit-pool model, drawing heavily on airline resources. As adoption increased, the model came under pressure.
The fourth edition of the ISAGO Program Manual explains that growing demand eventually exceeded what the established pool-member model could efficiently provide. A new operational audit model was introduced in September 2017, with audits under the revised framework beginning in 2018. IATA
That was a major transition.
The 2018 model moved toward independent professional auditors, a revised cost structure and an audit methodology that placed greater emphasis on implementation and on the relationship between a provider’s headquarters systems and its station network.
IATA’s 2019 Annual Review reported that the first audits under the transformed model were completed in 2018. It described a move away from volunteer auditors toward independent, professionally trained auditors and an increased focus on the implementation of standards and alignment between headquarters and stations. IATA
The next major transformation arrived in 2025.
In June of that year, IATA formally introduced another enhanced audit methodology aimed at deeper assessment of implementation, stronger standardization of procedures and training, and less operational variability across station networks. IATA
By 2026 the impact was visible in IATA’s own operating figures. The association reported that nearly 300 audits had been conducted during 2025 under the revamped methodology. In a May 2026 address, IATA said more than 230 GHSPs were participating across 441 accredited stations at more than 250 airports, with more than 200 airlines relying on ISAGO audit reports. IATA
Those figures reveal something important.
ISAGO is no longer simply an audit checklist that happens to be recognized internationally.
It is becoming part of a broader ecosystem consisting of standards manuals, digital gap-analysis platforms, professional auditors, data systems, registries, airline oversight, airport licensing considerations and regulatory recognition.
The architecture of the ISAGO program
ISAGO works at two organizational levels: headquarters and station.
That distinction reflects how large ground-handling companies actually operate.
A corporate or main headquarters may establish policy, governance, safety management, training standards, document control, risk-management processes and oversight arrangements for an entire network.
A station must then translate those systems into real operations.
The station is where passengers are checked in, bags are handled, ground support equipment is operated, aircraft are loaded, cargo is processed and weight-and-balance instructions are executed.
ISAGO therefore separates the question:
Does the organization have an effective system?
from the question:
Is that system actually functioning at this airport?
Under the current structure, the main headquarters audit covers Organization and Management and Training. Station audits can cover Organization and Management, Training and the operational disciplines applicable to the services performed at the location. These include Passenger Handling, Baggage Handling, Ramp Handling, Load Control and Cargo and Mail Handling. IATA
Operational scope is not simply chosen for convenience.
IATA’s Audit Handbook states that when a GHSP provides a service, that service must be included in the relevant audit scope; a provider cannot arbitrarily exclude areas of operation that it actually performs. IATA
That protects the audit from becoming an exercise in selecting only the easiest parts of an operation to demonstrate.
Registration begins with the organization’s headquarters framework. At least one station must also be accredited. Once findings have been satisfactorily closed, Headquarters Registration and Station Accreditation are granted for a 24-month validity period. IATA
The terminology is important.
IATA historically emphasized that ISAGO should not be confused with a conventional product or process certification scheme. The program instead awards Registration to the GHSP organization and Accreditation to applicable stations following successful completion of the audit process. The older Program Manual explicitly distinguished that recognition from traditional certification while emphasizing that the registration must be supported by a current audit report. IATA
In other words, ISAGO recognition is evidence of a successful independent audit against the program’s applicable requirements. It does not transfer responsibility for safety to IATA, nor does it replace the legal authority of a state regulator.
Who manages ISAGO?
IATA remains the program manager and custodian.
The ISAGO Program Manual assigns IATA responsibility for registration and station accreditation, allocation of audits, contracting audit-management support, auditor qualification, management of the Charter of Professional Auditors, program documentation, quality assurance, report distribution, program performance analysis and governance. IATA
The governance structure is designed to prevent ISAGO from functioning merely as a commercial audit service.
The program is maintained with input from the IATA Ground Operations Group, the Operations Advisory Committee and industry stakeholders. IATA’s management framework also requires defined accountability, quality-management processes, performance monitoring and periodic management review. IATA
Several actors therefore participate.
The GHSP owns the operational system being assessed.
IATA manages the program.
An ISAGO Agent, or GOA, coordinates audit administration and logistics.
Qualified ISAGO auditors conduct the assessments.
Airlines use the resulting reports as part of their own oversight systems.
Airports and regulators may use ISAGO as supporting evidence, a licensing requirement or, where formally recognized, an acceptable means of demonstrating compliance with specified requirements.
The architecture is therefore deliberately shared.
No single participant can produce the intended benefit alone.
A handler can undergo the audit, but audit duplication will continue if airlines refuse to recognize the result.
Airlines can subscribe to reports, but their benefit decreases if relevant providers are not in the program.
Airports and regulators can recognize ISAGO, but they still retain their statutory or contractual responsibilities.
The program works best as a network.
The professional auditor model
A standardized audit is only as credible as the people conducting it.
ISAGO audits are carried out by members of IATA’s Charter of Professional Auditors, known as CoPA.
According to IATA, these are the only auditors qualified to conduct ISAGO audits. Their qualification requires relevant education and experience, assessment, specific ISAGO auditor training and an evaluation audit. Membership is renewed subject to continued training, audit activity and performance assessment. IATA
That professionalization matters because ground operations require more than generic audit technique.
An auditor needs to understand what he or she is looking at.
Consider a load-control process. An auditor must know why load information matters, how instructions reach ramp staff, what evidence confirms reconciliation, which changes require control and how errors could affect the aircraft.
On a ramp, the auditor also needs to distinguish between harmless operational variation and a meaningful departure from a safety requirement.
The 2025 methodology raises that competency requirement further.
IATA’s current auditor training emphasizes assessing the operation as an integrated system. Auditors are trained to evaluate management systems, training governance, safety oversight, monitoring, communication and corrective action, while using evidence from observations, interviews, records and sampling. IATA
This reflects a broader development in aviation safety auditing.
The question is no longer simply, “Can you show me a procedure?”
It increasingly becomes, “Can you show that the procedure is understood, controlled, taught, monitored and consistently used?”
That is a harder question.
It is also a more useful one.
[PHOTO PLACEHOLDER]
Suggested image: Safety auditor interviewing ramp or operations personnel while observing aircraft handling.
Suggested caption: ISAGO auditors are members of IATA’s Charter of Professional Auditors and are expected to combine audit competence with practical ground-operations knowledge.
Suggested alt text: Aviation safety auditor observing ground handling procedures.
The standards beneath ISAGO
ISAGO cannot be understood without understanding the standards environment around it.
Historically, the program relied heavily on the ISAGO Standards Manual, known as the GOSM, and its GOSARPs.
That arrangement has changed.
The modern ISAGO program increasingly audits directly against provisions drawn from IATA’s primary industry manuals.
Three publications are now especially important: the Airport Handling Manual, the IATA Ground Operations Manual, and the IATA Cargo Handling Manual.
The Airport Handling Manual — AHM — is largely policy-oriented. IATA describes it as defining the “what to do” of ground handling. It includes industry-approved requirements covering areas such as management and safety, ground support equipment, ground handling agreements and training. IATA
The IATA Ground Operations Manual — IGOM — is more procedure-oriented. It addresses the “how to do” of frontline ground operations and seeks to reduce complexity created when multiple airlines, airports and ground handlers use different operating procedures. IATA
The IATA Cargo Handling Manual — ICHM — performs a similar standardization role across the cargo handling chain. It provides common operational procedures covering cargo processes from shipment preparation through carrier handling, flight movement and delivery. IATA
The current ISAGO model links audit disciplines directly to these standards.
Organization and Management draws primarily on AHM Chapter 6 provisions. Training draws on AHM 1110. Passenger handling corresponds with IGOM Chapter 1. Baggage is aligned with IGOM Chapter 2. Ramp handling draws on IGOM Chapters 3 and 4. Load Control is linked to IGOM Chapter 5. Cargo and Mail now use ICHM provisions. IATA
This is more than an editorial change.
It reduces the distance between the industry’s operating standards and the industry’s audit criteria.
A ground handler should no longer need one operating manual telling employees what to do and a separate ISAGO document reformulating much of the same requirement into audit language.
The strategic direction is increasingly:
industry standard → company procedure → documented gap analysis → independent audit → operational verification.
That chain is one of the most important developments in modern ISAGO.
GOSARPs: what they were and why they still matter
The acronym GOSARP is deeply embedded in the history of ISAGO.
The 2024 ISAGO Program Manual refers to GOSARPs as the program’s Standards and Recommended Practices contained in the ISAGO Standards Manual. Older audit systems assessed conformity directly against those numbered requirements. IATA
For many experienced ground-operations auditors and quality managers, “GOSARP” remains part of the working vocabulary.
But the terminology is being phased into a different model.
The March 2025 ISAGO Audit Handbook defines an audit provision as an individual requirement contained within the applicable industry standard and explicitly notes that these were previously referred to as GOSARPs. IATA
That sentence captures the transition particularly well.
Under the older architecture, ISAGO effectively maintained a dedicated standards layer.
Under the revamped architecture, ISAGO increasingly points directly to the operative IATA industry standards.
Why change?
Because duplicate standards create their own form of complexity.
If an IGOM procedure changes, a corresponding audit requirement may also need revision. If wording is duplicated across manuals, differences can emerge. Ground handlers then spend time reconciling the original operating requirement with the audit version of the same requirement.
Direct alignment reduces that problem.
It also changes the meaning of preparation.
A GHSP should not “prepare for ISAGO” by creating documents that exist only to satisfy an auditor.
It should operate according to the applicable industry standards, understand and control genuine variations, and use the audit as independent verification that the system functions as designed.
That is a more mature approach.
The audit becomes a test of the operation rather than the reason the operation was documented.
There is one remaining historical wrinkle in cargo.
During the 2025 transition, Cargo and Mail Handling still used the GOSM cargo module. IATA’s current checklist information states that ICHM replaced the CGM module beginning in 2026. IATA
One IATA preparation note refers to the replacement taking effect from 1 March 2026, while other current IATA material describes the ICHM change as effective from January 2026. The practical lesson for a GHSP is straightforward: audit preparation should always use the exact current checklist, effective standards and instructions assigned in the organization’s live ISAGO/OPS Portal environment rather than relying on an older downloaded timetable. IATA
That is particularly important during standards transitions.
Compliance with industry standards
The word “compliance” can be deceptively simple.
In aviation, compliance is not achieved merely because a procedure contains familiar language.
The redesigned ISAGO methodology distinguishes between the industry’s requirement, the GHSP’s documented implementation of that requirement and evidence that employees consistently perform the work accordingly.
That sequence matters.
Take aircraft turnaround safety as an example.
An industry standard may require a particular control.
The GHSP must first determine how that requirement applies to its operations.
It must then establish an appropriate company procedure.
That procedure may need to be communicated through manuals, training materials or work instructions.
Personnel must be trained.
Supervisors must understand their responsibilities.
Records may need to demonstrate that training, checks or controls occurred.
The procedure then has to survive contact with operational reality.
Does the morning shift do it?
Does the night shift?
Does a new employee do it?
Does the station still do it when an aircraft is late and the turnaround is under pressure?
Does a subcontractor do it?
What happens when a local airport rule differs?
How is the variation documented?
How does headquarters know whether stations are complying?
That is what implementation auditing is trying to expose.
It is the difference between a requirement existing and a control functioning.
IATA’s broader ground-operations standardization program argues that common standards can improve safety, simplify training, reduce operational variation and reduce oversight complexity. IATA
ISAGO is effectively the assurance mechanism attached to that philosophy.
Variations: where standardization meets reality
No global ground-operations standard can assume that every airport is identical.
Airport infrastructure varies.
Aircraft fleets vary.
National regulations vary.
Climatic conditions vary.
Airline contracts vary.
Technology varies.
Some stations use automated systems that others do not have.
Certain airports impose procedures that are more restrictive than the industry baseline.
Standardization therefore cannot mean pretending that local realities do not exist.
The revamped ISAGO methodology instead makes variations visible.
The GHSP conducts a gap analysis against applicable industry requirements and records whether its procedure conforms, differs or falls outside scope.
The concept is important because a variation is not automatically unsafe.
IATA’s 2025 Audit Handbook defines variations broadly enough to include requirements that are more restrictive, less restrictive or simply different from the published industry benchmark. IATA
This creates a more intelligent conversation than demanding identical wording.
A locally enhanced control may be safer than the baseline.
A different sequence may be required by airport infrastructure.
A national rule may supersede an industry procedure.
What matters is whether the variation is deliberate, understood, documented and safe.
IATA’s 2026 ground-operations analysis gives an interesting indication of how this works in practice. The association reported that 60% of declared variations it examined reflected differences in wording rather than substantive operational departures, and that many variations actually exceeded the IGOM baseline. IATA
That suggests standardization has two dimensions.
One is making genuinely different practices more consistent.
The other is identifying situations where organizations are already doing essentially the same thing but describing it differently.
Both matter because excessive variation makes training, contracting and airline oversight more difficult.
How the modern ISAGO audit works
The current methodology can be understood as four connected stages.
The first is the GHSP’s gap analysis.
The second is the independent Documentation Assessment.
The third is the Implementation Assessment.
The fourth is corrective action and closure.
IATA’s March 2025 Audit Handbook formally describes the audit in those four stages. IATA
The gap analysis begins with the provider.
The GHSP compares its organization and station procedures against the standards applicable to its scope of operations. It records documentary references and identifies conformity, variations and items that genuinely do not apply.
This reverses an outdated audit mentality.
Instead of waiting for an auditor to discover what the organization does, the GHSP must understand its own system before the external audit begins.
The auditor then performs the Documentation Assessment.
This stage validates whether the provider’s written policies, processes and procedures adequately address the applicable standards.
Crucially, much of this assessment can now happen remotely.
IATA moved documentation work into the OPS Portal and introduced sampling to streamline verification. IATA
Then comes Implementation Assessment.
This is where the paper system meets the actual operation.
The auditor observes work, interviews personnel, reviews records and uses other evidence where direct observation is not feasible.
The 2025 Audit Handbook is particularly clear on this point: while sampling is used during documentation assessment, the implementation assessment is intended to verify the procedures within the relevant operational scope rather than simply relying on a documentation sample. IATA
Finally, nonconformities require corrective action.
The provider must address deficiencies, establish corrective actions and provide evidence sufficient for closure.
ISAGO Registration or Station Accreditation is not granted or maintained simply because the audit visit is over.
Findings must be closed.
That is why a useful internal slogan for ISAGO preparation might be:
Know the standard. Map the procedure. Prove the implementation. Fix the weakness.
[PHOTO PLACEHOLDER]
Suggested image: Split visual showing an operations manual or tablet on one side and an aircraft turnaround on the other.
Suggested caption: ISAGO now separates documentation assessment from implementation assessment, asking both whether the procedure is compliant and whether it is actually being followed.
Suggested alt text: Ground handling manual and live ramp operation representing documentation and implementation audits.
Headquarters versus station: two different audit questions
The distinction between headquarters and station auditing deserves closer attention.
A headquarters is typically responsible for systems whose results may not be directly visible during a short visit.
Management review, internal oversight, safety policy, document control, competence frameworks, organizational accountability and change-management processes do not necessarily produce an observable event every few minutes.
They produce evidence over time.
That is why records, governance documents, management reports and system evidence become particularly important at headquarters.
The station is different.
Passenger processing happens continuously.
Bags move continuously.
Aircraft arrive and depart.
Ground support equipment is driven.
Loading occurs.
Operational communication can be heard.
Training should be visible through employee behavior.
Supervision can be observed.
A station audit therefore offers an opportunity to see whether corporate systems have survived the journey from headquarters to the ramp.
This is one of ISAGO’s strongest structural features.
Many organizational failures occur precisely at that interface.
Headquarters may publish a technically perfect policy while a station manager has never seen it.
A station may develop an effective workaround that corporate management does not know exists.
Training records may indicate completion while employees demonstrate poor understanding.
A corporate safety-management process may exist but receive little usable reporting from individual stations.
ISAGO connects those layers.
The audit is asking whether an organization is truly a system rather than a collection of independent airport operations carrying the same logo.
The ISAGO Registry
Audit standardization becomes far more useful when the resulting information can be shared.
That is the role of the ISAGO Registry.
Historically, the registry existed within IATA’s dedicated ISAGO systems. It has since moved to IATA’s ONE Source environment.
The public-facing registry allows users to determine which GHSPs and stations hold ISAGO status, while detailed audit reports remain restricted to participating ISAGO member airlines. IATA
That distinction balances transparency and confidentiality.
An airport, customer or industry participant can verify that a provider or station is included in the program.
An airline subscribing to ISAGO can access considerably more detailed audit information for oversight purposes.
Ground handlers can maintain information about their own networks.
The registry is therefore not just a badge directory.
Its real value lies in audit re-use.
An airline considering a GHSP at a particular airport can determine whether an applicable ISAGO report already exists.
The airline can then use that report as part of its risk-based oversight rather than automatically commissioning a new audit covering the same ground.
That does not necessarily mean the airline abandons all local oversight.
It means the airline can use its resources more intelligently.
Perhaps an ISAGO report sufficiently covers management systems and core operations, allowing the airline to concentrate its own resources on airline-specific differences, contractual performance, unusual risk factors or areas outside the ISAGO scope.
That is the practical meaning of audit reduction.
It should not mean “less safety.”
It should mean less duplication and more targeted oversight.
The public numbers illustrate the registry’s scale, although IATA’s various public pages are not always updated on exactly the same date. The current program page describes more than 230 registered GHSPs and more than 430 accredited stations. IATA’s May 2026 conference reporting gave the more specific figure of 441 stations at more than 250 airports, with more than 200 airlines relying on audit reports. IATA
The difference is best understood as a timing difference between public datasets rather than a contradiction in the basic direction of the program.
The economics of avoiding duplicate audits
The most measurable benefit of a shared audit system may be the audit that never has to take place.
IATA has begun publishing data showing how airlines use ISAGO reports to reduce duplicated oversight.
In figures reported from 21 airline groups during 2024, IATA recorded 446 airline audits cancelled because ISAGO information was available. Those airlines reported reduced oversight costs at 110 stations and fewer auditor-days at 335 stations. ISAGO reports were also used in procurement decisions at 271 stations and to complement airline Safety Management Systems at 396 stations. IATA
Those figures should be interpreted carefully.
They are program data supplied through IATA rather than an independent global economic study, and they do not imply that every ISAGO report will eliminate an airline audit.
But they demonstrate the mechanism.
Consider the cost structure of a traditional onsite audit.
The airline may pay for auditor travel, accommodation and working time.
The ground handler assigns managers and operational personnel.
Documents are prepared.
Interviews interrupt normal work.
Follow-up actions consume additional resources.
Multiply that by numerous airlines auditing the same provider and the inefficiency becomes obvious.
A common audit product creates the possibility of mutual reliance.
The resources saved can then be redirected toward higher-risk activities.
In safety management terms, that is potentially more valuable than repeatedly asking the same questions at the same station.
How a GHSP should prepare for an ISAGO audit
The worst way to prepare for ISAGO is to wait until the audit date is approaching and then begin “creating evidence.”
That approach usually exposes a deeper problem.
A mature ISAGO preparation process should start with the operating system itself.
IATA’s formal onboarding process now involves several digital environments.
A new GHSP creates or uses an IATA Customer Portal account, obtains ONE Source access, creates station accounts, requests the initial headquarters and station audits, completes the organization’s profile within IATA Connect, signs the required agreement and coordinates scheduling through an assigned ISAGO Agent. In parallel, the provider joins the OPS Portal and completes its gap analysis against the applicable standards. IATA
Administratively, that gets the organization into the program.
Operationally, much more work is required.
The provider needs a clear inventory of what it actually does.
Which stations are included?
Which airline customers are served?
Which services are performed directly?
Which are subcontracted?
Who controls training?
Where are manuals maintained?
Which processes are centralized?
Which are local?
Which operational standards apply?
Where are variations used?
Who owns those variations?
How are document changes communicated?
How are hazards reported?
How are risks assessed?
How does management know whether corrective actions are effective?
These are not “audit questions” in the narrow sense.
They are management questions.
A strong GHSP should then conduct an honest gap analysis.
The temptation during self-assessment is to declare conformity too easily.
For example, a company procedure might resemble an IGOM requirement but omit one essential control.
Or the procedure may be correct, but a related form is outdated.
Or headquarters may have a compliant manual while the station uses a local work instruction that conflicts with it.
These discrepancies are precisely what the gap analysis should expose before the auditor arrives.
The OPS Portal is designed for this purpose. IATA describes it as a centralized platform through which airlines and GHSPs can conduct gap assessments, declare the relationship between their operational documentation and industry standards, and share operational information. IATA
A GHSP with multiple stations can also clone gap analyses across its network and modify them where local differences exist.
That function is more important than it sounds.
A network handler should not have to remap identical corporate procedures separately at every station.
At the same time, cloning must not become an excuse to overlook genuine local variation.
The organization needs to distinguish:
what is truly standardized across the network,
what is centrally controlled but locally implemented,
and what is genuinely station-specific.
That distinction is likely to tell an auditor a great deal about the maturity of the organization.
Preparing the documentation
Documentation preparation should be based on traceability.
For each applicable provision, the organization should be able to identify where the requirement is addressed.
That reference needs to be precise enough that another person can find the evidence.
“Operations Manual” is not an adequate documentary reference if the manual contains hundreds of pages.
A stronger reference points to the relevant controlled chapter, section, procedure, revision or record.
More importantly, the referenced document must say what the organization claims it says.
A common audit weakness is documentary mapping that appears complete in a spreadsheet but collapses once someone opens the actual procedure.
Preparation should therefore involve a second-person review.
Someone who did not create the gap analysis should select references and verify them independently.
The company should also examine document control.
Are personnel using the current revision?
Are obsolete documents removed?
Are locally produced forms controlled?
Are airline-specific instructions identified?
Are electronic manuals available to the people who need them?
Can staff find the procedure quickly?
How does the organization communicate urgent operational changes?
A procedure is not truly controlled merely because it sits in a quality manager’s office.
It has to reach the operating environment.
Preparing training and competence evidence
Training deserves special attention because it connects written standards to human performance.
AHM training requirements now form a direct part of the ISAGO standards environment.
IATA’s AHM framework addresses minimum training requirements and competence for personnel performing ground-operational functions, while the revamped ISAGO approach assesses whether training governance supports actual operational readiness. IATA
A GHSP preparing for audit should therefore look beyond training certificates.
The deeper questions are whether employees were trained for the functions they perform, whether qualifications remain current, whether instructors and assessors are properly managed, whether recurrent training occurs when required, and whether changes in procedures trigger appropriate training or communication.
Auditors may also compare records against operational behavior.
If every employee supposedly passed training but the same procedure is being misunderstood across the station, the issue is not simply an individual mistake.
It may indicate a training-system weakness.
This is where modern audits become systemic.
The finding is no longer necessarily “Employee A did something wrong.”
The relevant question may become “Why did the organizational system allow multiple employees to understand this process incorrectly?”
That shift toward root causes is one of the characteristics of mature safety assurance.
Preparing the station for implementation assessment
No amount of document review can substitute for looking at the operation.
Before an ISAGO station audit, managers should therefore perform their own field verification.
Walk the ramp.
Watch aircraft arrival.
Observe chocking.
Observe equipment positioning.
Watch baggage operations.
Follow turnaround communication.
Inspect load-control interfaces.
Check passenger processes.
Visit cargo operations where applicable.
Observe how supervisors intervene.
Look at personal protective equipment.
Review how equipment defects are handled.
Observe what happens during a disrupted operation.
Then compare what employees actually do with what the manuals say they should do.
This exercise should not be treated as a rehearsal in which everyone is told to behave differently because an auditor is coming.
That defeats the purpose.
The goal is to identify the normal operating reality early enough to correct genuine weaknesses.
Management should also expect the auditor to interview staff.
Personnel should understand their jobs, but they should not be coached to recite scripted answers.
A useful auditor is interested in understanding the system.
Over-rehearsed employees can actually make that more difficult.
The strongest audit preparation is therefore boringly straightforward:
build a compliant system,
run it every day,
check it yourself,
correct problems,
maintain evidence.
Then the audit becomes verification rather than theatre.
[PHOTO PLACEHOLDER]
Suggested image: Ramp supervisor conducting a pre-turnaround briefing with a small ground team.
Suggested caption: Effective ISAGO preparation is operational rather than cosmetic: staff competence, supervision and routine implementation matter as much as documentation.
Suggested alt text: Ground handling employees attending an operational safety briefing.
Safety Management Systems and ISAGO
One of the most consequential elements of ISAGO is its relationship with Safety Management Systems.
Safety Management System — SMS — is sometimes misunderstood as an incident-reporting program.
It is much broader.
An effective SMS creates structured processes through which an organization identifies hazards, assesses risk, introduces controls, monitors safety performance and improves its systems.
ICAO consolidated global safety-management requirements in Annex 19, while its Manual on Ground Handling, Doc 10121, links ground-handling activity to broader system safety and provides guidance to states, aerodrome operators, airlines and ground handlers. ICAO describes the manual as connecting ground handling with SMS principles and assisting states in incorporating ground handling into State Safety Programmes. ICAO Store
ISAGO incorporates independent assessment of GHSP safety-management arrangements aligned with ICAO Annex 19 principles. IATA
That is important because ground handlers have historically occupied an unusual regulatory position in some jurisdictions.
Airlines, aerodromes and maintenance organizations have long operated within highly developed aviation regulatory frameworks.
Ground handling regulation has not always been equally uniform internationally.
ISAGO can therefore provide a structured safety-management baseline even where national ground-handling oversight is less prescriptive.
This does not make an industry audit a substitute for law.
It gives regulators and airports an additional instrument.
ISAGO for airports and regulators
ISAGO’s value is not restricted to airlines and GHSPs.
Airports have their own reasons to care about the quality of ground handling.
A ground-handling incident can close a stand, delay an aircraft, damage airport infrastructure, injure personnel and disrupt connecting operations.
Poor performance by one handler can affect airlines that have no contractual relationship with that handler.
The airport therefore has a system-level interest.
Regulators have an even broader concern.
Where ground handling is regulated, the authority needs evidence that service providers meet applicable safety requirements.
Where it is less directly regulated, authorities may still need a framework through which ground-operation risks are incorporated into national safety oversight.
IATA promotes ISAGO to both groups.
Its current program material states that airports and regulators may use ISAGO information to complement their own performance and compliance data, reduce the scope or frequency of duplicated oversight, support licensing schemes and — where a competent authority formally determines it appropriate — function as an Acceptable Means of Compliance, or AMC. IATA
The phrase “acceptable means of compliance” deserves emphasis.
AMC does not normally mean that an industry organization writes the law.
It means an authority recognizes a specified method as an acceptable way of demonstrating that a requirement has been met.
The regulator remains the regulator.
The airport remains responsible for its licensing and contractual decisions.
But ISAGO can become one piece of the evidence framework.
IATA has pursued formal Memoranda of Understanding with civil aviation authorities and airport organizations for that reason.
Its 2026 safety-audits fact sheet reported that 47 CAAs or airport authorities had recognized ISAGO through MoUs or similar instruments in the program data then being reported. IATA
One concrete example comes from Mauritania.
In 2023, IATA and Afroport Mauritanie announced an agreement under which the airport organization would promote IGOM, recognize ISAGO as an acceptable means of compliance for airport oversight and make ISAGO Registration and Station Accreditation a condition for ground handlers operating at the airport. Aviation Week
Kazakhstan provides another example of regulatory engagement: IATA reported that the country’s Civil Aviation Committee signed an MoU covering IOSA and ISAGO in December 2023. IATA
These examples reveal the direction of travel.
ISAGO is gradually moving from a purely airline-ground-handler relationship toward a broader oversight ecosystem.
Why ICAO Doc 10121 matters
ICAO’s Manual on Ground Handling, Doc 10121, is an important part of the international context.
The first edition was published in 2019.
ICAO describes ground handling as an integral part of the aviation system that directly affects flight and aerodrome safety. The manual provides guidance for stakeholders whose ground-handling activities may affect operational safety and specifically links those operations with safety-management principles. ICAO Store
For ISAGO, this matters in two ways.
First, it gives global institutional recognition to the principle that ground handling is not simply a commercial service.
It is part of aviation safety.
Second, it creates a bridge between state-level safety responsibility and industry-developed operational systems.
IATA states that ISAGO standards align with the relevant GHSP provisions in Doc 10121 and positions ISAGO as a possible mechanism to support regulatory oversight. IATA
This is particularly significant as regulatory attention to ground handling increases.
The long-term question is no longer whether ground handling deserves structured safety oversight.
The discussion increasingly concerns how that oversight can be achieved without producing several overlapping audit systems examining the same provider against slightly different requirements.
Global standards plus recognized common audits offer one possible answer.
The 2025 audit-method revolution
The most significant recent change to ISAGO was not the addition of another requirement.
It was a redesign of how the audit is conducted.
By mid-2025, IATA had introduced a model built around remote document assessment, standardized gap analysis, greater use of the OPS Portal, enhanced checklists tied directly to industry standards, more concentrated onsite implementation assessment and, in appropriate circumstances, single-auditor audits.
When previewing the model in May 2025, IATA described the changes as including single-auditor audits, remote documentation checks, stronger implementation focus, checklists mirroring AHM and IGOM, and reduced audit fees. IATA
That represents a philosophical change.
Traditional audits can waste onsite time reviewing documents that could have been examined weeks earlier from anywhere in the world.
An auditor sitting in a hotel meeting room reading manuals is not observing the ramp.
Moving appropriate document assessment offsite allows onsite time to be concentrated on activities that genuinely require physical presence.
That should include operational observation, interviews, equipment checks and verification of station-level implementation.
It also allows documentary weaknesses to be identified before the auditor travels.
The provider has greater visibility of what documentation is being assessed.
The auditor arrives with a more developed understanding of the operation.
The onsite phase can therefore become more investigative and less administrative.
That is the theory.
Its success depends heavily on disciplined digital preparation and good-quality gap analysis.
If a provider uploads inaccurate references or incomplete information, remote assessment does not magically create efficiency.
Digitalization only improves the process if the data supplied is reliable.
Sampling documentation without sampling away safety
The use of sampling sometimes creates concern because it can sound like “checking less.”
That interpretation misses the purpose of audit sampling.
The modern ISAGO methodology uses sampling during Documentation Assessment to verify the accuracy of the provider’s self-assessment efficiently.
The 2025 Audit Handbook states that ISAGO applies a sampling methodology to documentation assessment while implementation assessment uses direct operational verification and alternative evidence across the relevant scope. IATA
The concept is comparable to quality assurance elsewhere.
If an organization has hundreds of mapped requirements, an auditor can select a statistically meaningful sample to determine whether the provider’s mapping process is reliable.
If significant errors appear, confidence in the wider self-assessment declines.
The audit can then respond accordingly.
The point is not to replace judgement with arithmetic.
It is to direct auditing effort toward the evidence with the greatest assurance value.
This reflects a broader trend in aviation auditing: move away from mechanical checklist completion and toward evidence-based assessment of how a management system performs.
The OPS Portal and the digitalization of assurance
ISAGO’s transformation is as much technological as methodological.
The OPS Portal — formerly centered primarily around IGOM gap analysis — now accommodates a wider range of operational standards and allows airlines and GHSPs to record their relationship with those standards in a common environment.
The current platform includes IGOM, relevant AHM requirements and ICHM-related content. It supports self-assessment and the declaration of documentary compliance or variation. IATA
This creates possibilities that would have been difficult with spreadsheets circulated by email.
A multinational GHSP can establish a core gap analysis.
Stations can reuse that framework.
Local variations can be identified.
Auditors can review documentation remotely.
Data can be analyzed across stations.
Recurring differences can potentially be identified at network level.
This matters because the greatest safety value may eventually come not from an individual audit finding but from patterns.
Suppose the same loading-process variation appears across 20 stations.
That may indicate a corporate procedure that needs clarification.
Suppose several handlers report difficulty interpreting the same IGOM provision.
That may indicate an industry standard requiring improvement.
Suppose a particular discipline produces recurring findings internationally.
That can help direct training, standard development and safety initiatives.
The digital audit system therefore has the potential to turn ISAGO from a collection of reports into an industry learning mechanism.
IATA Connect and ONE Source: a more connected program
Two additional platforms support the modernization.
ONE Source now houses the ISAGO Registry environment.
IATA Connect provides organizational profiles and collaboration functions.
IATA’s 2026 safety-program documentation states that ISAGO was onboarded to IATA Connect in 2025, allowing ground-service providers to create profiles and manage partner relationships through the platform. IATA
A GHSP profile can contain business and operational information, customer relationships, fleet information and audit-related history.
This may seem administrative, but accurate provider data is critical to a network oversight program.
An audit system cannot allocate the correct scope if it does not know what services a provider performs.
An airline cannot efficiently use shared oversight if station and service information is unreliable.
A regulator cannot rely on registry information if the organization profile is obsolete.
Digital account management therefore supports something very basic: knowing who operates where, doing what, for whom, and under what audit status.
That is the information infrastructure beneath effective oversight.
Simplifying ISAGO program management
Audit methodology was not the only target of the recent overhaul.
IATA also identified the administrative burden surrounding the program.
Its modernization plan included simplifying contracting and payment, introducing online GHSP account management, creating customer-relationship management tools for inquiries, developing mobile audit functionality, providing more interactive audit information and revamping program documentation. IATA
The problem is familiar to anyone working with large assurance systems.
A program can have good standards but still frustrate participants through fragmented administration.
Separate spreadsheets, emails, invoices, portals, audit tools and document exchanges create hidden cost.
Users spend time figuring out the process instead of improving safety.
The direction of ISAGO’s simplification program is therefore toward a more integrated customer journey.
A GHSP should eventually be able to manage its profile, track audit status, maintain gap analyses, communicate with the program, access relevant outputs and follow corrective actions without stitching together multiple disconnected systems.
Auditors likewise benefit when assessment information can be captured efficiently in the operating environment.
IATA had previously described a future mobile audit application so that auditors could enter assessment information directly rather than waiting to return to a laptop and internet connection. IATA
The underlying principle is sensible:
administrative friction should not consume resources intended for safety assurance.
ISAGO does not eliminate airline responsibility
The promise of audit reduction can be misunderstood.
An airline cannot outsource its accountability merely because its handler appears in the ISAGO Registry.
ISAGO is an input to oversight, not a replacement for management responsibility.
Every airline operates a particular network, aircraft fleet and commercial model.
It may have procedures beyond the industry baseline.
Its contract may assign responsibilities differently.
Its risk profile may justify additional monitoring.
A provider may perform well overall but have a localized performance issue affecting one airline.
ISAGO therefore works best when incorporated into a risk-based airline oversight program.
The airline can use the report to avoid repeating generic assurance work while concentrating its own monitoring on airline-specific requirements, performance indicators, contractual controls and emerging local risks.
IATA itself describes ISAGO reports as complementary information for airline oversight and as an additional control supporting Safety Management Systems for outsourced ground operations. IATA
That language — complementary — is important.
Good audit reduction is selective.
Bad audit reduction is blind.
Safety beyond compliance
A compliant organization can still have an incident.
No audit system can guarantee otherwise.
That fact does not make auditing irrelevant.
It clarifies what an audit can realistically achieve.
ISAGO tests whether core organizational defenses exist and are working.
Those defenses include competent personnel, clear procedures, risk controls, supervision, effective communication, equipment management, internal oversight and corrective action.
Each layer reduces the likelihood that a single human mistake becomes an accident.
This is particularly important in ground handling because individual errors often occur in dynamic conditions.
A ramp worker may be tired.
A departure may be late.
Weather may deteriorate.
Equipment may fail.
A gate change may compress preparation time.
A new employee may misunderstand an instruction.
A robust system is designed on the assumption that human beings will sometimes make mistakes.
Its job is to prevent those mistakes from aligning catastrophically.
That is why safety management and standardization matter more than simply demanding perfect individual performance.
The connection with ground support equipment
Ground support equipment illustrates how ISAGO can interact with a broader safety initiative.
IATA’s research identifies GSE as a major source of aircraft ground damage and has promoted “Enhanced GSE” incorporating technologies such as anti-collision systems and improved low-speed control.
The association estimates that moving 75% of the relevant global fleet toward Enhanced GSE could reduce expected ground-damage cost per turn by approximately 42%. IATA
IATA began integrating the Enhanced GSE Recognition Program with ISAGO station activity.
From April 2025, GSE fleet declarations became mandatory at ISAGO stations, according to IATA’s ground-handling conference material. IATA
That is an example of ISAGO acting as an implementation channel.
Instead of creating a completely separate safety universe for every new initiative, industry programs can connect them to an established assurance framework.
Over time, this could make ISAGO increasingly valuable as a vehicle for translating new ground-safety knowledge into standardized operational practice.

Standardized training: one of the less visible benefits
One of the industry’s persistent costs is repeated training.
A handler may serve many airlines, each with slightly different procedures.
Employees can consequently receive several versions of training for tasks that are fundamentally similar.
This creates expense and cognitive complexity.
Global operating standards attempt to establish a common baseline.
IATA’s argument is that broader implementation of AHM training standards and IGOM operational procedures can reduce unnecessary duplication while improving recognition of employee competence.
In 2026, IATA estimated that greater adoption of common AHM-based ground-handling training requirements could unlock approximately $83.5 million in annual industry savings. IATA
Again, that should not be interpreted as eliminating necessary airline-specific training.
Differences will remain.
Aircraft types differ.
Systems differ.
Commercial processes differ.
National regulations differ.
But the number of unnecessary differences can be reduced.
ISAGO supports that objective by testing whether the organization’s training system aligns with the common baseline and whether those trained procedures are actually implemented.
Standardization is therefore not merely a manuals project.
It is a workforce project.
The operational benefits for a GHSP
Why should a ground handler voluntarily expose itself to a demanding independent audit?
The first answer is market access.
Some airline customers consider ISAGO status when selecting or overseeing providers.
Some airports and regulators recognize or require ISAGO in their local oversight arrangements.
Registration can therefore have commercial value.
But the stronger long-term argument is internal.
A well-prepared ISAGO program forces an organization to map itself.
Management has to understand which standards apply.
Corporate policy has to connect with station procedures.
Training responsibilities have to be clear.
Variations become visible.
Subcontracted functions must be controlled.
Internal assurance becomes easier to structure.
Corrective actions require ownership.
For a large GHSP, that discipline can be more valuable than the external badge.
The audit may reveal inconsistency that had become normalized.
One station may be using an obsolete procedure.
Another may have developed an undocumented variation.
A recurrent problem may have been repeatedly treated as a local employee issue even though the real cause sits in a corporate process.
The audit provides a reason to connect those dots.
This is why the best organizations should treat findings as data rather than embarrassment.
A finding is useful when it identifies a weakness before that weakness produces a serious event.
The benefits for airlines
For airlines, ISAGO offers three principal forms of value.
The first is independent assurance.
An airline can obtain information produced by auditors who are not the ground handler’s internal quality staff and are not simply the airline’s own commercial representatives.
The second is standardization.
When multiple handlers are measured against the same baseline, oversight becomes easier to compare.
The third is efficiency.
Airlines can use existing reports to reduce repetitive audits and focus their own resources on the risks unique to their operation.
There is also an SMS benefit.
Outsourced activities remain part of an airline’s risk landscape.
ISAGO reports can contribute evidence to the airline’s assessment of contracted ground operations.
The 2024 usage data published by IATA shows that participating airlines were already using reports not only to cancel duplicated audits but also for procurement and Safety Management System purposes. IATA
That is arguably more significant than audit reduction alone.
It means the audit report is becoming an operational decision-making input.
The benefits for airports
Airports benefit from standardization because the apron is a shared environment.
One poorly managed operator can create risk for everyone.
A collision does not remain neatly inside a commercial contract.
An aircraft damaged on stand may delay a gate.
A disabled piece of equipment can obstruct a service road.
An unsafe driving culture affects other airport users.
A spill or cargo event may trigger emergency response.
Standardizing GHSP management and operational practices therefore supports the airport’s own safety objectives.
ISAGO can also strengthen licensing.
Instead of an airport inventing an entirely separate technical audit system, it may use ISAGO status as part of the evidence required from ground handlers, while maintaining oversight of airport-specific requirements.
This can be particularly attractive at airports with many operators.
The airport retains control over access to its infrastructure while benefiting from a global ground-handling assessment framework.
The benefits for regulators
A civil aviation authority faces a different challenge.
Its responsibility is not merely commercial efficiency.
It must establish adequate oversight of aviation safety.
Ground handling historically varies significantly in how directly it is regulated from one jurisdiction to another.
ICAO’s Doc 10121 has encouraged a more structured approach to incorporating ground handling into national safety systems. ICAO Store
ISAGO offers regulators an established source of industry assurance.
A regulator may use it to complement inspections.
It may recognize it within a licensing framework.
It may use the reports indirectly through airlines.
Or it may formally define ISAGO as one accepted way of meeting particular requirements.
The benefit is potential harmonization.
If every state designs a completely different GHSP audit model, a global handling company will again face the duplication ISAGO was created to reduce.
The regulatory challenge is therefore to preserve sovereign oversight while making sensible use of credible industry systems.
That is why IATA continues to advocate formal recognition rather than simply assuming an industry audit has legal authority everywhere.
The benefits for frontline staff
The least discussed beneficiaries may be the people actually working on the ground.
Standardized procedures reduce ambiguity.
Better training improves confidence.
Clearer supervision reduces conflicting instructions.
Strong equipment-management systems reduce exposure to defective GSE.
Effective hazard reporting gives workers a mechanism to identify unsafe conditions.
A functioning SMS should enable lessons from incidents and near misses to be translated into preventive controls.
Standardization also improves mobility.
An employee moving between stations or employers should not have to completely relearn a universal task simply because every organization developed an entirely different method.
Some local and airline differences will always remain.
The objective is to distinguish necessary differences from inherited complexity.
For a workforce operating under considerable time pressure, simplicity can itself be a safety control.
What ISAGO cannot do
A credible examination of ISAGO also needs to recognize its limits.
An audit is a snapshot.
A station may pass an audit and later deteriorate.
Managers can change.
Staff turnover can accelerate.
Equipment fleets can age.
Training can lapse.
Commercial pressure can increase.
An airline contract can change operating responsibilities.
New hazards can emerge.
A two-year recognition cycle therefore cannot substitute for continuous internal assurance.
Second, standardized requirements cannot anticipate every local hazard.
A global manual needs local risk assessment.
Third, an audit report depends on evidence.
Auditors can observe only a limited period of operations.
They need records and interviews to understand what happens outside that window.
Fourth, recognition does not remove accountability from airlines, airport operators, GHSP management or state regulators.
Everyone retains their own responsibilities.
Finally, audit quality must itself be managed.
ISAGO therefore includes auditor qualification, performance monitoring, report quality control and program governance.
The strength of the program depends on those assurance mechanisms remaining credible.
No safety program should be judged solely by the number of organizations listed in its registry.
The more meaningful test is whether it changes operational behavior.
The question of audit culture
There are two ways an organization can approach an audit.
The first is defensive.
Hide weaknesses.
Prepare only what the auditor will see.
Brief employees to say the right thing.
Treat findings as failures to be minimized.
Return to normal after the closing meeting.
The second approach is developmental.
Use the standard as a structured benchmark.
Find weaknesses before the auditor does.
Welcome evidence that a process is not functioning.
Correct root causes.
Compare stations.
Track recurring problems.
Use findings to improve management decisions.
Only the second approach produces sustained safety value.
ISAGO cannot force an organization to have a healthy audit culture.
But its increased focus on implementation makes superficial compliance harder.
An operation that exists only in a manual will be more likely to fail when the auditor goes to the gate, warehouse or ramp.
That may be the single most important effect of the 2025 redesign.
From checklist auditing to system auditing
The aviation industry has learned that compliance checklists are necessary but insufficient.
A traditional audit can produce an impressive score while overlooking relationships between requirements.
Training may be compliant in isolation.
Document control may be compliant in isolation.
Safety reporting may be compliant in isolation.
Yet all three may fail to work together.
The new ISAGO auditor-training philosophy explicitly emphasizes examining ground operations as an integrated system rather than as disconnected procedural checks. IATA
That approach changes the auditor’s line of inquiry.
If an employee deviates from a procedure, the auditor might ask:
Was the employee trained?
Was the procedure accessible?
Was supervision adequate?
Was a local variation formally approved?
Did management know the variation existed?
Was it captured in the gap analysis?
Had internal audits detected it?
Was a similar problem reported elsewhere?
Did management review trend data?
Suddenly, one observation on the ramp can test multiple layers of the management system.
That is much closer to the way real accidents develop.
They are rarely caused by one isolated failure.
ISAGO and operational resilience
Safety and resilience are increasingly connected.
A standardized operation is generally easier to recover when disrupted.
Consider a major weather event, system outage or capacity problem.
Staff may be reassigned.
Aircraft may park at different stands.
Turnaround sequences may change.
Workloads rise.
Communication becomes more difficult.
During disruption, employees rely heavily on familiar processes and clear responsibilities.
An operation built on undocumented local habits can become fragile.
A standardized operation has a stronger baseline.
This does not mean every contingency can be scripted.
It means the organization has a known operating language from which controlled deviations can be made.
IATA’s current ground-operations agenda increasingly frames standards, digitalization and modern equipment as elements of operational resilience rather than separate projects. IATA
ISAGO provides the assurance layer connecting those ambitions with implementation.
What the 2026 numbers tell us
By 2026, ISAGO had reached a scale large enough to provide useful indications about international ground handling.
IATA reported nearly 300 audits completed during 2025 under the revamped model.
More than 230 ground handling service providers participated.
The network covered 441 accredited stations across more than 250 airports.
More than 200 airlines were using the reports.
At the same time, IATA’s operational-standardization data showed that organizations were increasingly publishing IGOM adoption information and making variations visible. IATA
These numbers should not be interpreted as evidence that ground handling is now globally standardized.
Far from it.
Hundreds of airports and thousands of handling operations remain outside the ISAGO network.
But the numbers indicate that the program is no longer marginal.
It now has sufficient participation to influence how the industry thinks about ground-handler oversight.
That influence may ultimately be more important than the registry count itself.
A practical example: what an audit might reveal
Imagine a fictional GHSP station handling several international airlines.
Its corporate manual correctly requires a defined aircraft-arrival safety procedure.
The station’s formal work instruction matches the industry standard.
Training records show that all ramp employees completed the required module.
On paper, everything appears satisfactory.
During implementation assessment, however, the auditor observes three arrivals.
On the first, the procedure is followed correctly.
On the second, one control is completed late.
On the third, a different team follows an informal shortcut.
Interviews reveal that experienced employees taught the shortcut to newer employees because they believe it saves turnaround time.
The station supervisor knows this happens during peak periods.
No hazard report has been submitted.
The internal audit completed four months earlier reviewed documentation but did not observe an aircraft arrival.
This is not merely one frontline employee failing a procedure.
It potentially raises questions about supervision, safety culture, training effectiveness, internal assurance and operational pressure.
A strong audit methodology should see the system behind the act.
That is what ISAGO’s current implementation emphasis is intended to achieve.
Another example: a variation that is not necessarily a failure
Now consider another station.
Local airport rules require a more restrictive vehicle-control procedure than the IGOM baseline.
The GHSP has documented the difference.
The gap analysis identifies it as a variation.
The local procedure meets the regulatory requirement.
Employees are trained.
The station monitors compliance.
Headquarters has approved the local difference.
The variation is therefore transparent and controlled.
A global standardization program must be capable of recognizing that situation.
Otherwise standardization itself would become unsafe by encouraging companies to ignore legitimate local requirements.
The objective is not uniformity at any cost.
It is controlled harmonization.
Why the registry can influence procurement
Ground-handler selection is partly a commercial decision, but safety and operational quality are increasingly integral to procurement.
An airline evaluating two potential providers will consider price, staffing, equipment, network capability and service performance.
Audit information adds another dimension.
A current ISAGO report can provide structured evidence about management systems and operational implementation.
IATA reported that airlines used ISAGO information at hundreds of stations for procurement activity in its 2024 benefit data. IATA
This creates an incentive effect.
A GHSP with robust standardized operations may become easier for airlines to evaluate.
A provider that refuses common standards may face more individual audits and greater customer scrutiny.
In that sense, ISAGO can use market mechanisms to encourage safety standardization.
The audit is no longer only about passing.
It can affect commercial credibility.
A more intelligent future for oversight
The most promising direction for ISAGO is not simply more audits.
It is better integration of audits with operational data.
A mature safety system should know where its risk is increasing before an accident occurs.
Audit findings are one source of evidence.
Incident reports are another.
Employee hazard reports are another.
Ground damage data, equipment data, training data and operational performance data provide additional context.
IATA’s wider safety architecture includes data-sharing systems such as its Incident Data Exchange, and the association increasingly encourages ground handlers to participate in safety-data programs alongside audit activity. IATA
The long-term opportunity is significant.
If industry data shows an increase in a particular type of loading error while audits show repeated control weaknesses in the same process, the two signals reinforce each other.
Standards can then be updated.
Training can be targeted.
Audit attention can be adjusted.
Technology investment can be prioritized.
That is how audit programs evolve from compliance systems into risk intelligence systems.
Could ISAGO become a de facto global ground-handling license?
Not exactly — and the distinction is important.
ISAGO is an industry program managed by IATA.
States remain responsible for aviation regulation within their jurisdictions.
Airports control operating permissions under applicable law, regulation and contractual arrangements.
Therefore ISAGO itself does not possess universal legal authority.
However, its practical influence can become similar to a licensing prerequisite where individual authorities or airports choose to recognize or require it.
That is already occurring in some jurisdictions.
The result is a layered model.
The state defines law.
The airport defines applicable local operating requirements.
The airline maintains responsibility for oversight of outsourced services.
The GHSP operates the service.
ISAGO provides a common independent assurance mechanism that several of those stakeholders can use.
That may ultimately be more useful than trying to transform ISAGO into a regulator.
Its strength lies in interoperability.
The case for harmonization
Aviation became globally scalable because it standardized many fundamental things.
Pilots use internationally understood procedures.
Aircraft operate within standardized airworthiness systems.
Airports follow common principles.
Dangerous goods move under highly structured international requirements.
Ground handling, by contrast, historically accumulated countless airline-specific variations.
Some are necessary.
Many are not.
Every unnecessary difference increases complexity.
Complexity increases training demand.
It increases the opportunity for misunderstanding.
It makes supervision harder.
It complicates audits.
It can make staff less certain which procedure applies to which airline.
This is why the relationship between IGOM and ISAGO is so important.
IGOM establishes the common operational baseline.
ISAGO checks whether the baseline has actually entered the organization’s operating system.
The program is therefore not simply auditing the ground handler.
It is testing the industry’s ability to standardize itself.
The next challenge: proving safety outcomes
ISAGO has good evidence of process benefits.
It can measure registrations.
It can count accredited stations.
It can count audit reports.
It can demonstrate cancelled duplicate audits.
It can measure findings.
The harder question is the one all safety programs eventually face:
How much safer has the operation become because of the program?
Establishing direct causation is difficult.
Ground-handling safety is influenced by equipment, staffing, airport infrastructure, airline procedures, technology, regulation, training, reporting culture and traffic levels.
If damage rates fall, ISAGO may be one contributor among many.
If damage rates rise, that does not automatically mean audits failed; traffic growth or reporting improvements may be involved.
The responsible approach is therefore to avoid simplistic claims.
The stronger argument for ISAGO is based on safety logic.
Organizations with effective management systems, standardized procedures, competent staff, controlled variations and independent verification possess stronger defenses than organizations without them.
Auditing those defenses does not guarantee a perfect outcome.
But it makes invisible weaknesses more likely to be discovered.
ISAGO’s relevance in an era of staff shortages
Ground handling has faced persistent workforce challenges since the pandemic disruption.
High turnover creates a particular safety risk because experience leaves faster than organizations can replace it.
New employees require training.
Supervisors carry heavier coaching loads.
Experienced workers may be promoted quickly.
Contracting arrangements may change.
Procedural simplification becomes increasingly valuable under these conditions.
IATA has repeatedly argued that standardization is especially important where workforce shortages increase training pressure. IATA
ISAGO can help determine whether organizations respond to staffing pressure by maintaining standards or quietly weakening them.
For example, are competence requirements preserved when recruitment accelerates?
Are inexperienced employees supervised?
Are training records complete?
Are recurrent requirements postponed?
Are subcontractors held to the same operational controls?
These are precisely the management-system questions that become critical during rapid workforce change.
Why senior management should care
ISAGO is sometimes treated as the responsibility of the quality department.
That is a mistake.
Quality personnel may coordinate the audit, but they do not own the operation.
Senior management controls resources.
Operations management controls day-to-day execution.
Training departments control competence systems.
Safety teams manage risk.
Engineering or GSE teams control equipment.
Station managers control local implementation.
Procurement teams manage subcontractors.
IT systems may control critical operational information.
Human-resources decisions influence staffing and competence.
An ISAGO finding in any of these areas cannot be sustainably closed by a quality manager rewriting a sentence in a procedure.
Management involvement is therefore fundamental.
The audit should be understood as a test of organizational governance, not as an exam for the compliance department.
What a good corrective action looks like
The quality of corrective action determines whether an audit produces lasting benefit.
A weak corrective action treats the symptom.
“Employee was reminded.”
“Procedure was reissued.”
“Staff were instructed to comply.”
Those actions may be necessary, but they often fail to explain why the problem occurred.
A strong corrective-action process asks why the control failed.
Was the procedure unclear?
Was training ineffective?
Was supervision insufficient?
Was staffing inadequate?
Was the required equipment unavailable?
Did a performance target create pressure to bypass the procedure?
Was the document inaccessible?
Was a software design encouraging the wrong behavior?
Was the same issue present at other stations?
Corrective action should therefore reach the root cause far enough to prevent recurrence.
This is where audit value becomes organizational learning.
Closing a finding is administrative.
Preventing the finding from returning is safety management.
ISAGO and the pursuit of consistency
The word consistency appears repeatedly in discussion of ISAGO.
That is not accidental.
Ground handling operates at scale.
An airline passenger expects broadly comparable safety whether boarding in Nairobi, London, Dubai, Singapore, Toronto or São Paulo.
The aircraft certainly requires it.
A cargo restraint is not less important because the departure airport is small.
A load-control error does not become harmless because the station has fewer flights.
A ground-power unit can damage an aircraft anywhere.
Global aviation therefore depends on local operations producing consistently acceptable outcomes.
ISAGO’s task is to help make that consistency visible and auditable.
The program does not eliminate local characteristics.
It establishes a common safety grammar beneath them.
The benefits, considered together
The case for ISAGO is strongest when its benefits are viewed as a system rather than individually.
For the GHSP, it provides independent validation, a framework for improving management systems, reduced exposure to repetitive customer audits and potentially stronger commercial credibility.
For airlines, it supplies standardized audit information, supports outsourced-operation oversight and can reduce unnecessary audit activity.
For airports, it provides an established benchmark that can complement local operating and licensing requirements.
For regulators, it offers a mature industry assessment program that can support risk-based oversight and, where formally adopted, acceptable-means-of-compliance arrangements.
For frontline personnel, standardization can reduce conflicting procedures and improve training consistency.
For the wider industry, common standards generate comparable data.
And for safety management, the most valuable benefit may be the connection between all of these elements.
An audit finding at one station can reveal a network problem.
A recurring variation can reveal unnecessary complexity.
A pattern across handlers can reveal a weakness in an industry standard.
A standard can then be revised.
Training can change.
Audits can test implementation.
Data can measure whether the intervention worked.
That is a safety feedback loop.

Nearly two decades on, the central idea remains the same
When IATA began working on ISAGO in late 2006, the industry’s problem was easy to describe.
Aircraft were being damaged on the ground.
People were being injured.
Ground handling differed significantly between operators.
The same providers were being audited repeatedly.
The solution was to build a common standard and a common audit framework.
The first trial audits followed in 2007.
ISAGO formally launched in February 2008. IATA
The system has since gone through several generations.
It moved from an airline audit-pool model toward independent professional auditors.
It separated headquarters systems from station accreditation.
It strengthened implementation assessment.
It professionalized auditor qualification through CoPA.
It developed digital registries.
It moved gap analysis into the OPS Portal.
It began replacing standalone GOSARPs with audit provisions drawn more directly from AHM, IGOM and ICHM.
It shifted documentation work away from valuable onsite time.
It created a stronger mechanism for declaring and managing operational variations.
It connected with wider initiatives such as Enhanced GSE.
And it increasingly positioned itself not only as an airline assurance mechanism but as a tool that airports and regulators can incorporate into wider oversight.
That evolution matters because the ground-handling environment continues to become more demanding.
Aircraft fleets are growing.
Turnaround pressure remains intense.
Ground handlers continue to manage labor constraints.
Technology is changing.
Digital loading and messaging systems are expanding.
Equipment is becoming increasingly automated.
Regulators are paying more attention to the ground-handling safety chain.
And airlines remain under pressure to control costs without diluting safety.
Against that background, duplicate oversight looks increasingly wasteful.
But weak oversight would be dangerous.
The challenge is therefore not to audit more.
It is to audit intelligently.
The ultimate measure of ISAGO will never be the logo on a certificate.
It will not be the number of documents uploaded to a portal.
It will not be the size of the registry.
And it will not be whether an organization manages to complete an audit with relatively few findings.
The real test happens at 3:30 in the morning on a wet ramp when an aircraft is late.
It happens when staffing is short.
When a new employee is working alongside an experienced one.
When a belt loader approaches a fuselage.
When a last-minute baggage change reaches load control.
When cargo needs to be restrained correctly.
When a supervisor must decide whether operational pressure justifies stopping a turnaround.
When a ground worker sees a hazard and decides whether to report it.
When the procedure in the manual meets the real world.
That is where safety standards either become operational behavior or remain words on a page.
ISAGO’s recent transformation recognizes that reality.
Its increasing emphasis on implementation is therefore more than an audit-method change.
It represents a shift in what the industry considers credible evidence of safety.
A company cannot simply say it has a system.
It must demonstrate that the system works.
Conclusion: safety starts before the aircraft moves
Aviation is often judged by what happens in the sky.
Yet every flight begins and ends on the ground.
Before takeoff, dozens of actions determine whether the aircraft is correctly loaded, safely serviced, free from damage and ready to operate.
After landing, another complex sequence begins.
Most of those actions are completed safely every day by hundreds of thousands of ground-operations professionals around the world.
That success can make the system appear simpler than it is.
It is not simple.
It is disciplined.
ISAGO exists to test that discipline.
Its origins lie in a period when the aviation industry recognized that fragmented ground-handling audits, large damage costs and operational differences required a more coordinated response.
Its first answer was a common audit standard.
Its modern answer is considerably broader.
Today, ISAGO connects independent auditing with common industry manuals, professional auditor qualification, Safety Management Systems, network standardization, digital gap analysis, station accreditation, airline oversight, airport licensing considerations and regulatory recognition.
The older GOSARP-driven audit model is giving way to a system in which AHM, IGOM and ICHM increasingly become the direct operating and audit reference points.
The audit itself is changing from a documentation-heavy exercise toward a combination of remote documentary verification and sharper onsite assessment of implementation.
The Registry allows the resulting assurance to be reused.
The OPS Portal makes variations visible.
CoPA professionalizes the auditor population.
Airports and regulators can incorporate the system into broader oversight.
Airlines can reduce repeated audits without abandoning responsibility.
GHSPs can use the framework to discover where corporate intent and operational reality have drifted apart.
None of this guarantees that a ground-handling incident will never happen.
No credible safety system can make that promise.
The value of ISAGO is more practical.
It creates a common way to ask whether the controls that should prevent an incident actually exist, whether employees understand them, whether managers monitor them, whether stations apply them consistently and whether weaknesses are corrected when discovered.
That is a significant task.
In May 2026, IATA reported that more than 230 ground handling service providers, 441 accredited stations at more than 250 airports and more than 200 airlines were already participating in that system. Nearly 300 ISAGO audits had been conducted during 2025 under the redesigned model. IATA
The numbers will change.
The central problem will not.
As global aviation grows, more aircraft will have to be turned around safely, efficiently and consistently at more airports by increasingly interconnected groups of airlines, handlers, contractors and service providers.
The industry cannot manage that complexity indefinitely through thousands of separate interpretations of what safe ground handling should look like.
It needs common standards.
It needs credible implementation.
It needs evidence.
And it needs oversight that is rigorous without being needlessly repetitive.
That is the space ISAGO was created to occupy.
Almost two decades after its launch, the principle behind it remains remarkably direct:
A safe flight does not begin at takeoff. It begins with the people, procedures, equipment and decisions surrounding the aircraft while it is still on the ground.

Editorial note
This article reflects publicly available IATA and ICAO information current through September 2026. ISAGO standards, audit checklists, manual editions, platform procedures and program requirements are periodically revised. A GHSP preparing for an actual audit should therefore use the current ISAGO Audit Handbook, Program Manual, audit contract, OPS Portal requirements and applicable editions of AHM, IGOM and ICHM supplied or identified for its audit rather than relying on historical requirements described in secondary material. IATA’s current public material confirms that the ISAGO Checklist now draws from the latest AHM and IGOM standards and that ICHM has replaced the former standalone Cargo and Mail GOSM module in the current standards architecture. IATA

