How to keep audit-ready records in a flight school

In most schools, audit preparation turns into a frantic document hunt that starts weeks in advance. But what an audit actually examines is not the number of documents — it is whether the same event looks the same across different records. The six rules below turn preparation from a project into a natural by-product of daily work.

1. Plan and actual should be two states of one record

This is where the most common inconsistency appears: the plan lives in one file and the completed flight in another logbook. When they are separate records, the difference can only be found by comparing them by hand.

The right structure makes the completed flight the updated state of the plan. When actual departure and arrival times are written into the plan’s own row, the difference between planned and actual becomes visible automatically, and two separate versions of reality never appear.

2. Enter the duration once and let it post itself

A flight’s duration must land in at least three places: the student’s total hours, the progress of the relevant exercise, and the aircraft’s utilisation record. Written by hand, those three eventually disagree.

Entering the duration in one place and deriving the other three from it is the easiest structure to explain in an audit. The answer to “where does this figure come from?” is the same record every time.

3. Check currency at planning time

A flight flown on an expired medical is a finding that cannot be corrected afterwards. That is why currency has to be checked while the plan is being saved, not on a report screen.

In practice that means: when a student is selected on the planning screen and their document is not valid, they cannot be selected, and the reason shows in the row. A warning is not enough — you need a block.

4. Show where each form is waiting, in one list

With evaluation forms, the problem is usually not the content but not knowing where the form is stuck. Has the instructor filled it in? Has the student approved it? Has management closed it?

Tracking the approval chain with a status field and listing everything pending in one place removes the “missing form” finding almost entirely.

5. Make changes traceable

Correcting a record afterwards is not a problem in itself. The problem is not knowing who changed what, and when.

An audit trail that keeps every change with its user, timestamp and old and new values turns corrections from something suspicious into an ordinary part of the process.

6. Make the output match the paper format

Most documents requested in an audit are presented in a familiar layout. Having the system’s output use the same column structure as the paper form makes the auditor’s job easier and removes the need for cross-referencing.

In short

Being audit-ready is not about completing a folder; it is about daily work producing consistent records on its own. Apply these six rules and the preparation phase stops being a separate job.