Regulations and compliance · Practical guide

Part 11: producing complete copies for inspection

An inspection copy must let the recipient understand and use the requested record. A successful download and a matching file count prove little about the contents. Identify the records, dates, versions and relationships needed, then check what the recipient can actually do with the export, including when several systems and file formats are involved.

Table of contents

At a glance

What should a complete Part 11 inspection copy contain and allow inspectors to do?

Section 11.10(b) requires the ability to generate accurate, complete human-readable and electronic copies for FDA inspection, review and copying. FDA’s 2003 guidance describes enforcement discretion for this requirement while leaving predicate-rule obligations in place. Give inspectors reasonable, useful access and preserve the record’s content and meaning. A PDF may be suitable, but the format does not demonstrate completeness.

  • Define export order based on record content and selection limit.
  • Identity, context, and usability in addition to the number are to be verified.
  • Consider FDA enforcement policies and existing recordkeeping obligations separately.

1. Translate the request into a clear scope

Retain clearly specified records for the relevant time period, batch, or test procedure requested. Clarify whether specific versions or additional information are required for proper understanding. A request for "all reports" is often overly vague when multiple report types and analysis statuses exist.

The article requires the specific FDA/Predicate Rule applicability. §211.180(c) requires the availability of required records or copies for authorized inspections in the relevant drug-CGMP area. The scope decision for Part 11 and the specific selection of an inspection copy are linked, but not the same task.

Sources: [1] [2] [3]

2. Assess separate readability and electronic use

§11.10(b) specifies both human-readable and electronic formats. A human-readable version supports understanding, while the electronic version may offer additional usage possibilities depending on the record type. What is essential is not to provide as many formats as possible, but to ensure appropriate access to the required content.

The FDA Guidance recommends, among other things, widely used portable formats and established conversion and export pathways. It cites PDF, XML, and SGML as examples. However, this does not imply that every PDF output is complete, nor that a specific file extension is mandated across all systems.

Sources: [1] [3]

3. Define the content of the release package

The following example laboratory test specifications cover four required laboratory tests: A1, A2, B1, and B2. The appropriate Drug-CGMP Laborscope is accepted. The specific data elements required must be derived in practice from the records and their relevance; not every technical log is automatically included.

Example: Proposed package for four laboratory tests
ComponentExpected statementCheck before handover
Readable reports A1, A2, B1, B2 Understand test results, units, relationship to the inspection procedure, and required confirmations. Full content visible; identifiers and status clearly defined.
Required electronic test data Underlying data and required dynamic properties are available. Appropriate access and assignment to the respective report available.
Necessary method- and calculation context Trace how the result was generated. Used stands and factors clearly assigned.
Relevant change/revision context Identify which changes and evaluations are relevant to the record. Association and temporal referencing remain clear.
Companion Package Description Explain scope, formats, and required reading aids. No ambiguous abbreviations or unexplained selection filters.

Sources: [4] [5] [1]

4. Verify the selection independently of the export counter

Establish an independent expectation for the requested record identities prior to export. A control report generated by the same faulty filter would not constitute strong counter-evidence. Therefore, compare the output against an appropriate reference, for example, a traceable procedure list.

In this example, four records are expected. All four identifiers are present, yet B2 shows only the static endpoint value. The evaluation context required for the requested inspection is not accessible from the package. Thus, while the number of records is correct, their usability for inspection purposes remains insufficient. The internal matrix separates this issue from missing records and an incorrect evaluation status; it does not prescribe any regulatory sample size.

Own export target matrix with intentional failures
OutputIndependently established expectationAssessmentConsequence
A1,A2,B1,B2 Exactly these four records Amount of identity correct; check content separately. Continue the content and usability review.
Four correct records; B2 only as static endpoint value Required evaluation context available for the requested review access The appropriate record volume does not yet establish sufficient inspection copy. Complete suitable readable or electronic display and check actual usability.
A1,A2,B1 Four required records The requested record is missing. Do not issue as a complete package.
Four correct IDs, but incorrect evaluation status for B2 For B2, the specified relevant status Number and IDs do not meet requirements for correct content. Update the source reference and reverify the affected edition.

Sources: [1] [5]

5. Test the access using the intended reading tools

Open the output package under the specified conditions and systematically verify the required functions. Are tables readable, characters and units correct, attachments accessible, and references clear? If specific software or a reader is required, its role in the deployment procedure must be defined.

The FDA Guidance addresses search, sort, and trend capabilities: Where such functions are available within the system, copies thereof shall be provided upon request, if reasonable and technically feasible. This is not a universal requirement to include every internal application function. For questions regarding official use, §11.10(b) mandates coordination with the regulatory authority.

Sources: [1] [3]

6. Maintain the required data context

In dynamic laboratory records, a static view of results may lose information or attributes that are essential for a complete original traceability. The FDA Data Integrity Guidance explicitly addresses this limitation. Determine which information is required for reconstructing the specific procedural sequence, and verify its retention during the export process.

Conversely, not every static record is unsuitable. Some devices generate a static original record. The appropriate question, therefore, is not "PDF or original software?" but rather whether the content and meaning of the required record are preserved and remain accessible using appropriate means. File size alone is not a measure of quality.

Sources: [5] [4] [2]

7. Do not use Enforcement Discretion as an exemption for exports

The 2003 FDA Scope Guidance outlines limited enforcement discretion for certain Part 11 copy requirements. At the same time, it requires reasonable and useful access during inspections and references existing predicate rules. A statement such as "We do not export anything by default" would not be covered thereby.

