Partner Reporting - Internal
airportr· Partner Reporting

Internal overview · build status across partners and KPI groups

Generated 29 Sep 2026 10:31
Internal only. Do not publish this page to a partner — it lists every partner side by side. Each partner gets their own landing page, which names only them. Each partner opens in a new window, so this page stays where it is.

Partners

PartnerAirportsOn-Time PerformanceBooking & Bag VolumeBag Path, Cancellations & RepatriationsLogistics FeesNPS & Service Feedback
ATALHR, LGWbothbothbothbothboth
AKSZRH, GVAbothbothbothbothboth
OpusFRAbothbothbothbothboth
WIMBVIEbothbothbothbothboth
SwissportZRH, GVA, VIE, EDIpaidpaidpaidpaidpaid
Dunedin CouriersEDIbothbothbothbothboth

KPI groups against the standard

#GroupBoardStatusNote
1OTPOn-Time Performancebuilt
2Booking VolumeBooking & Bag Volumebuilt
3Bags VolumeBooking & Bag VolumebuiltBag Path drilldown lives on the ops board.
4Doorstep Cancellations & RepatriationsBag Path, Cancellations & RepatriationsbuiltSlot and driver cuts not built - see the board.
5Financial DataLogistics FeesbuiltDriver cut impossible - no driver field on the fee source.
6Compliance & Data—not builtDoorstep Seal compliance now looks viable - Tamper Aware Seal Code exists on Silver ABC_BagJourney. Incidents and Missed Injections still sit on the thin Agents DB tracker.
7NPS & Service FeedbackNPS & Service FeedbackbuiltBasis is the FEEDBACK date, not the collection date - these periods do not line up with the other boards. Driver Tips remain unsourced; Driver Rating is dead.

Drilldowns that cannot be built

GroupDrilldownWhy
2Forecast DataNo forecast source exists anywhere in Tableau.
4Cancellation by slotOnly on the delivery-date fee source; cancellations are cancelled-date. Mixing bases would not reconcile.
4Cancellation by driverNo driver on Cancelled_Booking, and most cancellations precede courier assignment.
5Fees by driverNo driver field on the fee source; the driver source carries no fees. Needs a warehouse view with both.
7Driver TipsTips carry no date and no courier, so they cannot be periodised or attributed.
Why 4 boards for 7 groups. Booking Volume and Bags Volume share every drilldown and differ only in the measure, so they are one board with a toggle. Bag Path sits with Cancellations and Repatriations because it answers the same question — what happened to the bag. Splitting either would duplicate tables and let the halves drift apart.