IOSA audit preparation that proves every standard documented and implemented, months before the auditor arrives
Every IOSA standard tied to its manual and proof, with gaps found months before the audit.
See one case, screen by screen ↓IOSA audit preparation is the work an airline does before its IOSA renewal audit to show that every applicable ISARP is documented in a current manual paragraph and implemented in its records. IOSA Audit Preparation gives that work to seven agents that map each standard to its manual paragraph, sample the records, catch references broken by manual revisions and draft the corrective action for every gap. The quality assurance manager accepts and assigns, and the Director of Quality signs the conformance report.
How to choose AI for airlines: a buyer's guide to agentic AI solutions →
Updated
Every airline on the IOSA registry must pass an IOSA renewal audit every two years to stay registered. Registration is a condition of IATA membership, and the FAA/DOT codeshare safety program accepts the audit for foreign codeshare partners. ISARP compliance is proved one standard at a time: each ISARP that applies must be documented in a current manual paragraph and implemented in the records. Most quality teams rebuild that proof by hand each cycle: a reference matrix of about 870 standards typed in one row at a time, and evidence chased by email from every department in the last weeks before the audit.
The risk is in what changes between audits. A manual revision moves a paragraph and the matrix still cites the old one. A former station of an acquired airline keeps using its old form. In a risk-based IOSA audit, the IOSA remote document review now comes before the on-site week, so a gap the quality team has not found by then is likely to become a finding, and each finding needs an IOSA corrective action plan before it can be closed.
Estimated split for one renewal cycle at a large network airline, by hand and with the solution.
Seven agents map, check, sample and draft the fix for every IOSA standard and check each other; the quality manager accepts, assigns and signs.
Corvane Airways, a network carrier with its hub at DEN, is 172 days from its risk-based renewal audit: remote document review March 1–19, 2027, on-site at DEN April 5–9, against ISM Edition 18. It is also folding in the manuals of Halvard Air, a regional airline it acquired in March 2026. Here is one Thursday morning, screen by screen, in the working solution.
Overnight the agents re-checked all 871 standards that apply to Corvane. 742 are filled. The Readiness Agent could not fill 68: 23 have no valid manual reference and 45 are not shown as done in the records, and 19 of them come from Halvard Air. Marisa Calloway's Today screen lists five things that need her, starting with GRH 3.1.5.
“Three things need you today: the GRH 3.1.5 fix, 54 mappings you can accept in one decision, and 9 drafted corrective actions.”
Every applicable standard is a spine on a shelf by discipline: ORG, FLT, DSP, MNT, CAB, GRH, CGO and SEC. A spine is filled when it is documented and done, half filled when the manual says it but the records do not show it yet, hollow when no current paragraph documents it, and tinted when an agent has proposed a mapping that waits for her. Beside it, the Readiness Agent explains how it decides.
“Each night I check every spine three ways: a current manual paragraph documents it; records from the last 24 months show it done; and a second agent agrees. Only then is a spine filled.”
GRH 3.1.5 covers fueling with passengers on board. The IOSA reference matrix still cites GOM 4.6.2, Revision 11. The Revision Checker found that Revision 12, effective July 1, 2026, deleted it when the Halvard fueling procedure was merged into the GOM. The Mapping Agent linked the current text, GOM 4.7.3, at 0.96 confidence, and the Revision Checker agreed it is current and covers the cabin crew notification.
The Mapping Agent only proposes. Below 0.85 confidence it asks instead, and no proposal is shown until a second agent agrees.
The Evidence Agent sampled 120 September fueling records. DEN and ORD are 40 of 40. At SEA, 37 of 40 show the cabin crew notification; 3 are on the Halvard form HV-GO-17, which has no field for it. Marisa asks why SEA is different, and the answer cites the record, the form and the revision.
“This is a stock and briefing problem at one station, not a procedure problem.”
Marisa reads the sources and accepts GOM 4.7.3 Revision 12 with reason code A1, “Mapping correct as proposed”. The superseded reference GOM 4.6.2 comes off the matrix. The spine turns half filled: documented, not yet shown as done.
“I, Marisa Calloway, sign this decision. It is recorded with the time, the reason and the sources.”
She assigns CA-2026-061 to Ground Operations and Carmen Delacroix, due December 15, 2026, with a reminder three days before. The note to the liaison is already written: retire HV-GO-17 at SEA first; the December re-sample closes it. A manual change, MCR-2026-118, will correct the matrix row. When the re-sample comes back clean, a person verifies and closes the action, and the spine fills.
The Corrective Action Drafter wrote CA-2026-061 at 04:44: the root cause (the Halvard fueling log stayed in use at SEA after Revision 12 withdrew it), the action (remove the HV-GO-17 stock at SEA, brief the 14 SEA fueling supervisors), and the evidence that will close it (40 SEA records re-sampled, none failing). It now sits, assigned, among the 62 corrective actions drafted from the 68 gaps; 8 others still wait for Marisa to approve, edit or reject.
The Corrective Action Drafter drafts only. A person approves, edits or rejects it with a reason.
The Revision Checker re-checked the 31 references into six revised manuals and found 9 broken. MCR-2026-118 shows the old and new text of GOM 4.7.3 step 6, which now adds “Form HV-GO-17 is not used at any station.”, and the matrix row from GOM 4.6.2 (Rev 11) to GOM 4.7.3 (Rev 12). Sam approves it in the manual system; the Revision Checker confirms the published text.
The Integration Agent read Halvard Air's 9 manuals: 486 procedures in IOSA scope, 401 matching a Corvane procedure, 52 already merged, 14 in conflict and 19 gaps on the shelf. Winter makes HAL-C-07 the first to decide: SEA and PDX still post the 2024–25 de-icing holdover table. Elliot Vance, the IOSA Coordinator, decides each conflict.
The Integration Agent never merges manuals; every conflict goes to the IOSA Coordinator.
From the shelf and the people who own each discipline, the Audit Rehearsal Agent built the on-site week at DEN, 8 interviewees and 214 likely questions, and an evidence pack per discipline. Carmen Delacroix is 19 of 24 ready: the question “Show me how the cabin crew are told fueling has started at SEA” is marked record missing until CA-2026-061 closes.
The evidence packs are released to the auditor only when a person says so.
The same audit cycle, seen by the five people who carry it: what their preparation looked like, and what it looks like now.
Seven agents map, check, sample and draft the fix for every IOSA standard and check each other; the quality manager accepts, assigns and signs.
Plans the nightly check across every applicable IOSA standard, gives the work to the other agents, writes the morning note and the weekly note, and says which spines it could not fill and why.
Proposes the manual paragraph that documents each standard, with its confidence, from the manual library and the licensed ISM data.
Reads every manual revision the day it is published, re-checks each IOSA reference into it, flags superseded or moved paragraphs and checks every proposal the Mapping Agent makes.
Samples the records that show a procedure is implemented, by station and month, reads each one and names the records that fall short.
Drafts the IOSA corrective action plan for every gap — root cause, action, owner, due date and closing evidence — and the manual redline that goes to the manual owner.
Reads the acquired airline's manuals against yours and against the ISARPs, and sorts each procedure as matched, merged, in conflict or missing.
Builds the on-site week, the evidence pack per discipline and the questions each interviewee is likely to hear, and checks every answer has its record.
Accepts mappings and assigns gaps; manual owners approve changes; the Director of Quality signs. The agents propose; a named person decides.
Ask in plain words, or tell an agent what to do. Every answer cites the manual paragraph, revision or record it came from.
Why is SEA different?
SEA joined from Halvard Air in March 2026. Its September fueling records are 37 of 40 on the Corvane form CV-GO-41; the other 3 are on HV-GO-17, the Halvard form, which has no field for the cabin crew notification. GOM Revision 12 withdrew it at all stations by September 30, so this is a stock and briefing problem at one station, not a procedure problem.
What exactly changed in Rev 12?
GOM Revision 12 took effect on July 1, 2026 and deleted 4.6.2; its content moved to new 4.7.3. The IOSA reference matrix was last edited in March 2025 and still says GOM 4.6.2 Rev 11. The current paragraph covers both the captain and the cabin crew notification.
Re-sample SEA after Dec 1
Planned: 40 SEA fueling records from December 1–10, with the answer on December 11 on whether every one shows the cabin crew notification. If any fail, CA-2026-061 is reopened rather than closed.
Why is MNT 2.6.4 at risk of repeating?
SEA's register shows 7 of 96 tools past calibration, the oldest 41 days. This is the same finding as April 2025 at MIA; the fix, a monthly report to the station manager, never reached SEA.
13 screens from the working solution, on its sample data. Pick one to see it large.
The audit cycle and the rules the agents work to are settings. Only the IOSA Coordinator or the Director of Quality changes them, and every change is signed and logged.
| Setting | Default | Choose from |
|---|---|---|
| IOSA Standards Manual | Edition 18 | Edition 18 · Edition 17 |
| Audit type | Risk-based renewal audit | Risk-based renewal audit · Conventional renewal audit |
| Propose a mapping at confidence | 0.85 | Below this the Mapping Agent asks instead of proposing |
| Bulk-accept floor | 0.92 | Only mappings at or above it can be accepted in one decision |
| Evidence age | 24 months | Older records do not count as implemented |
| Records sampled | 40 | Per station, per standard, each sample |
| A failing record | Any failure | One failing record makes the standard “not shown as done” |
| Escalation | After 2 missed reminders | To the department head; reminders 3 days before each due date |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in the live solution · “estimated” = our estimate · “typical” = published figures (IATA Safety Audit Programs fact sheet, June 2026 — 449 airlines on the IOSA registry, 916 standards in the ISM, 229 risk-based audits in 2025 that found on average about twice the non-conformities of conventional audits; and, for the codeshare context, the FAA/DOT Codeshare Safety Program Guidelines). ISM text is IATA's copyright: the working solution paraphrases each standard, and the standard numbers on its screens are illustrative, matched to the airline's licensed edition at set-up. People, Corvane Airways and Halvard Air named on this page are fictional — characters and sample data in the working solution.
IOSA audit preparation is the work an airline does before its IOSA renewal audit to show that every applicable ISARP is documented in a current manual paragraph and implemented in its records. IOSA Audit Preparation gives that work to seven agents that map each standard to its manual paragraph, sample the records, catch references broken by manual revisions and draft the corrective action for every gap. The quality assurance manager accepts and assigns, and the Director of Quality signs the conformance report.
Risk-based audits review your documents remotely before the on-site week, so the proof has to be complete months earlier. The solution re-checks every applicable standard each night, shows readiness on one shelf by discipline, and counts down to the document review and the on-site audit. In the working solution, all 68 gaps are found with a drafted fix 172 days before the on-site audit.
Documented means a current manual paragraph says the airline does it; implemented means the records show it is done. The Mapping Agent and Revision Checker handle the first, and the Evidence Agent samples records by station and month for the second. A standard is filled only when both are accepted and a second agent agrees.
The Revision Checker reads each revision the day it is published and re-checks every IOSA reference into it. A paragraph that was deleted or moved is flagged the next morning, and the Corrective Action Drafter writes the manual change as a redline for the manual owner to approve.
Yes. The Integration Agent reads the acquired airline's manuals against yours and against the ISARPs and sorts each procedure as matched, merged, in conflict or missing. The IOSA Coordinator decides each conflict; the agent never merges manuals itself.
Yes. The agents re-check that the fix for each finding and observation from the previous audit still holds, and the Evidence Agent flags the ones at risk of repeating, such as a calibration fix that never reached a newly joined station, so you can act before the auditor looks.
Yes. Agents propose, cite and draft; a named person accepts every mapping and approves every corrective action with a reason code and signature. Only the Director of Quality signs the conformance report, and nothing goes to IATA or the auditor unsigned.
The Agentic Solution Engine builds and deploys it from your requirements and documents: your licensed ISM data, your manuals and reference matrix, and the systems that hold your station, training and maintenance records. It goes live once every quality gate has passed, and we walk you through it on your own manuals first.
Every report routed the same day, every repeat linked before it is scored.
1-min demoAviation Safety Action Program (ASAP)Every ASAP report ready before the ERC meets, every action tracked to closure.
1-min demoSafety Investigation ManagementReports drafted in days, not weeks, with every finding tied to its evidence.
1-min demoWe'll run IOSA Audit Preparation on a sample of your own manuals, reference matrix and station records.