Answer the records request in one download.
An evidence package for a period and a scope, a release copy for a public request, or the whole program as one binder. Every document carries a code anyone can check, and every file in a package has its checksum in the manifest.
Read the full guide in the docs →
The answer exists before the question.
Used by safety and compliance managers, accountable managers, and whoever answers the regulator, the insurer or the customer.
Ready before anyone asks.
The record is written as the work happens, so the answer already exists.
Checkable without an account.
Anyone can check a document's code at rotorlab.app/verify.
Nothing quietly disappears.
Records are voided with a reason rather than erased, and an open legal hold stops disposal.
Every line of it, explained.
Real documents from a demonstration organization. Pick one, then click a numbered section to see what it shows and why the person reading it cares.
-
What it shows. Every file in the package is listed with its size and its checksum. Change one byte of one file and it no longer matches.
Where it comes fromWritten when the package is produced, over the files as they went in.
Why the reader caresThe recipient can confirm they hold exactly what was produced, with nothing but the package itself, and the package also carries plain instructions and a checker that runs offline.
-
What it shows. The flights, aircraft, defects, work orders, people, training, occurrences, authorizations, legal holds and disposals in the period and scope, as the organization filed them, corrections and voids included.
Where it comes fromRead from the records as they stand the moment the package is produced. Nothing is retyped.
Why the reader caresA regulator reads the primary record, with who filed it and when, rather than a slide about it.
-
What it shows. The same records as lists anyone can open in a spreadsheet, and as documents: the flight register and one maintenance log per aircraft, each PDF carrying its own document code.
Where it comes fromProduced from the records in the package, so the list, the document and the record agree.
Why the reader caresThe insurer files the PDF, the analyst sorts the list, and both can check the same code.
-
What it shows. The organization's activity log for the period, with the result of its chain check, and the independent timestamp proofs for the records that have been timestamped.
Where it comes fromThe activity log is written as people sign in, file, change, hold and release records. Timestamps are taken daily.
Why the reader caresA successor inherits a program whose history is intact, and an auditor can see when a record existed and that it was not altered afterwards.
-
What it shows. Aircraft in service, grounded now, condition unknown, on caution, and the flying in the period, each a number with its date.
Where it comes fromRead from the aircraft register and the flights at the moment the document is issued.
Why the reader caresThe first thing an accountable manager or a regulator reads: the state of the whole program, stated plainly and dated.
-
What it shows. Every member with their role, their currency standing, whether they were qualified for the flying they did, and their flights and time in the period.
Where it comes fromThe roster, the training sign-offs and the flights on record.
Why the reader caresWho flew and whether they were current when they did is the question every audit asks first.
-
What it shows. Current, renewal due soon, or lapsed, with the requirement named: here recurrent training for one member and recent flying for another.
Where it comes fromCredentials, training records and the organization's own currency rules.
Why the reader caresAn insurer would rather see a lapse stated by the organization than find it later. The document says it, and the organization answers for it.
-
What it shows. Every open defect with its severity, when it was reported and what it does to the aircraft: here a grounding defect that keeps an aircraft on the ground until it is rectified or deferred.
Where it comes fromDefects raised and graded in Maintenance.
Why the reader caresDefects are known, graded and acted on, which is what a regulator or an insurer wants to see before a loss, not after.
-
What it shows. The period the register covers, how many flights were flown in it and the flight time they add up to.
Where it comes fromThe flights filed in the period, by log upload, by the ground station or by hand.
Why the reader caresTotals a customer can tie to an invoice and an insurer can tie to a declared exposure.
-
What it shows. One row per flight and person on it, simulator sessions left out, crew time counted per person, times in h:mm so the rows add up to the totals.
Where it comes fromPrinted on every register, in the same words.
Why the reader caresThere is nothing to argue about later: the reader knows what was counted and how before reading a single row.
-
What it shows. The date, the flight number, the aircraft, the person and their duty, day or night, and the mission.
Where it comes fromEach row is a flight on the record, numbered, with its own page in RotorLab and its log where one is held.
Why the reader caresA regulator can point at any row and ask for that flight, and the organization can hand it over.
-
What it shows. Each person's time on the flight in h:mm, the whole flight unless a shorter time was recorded for them.
Where it comes fromThe flight's duration, read from its log when one is held and otherwise as entered.
Why the reader caresThe column sums to the total above it, so the reader can check the arithmetic on the page.
-
What it shows. The pilot, their organization and every credential they hold, with who issued it and when it expires. Personal details are masked in this excerpt.
Where it comes fromThe pilot's own details in RotorLab.
Why the reader caresAn employer, a chief pilot or an insurer sees who holds what, on the same page as the flying.
-
What it shows. Flights, flight time, sorties, landings and night flights for the period, and the page says the time is the sum of the rows below it.
Where it comes fromComputed from the flights in the period. Hours flown before the record began are shown apart, never folded in.
Why the reader caresA career total nobody can check is not a figure anyone should sign. This one can be checked row by row.
-
What it shows. How much of the time came from flight logs held, how much was entered by hand, and how many flights were entered more than a day after they were flown.
Where it comes fromEach flight knows whether a log backs it and when it was filed.
Why the reader caresThe reader sees the quality of the hours before trusting them, which is exactly the question an auditor would otherwise have to ask.
-
What it shows. The flights and h:mm this person logged in each duty: pilot in command here, and any other crew duty they were named for.
Where it comes fromThe crew recorded on each flight.
Why the reader caresPilot-in-command time is what a regulator counts, and it is separated from time as crew.
-
What it shows. Each requirement, whose rule it is (the regulation or the organization's own), its standing today and the detail: what is due, when, and what the last qualifying event was.
Where it comes fromCredentials, training sign-offs and the flights, read against the organization's rules on the day of issue.
Why the reader caresStanding is stated as at the issue date and says so, so a lapse last week is not buried inside a quarter's report.
-
What it shows. The aircraft's name, registration, serial and model.
Where it comes fromThe aircraft register.
Why the reader caresThe log belongs to one airframe. When the aircraft is sold, the log goes with it and the buyer can see what they are getting.
-
What it shows. The hours and flights on record, and how many of those hours came from flight logs held against hours entered by hand.
Where it comes fromThe flights filed on this aircraft.
Why the reader caresInspections count down from these hours, so the reader sees how well founded they are before reading what is due.
-
What it shows. Go, caution or no go as of the day the log was issued, and why: here a motor near its life limit.
Where it comes fromOpen defects, deferrals, the program and component life, read together.
Why the reader caresThe reading an inspector asks for by name, with the reason beside it rather than in someone's head.
-
What it shows. Every task in the aircraft's maintenance program with its kind and interval, in hours or months, and when it was last done.
Where it comes fromThe program set up for the aircraft in Maintenance, and the released records that complete each task.
Why the reader caresProof that a program exists and is being followed, which is what the regulator and the insurer both ask to see.
-
What it shows. For each task, when it is next due in hours or on a date, how much is left, and its state: in limits, approaching, due or overdue.
Where it comes fromThe interval against the hours and flights on record.
Why the reader caresA task past its limit is printed as overdue, and the same reading grounds the aircraft in the program status above.
-
What it shows. The public page at rotorlab.app/verify, open to anyone, no account and no upload.
Where it comes fromEvery PDF RotorLab issues prints its document code in its footer, and a package prints its code in its manifest.
Why the reader caresThe person who was handed the document does not have to take the sender's word for it.
-
What it shows. The code as printed on the document, typed in.
Where it comes fromThe footer of the PDF, or the manifest of a package. Masked in this excerpt.
Why the reader caresA code is short enough to read out over the phone and type on any device.
-
What it shows. The check runs on the page; the reader sends nothing but the code.
Where it comes fromRotorLab's own record of what it issued.
Why the reader caresA regulator, an insurer or a customer can do this in the meeting, on their own phone.
-
What it shows. Whether a document with this code was issued through RotorLab at all.
Where it comes fromThe code was recorded when the document was issued.
Why the reader caresA made-up code, or one typed wrong, says so plainly.
-
What it shows. The organization the document was issued for, its type, its title and when it was issued. Below this, the reader gives the page the file they were sent and it is compared, byte for byte, with what was issued.
Where it comes fromRotorLab's record of the issue, and the file the reader holds.
Why the reader caresThis is exactly what the check proves: that the document was issued, for whom, and that the copy in hand is byte for byte the file issued. It does not say the records behind it are true, and it is not a digital signature.
The documents are from a demonstration organization and the excerpts leave out their document codes. Yours carry a code on every page, checkable at rotorlab.app/verify.
From the request to a checked package.
The package is built from the records you already keep.
Log the request
Who asked, why, the period, the scope and when the answer is due.
Build the package
An evidence package or a release copy, assembled from the records.
Hand it over
One download, with a manifest and a checksum for every file.
They check it
At rotorlab.app/verify, with no account, any time.
What goes into a package.
The detail behind audit and evidence, as it works today.
For a period and a scope.
Requests logged with who asked, the request number and the due date.
The whole program.
Manual, frozen dossiers, declarations and registers in one archive.
Codes on every document.
Each PDF carries a code that opens its public check at rotorlab.app/verify.
A register of releases.
Everything the organization has handed out, newest first.
Hash-chained.
Sign-ins, changes, filings, holds and releases, searchable and exportable.
Anchored daily.
Records are timestamped daily by independent time-stamping services.
How the evidence holds up.
Stated plainly, so it can be checked.
| Integrity | A checksum for every file in a package or binder, listed in its manifest, with plain written steps to check it that need no account. |
|---|---|
| Activity log | Hash-chained: an entry removed or altered afterwards shows, and the package carries the result of the check. |
| Timestamping | Records are timestamped daily by independent time-stamping services, and the proofs travel with the package. |
| Retention | Your organization sets the only two scheduled removals: stored raw log files after the log window, and precise positions reduced to the rounded area after the position window. |
| Legal hold | By matter, covering an aircraft, a pilot, a job, a span of dates or every record. An open hold blocks disposal. |
| Public view | The verification page shows who a document was issued for, its type, title and date, and whether the file you hold is byte for byte a file issued under its code. |
Put your program on the record.
Talk to us about your fleet, or start a trial and file your first flight today.
