--- title: "EPHOR Ai: Training Oversight & Approval Software" description: "EPHOR Ai is training oversight software for an airline and its aviation authority: inspector observations, training material approval, certificates of approval." canonical: https://www.flightatom.com/products/ephor.html last_updated: 2026-10-27 publisher: FlightAtom --- # EPHOR Ai · Training oversight and approval software: One record of what was observed, and exactly what was approved. EPHOR Ai lets an airline and its civil aviation authority run training oversight from one shared record: publish the training programme, arrange inspector observations, get course material approved, and keep instructors on the approved version. Each approval is pinned to the exact files reviewed and issued as a numbered certificate of approval that both organizations receive, and every decision is made by an authorized person and kept in an append-only history. [Request a demo of EPHOR Ai](https://www.flightatom.com/#demo-ephor) · [Explore EPHOR Ai](https://www.flightatom.com/products/ephor.html#product-tour) [Email me the brochure, EPHOR Ai](https://www.flightatom.com/resources/brochure.html#product=ephor&placement=hero) Airline training and compliance teams, instructors and civil aviation authority inspectors · Independent product · Fits your operation as it changes ![An EPHOR Ai Certificate of Approval with authorization number AUT-0007 and its record fingerprint (SHA-256). Recurrent CRM is approved under request APR-0007, version 2 of 2, requested by Demo Airline and approved by Demo Aviation Authority on 1 October 2026. Below are the statement that the approval applies to that version only, the authority's approval note and the airline's covering note, using synthetic demonstration data.](https://www.flightatom.com/products/screens/current/ephor-signature-20261011.webp) *Each approval issues a numbered certificate · Demonstration data* ## In brief: What is EPHOR Ai? EPHOR Ai is FlightAtom's training oversight and approval software, shared by an airline and its civil aviation authority. The operator publishes its training programme and submits course material; authority inspectors request observations, record attendance and outcomes, and approve or return what is submitted. Each approval is pinned to the exact file versions reviewed and issued as a numbered certificate of approval with a SHA-256 fingerprint for every file. - **Category:** Training oversight and approval software - **Built for:** Airline training and compliance teams, instructors and civil aviation authority inspectors - **Automation:** Oversight and approval workflow with append-only history; every decision is made by a person, not by AI - **Availability:** Available · independent product - **Fits your operation:** As your operation grows or changes, we adapt EPHOR Ai to fit, and you approve each change before it goes live. ## An example workflow · EPHOR Ai: Change the training plan. Keep the approval clear. An operator changes a training session after observation has been confirmed. The reviewer needs to see what changed and reconfirm attendance. 1. **Make the change visible** — Update the training session. A material change marks the observation as needing reconfirmation so the inspector can review it again. 2. **Review the current package** — In the separate approval workflow, submit a document package. The reviewer can request changes or record a decision against its exact revision. 3. **Keep the decision with the record** — Inspect the approval snapshot and history to establish what was reviewed, by whom, and at which revision. **The resulting record:** An updated observation record and a separate approval package, each retaining its changes and decisions. **The human decision:** The authorized reviewer makes the decision against the package revision and records any conditions or required changes. [Walk through this scenario with us](https://www.flightatom.com/#demo-ephor) ## How it works · EPHOR Ai: From course folder to certificate, version by version. Marking a course folder complete freezes it as a numbered version. When a person at the authority approves it, EPHOR Ai issues a certificate for that exact file set, and instructors see the course only while its current version is approved. 1. *Version 1 · Operator* · **Course folder frozen** · Demo Airline marks its recurrent CRM course folder complete, freezing its PDF, PowerPoint and Word files as version 1. 2. *Returned for changes* · **Returned with a note** · A Demo Aviation Authority inspector returns version 1 with a note on what to change. 3. *Version 2 · Operator* · **Revised deck resubmitted** · The airline replaces one slide deck and resubmits; the inspector sees which files were added, changed or removed since version 1. 4. *Approved* · **Certificate AUT-0007 issued** · The inspector approves version 2, and its certificate lists each file's SHA-256 fingerprint and both decisions, return and approval. 5. *Version 3 · Operator* · **Version 3 opened** · The course leaves the instructor library until the authority approves a new version; the version 2 approval and certificate stay on record. *Append-only* · **The record only grows** · Each step is a record event; record events, approval files, comments and certificates sit in tables that refuse edits and deletions. *Example with fictional organizations, course and certificate number: one training course's approval history, oldest entry first.* ## Inside EPHOR Ai: Follow the programme and the approval queue. These EPHOR Ai screens were captured in an isolated demo with neutral organization labels and synthetic records. Open a screenshot to inspect the workflow. ### Publish the training programme The month calendar an inspector sees after the airline publishes its training programme. Each session type has its own colour, and sessions without a confirmed time show as time TBC. Synthetic demonstration data. ![EPHOR Ai Training schedule in calendar view for October 2026, signed in as an authority inspector. A colour legend covers simulator, line training, line check, OPC, base training, ground school, recurrent, CRM, SEP, TTT and type rating sessions. Below it is a month grid of sessions published by Demo Airline, each showing a start time or 'time TBC', with synthetic demonstration data.](https://www.flightatom.com/products/screens/current/ephor-1-20261011.webp) *Publish the training programme · Demonstration data* ### Answer each observation request The airline's queue of observation requests from the authority. It holds a new in-person request to acknowledge, confirm or decline, one request being arranged, and a confirmed remote observation with its arrangements and a joining link that is kept out of email. Synthetic demonstration data. ![EPHOR Ai Observation requests screen for a Demo Airline administrator. Under Awaiting your response: an inspector's request to attend a simulator session in person, with Acknowledge, Confirm and send arrangements, Cannot host this session and Audit trail actions, and an OPC request over Microsoft Teams marked Being arranged. Under Confirmed: an OPC observation over Microsoft Teams listing the arrangements, access, a Demo Airline contact and an Open the meeting link, with a note that the link is kept out of email and the calendar feed, with synthetic demonstration data.](https://www.flightatom.com/products/screens/current/ephor-2-20261011.webp) *Answer each observation request · Demonstration data* ### Reconfirm after a session changes An inspector's observations that need attention. The airline changed two sessions after confirming them, so both now wait for re-confirmation. The airline could not host a third, and it gives a reason and suggests an alternative. Synthetic demonstration data. ![EPHOR Ai My observations screen for an authority inspector, under Needs your attention. A ground school observation and a simulator observation are marked Needs re-confirmation, with a notice that Demo Airline changed the session after confirming it and that re-confirming sends it back to be arranged again. Each shows its earlier arrangements and Re-confirm with Demo Airline and Withdraw buttons. A line check observation is marked Alternatives offered, with the reason No observer seat available, the airline's explanation suggesting another flight, and an Ask Demo Airline to reconsider button, with synthetic demonstration data.](https://www.flightatom.com/products/screens/current/ephor-3-20261011.webp) *Reconfirm after a session changes · Demonstration data* ### See what changed between versions An authority reviewer's view of a course folder whose second version is frozen and awaiting a decision. Version 2 is compared with version 1 file by file, with Approve and Return to pending buttons. Synthetic demonstration data. ![EPHOR Ai Training Material page for the Line check briefing folder, sent from Demo Airline to Demo Aviation Authority and marked Awaiting your decision. It shows the airline's covering note, a notice that version 2 is complete and frozen, and a version selector for v1 and v2. A What changed panel compares version 2 with version 1 (1 added, 1 updated, 1 removed, 2 unchanged) and lists the updated briefing slides, the added debrief form and the removed intervention notes, each with a link to the original. Approve and Return to pending buttons sit below, with synthetic demonstration data.](https://www.flightatom.com/products/screens/current/ephor-4-20261011.webp) *See what changed between versions · Demonstration data* ### Certificate of approval Page 1 of the numbered Certificate of Approval issued when the authority approved version 2 of a course. It shows who requested, submitted and approved the course, what the approval covers, and each approved file with its SHA-256 fingerprint. Synthetic demonstration data. ![Page 1 of an EPHOR Ai certificate PDF on a light grey ground. Under the EPHOR Ai wordmark and the line 'Shared training observation record — Demo Airline and the Demo Aviation Authority' is the title Certificate of Approval, followed by authorization number AUT-0007 and a record fingerprint (SHA-256). The certificate covers the Recurrent CRM course under request APR-0007, version 2 of 2, requested and submitted by Morgan Hale of Demo Airline and approved by Ines Varga of Demo Aviation Authority on 1 October 2026. Section 1 states that the approval applies to that version only, then gives the approval note and the covering note. Section 2 lists the course's Word, PowerPoint and PDF files with their sizes and SHA-256 fingerprints, with synthetic demonstration data.](https://www.flightatom.com/products/screens/current/ephor-5-20261011.webp) *Certificate of approval · Demonstration data* ### Instructors see approved courses only A flight instructor's library, limited to Training Material and Account. It lists only the course folders whose current version the authority has approved. Synthetic demonstration data. ![EPHOR Ai Training Material library signed in as a Demo Airline flight instructor, with only Training Material and Account in the sidebar. Course folder cards cover company indoctrination, Type A FFS recurrent, SEP wet drill, instructor standardisation, upset prevention and recovery, Recurrent CRM, dangerous goods awareness and cabin crew recurrent. Each card is marked Approved by the Authority and shows its file count, version, approval date, reference and an Open folder button, with synthetic demonstration data.](https://www.flightatom.com/products/screens/current/ephor-6-20261011.webp) *Instructors see approved courses only · Demonstration data* [Request a demo of EPHOR Ai](https://www.flightatom.com/#demo-ephor) · [Email me the brochure, EPHOR Ai](https://www.flightatom.com/resources/brochure.html#product=ephor&placement=product_tour) ## Capabilities: From the published programme to the certificate of approval. The operator's programme, the inspectors' observations, the course material and every decision sit on one record that both organizations work from. ### Prove exactly which version was approved Each approval issues a numbered certificate of approval as a PDF, listing every approved file with its SHA-256 fingerprint, the approver's note and the decision history. The certificate is stored unchanged, and the same PDF is emailed to both organizations. ### Keep instructors on the approved version Instructors see only the version of each course that the authority has currently approved. A course leaves their library as soon as a new revision opens, and the approval is checked again on every file download. Instructor accounts can open this library and change their own password, and EPHOR Ai refuses them everywhere else, even through a direct link. ### Arrange every observation on the record Inspectors ask to attend in person or over Microsoft Teams, with a warning if a colleague has already requested the session. The operator confirms with arrangements or chooses a reason it cannot host and explains it, the inspector can ask it to reconsider, and a request still waiting on the operator when the session runs is recorded as not accommodated. Teams joining links are shown only to the observing inspector and the operator, never in email, calendar feeds or exports. ### Reconfirm when a session changes Each change to a session is saved as a new version. A change to the date, time, session type, location, instructor or remote availability sends a confirmed observation back: the inspector reconfirms against the new version, the operator confirms the arrangements again, and both receive a before-and-after summary. A corrected note does not trigger this. ### Count only sessions that were observed The coverage report, in PDF or CSV, lists every session in the period and counts a session as observed only when an inspector was confirmed and attended. Open requests, requests the operator could not host or never confirmed, and reports still due are counted separately, with totals by inspector and by attendance mode. ### See what changed between versions Reviewers compare a course folder with any earlier version and see which files were added, changed or removed, and both organizations can comment on individual files. Operators submit PDF, PowerPoint and Word files, PDFs open inline, and EPHOR Ai refuses Office files that contain macros or embedded content. ### Publish the training programme Inspectors see the published programme in calendar and list views, from simulator, line check and OPC sessions to ground school, CRM, SEP and type rating training, and request to observe straight from it. Times can stay unconfirmed, each session states whether it can be observed remotely, and a CSV import is previewed row by row and cannot be committed until every error is fixed. ### Exchange approval packages both ways Either organization can open a request for the other to decide, or share files for information. Marking a request complete freezes its files as a numbered version, a request sent back must include a note on what needs to change, and the database refuses any request where one organization would both submit and approve. ### Keep both organizations informed Observation requests, confirmations and outcomes, approval submissions and decisions, and comments each email the other side once saved, and a failed email never blocks or undoes the record. Messages stay behind sign-in, with email saying only that one is waiting. The operator shares monthly audit PDFs, each with its version history, and both organizations get one PDF summary after each day with programme or approval changes. ## Workflow & control: Each step belongs to one side. Every step stays on the record. EPHOR Ai has no AI of its own. Its strength is what the server and database enforce: which organization may act at each step, which version a decision covers, and a history the database refuses to edit or delete. ### Each step belongs to one organization Inspectors request observations, the operator confirms them or explains why it cannot host, and only the observing inspector records the outcome. The server checks the organization on each of these actions, and the database refuses an approval request where one side would both submit and decide. ### History the database will not edit Record events, the audit trail, approval files, comments and certificates are kept in append-only tables that refuse edits and deletions, and the audit trail exports as CSV for any date range. Inside EPHOR Ai, the authority's downloads, report exports and sign-ins are internal events that operator users cannot see. ### Two-factor sign-in, for people and assistants Password sign-in always requires a six-digit code sent by email, and disabling an account ends its active sessions immediately. A local MCP connector lets a tool-using assistant list and edit training sessions, preview imports and work on approval requests, signed in as a person and limited to that person's permissions. ### Operational boundaries Each deployment is set up for one operator and its authority, including organization names, local time zone, sign-in method and email delivery, so adding another operator or authority is implementation work. The operator's administrators can also create and manage the authority's EPHOR Ai accounts, and each such action appears on the authority's own activity trail. Approval packages take PDF files; training material takes PDF, PowerPoint and Word files up to 25 MB; PowerPoint and Word previews are text only, and versions are compared by file rather than by page or slide. Conflict warnings inform inspectors but do not block a request. EPHOR Ai records decisions made by authorized people; it does not grant regulatory authority. ## Evaluate EPHOR Ai: Make the next step measurable. Agree a representative sample and a baseline from your current process. These are proposed evaluation measures, not published performance results. ### Bring a representative example A training session change and a document package with a revision. ### Inspect the complete workflow Inspect the operator and reviewer views, reconfirmation, and approval snapshot. ### Compare with your baseline Approval turnaround; revision queries; reconfirmation completeness. [How to structure an evaluation](https://www.flightatom.com/resources/evaluation-guide.html) · [Compare product responsibilities](https://www.flightatom.com/platform.html#compare) · [Deployment and data handling](https://www.flightatom.com/trust.html#deployment) ## Related reading: Go deeper on the workflow. - [Aviation training management software](https://www.flightatom.com/solutions/aviation-training-compliance-software.html) - [Training and recruitment products](https://www.flightatom.com/platform/competency.html) ## Questions & answers: Before you book a demo. ### How do inspectors request to observe a training session in EPHOR Ai? An inspector requests the session and asks to attend in person, over Microsoft Teams, or either way; Teams is offered only for sessions the operator has marked as observable remotely. The operator can acknowledge the request first, then confirms it with arrangements or chooses a reason it cannot host and explains it. Inspectors can follow their observations in a private calendar feed, where unconfirmed requests appear as tentative. After the session, only the observing inspector records attendance and the outcome. ### What happens when a training session changes? Each change to a session is saved as a new version. If the date, time, session type, location, instructor or remote availability changes, a confirmed observation goes back for reconfirmation against the new version, and the inspector and the operator receive a before-and-after summary. A corrected note does not trigger reconfirmation. Cancelling a session withdraws its observations and tells the inspectors. ### Can either organization request approval? Yes. The operator or the authority can open a request for the other to decide, or share files for information without a decision. The database refuses any request where one organization would both submit and approve. Marking a request complete freezes its files as a numbered version, and a request that is sent back must include a note on what needs to change. ### What does EPHOR Ai's certificate of approval contain? Each approval issues a numbered certificate of approval as a PDF. It lists every approved file with its SHA-256 fingerprint, the version approved, the approver's note and the decision history. The certificate is stored unchanged and emailed identically to the operator and the authority. ### Can instructors use course material before the authority approves it? No. Instructors see only the version of each course that the authority has currently approved. When the operator opens a new revision, the course leaves the instructor library until it is approved again, and the approval is checked again on every file download. ### How does EPHOR Ai count observation coverage? A session counts as observed only when an inspector was confirmed by the operator and attended. The coverage report lists every session in the period, leaves cancelled sessions out of the percentage, and counts open requests, requests the operator could not host or never confirmed, and reports still due separately. It exports as PDF or CSV. ### Does EPHOR Ai approve training automatically? No. EPHOR Ai has no AI and makes no decisions. Every confirmation, observation outcome, approval and return is recorded by an authorized person, and each approval stays attached to the exact file version it covers. ### Does EPHOR Ai require AURORA Ai? No. EPHOR Ai is a standalone workspace for training oversight, observation coordination and approval records between an operator and its authority. ### What happens to EPHOR Ai when our operation grows or changes? As your fleet, routes, rules or teams change, we adapt EPHOR Ai to match, and you approve each change before it goes live. ## See EPHOR Ai in action: Start with your workflow. A focused walkthrough, with the people and decisions that matter to your team. [Request a demo](https://www.flightatom.com/#demo-ephor) --- Source: https://www.flightatom.com/products/ephor.html Contact FlightAtom: hello@flightatom.com · Request a demo: https://www.flightatom.com/#contact