Skip to content
Safety Management Systems (SMS)

Safety management,
operated for you.

One safety program for your operation. Evidence-connected agents and assigned EE people turn reports into investigations, controls, verified action and learning.

Planned · discovery calls open
Book a discovery call

Discovery first. Scope, deployment availability, service coverage and fees are agreed before an engagement starts.

FROM A CONCERN TO A CLOSED LOOP

These synthetic scenarios illustrate the intended service. They are not customer cases, live demonstrations or evidence of production availability.

A pilot reports between dutiesSYNTHETIC
ILLUSTRATIVE CASEPLANNED WORKFLOW

Unstable approach concern

  1. 01CaptureVIEWING
  2. 02Retain locally
  3. 03Receive securely
  4. 04Return feedback
SOURCE CONTEXT
Pilot observation
Photo attachment
Device capture time
Capture
Synthetic pilot scenario. Planned native workflow; voice and photos support reporting, not a certified physical inspection.
Read the process
  1. CaptureA pilot records a voice note and photo, then checks the proposed facts before submission.
  2. Retain locallyAn interruption leaves a protected local draft. Queued means it is still on this device, not received by the service.
  3. Receive securelyAfter connectivity returns, an acknowledged receipt confirms delivery. Assigned EE staff take the next action.
  4. Return feedbackThe reporter uses the receipt to follow permitted updates and answer questions without seeing the investigation’s restricted material.
01Capture the concern

Keep the observation.
Keep the context.

  • Native iPhone and iPad capture with voice, photos and manual entry.
  • Clear draft, queued and received states through interruptions.
  • A receipt and a two-way feedback path, with access matched to the reporting mode.
Book a discovery call
A calibration escape reaches the safety teamSYNTHETIC
ILLUSTRATIVE CASEPLANNED WORKFLOW

Torque tool calibration exception

  1. 01Link the sourcesVIEWING
  2. 02Expose uncertainty
  3. 03Assess and act
  4. 04Assign the controls
SOURCE CONTEXT
Calibration record · overdue
Work cards · partial coverage
Aircraft / serial matches · review
Link the sources
Synthetic maintenance scenario. An association is a lead for review, not proof that an aircraft is affected or released.
Read the process
  1. Link the sourcesThe agent connects a calibration exception to available tool records, work cards, serials and aircraft effectivity.
  2. Expose uncertaintyMissing records, stale feeds and uncertain matches stay visible. Suggested facts carry their source and revision.
  3. Assess and actA competent, appointed EE person assesses the evidence and acts within the recorded authority. Maintenance certification stays with appropriately authorized personnel.
  4. Assign the controlsContainment, follow-up work and control owners are recorded with due dates and evidence requirements; an open task is not proof of completion.
02Connect the evidence

Find the affected work.
Make the next move.

  • Evidence-linked agent work, including missing coverage and stale inputs.
  • EE staff handle investigation, coordination and authorized decisions.
  • One traceable chain from hazard to control, task and verification.
Book a discovery call
An airline introduces a new operating patternSYNTHETIC
ILLUSTRATIVE CASEPLANNED WORKFLOW

New operating pattern

  1. 01Define the changeVIEWING
  2. 02Rehearse scenarios
  3. 03Resolve the gaps
  4. 04Record the decision
SOURCE CONTEXT
Operational baseline
Training readiness
Interface / emergency arrangements
Define the change
Synthetic airline scenario. A rehearsal explores possibilities; it does not predict an accident rate or authorize operations.
Read the process
  1. Define the changeThe team defines a fleet, route or procedure change and the affected operational interfaces.
  2. Rehearse scenariosAgents prepare evidence-based safety rehearsals and alternative control plans. Assumptions and uncertainty remain attached to every proposal.
  3. Resolve the gapsEE staff coordinate actions, training, emergency arrangements and evidence before the planned introduction.
  4. Record the decisionThe person holding the applicable authority records the consequential decision. The certificate holder retains its regulatory responsibilities.
