EPHOR · Training oversight and approvals

One shared record for training oversight and approvals.

Publish the training programme, coordinate inspector attendance and preserve the exact document revision behind each approval.

Email me the brochure (PDF · 1.4 MB)
Training managers, compliance teams and regulatory inspectorsIndependent product
EPHOR current interface with synthetic demonstration data
Keep the training programme visibleDemonstration data · Click to enlarge
An example workflow · EPHOR

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. 01

    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. 02

    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. 03

    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 ↗
Inside EPHOR

See the work, from start to finish.

Explore the current product interface with demonstration data. Open any screenshot for a closer look.

01 / EPHOR

Keep the training programme visible

Review scheduled sessions, instructors, locations, and changes in a shared list.

EPHOR current interface with synthetic demonstration data
Keep the training programme visibleDemonstration data · Click to enlarge
02 / EPHOR

Plan the programme together

Switch to the calendar to see the pattern of training and coordinate observation.

EPHOR current interface with synthetic demonstration data
Plan the programme togetherDemonstration data · Click to enlarge
03 / EPHOR

Follow the approval package

Track the document submission, its version, and the party responsible for the next decision.

EPHOR current interface with synthetic demonstration data
Follow the approval packageDemonstration data · Click to enlarge
Capabilities

The details that keep work moving.

Publish the training programme, coordinate inspector attendance and preserve the exact document revision behind each approval.

Publish the training programme

Use calendar and list views to publish session types, dates, instructors, locations and remote-observation options. Unsettled times can remain explicitly unconfirmed.

Preview before importing

Review a CSV import plan before committing it. Stable session references support updates when the programme changes.

Coordinate observation attendance

Keep inspector requests, operator acknowledgments, arrangements and confirmations attached to the training session.

Make schedule changes traceable

Preserve session versions and reconfirm attendance after material changes, so an old arrangement cannot silently become the new record.

Exchange approval packages

Either organization can prepare a request for the other to decide. Organize supporting PDFs in folders and review the package as a whole.

Keep the decision with its revision

Preserve file revisions, comments and decision history, with a downloadable approval certificate tied to the recorded outcome.

Share audit records

Publish audit PDFs, maintain their version history and retain the status of withdrawn or restored material.

Report oversight coverage

Export observation coverage and activity records to CSV or PDF, and keep organizational communication in the shared workspace.

Workflow & control

Structured access. Accountable decisions.

EPHOR makes coordination work accessible to people and authenticated tools while preserving the same record and permissions.

An authenticated MCP interface

Connected assistants can access implemented schedule, import, approval-package and comment tools through the EPHOR sign-in flow.

Recorded human decisions

An approval belongs to an authorized user and an exact package revision. Tool access does not create regulatory authority.

Changes that explain themselves

Session history, reconfirmation and package revisions make the reason for the next action visible to both organizations.

Evaluate EPHOR

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.

Questions & answers

Before you book a demo.

Does EPHOR require Aurora?

No. EPHOR is a standalone workspace for training oversight, observation coordination and approval records.

What happens when a training session changes?

EPHOR preserves the session history. Material changes trigger attendance reconfirmation so both organizations can review the new arrangements.

Can either organization request approval?

Yes. Either organization can prepare a package for the other to decide, or share material without requesting a decision.

Does EPHOR approve training automatically?

No. EPHOR records decisions made by authorized users and preserves the package revision behind each decision.

See EPHOR in action

Start with your workflow.

A focused walkthrough, with the people and decisions that matter to your team.

Request a demo