Skip to main content

How to use the Codeshare Synchronization Audit

The Codeshare Synchronization Audit checks whether a partner carrier's marketed schedule matches the operating carrier's own-metal schedule. It identifies the following discrepancies:

  • ADD — the operating carrier has a flight, but the partner does not market it
  • DELETE — the partner markets a flight with no operating record
  • UPDATE — both schedules exist but key attributes differ

Use this audit when you need a daily, bidirectional check of one operating carrier and one partner carrier for a specific flight range.

When to use it​

Use this audit to:

  • verify codeshare alignment for a partner carrier
  • find ghost flights and missing marketing records
  • detect timing, equipment, terminal, or meal service mismatches
  • confirm partner schedule changes before they are published

What you need​

  • operating_carrier — the IATA code of the carrier operating the flight
  • partner_carrier — the IATA code of the marketing partner
  • flight_range_start and flight_range_end — the operating flight number range
  • dataset_id — the published SSIM dataset to audit (current schedule)

Default flight range behavior​

If you do not specify a flight range, the agent automatically uses:

  • flight_range_start = 1
  • flight_range_end = 9999

That means the audit will cover all operating flights for the selected carrier.

How it works​

The audit compares two sets of data:

  • operating carrier truth from ssim_3 and ssim_4 DEI records
  • partner marketing reality from ssim_3 and ssim_4 DEI records

It expands both sides into daily schedule dates, filters only future dates, then joins them to find ADD, DELETE, or UPDATE actions.

Example prompts​

MaestrowPROMPT
Run the codeshare synchronization audit for partner AF and operating carrier DL, flights 1 to 100.
MaestrowPROMPT
Run the codeshare sync report for AM operating flights in the 1 - 2000 range against DL marketed flights.
MaestrowPROMPT
Check if BT's marketed flights match KM's operating schedule for flights 2800-2849.
MaestrowPROMPT
Perform a codeshare audit between KM as the operating carrier and all of its marketing partners listed in the company profile.

What you will see​

The audit returns rows grouped by consecutive dates requiring the same action. Each row includes:

  • partner carrier and flight number
  • operating flight number
  • departure and arrival stations
  • action (ADD, DELETE, UPDATE)
  • mismatch details for updates
  • start/end dates for the discrepancy block
  • operating departure/arrival times, UTC offsets, equipment, meals, and terminals

Best practices​

  • Always provide both operating_carrier and partner_carrier.
  • Use a specific flight range when you only need a subset of flights.
  • If you want a full carrier audit, leave the range unspecified.
  • Export the results to CSV when the report contains more than 10 discrepancy blocks.

Tips​

tip

For a single operating carrier against multiple partners, run one audit per partner.

tip

The audit only includes service type J flights, so it excludes surface and helicopter equipment.

tip

The tool automatically uses the latest published SSIM dataset when the agent resolves dataset_id.

tip

Pro Tip:

Even though the audit tool filters for Service Type 'J' (Scheduled Passenger), airlines often publish charter, positioning and ferry flights under 'J'. The audit defaults to flight range 1 - 9999 for operating flights. To keep the audit clean and run it expeditiously, use operating flight ranges. You can ask Maestrow to provide the ranges. This will ensure the audit includes only scheduled commercially operated flights.

See also​