How to verify a ProvenFlight logbook export
Every interview package and printed ledger carries a short export ID. What that ID proves, what it never shows, and how anyone holding the document looks it up.
In an airline interview, you need to be able to defend the numbers in your logbook. A clean logbook helps, and a document the reviewer can check for themselves helps more. Every ProvenFlight interview package and ledger PDF carries a short export ID, so a recruiter, a reviewer, or you can confirm the file is a real ProvenFlight document without anyone opening the logbook itself.
What gets printed
The cover and each page include a line in this shape: Export PF-XXXX-XX · verify at ProvenFlight.com/verify. The ID uses a character set that survives being read aloud or retyped from paper. The URL is the public lookup page, not a login. Your original records in a package carry the ID in a thin band below each page, so nothing is printed over them.
You get a new export ID every time you download an interview package or a ledger. Bring the printed copy, the file, or both. If someone asks where a total came from, the PDF already states the conversion method, and the ID lets them confirm the document itself.
If you are holding the PDF
Open ProvenFlight.com/verify, enter the ID from the cover or any page, and look up the record. You can paste the whole cover line; the page will pick out the ID.
A matching record confirms:
- That ProvenFlight issued this ID.
- The generation date.
- The name stamped on the document.
- Military or civilian view, layout, and conversion convention.
- The date range and flight count in that export.
- Whether the pilot digitally signed it at generation.
- A SHA-256 hash of the exact PDF that was issued.
- For an interview package, each original record it held, by title, page count and fingerprint.
The page never shows flights, hours, routes, file names, or the records themselves. Holding an export ID is not access to the logbook.
Checking the PDF file
If you have the PDF rather than a paper copy, hash it and compare the result with the SHA-256 on the verify page:
- macOS or Linux:
shasum -a 256 file.pdf - Windows:
certutil -hashfile file.pdf SHA256
A matching hash means this is the exact file ProvenFlight issued. A printout cannot be hashed; the record still confirms the ID, generation date, and stamped name on each page.
If the lookup finds no record
The page reports a missing ID the same way whether the code was mistyped, the document was not generated by ProvenFlight, or the generating account is no longer open. Verification records are deleted with the account. That is intentional: a closed account does not leave a public trail of name, date range, or flight count.
What this does not replace
An export ID checks the generated PDF. It does not replace ARMS, CAFRS, or other source records, and it does not change airline or FAA instructions. Use it next to the printed methodology and the totals bridge that explains military-to-civilian differences.
ProvenFlight does not submit applications, sign FAA forms, or attest that a reviewer's preferred conversion matches yours. The ID proves the document's origin and fingerprint. Defending the numbers is still the pilot's job, now with a page the other person can open independently.
How to use it in an interview package
- Download a current interview package after the logbook is reviewed.
- Keep the file and a printed copy with the export ID visible on every page.
- Keep the totals bridge and your official career summary in it, so differences are already itemized.
- If a reviewer wants to confirm the PDF, point them to ProvenFlight.com/verify and the ID on the cover.
See the binder guide for what goes behind each tab, the export formats page for every export, and the transition checklist for the records to gather first.