03Prepare the change

See the interfaces.
Before the change.

  • Management of change connected to the current operational baseline.
  • Scenario rehearsals and control options with explicit assumptions.
  • A decision record that names the actual authority and remaining conditions.
Book a discovery call
The follow-up shows a control is not workingSYNTHETIC
ILLUSTRATIVE CASEPLANNED WORKFLOW

Repeat calibration escape

  1. 01Gather the proofVIEWING
  2. 02Check effectiveness
  3. 03Reopen the action
  4. 04Share the learning
SOURCE CONTEXT
Implementation evidence
Repeat finding
Effectiveness review · failed
Gather the proof
Synthetic assurance scenario. Closure requires the evidence and authority defined for the actual program.
Read the process
  1. Gather the proofThe service gathers the agreed evidence of implementation and checks its coverage and freshness.
  2. Check effectivenessAn assurance review compares the result with the intended control, rather than treating a completed checklist as success.
  3. Reopen the actionA failed effectiveness check reopens work, revises the control and assigns the next evidence requirement.
  4. Share the learningEE publishes the permitted reporter update and relevant safety learning. Management sees remaining risk, overdue work and the next decision needed.
04Check what changed

Test the control.
Close the loop.

  • Indicators and assurance findings retain their source and coverage.
  • Failed controls return to active work with a responsible owner.
  • Reporter feedback, briefings and training connect learning to daily work.
Book a discovery call

A complete safety management loop.

The shared core connects the four SMS components. Profiles add the obligations and operating context for each approval, without splitting your safety picture into separate products.

Safety policy & accountability

The operating scope, policy, objectives, appointments and decision authority are explicit. Emergency-response coordination and organizational interfaces are included where applicable.

Safety risk management

Reports, hazards, investigations and changes lead to assessed risks, control options and assigned actions. Decisions retain their rationale and source evidence.

Safety assurance

Indicators, compliance monitoring, audits and effectiveness checks reveal what is working, what is missing and what needs further action.

Safety promotion

Role-based learning, safety communication, briefings and reporter feedback bring the lessons back to the people doing the work.

One SMS. The right operating profile.

All profiles below are planned. Discovery establishes the jurisdiction, certificate holder, activities and interfaces before implementation. A corporate group does not receive one blanket compliance status.

Planned SMS operating profiles · reviewed 2026-10-23
ProfileApplicabilityOperational focus
Airlines · Part 121PlannedBook a discovery call FAA Part 5 safety management for Part 121 operations.Fleet and network changes, operational interfaces, safety indicators and emergency-response coordination.
Charter & commuter · Part 135PlannedBook a discovery call FAA Part 5 with the operator’s actual certificate, activity and implementation timeline.Distributed reporting, flight-risk workflows, operational change and proportionate assurance.
Maintenance · Part 145PlannedBook a discovery call Separate FAA-only voluntary, U.S.–EASA bilateral and direct EASA Part-145 configurations.Work cards, calibration, serial and aircraft effectivity, human factors and maintenance handoffs.

Additional jurisdictions and operating activities are scoped separately. The listed profiles do not imply UK approval coverage.

Report where the work happens.

Native iPhone & iPad

Planned voice and photo capture, editable facts, protected local drafts and receipts. Camera and microphone access are explicit. A failed connection leaves a recoverable state, not a false delivery confirmation.

A focused work queue

Assigned EE staff get evidence, agent results, missing information and the next authorized action. iPad layouts support reviewing the record alongside the decision. Notifications open an access-checked destination without exposing a case on the lock screen.

Agents that move the work forward

Capture assistance, investigation briefs, control planning, assurance analysis and rehearsals retain source citations and uncertainty. Authorized routine actions can run in the background; consequential decisions follow the recorded authority.

Connected on your terms

