Inspection-Ready Document Retrieval: A Practice Exercise

Inspection-ready retrieval means producing the records that answer the request, with the correct identity, time context and supporting evidence. Finding today's SOP is not enough when the request concerns a procedure used months earlier. An exported file also needs a clear relationship to its source and to what the team actually supplied.

In this practice exercise, you will select a historical procedure, verify its approval and execution references, and prepare a response manifest. You can complete it using the supplied record cards in a blank document or spreadsheet. No EDMS account, production data or external download is needed.

This is a documentary tutorial, not a demonstration of a specific product interface. All practice records and names are invented. Primary regulatory sources were checked October 6, 2026. Completing the exercise does not establish inspection readiness for an actual organization.

Set up the practice request and record cards

Copy the following request into a new document headed Practice response RQ-12:

“

Provide the procedure effective on July 15, 2026 for the tray check, its approval evidence, and the execution record for practice lot LOT-77 showing which procedure was used.

The practice assumes one site, North, and one controlled procedure identity, SOP-12. Dates are calendar dates in that site's record convention. The exercise defines revision 3 as effective from January 10 through July 19, inclusive; revision 4 becomes effective July 20. There is no intraday boundary to infer here.

Create seven separate record cards by copying each table row into its own labeled section. The supplied content column is the complete content of each toy record; it is not an excerpt from an unavailable document. The cards are deliberately short so that you can inspect every relevant relationship. They are not operational manufacturing instructions.

Keep the cards unchanged during the first run. Create a separate working manifest with columns for request part, selected source, revision/date context, evidence checked, result and proposed response artifact. Do not put a check mark against a request part merely because a similarly named file exists.

Checkpoint: your workspace contains one request, seven cards and a blank manifest. You can read every toy input without logging into another system. This is the complete practice environment.

Step 1: Turn the request into three evidence questions

Write these three lines in the manifest:

1. Which SOP-12 revision was effective on July 15 at North?
2. Which record demonstrates approval of that revision?
3. Which execution record identifies what LOT-77 used?

The request is historical. It does not ask only for the latest procedure, every procedure version or every lot record. Preserving that distinction prevents an easy search result from changing the question.

In a real request, record the requester's wording, request identifier, date/time received, responsible coordinator and agreed scope. If “the applicable SOP” could mean current, effective on an activity date, or referenced by a specific execution record, resolve that ambiguity through the inspection coordinator. Continue identifying candidate records while leaving the ambiguous selection unresolved.

For US drug-CGMP records, 21 CFR 211.180(c) addresses ready availability during retention at the relevant establishment, including immediate electronic retrieval from another location. Paragraph (d) addresses originals or true copies. It does not establish a universal response-time number for this practice drill. 21 CFR 211.180.

Checkpoint: three evidence questions are recorded, and July 15 remains the selection date. No timing target has been invented as an FDA rule.

Step 2: Select by controlled identity and date

Compare cards A, C and F. All describe a tray check. Only A is the controlled revision whose effective interval includes July 15. Card C is current later in the exercise; card F has a convincing filename but the same later content without the controlled source relationship.

Select REG / SOP-12 / revision 3, using card G to corroborate the effective-history relationship. Record why C and F were excluded from this request part. Do not delete them or relabel them; they are useful evidence of what the search returned.

This selection uses the fixture's explicit effective dates, not the date a PDF was downloaded. Approval date, effective date, revision date and export date can differ. A document approved July 19 cannot be treated as effective July 15 merely because both events occurred in July.

In an EDMS, inspect the object identifier, revision, lifecycle state and effective history. If a display shows only Current, obtain the historical context rather than assuming older content never existed. A permission-limited search returning no result is also different from proof that a record is absent.

Checkpoint: the procedure row identifies card A, revision 3, with July 15 inside the supplied effective interval. A response using card C or F has failed this checkpoint even if the file opens correctly.

Step 3: Resolve approval and execution independently

Follow card A's approval reference to AP-3, card B. Compare the identity and revision in both cards. AP-4 is a real approval in the fixture, but it approves revision 4 and cannot authorize revision 3 by association with the same title.

Then inspect EX-77, card E. It names LOT-77, North, July 15, SOP-12 revision 3 and practice tray A. Those facts agree with the selected procedure. Record that agreement in the manifest without converting this toy check into a claim that an actual batch complied with all requirements.

Keep the evidence roles separate: the SOP states the instruction, the approval record establishes its decision history, and the execution record describes the activity. One cannot substitute for the others. A current SOP cannot prove what a historical operator actually used.

For EU human-medicines GMP, Chapter 4 requires document relationships and controls to be defined and addresses approval, effective dates and regular review to keep documents up to date. Its retention section also addresses locating records and protecting their integrity. These principles support attention to document context; this tutorial does not assess the separate veterinary framework. EU GMP Chapter 4, January 2011 revision, sections 4.1–4.5 and 4.10.

Checkpoint: the candidate response contains A, B and E. Card G supports the selection in the working evidence. No unexplained mismatch between revision, date or lot remains in the first run.

Step 4: Prepare a traceable copy and response manifest

