Close the evidence gap before closing the record
A missing page, an unexplained counter difference and an unreadable signature are different problems. Treat the gap as a controlled question with an owner and evidence path—not a blank field that must be filled at any cost.

Illustrative image—not evidence of a real case or verified capability.
Make the question small enough to answer
A note saying 'history missing' rarely tells the next person what to obtain. Identify the exact asset, relevant period, event and decision affected. Is the issue an absent removal record, an unreadable release document, a conflict between counters, or uncertainty about an installed configuration? Those questions need different evidence. Record what is present as carefully as what is missing, including source identity and the version received. EASA's published continuing-airworthiness review material discusses continuity, integrity and traceability of records. Use those as analytical questions here, not as a shortcut to declaring the records acceptable under a particular authority or operating arrangement.
Preserve the evidence before correcting it
Keep the received file or document linked to its sender, receipt date and relevant asset. If a clearer copy arrives, retain the relationship between versions instead of silently replacing the earlier file. A storage hash can help compare file bytes; it cannot prove that the issuing person had authority or that the content is true. Mark a transcription as a transcription and retain the source image. If a date or serial was entered incorrectly in an index, distinguish correcting that index from amending an underlying technical record. The responsible organisation's controlled process determines who may amend that record and how the original entry remains identifiable.
Follow a recoverable chain
Assign an owner to seek the missing evidence from the actual record holder or issuing organisation. Describe the requested event and identity precisely enough to avoid receiving another unrelated certificate. Track requests, responses and unsuccessful attempts without presenting silence as confirmation. A recovered record should explain where it came from and which part of the question it resolves. For life-limited or time-controlled items, determine the particular evidence requirement rather than imposing the same 'back-to-birth' demand on every nut, tool and consumable. IATA's public material distinguishes LLP and time-controlled-component documentation as a specific technical subject; the applicable requirement still needs a competent determination for the item and transaction.
Keep a calculation separate from a fact
When counters disagree, retain each value with its unit, basis date and source. Hours, cycles, time since new and time since overhaul are not interchangeable fields. A calculated estimate may assist investigation, but label its assumptions and uncertainty; do not write it back as an authoritative historical total simply to remove a warning. A hypothetical spreadsheet showing a difference between two dates is a starting point for reconciliation, not evidence that an aircraft or component accumulated exactly that amount. Record the decision, responsible reviewer, scope and unresolved limitations when the discrepancy is assessed. An unknown counter must remain unknown until the evidence and authorized process support a different status.
Close only the question actually resolved
The closing note should state which evidence answered which question and what remains outside the decision. A readable copy can close a legibility issue without closing a missing-history issue. A confirmed serial identity does not establish remaining life or installation eligibility. Keep any consequential hold connected to the unresolved point and the function responsible for reassessing it. For a first practical improvement, review a handful of real internal exceptions using this structure and ask whether another reviewer can follow the reasoning without a private explanation. The outcome sought is a reliable evidence trail, not a perfect-looking database that hides uncertainty or a platform badge that substitutes for technical authority.
Sources & scope
This is editorial educational analysis. Licensed manuals are not reproduced; Iranian applicability and independent technical approval are not established. Actual operations require current controlled sources and authorized decisions.
Continue with the Library tools
Related reading
On this page
Test the idea, not just your memory
Short learning scenarios with explained answers—not a qualification test, training certificate or operational decision.