The short answer is that auditors usually start with the records that let them reconstruct what work was done, who did it, what data and parts were used, what inspections occurred, and who approved return to service or maintenance release. They are generally looking for traceability, record completeness, and evidence that your documented system matches actual practice.
The exact records requested vary by authority, ratings, capabilities, product types, subcontracting model, and any prior findings. A line station, component shop, engine shop, and avionics repair operation will not all be sampled the same way. But in most Part 145 environments, the records most likely to be requested include:
Work package and job records: work orders, task cards, travelers, discrepancy records, inspection steps, sign-offs, dates, and labor entries.
Maintenance release or return-to-service records: the completed release documentation and the basis used to support it.
Approved maintenance data used for the work: revision-controlled manuals, instructions for continued airworthiness, repair data, engineering authorizations where applicable, and evidence the current version was available at the time of work.
Personnel qualification and authorization records: training, recurrent training, certifications where applicable, authorization rosters, and records showing who was permitted to perform, inspect, and approve work.
Tooling and test equipment records: calibration status, due dates, out-of-tolerance investigations where relevant, and evidence the equipment used was controlled.
Parts and material traceability records: receiving inspection, shelf-life control where relevant, batch or serial traceability, source documentation, and segregation of serviceable versus unserviceable material.
Component history and serialized records: removal/installation history, life-limited status where relevant, prior maintenance history available to the station, and tag or status documentation.
Nonconformance, rework, and corrective action records: discrepancy disposition, repair versus scrap decisions, concession or deviation control where allowed by your system, and evidence that corrective actions were implemented and closed.
Contract review and customer authorization records: evidence the work performed matched approved capability, customer scope, and any accepted limitations.
Supplier and subcontract process records: outside processing approvals, supplier controls, incoming acceptance, and how outsourced steps were traced back into the maintenance record.
Manuals, procedures, and change control records: current repair station manual procedures, revisions, distribution control, and evidence that changes were reviewed and implemented in a controlled way.
Training, occurrence, and internal oversight records: internal audits, remedial training, incident follow-up, and management actions tied to prior findings.
In practice, auditors are often less interested in the presence of a document than in whether the record set is internally consistent. They will often sample a completed job and test questions like these:
Does the work order match the capability and approved data used?
Were the people who performed and inspected the work authorized at that time?
Was the equipment used in calibration when the work was done?
Can installed parts be traced to acceptable source and receiving records?
Do discrepancies, rework, and inspections line up with the final release?
Do timestamps, signatures, and revisions make sense, or were records completed late or reconstructed?
Does the electronic system audit trail support the sequence shown on the paperwork?
That last point matters more in digital environments. If your MRO records are split across ERP, MRO software, QMS, document control, and spreadsheets, auditors may request records from several systems for one sample event. In brownfield operations, the issue is often not missing data but conflicting data, weak revision control, broken links between systems, or manual transcriptions that are hard to validate.
Certain conditions usually increase the chance that an auditor asks for more records or expands the sample:
Missing or illegible sign-offs
Backdated or bulk-entered transactions
Gaps in serial, batch, or lot traceability
Use of superseded maintenance data
Expired training or authorization records
Calibration lapses or unresolved out-of-tolerance events
Manual workarounds outside approved procedure
Inconsistent status tagging for parts or assemblies
Outsourced processing with weak evidence of control or acceptance
If those issues exist, the inspection can shift from document sampling to a broader review of your control system. That does not automatically determine an outcome, but it does increase the effort needed to explain and defend the record trail.
Electronic records are generally acceptable only to the extent that they are complete, attributable, retrievable, protected from uncontrolled change, and supported by your procedures and actual practice. A digital system does not reduce scrutiny by itself. In some shops it improves traceability; in others it exposes integration debt that paper had been hiding.
Full replacement of legacy systems is often not the practical answer in a regulated MRO environment. Many organizations run mixed platforms because replacing ERP, MRO, QMS, and document control systems at once creates qualification burden, validation cost, downtime risk, retraining effort, and new traceability gaps during transition. A more realistic approach is usually to tighten evidence trails across existing systems, define system-of-record ownership clearly, and control handoffs and change management.
A useful way to prepare is to pick several closed work orders and verify that a reviewer can move from intake through execution to release without asking for undocumented tribal knowledge. If that cannot be done quickly, your issue is usually retrieval discipline, integration quality, or record governance rather than lack of software.
At minimum, be ready to produce a coherent sample package showing:
the initiating work scope and discrepancy
the approved data used and its revision status
personnel authorization and training status
tooling and test equipment control
parts and material traceability
inspection and rework evidence
the final release decision and supporting sign-offs
No single checklist guarantees what an auditor will ask for, because surveillance focus and sampling differ. But if your organization can consistently produce those record sets, with clear traceability and controlled changes, you are usually prepared for the most common Part 145 inspection requests.
Whether you're managing 1 site or 100, Connect 981 adapts to your environment and scales with your needs—without the complexity of traditional systems.
Whether you're managing 1 site or 100, C-981 adapts to your environment and scales with your needs—without the complexity of traditional systems.
