Controlled Printing in Pharma: Issue and Reconcile Copies

Controlled printing connects an authorized source revision to a specific permitted paper use and a documented disposition. A watermark alone does not control where a copy goes, whether its content printed correctly or whether it is still suitable after a revision becomes effective.

Use this procedure to design or assess printing from a pharmaceutical EDMS. It covers operational SOP copies, reference prints and blank forms, with separate treatment once a form contains recorded activity. The examples use fictional documents and records; they are not screenshots or results from a named system.

The regulatory discussion addresses US drug CGMP and EU human-medicine GMP. Your approved procedures must define actual roles, copy classes and retention. Numbered copies, receipt acknowledgments and expiry labels below are proposed control methods, not universal requirements to use a particular stamp or software product.

1. Classify the requested print before issuing it

Start with document ID, revision, current status, purpose, destination, requesting person and whether the paper will capture regulated data. “Print the SOP” is insufficient when the request could mean a controlled operational copy, training material or a draft for review.

If the requester cannot establish the class or intended use, stop issuance and obtain that information. A default “uncontrolled when printed” label does not make an operational need disappear.

For EU human-medicine GMP, the current Chapter 4, sections 4.1–4.3 addresses document controls, careful reproduction, identification, authorization and effective dates. The Commission's current index lists the January 2011 version; the PDF is revision 1, operational June 30, 2011. Sources were checked October 6, 2026.

2. Select the authorized source and permitted revision

Retrieve the source through the approved repository route. Confirm the exact ID, revision, status and applicability to the destination. An email attachment, local download or recently opened file is not proof that it is the authorized source.

Approval and effectiveness can be separate states. A newly approved procedure intended to become effective next week should not automatically replace today's operational instruction. If a future-effective revision is printed for training, identify that purpose and prevent it from being confused with an operational copy.

Record the basis for the choice in the issue record. If two locations legitimately operate under different approved transition dates, capture that location-specific authorization. Do not silently choose the numerically highest revision.

For US production/process procedures, 21 CFR 211.100 establishes relevant written-procedure and approval obligations. Batch documentation has more specific requirements: 211.188(a) addresses an accurate reproduction of the appropriate master record, checked, dated and signed. Do not extend that batch-record provision into a universal rule that every reference print requires the same handling.

3. Verify the physical output before release

Inspect the rendition through the actual printing path that will be used. Compare it with the authorized source for document identity, revision, page sequence, completeness, legibility, tables, figures, symbols and any required approval/signature information. A successful print-job notification only establishes that the job was processed.

Check the places where reproduction can change meaning: a cropped unit, missing negative sign, hidden table column, detached figure caption or blank page with an omitted continuation. Verify duplex orientation, scaling and page range where those settings affect the output. If the controlled design requires a complete packet, a manually selected subset must not be issued as the full procedure.

For an electronic record/signature within Part 11 scope, 11.50(b) includes the signature manifestations in its human-readable form. An approval badge visible in the EDMS does not establish that a printout carries the necessary information. Printing also does not prove that every underlying electronic record can be discarded.

If output is incomplete or ambiguous, hold the issue, investigate the rendition/print settings and verify a corrected output. Record spoiled copies according to the applicable process. Do not handwrite a correction onto the operational instruction merely to avoid producing the right authorized rendition.

4. Register and deliver the issued copy

Use the following register for an issued-copy process. Copy IDs can be generated by your EDMS or another controlled method. The ID needs to distinguish copies within the chosen process; a date alone may not distinguish multiple issues on the same day.

Deliver the packet to the stated destination and establish receipt when the process requires it. Reconcile extra copies and output left in the printer. A controlled issue log is incomplete if the operator prints three copies but records only the one handed over.

Define how recipients obtain replacements and report missing or damaged copies. Decide whether onward copying is permitted and how it is controlled. Labels such as “copy prohibited” communicate a rule; they do not technically prevent photocopying. The operating procedure and follow-up need to address that limitation.

5. Keep blank-form issuance separate from completed-record retention

Blank forms can become original records when personnel enter data. The controls must account for that transition. Define how users obtain additional pages, correct an erroneous entry, replace a damaged form and account for unused or spoiled issues.