Copy the complete text of A, B and E into three new sections named RQ-12-01, RQ-12-02 and RQ-12-03. Above each, label it “Practice response copy” and record its source card and controlled identity. Preserve the original toy content exactly. This makes the copy exercise executable without pretending to export a real EDMS file.

Compare each copy with its source card. Check that the full approval reference, effective interval and execution context remain present. Record the comparison in the manifest. A second participant can perform this check if available; if you are working alone, identify it as a self-check rather than inventing an independent reviewer.

Your completed first-run manifest should read as follows:

Add an overall state: Prepared for practice review; not delivered to an inspector. List A, B and E as the three proposed response records and G as working support. Do not call the three-record set Complete in a real inspection until it is checked against the actual request and any clarified scope.

FDA's 2003 Part 11 scope guidance recommends copies preserving record content and meaning and discusses useful access and feasible search/sort capability. A flattened PDF is therefore not automatically sufficient for every electronic record. Preserve necessary metadata and relationships for the particular request. FDA guidance, section III.C.4.

Checkpoint: the three response copies can be traced back to the supplied cards and understood without verbal explanation. No source record was changed to make the response appear consistent.

Step 5: Break the fixture and recognize an unresolved response

Duplicate your working document for a second run. Hide card B from the learner's available evidence and add this condition: “AP-3 access denied to the retrieval account.” Leave all other cards unchanged.

The correct procedure and execution selections remain A and E. The approval request part is now Unresolved: referenced approval not available to the current retrieval account. It is not Absent, Not required or Approved because the SOP says so. Record an access-resolution task for the authorized repository owner through the coordinator. Do not borrow someone else's credentials or substitute AP-4.

Restore access to B and repeat the identity comparison. The approval row can return to Verified once the evidence is actually available. Retain a note of the resolved access issue in the practice working record. This teaches a recoverable retrieval failure without changing the underlying historical record.

For a different failure, change only the practice copy RQ-12-01 to use card C. The reviewer should detect that July 15 precedes its July 20 effectiveness. Mark the proposed artifact Incorrect, rebuild it from A and repeat the copy comparison. Preserve the rejected practice artifact's disposition so there is no ambiguity about which candidate is current.

The causal error is selecting by today's status or filename instead of the requested date and controlled identity. Checking the wrong file's checksum more carefully would not correct it. The selection decision must be fixed before copy verification can pass.

Optional variation: the retrieved records genuinely disagree

Start a separate third run from the original cards. Replace only the exercise's card E with: “Practice lot LOT-77. Site North. Activity date July 15, 2026. Operator J. Reed recorded practice tray B checked under SOP-12 revision 4.” This is an intentionally altered toy input, not permission to modify a real execution record.

A and B still answer which revision was effective and approved for July 15. The replacement E now records use of a different revision. Keep all three responsive records and identify the discrepancy for the coordinator and responsible process owner; do not substitute C for A to make them agree, or change E to revision 3. Retrieval and faithful copying can succeed while the underlying activity remains unexplained. The packet alone cannot determine whether this was a recording error, unauthorized use or another cause. Record that interpretation as Unknown and route it for assessment. Reset E to its original content before repeating the first-run checkpoints.

Step 6: Separate internal preparation from authorized delivery

In actual inspection work, follow the coordinator's established response process and the inspector's request. Internal checking should support accurate, timely access; it must not become a reason to conceal responsive records or impose an invented delay. If evidence is missing or inaccessible, communicate its actual status through the responsible contact and keep the resolution visible.

Record the exact artifacts supplied, transmission or presentation method, recipient and time, plus any later corrected or supplementary response. A preparation manifest is not proof of delivery. A delivery receipt is not proof the inspector accepted the explanation or found no issue.

Clinical inspections also have distinct source-record and metadata considerations. FDA's October 2024 Revision 1 clinical electronic-systems guidance discusses reconstructing investigations and providing associated metadata/audit information. Do not assume the simplified SOP packet above is sufficient for clinical source data or that human-medicines GMP retention rules determine clinical retention. FDA clinical guidance, question 5.

For the practice exercise, stop at prepared copies and the verified manifest. Nothing should be sent outside the exercise. You have completed the lesson when you can explain the selection, detect the wrong-version case, retain the unresolved approval state and resolve it without rewriting history.

Turn the exercise into a useful readiness check

Repeat the pattern using an internally authorized non-sensitive fixture from your own environment. Include one historic revision, one unavailable record and one misleading current copy. Observe time to locate, verify and prepare separately. A fast search with a wrong version is a failure; a slow but correct result identifies a different improvement opportunity.

Record which delay arose from indexing, permissions, unclear ownership, unavailable history or export limitations. Those causes require different fixes. The audit-trail requirements guide helps with event interpretation; the document-control guide addresses the lifecycle producing those records.

Assyro publishes this tutorial. If you evaluate its document-management workflow, use the same historical-retrieval question and ask to inspect actual evidence in the configured product. No retrieval-time guarantee or automatic inspection-response capability is established here. Discuss the workflow with Assyro after defining the record relationship your team needs to retrieve.