Skip to main content
📖 Flight Books & Manuals·3 min read

Creating a new manual version after a compliance update

Every approved compliance change creates an auditable trail. Flight Lyceum automatically versions your manuals so you always have a clear record of what changed, when, and who approved it.

Versions created automatically

When you approve an AI-generated update from the review queue, Flight Lyceum automatically creates a new version of the affected manual with the approved changes applied. You don't need to manually trigger this: it happens as part of the approval workflow.

Creating a manual version manually

You can also create a new version at any time to record a manual revision that you made outside the system.

  1. 1Open the manual in Flight Books.
  2. 2Click the version history icon (clock icon) in the top right.
  3. 3Click Save current version.
  4. 4Enter a version label (e.g. 'Rev 4.3') and optional change notes.
  5. 5Click Save.

Tip: Version labels are searchable, so use a consistent naming convention: the ISO date format (YYYY-MM-DD) or your school's existing revision numbering works well.

Viewing version history

Every manual has a complete version history accessible from its detail view. You can see the change log for each version, who approved it, and compare any two versions side-by-side.

Downloading a specific version

You can download any version of a manual: not just the current one. This is useful when you need to provide a specific revision to an authority or auditor.

  1. 1Open the manual's version history.
  2. 2Find the version you need.
  3. 3Click Download PDF next to that version.

Rolling back to a previous version

If an approved change needs to be reversed, you can roll back the manual to any previous version.

  1. 1Open the manual's version history.
  2. 2Click the version you want to restore.
  3. 3Click Restore this version.
  4. 4Confirm the rollback: this creates a new version that is identical to the selected one.

Note: Rolling back doesn't delete the intervening versions: they remain in the history. The rollback itself is recorded as a new version entry.

Was this article helpful?