A digital technical-record system can make routine access convenient while creating a difficult exit if records cannot be exported with their meaning intact. An aircraft owner should assess portability alongside features. The relevant asset is the usable technical history, including the context needed by authorised people who will read it after the supplier relationship ends.
Define a usable export
An export should identify the aircraft and components, the relevant events and the documents supporting them. Depending on the system and applicable requirements, signatures, links, corrections and revision history may also need preservation. FAA AC120-78B provides US guidance for electronic signatures, recordkeeping and manuals; the intended operation requires its own applicability assessment. A hypothetical download containing hundreds of unnamed attachments may preserve files while losing their relationship to the maintenance record. Ask the supplier to demonstrate an organised export that a qualified reviewer can navigate without relying on access to the original interface or undocumented staff knowledge.
Test departure while access works
Use a representative record set and ask an authorised reviewer to reconcile it outside the system. Include an amended record, a replaced component and a linked work package. The test should reveal what is lost or difficult to interpret. Agree the output format, frequency, delivery route and any charge before the contract is signed. Supplier claims about standard formats should be checked against the actual export. A portability test is especially valuable when one platform combines data from several custodians. Each contributing organisation’s rights, responsibilities and retention obligations still require examination rather than disappearing inside a shared dashboard.
Plan for interrupted access
Consider subscription expiry, an unresolved invoice, cyber disruption or the supplier ceasing service. Establish authorised backup arrangements and the process for restoring access without creating uncontrolled duplicate records. Updates need a clear source so a backup does not become an apparently current but incomplete history. FAA maintenance-record guidance reinforces the importance of the underlying record within its stated scope. The owner’s commercial concern is continuity: a change of operator or sale should not be held up because the parties discover that only one administrator knew how to extract the evidence required by the next technical reviewer.
Allocate the continuing obligation
The software contract should identify support, retention, exit assistance and responsibilities when data are corrected or migrated. Qualified advisers should review those terms alongside the operator’s actual recordkeeping arrangements. Estimate the cost of migration and validation rather than assuming it is included in a low subscription price. The investment decision can then compare convenience during service with the full cost of preserving the history. A successful exit test gives an owner concrete evidence that the record remains usable. It does not prove every entry is correct, so technical verification and supplier portability should continue as distinct controls.