FDA's December 2018 data-integrity guidance, Q6, discusses controlled blank forms, numbered sets where appropriate and reconciliation. It also addresses retaining incomplete or erroneous forms with justification for replacement. This is drug-CGMP guidance, not a mandate to serialize every piece of office paper. See the FDA guidance.

Once a form contains regulated activity, do not treat withdrawal of its template as authorization to destroy that completed record. A completed revision-4 form can remain a required record of what happened, even after revision 5 becomes the version to issue for future work.

The issue register should link used forms to the applicable record set or reconciliation evidence. Preserve the distinction between “removed from future use” and “disposed of after its required retention.” A destruction decision needs the applicable record/retention authority; it cannot follow automatically from an obsolete-template status.

6. Replace operational copies when the applicable revision changes

Use the change's approved implementation plan to determine which copies need replacement and when. Generate the affected-copy list from the register, verify the destinations and coordinate the handoff to the new authorized revision.

For each old operational copy, record its actual outcome: retrieved and withdrawn, replaced at its location, located but temporarily controlled under an authorized arrangement, or not accounted for. Keep a missing copy unresolved while its consequences are assessed. Issuing a new copy does not establish that the old one is gone.

If a location cannot confirm withdrawal, establish the immediate control for that location and notify the accountable process/quality owner. Assess whether the outdated instruction could still be used and whether any activity was affected. The appropriate response depends on the process and change; this article does not prescribe automatic shutdown or automatic continued use.

The documentary control should match reality. An EDMS status change cannot physically remove a paper copy from a workstation. Receipt/withdrawal evidence, location checks and recipient responsibilities connect the electronic change to paper use.

Worked example: one copy remains unaccounted for

Fictional Meridian Pharma issues a four-page SOP, M-210 revision 4, to two operational locations. Its approved plan makes revision 5 effective on Day 10. A separate associated form, M-210-F, also has a new template revision, while completed revision-4 forms remain records. These issue records and outcomes are illustrative.

The team cannot mark the change fully reconciled merely because both new packets were delivered. C-042 still has a missing disposition. It also cannot destroy F-018 to make the old revision disappear from its records: that row describes completed evidence, not an obsolete blank template.

Now change the starting input: the request says only “two copies of M-210,” with no destination or use. The procedure stops at classification. The operator needs to know whether these are operational instructions, training/reference materials or blank forms before choosing the issue controls.

A separate rendition failure also stops release: if revision 5 prints as three pages because a page range was retained from a previous job, the packet fails the defined four-page completeness check. Printing the correct revision number on the remaining pages does not cure the missing content.

Reconcile a replacement blank form without losing its predecessor

For a separate fictional issue, the register lists four blank forms, F-101 through F-104. The approved process requires every issued form to have an evidenced disposition. The return packet contains:

Two used plus one spoiled plus one unused accounts for all four original issues. If replacement F-105 is then issued for F-103, record a fifth issue, linked to F-103 and its justification. Do not overwrite F-103's identity or discard its entries. The reconciliation now needs five dispositions, including the eventual outcome of F-105.

If F-104's return evidence is missing, the first reconciliation has only three evidenced dispositions. Keep F-104 unresolved; do not infer its return from the fact that the activity needed only two completed forms. Counts expose the gap, while individual IDs establish which evidence is missing.

Verify closure and handle exceptional printing

Before closing an issue or replacement event, confirm that the register agrees with the physical/record state, required output checks are complete and each exception has an accountable disposition. Keep missing evidence distinct from a demonstrated failure. A recipient's unsupported recollection may identify the next person to ask, but does not automatically close a controlled withdrawal.

Plan downtime printing before the EDMS is unavailable. Identify the approved fallback source, how its revision/status will be checked, who can authorize issue and how events will later be reconciled. If the fallback cannot establish the correct operational instruction, escalate through the approved contingency process instead of guessing that an old local file is current.

When comparing software support, demonstrate the whole path: source selection, rendition, physical print, issue record and replacement evidence. Ask what remains a human responsibility after the print leaves the system. The appropriate assurance belongs to the configured process described in our computerized-system-validation guide, not to the word “controlled” in a print-menu option.