Scoped integrations and MCP connect approved tools to the same evidence and authority model. Imports preserve provenance, revision, freshness and missing coverage. Access does not expand because an agent requested it.

An operated service, with a clear handoff.

Establish the baseline

Identify approvals and profiles. Appoint roles. Reconcile existing reports, hazards, risk registers, controls, training and evidence. Record what is missing before treating an import as complete.

Run the agreed program

EE coordinates reports, investigation, risk work, action evidence, assurance and promotion. Work stays connected to aircraft, maintenance and operational records where those sources are available.

Know when you are needed

Receive a specific request tied to a reserved authority, operational action or missing source. Routine service work does not wait for a generic customer approval gate.

Retain continuity

Agree service coverage, escalation and emergency channels, retention rules, export format and exit arrangements. Reporting to an authority is tracked separately from receiving a report internally.

Trust the record. Know who can act.

Planned reporting supports identified, confidential and anonymous channels with distinct access and identity handling. Current permissions govern each read, action and agent run. Source revisions, decision rationale, command receipts and evidence history make the work reviewable.

Assigned EE people perform the service within their authority. Internal support and observability follow their own scope; they do not give ordinary customer administrators access to restricted safety material. Training use is separately controlled.

Safety reporting is not an emergency service. Existing operational and emergency procedures remain the immediate path for urgent hazards.

Questions before you start.

Can we use SMS on its own?

Yes. The planned service is one standalone SMS with the profiles your operation needs. Part 145 Management and Asset & Fleet Management are complementary products, not mandatory base plans. Discovery establishes the actual deployment scope and fees.

Who handles the work and decisions?

Assigned EE staff operate the agreed service: reviewing evidence, investigating, coordinating action and following through. Competent EE personnel can act in appointed or authorized roles. Responsibilities reserved to the accountable manager, certificate holder or authorized certifying staff remain with the actual holder of that authority; they are not replaced by an agent or a generic approval click.

Does every Part 135 operator have the same deadline?

No. FAA guidance distinguishes existing certificate holders and applicant stages. Operators certificated before May 28, 2024 have a May 28, 2027 implementation deadline; new applications from May 28, 2024 generally require SMS upon certification. The service must use the organization’s actual status, not a blanket countdown.

Is SMS mandatory for every repair station?

No. FAA-only Part 145 participation in the FAA SMS Voluntary Program is distinct from U.S. repair stations holding EASA approval under the bilateral arrangements and organizations approved directly under EASA Part-145. The applicable approval path determines the profile, evidence and external obligations.

What happens when a phone is offline?

The planned native flow preserves eligible protected drafts and queued reports locally. It shows received only after service acknowledgment. AI processing and cross-device availability require connectivity; photos and voice notes cannot certify an inspection or establish a regulatory reporting receipt.

Who can see a safety report?

Access follows the program’s reporting mode and recorded authority. Confidential handling restricts identity to authorized roles; anonymous intake has a separate identity boundary. Assigned EE personnel can see the material needed for their service role. Governed internal support and observability can use authorized content; training use has a separate policy. General customer administrators do not automatically inherit safety-case access.

Does using this service establish compliance?

The intended service supports operating an SMS and retaining reviewable evidence. Compliance depends on the organization’s applicable requirements, implemented processes, people and actual operation. The product itself is not an FAA or EASA approval, and it does not guarantee acceptance or safety outcomes.

How do onboarding, continuity and exit work?

We establish the approval scope, appointments, reporting channels, source imports, data reconciliation, retention and export needs before service starts. Coverage hours, response expectations, escalation routes and continuity arrangements are agreed for the engagement. Exit includes the agreed records and evidence export; no universal 24/7 coverage is implied.

The regulatory basis, made explicit.

Source review: 2026-10-23. Requirements and implementation timelines are applied to the actual organization; a planned product profile is not a regulator’s acceptance.

Start with your operation.
Build the safety loop around it.

Book a discovery call