Document the relevant limits of the specific release pathway and assess alternative appropriate distribution methods. This may include access to human-readable records at the site using existing hardware and established procedures. The document does not establish a universal transfer service or a regulatory-standardized package for all inspections.

Sources: [3] [2]

8. Organize the handover as a controlled work step

A small team should first know who provides the technical clarification of the request, who performs the export, and who evaluates the completeness of the agreed scope. This internal role assignment does not require a universal additional QA signature. Responsibility must align with existing duties and the specific record in question.

Maintain a clear record of the actual version delivered and any defined limitations to ensure accurate traceability in subsequent inquiries. When changes are made to report templates, filters, or data models, assess whether the prior export documentation remains valid and applicable.

  • Define record types, time periods, identities, and relevant statuses.
  • Intended-use-driven planning for legible and electronic availability.
  • Include necessary metadata and relationships.
  • Compare to an independent expectation.
  • Check readability and required usability features.
  • Clarify technical limits transparently.
  • Maintain traceability of the supplied package and responsibilities.

Sources: [1] [2] [3]

Project experience and collaboration

Test the export against a specific inspection request

From a prepared inspection question, process owners and IT identify which records and relationships must be provided. An authorised colleague then tries to answer using only the output package. A complete, intelligible export may suffice. Missing history or analytical functionality may need an additional access route. We support selection and comparison and document the limits. A matching file count does not establish a complete answer to the underlying question.

Frequently asked questions about Copies for inspection

Does Part 11 require exclusively PDF copies?

No. §11.10(b) refers to human-readable and electronic copies. The FDA Guidance lists PDF only as one example among several format examples. Suitability depends on the required content and usability, not solely on a specific file extension.

Sources: [1] [3]

Is the correct number of exported records sufficient?

No. In addition to the number of records, verify identities, statuses, and required content. In the example for this article, all four expected records are present. However, for B2, the required evaluation context needed for the requested review is missing. Therefore, the correct number of records alone does not establish an appropriate inspection copy.

Sources: [1] [5]

Must we export all technical metadata?

Not generically every technical content. What is essential is the required information for understanding and reconstructing the specific record. Define this extent based on the activity and predicate rule. Important interrelationships must not be missing solely due to their technical storage.

Sources: [5] [4]

Must electronic copies always possess the same search functions?

The FDA Guidance recommends retaining existing search, sort, or trend capabilities if such features are reasonable and technically feasible. This condition is part of the stated requirement. A blanket requirement for every internal application function would exceed the scope of the described approach.

Sources: [3]

Can an inspection copy consist of multiple files?

An appropriate justification may require multiple interrelated components. Ensure their assignment and usability, for example, through a clear package description. The number of files is not an end in itself; the required content must be evaluable without ambiguous relationships or missing components.

Sources: [1] [5]

Does a static print suffice for laboratory instruments?

This depends on the type of original record. For certain dynamic data, a static printout may not capture all required attributes and information. The FDA outlines this limitation. Static original records, on the other hand, may be evaluated differently; a one-size-fits-all approach for all devices would be inappropriate.

Sources: [5]

What do we do with a proprietary format?

Review established, appropriate export options and the required reading tools. Determine which information or functionalities are retained. For questions regarding the regulatory authority to verify or copy the output, §11.10(b) explicitly mandates coordination with the FDA.

Sources: [1] [3]

Does the FDA Guidance from 2003 release any copying obligation?

No. The described enforcement policy there is limited, and Predicate Rules remain substantially applicable. The Guidance expects reasonable and useful access during an inspection. It is not a basis for a blanket exclusion of electronic availability or incomplete records.

Sources: [3] [2]

Is an inspection copy automatically an appropriate long-term archive?

This conclusion goes too far. A package generated in response to a specific inquiry may cover only a limited time period or scope. The long-term retention of all required records and the significance thereof requires a separate, justified evaluation.

Sources: [2] [3]

Which preparation helps a small and medium-sized enterprise (SME) the most?

A traceable sample export of a typical end-to-end process, featuring an independent selection list and documented readouts, serves as a practical workflow aid. Add a modified record. This reveals common gaps prior to the need for a time-sensitive actual release.

Sources: [1] [3] [5]

Sources and review date

Source date: 7 October 2026. eCFR notice period until 5 October 2026; separate consideration of binding regulatory text and non-binding FDA Guidance. Examples and tables are internal work aids and do not represent completed product testing.

  1. 21 CFR Part 11 – Electronic Records; Electronic SignatureseCFR display until 05.10.2026; §§11.1–11.300.
  2. 21 CFR §211.180 – General requirementseCFR availability up to 05.10.2026; specifically (c), (d) regarding availability and copies.
  3. FDA: Part 11 – Scope and ApplicationFinal guidance. The PDF is dated August 2003 and the status page September 2003. See sections I and III.A–C.
  4. 21 CFR §211.194 – Laboratory recordseCFR notice until 05.10.2026; paragraphs (a)(1)–(8), (b)–(e).
  5. FDA: Data Integrity and Compliance With Drug CGMP – Questions and AnswersFDA Data Integrity Q&A, December 2018: Questions 1(d), 9 and 10 regarding dynamic data and copies, as well as Question 17 concerning access to requested electronic records. The 2003 Scope Guidance is addressed separately.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Jointly develop the specific evidence process

We support you in establishing a traceable export and distribution process for your required records, with a focus on content, clear context, and practically verifiable handover.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Send a project enquiry Customer testimonials →