Air-Cargo Shipment-Handover Architecture Director — Global Forwarding

The mandate

Airline and forwarder partners are enabling ONE Record at different speeds, yet export stations still exchange responsibility through airwaybill messages, portal updates, email and warehouse scans that disagree. A technically shared shipment object does not by itself decide whether cargo is accepted, secured, screened, built, manifested or recoverable. The defined problem is to translate connected data into dependable physical and commercial handovers.

The deliverable is an Air-Cargo Shipment-Handover Architecture defining the event, evidence, accountable party, access right, exception clock and physical acceptance condition at each shipper-to-consignee boundary. It must accommodate API-enabled and legacy partners concurrently, preserve security and customs obligations, and prevent a digital event from representing custody or readiness that has not occurred physically.

The first four weeks end only when twelve shipment journeys and their responsibility breaks are accepted. Regulatory constraints face a separate second acceptance gate in week six, followed by special-cargo constraints at the third gate in week eight. The evidence-to-decision model is due at week thirteen, station controls at week eighteen and partner transition waves at week twenty-three. Four live handovers provide the seventh proof point by week thirty; the eighth milestone at week thirty-two releases the final architecture, acceptance pack and implementation backlog.

Acceptance requires client teams and nominated partners to recover unseen identity mismatch, late security status, rejected dangerous-goods evidence, handler capacity loss and destination access failure while preserving cargo custody and customer truth. The Air Freight President signs only when operational owners can act from the shared record, challenge an incorrect event and complete a manual fallback without consultant interpretation.

The client will provide contracts, station procedures, message and event samples, ONE Record profiles, airwaybill histories, cargo-status data, security and customs rules, exception logs and empowered partner owners. Exclusions include API construction, production-system configuration, security approval, customs filing, live cargo acceptance, carrier selection, contract amendment, individual shipment command and assurance that every external party adopts the standard.

Why this is external work

Digital teams understand the standard, while station teams understand physical cargo; neither owns the cross-company decision boundary. An independent air-freight operator can reconcile shared data with custody, acceptance and recovery practice without becoming a software implementer, regulated approver or advocate for one airline or handler.

What you will own

• Trace twelve shipment journeys across booking, receipt, screening, acceptance, build, manifest, departure, breakdown, clearance and delivery.
• Define each handover’s physical state, event evidence, accountable publisher, authorised reader, challenge route and decision clock.
• Separate information visibility from contractual custody, regulatory acceptance, security status and operational readiness explicitly.
• Design coexistence controls for ONE Record, Cargo-XML, portal, email and manual station evidence.
• Build station playbooks for incorrect events, unavailable partners, duplicated identities, late changes and lost connectivity.
• Rehearse special-cargo rejection, handler constraint, identity mismatch, destination denial and controlled manual fallback.
• Deliver the architecture, event matrix, partner rules, station playbooks, trial evidence and an accepted mobilisation backlog sequenced by gateway readiness, custody risk and partner dependency.

Candidate qualifications

• Led international air-freight forwarding operations across origin, gateway, airline, handler and destination boundaries.
• Implemented ONE Record or comparable shared shipment-data standards in live operational handovers.
• Distinguished digital event publication from physical custody, security acceptance and contractual responsibility consistently.
• Designed fallback operations where modern APIs and legacy cargo messaging had to coexist safely.
• Understood dangerous goods, security, customs and special-cargo decisions without claiming regulated approval authority.
• Transferred cross-company operating architecture through partner-led physical trials and deliberately corrupted event evidence, with accountable station owners proving challenge, fallback and recovery decisions.

Non-negotiables

• Can lead ten station laboratories and four Frankfurt-governed trials within eight months.
• Direct experience in air-freight operations and shipment-data transition is required; API architecture alone is insufficient.
• Will disclose airlines, handlers, forwarders, cargo platforms, technology firms and customs-service interests.
• Will not build APIs, accept cargo, file customs, approve security or promise universal partner adoption.

1. 49 words maximum. Describe a digital cargo event that asserted a physical handover which had not occurred.
2. 49 words maximum. How would you test a ONE Record handover when one partner remains on legacy messaging?
3. 49 words maximum. Which station and partner evidence must be available before milestone one?