Code-share compliance,
on the same picture.
Joint occurrence reporting, joint findings, shared SPIs — under explicit data-share policies. Your partner sees what you explicitly link into the shared slice. Never a shared drive, never a “can you resend” email.
Two organisations.
One operational picture.
Each channel is a versioned policy. The records each side shares are explicit; the records each side keeps are explicit too. Bumping the policy version preserves the old one for the audit — nothing is overwritten.
What sits inside the policy.
Scope of records, retention, redaction rules, dispute resolution. Versioned. Approved by both accountable managers. Held against the partnership record itself — never on a shared drive.
Five moments.
No spreadsheets.
- When you onboard a code-share partner.A partnership is a record, with a scope.
Define the partner, the agreement reference, the contact roles. The platform creates the partnership record, opens the data-share scope, and primes the joint-occurrence lane against your taxonomy.
- When a joint occurrence is reported.One report, two organisations, one workflow.
Either side files the occurrence; the platform routes it to the joint lane, classifies it against the shared taxonomy, and surfaces it on both safety dashboards. Reporter identity protections honour both organisations’ Just-Culture policies.
- When you scope a data-share policy.Versioned, audit-trail, opt-in per record-type.
Pick the record types you share — joint occurrences, ETOPS SPIs, joint findings, training attestations. Each scope is a versioned policy document. Bumping the version preserves the old one for the audit.
- When joint findings need coordinated closure.Owner ≠ verifier — across the org boundary.
A finding raised against the partnership opens a corrective action with one organisation as owner and the other as verifier. The effectiveness gate works across the boundary; the workflow refuses closure until both sign.
- When the regulator audits the partnership.The shared lane is the package.
No screenshot mosaic, no last-minute spreadsheet. The shared records, the policy versions, the signature chain — all live, all time-stamped. Generate the regulator-ready package scoped to the inspection in one click.
Partnerships don't live
in a silo.
Joint records flow into the rest of your safety system without an integration project. Four examples that matter on Monday morning.
Open the platform.
Scope a data-share policy.
Walk through a code-share onboarding, a joint-occurrence flow, and a policy-version bump — with the founder, on your partnership shape, in 30 minutes.