Keep the training programme visible
Review scheduled sessions, instructors, locations, and changes in a shared list.

Publish the training programme, coordinate inspector attendance and preserve the exact document revision behind each approval.
Email me the brochure (PDF · 1.4 MB)
An operator changes a training session after observation has been confirmed. The reviewer needs to see what changed and reconfirm attendance.
Update the training session. A material change marks the observation as needing reconfirmation so the inspector can review it again.
In the separate approval workflow, submit a document package. The reviewer can request changes or record a decision against its exact revision.
Inspect the approval snapshot and history to establish what was reviewed, by whom, and at which revision.
An updated observation record and a separate approval package, each retaining its changes and decisions.
The authorized reviewer makes the decision against the package revision and records any conditions or required changes.
Explore the current product interface with demonstration data. Open any screenshot for a closer look.
Review scheduled sessions, instructors, locations, and changes in a shared list.

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

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

Publish the training programme, coordinate inspector attendance and preserve the exact document revision behind each approval.
Use calendar and list views to publish session types, dates, instructors, locations and remote-observation options. Unsettled times can remain explicitly unconfirmed.
Review a CSV import plan before committing it. Stable session references support updates when the programme changes.
Keep inspector requests, operator acknowledgments, arrangements and confirmations attached to the training session.
Preserve session versions and reconfirm attendance after material changes, so an old arrangement cannot silently become the new record.
Either organization can prepare a request for the other to decide. Organize supporting PDFs in folders and review the package as a whole.
Preserve file revisions, comments and decision history, with a downloadable approval certificate tied to the recorded outcome.
Publish audit PDFs, maintain their version history and retain the status of withdrawn or restored material.
Export observation coverage and activity records to CSV or PDF, and keep organizational communication in the shared workspace.
EPHOR makes coordination work accessible to people and authenticated tools while preserving the same record and permissions.
Connected assistants can access implemented schedule, import, approval-package and comment tools through the EPHOR sign-in flow.
An approval belongs to an authorized user and an exact package revision. Tool access does not create regulatory authority.
Session history, reconfirmation and package revisions make the reason for the next action visible to both organizations.
Agree a representative sample and a baseline from your current process. These are proposed evaluation measures, not published performance results.
A training session change and a document package with a revision.
Inspect the operator and reviewer views, reconfirmation, and approval snapshot.
Approval turnaround; revision queries; reconfirmation completeness.
No. EPHOR is a standalone workspace for training oversight, observation coordination and approval records.
EPHOR preserves the session history. Material changes trigger attendance reconfirmation so both organizations can review the new arrangements.
Yes. Either organization can prepare a package for the other to decide, or share material without requesting a decision.
No. EPHOR records decisions made by authorized users and preserves the package revision behind each decision.
A focused walkthrough, with the people and decisions that matter to your team.