Provider oversight,on one connected operation.
Every supplier, MRO and provider agreement is a governed record — type, scope, dates and the obligations it carries. An oversight lifecycle the workflow can’t skip, sharing scoped exactly to what you mean, and the findings that link straight back to the provider.
An oversight stage
you can’t skip.
A provider runs through a fixed oversight lifecycle. The workflow refuses to advance past a stage that isn’t complete, and the accountable manager is the last signature — whoever performed the work.
- Procurement · ComplianceSTAGE 01Onboard the provider as a record
- Compliance Monitoring ManagerSTAGE 02Define scope, obligations and dates
- Quality AssuranceSTAGE 03Run oversight — audit, findings, evidence
- Accountable ManagerSTAGE 04Accountable manager signs the outcome
Share exactly
what you mean to.
Data sharing is scoped on the record — only the modules and record types you choose, only after Annex-19 confidentiality clears. The change and its audit trail commit together.
Pick exactly which modules and record types each partner can see — explicit, never implicit.
Sensitive records gate behind confidentiality tiers before anything is ever shared.
The change and the audit record commit together — the trail is the workflow, not a PDF.
Providers sit beside
the work they touch.
A provider record lives on the same connected operation as your occurrences, findings and corrective actions. An oversight finding links back to the provider — partner oversight builds up as the work happens, not at audit time.
What a partnership record holds.
The provider organisation, the agreement type and scope, the dates it runs, and the obligations it carries — held on the record, then linked to the occurrences, findings and actions that involve the provider.
Five moments.
No spreadsheets.
- When you sign a new provider.Onboard the agreement as a record.
Capture the provider organisation, the agreement type — maintenance, ground handling, codeshare, interline — and the scope it covers. You get a referenced partnership record, not a contract buried in a folder.
- When the agreement carries obligations.Record the obligations on the record.
List the regulatory requirements the agreement carries against the partnership record itself. The oversight you owe for this provider sits with the provider, not in a separate compliance binder.
- When a provider is involved in an event.Link the occurrence or finding.
An occurrence or audit finding that involves the provider links straight to the partnership record. Partner oversight builds up in your operational picture as the work happens — not at audit time.
- When oversight raises a finding.It links back to the provider.
A finding from a provider audit carries your standard severity, SLA and closure gate, and links back to the partnership. The corrective action rides the same effectiveness gate as any internal finding.
- When the regulator asks about a provider.Pull the oversight history.
Open the partnership record and read its linked occurrences, findings and corrective actions in one place. The provider’s oversight history is already assembled — no screenshot mosaic, no last-minute spreadsheet.
Partnerships don't live
in a silo.
The work that involves a provider links straight to its record — no integration project. Four connections that matter on Monday morning.
Open the platform.
Walk a provider review.
See a provider onboarded as a record, the oversight lifecycle it can’t skip, and a finding linked back to the provider — with the founder, in 30 minutes.