Part 147 · Available today (training engine)
Program catalogs
Your curriculum lives as a program → course → lesson hierarchy, so the catalog and the records share one structure instead of drifting apart in binders. It replaces the curriculum kept in binders that never match the records.
Launching the first quarter of 2027.
Illustrative — every screen reflects your own data.
Who it's for
An AMT school administrator who needs the curriculum and the student records to share one structure rather than drifting apart between a binder and a spreadsheet.
What it replaces
The curriculum kept in binders that never quite match the records.
What program catalogs gives you
- Program → course → lesson hierarchy mirroring your curriculum
- Catalog and records share one structure
- No curriculum in binders that never match the records
Curriculum as a program → course → lesson hierarchy
An AMT school's curriculum lives as a program → course → lesson hierarchy that mirrors the way the school already teaches it, so the catalog and the student records share one structure instead of drifting apart between a binder and a spreadsheet. Each lesson sits under its course, and each course under its program.
- Program → course → lesson hierarchy mirroring your curriculum
- Catalog and records share one structure
Records hang off the same tree
When a lesson belongs to a course and a course to a program, a student's record hangs off the same tree the curriculum is built from — there's no second copy to keep in sync. It replaces the curriculum kept in binders that never quite match the records, so the catalog and the records stay one structure instead of two.
- Student records hang off the same tree the catalog is built from
- No curriculum in binders that never match the records
How an operator uses this
An AMT school's curriculum lives as a program → course → lesson hierarchy that mirrors the way the school already teaches it, so the catalog and the student records share one structure instead of drifting apart between a binder and a spreadsheet. When a lesson belongs to a course and a course to a program, a student's record hangs off the same tree the curriculum is built from — there's no second copy to keep in sync. It replaces the curriculum kept in binders that never quite match the records.
Illustrative — every screen reflects what's in your own data, nothing more.
How it works
Program catalogs, step by step
Build the curriculum as a program → course → lesson hierarchy.
Each lesson sits under its course, and each course under its program.
Student records hang off the same tree the catalog is built from.
The catalog and the records stay one structure instead of two copies.
Questions
Program catalogs — frequently asked
Does the catalog mirror how we actually teach?
Yes. The curriculum is a program → course → lesson hierarchy, so the catalog mirrors the way the school already structures its courses rather than forcing a separate shape.
Do the records use the same structure as the catalog?
Yes. Student records hang off the same program → course → lesson tree the catalog is built from, so there's no second copy to keep in sync with binders.
Keep exploring
Other features in Part 147
Enrollments & progress
Per-student dashboards that update as lessons are logged.
Deep diveClassrooms & attendance
Classroom scheduling with per-session attendance against the roster.
Deep diveTraining records
Completion history built automatically; student portals show the same progress.
Deep diveAMTS cohorts
Class cohorts on a Planned → Active → Graduated lifecycle.
Deep diveCompetency tracking
Per-student, per-subject General / Airframe / Powerplant competency.
Deep diveGraduation records
A&P ratings awarded (Airframe, Powerplant, or both).
Deep diveEvery Part 147 workspace also includes the platform-wide backbone — logbook, credentials, compliance, reporting, and audit trail.
See the backboneSee program catalogs on your operation.
It's part of the Part 147 workspace. Request a demo or join the waitlist.