CMO CDMO Quality Systems: a Practical Buyer’s Guide

CMO CDMO quality systems connect the people, procedures, records, and decisions used to manufacture a drug under contract. For an owner’s quality lead, the central question is whether the contractor supplies enough reliable evidence to support oversight and disposition. For a contract manufacturer’s quality head, it is whether each owner’s expectations can be translated into executable responsibilities without compromising the site’s own quality authority.

Here, CMO means contract manufacturing organization; CDMO means contract development and manufacturing organization. These are working business labels, not substitutes for an activity map. This guide concerns commercial finished-drug manufacturing relationships. Development work should be identified separately rather than silently included in a commercial manufacturing agreement. The worked exercise concerns an ordinary tablet lot, not a product with specialized release provisions.

Binding law, nonbinding FDA guidance, and negotiated site practice answer different questions. Under 21 CFR 200.10(b), FDA regards extramural contract facilities as an extension of the manufacturer’s own facility. That does not make every recommended contractual provision a legal requirement.

FDA’s listing identifies Contract Manufacturing Arrangements for Drugs: Quality Agreements as final guidance issued in November 2016. The listing’s content-current date is 05/07/2020. The guidance states that it is not binding on FDA or the public. This article follows the relationship interfaces; the broader regulatory framework belongs in the Part 211 readiness guide.

Start with a jointly reviewed operation map. Identify the product, site address, operation, performing organization, governing procedure, resulting record, reviewer, and recipient. Include work that can disappear between organizational charts: receipt of owner-supplied materials, sample transfer, external testing, packaging reconciliation, storage, transport instructions, and follow-up after distribution. Mark exclusions explicitly. An owner supplying a method does not answer who performs testing or investigates a problematic result.

As site practice, use named roles rather than individual names in the responsibility map, then maintain a separate contact list with deputies. Give each activity an execution owner, a review authority, and a handoff output. Where both organizations participate, explain the division of work instead of putting ‘shared’ in every cell. Joint investigation, for example, might mean contractor-led equipment reconstruction and owner-led review of product history.

FDA’s nonbinding guidance recommends identifying the manufacturing sites and services, addressing materials management, and describing how product and process knowledge moves between the parties. Turn those topics into operating instructions. Identify the current product specifications, methods, manufacturing instructions, and known process concerns before work starts. Record who resolves conflicting versions and how revised instructions reach the people performing the operation.

Binding law also matters at execution: 21 CFR 211.100(b) requires production and process-control procedures to be followed and performance to be documented at the time. A responsibility map should therefore lead to actual instructions and records, not remain a presentation prepared only for the initial meeting.

Treat selection as a test of the proposed operations, not a comparison of polished quality manuals. The following evidence requests are recommended buyer practice. Adjust their depth to the product, operation, available history, and identified concerns. This guide does not prescribe an audit interval or a universal number of records to sample.

Ask the proposed site to explain a completed quality decision using appropriately controlled records. Look for a coherent account of what happened, who had authority, what evidence was available, and how follow-up was verified. A procedure is useful, but the ability to retrieve records and explain exceptions is a different form of evidence. Before exchanging confidential material, agree how representative or redacted records will remain technically intelligible.

Document the qualification decision with its boundaries. ‘Accepted for packaging at Site A’ is more useful than an unqualified statement that the organization is approved. Identify conditions, outstanding evidence, restrictions, and the person authorized to decide whether a gap prevents the proposed work. Distinguish a contractor’s promise to provide something later from evidence already reviewed.

If evaluating electronic systems, ask neutral workflow questions: can a reviewer find the underlying data, distinguish versions, identify decision authority, and retrieve a complete package? Can access be limited to the correct owner without concealing shared equipment information relevant to an investigation? These are evaluation questions, not claims that any particular software supplies the controls.

Binding law — 21 CFR 211.22 gives the quality control unit responsibility and authority to approve or reject specified materials and drug products, and authority to review production records for errors and their investigation. It expressly makes the QCU responsible for approving or rejecting drug products manufactured, processed, packed, or held under contract by another company. Its responsibilities and procedures must be written and followed. The same section addresses adequate laboratory facilities and QCU approval or rejection of procedures and specifications affecting product identity, strength, quality, and purity.

FDA’s nonbinding guidance explains the contract-facility role: ‘Contract facilities are responsible for approving or rejecting the product or results of their manufacturing operations (e.g., test results, finished dosage forms, or in-process materials).’ It separately identifies the owner’s responsibility for approving or rejecting drugs manufactured by the contract facility, including for final release. Write each party’s QCU role into its own procedures and the interface agreement; an owner signature does not replace the contractor’s quality decision.

For the ordinary finished-drug situation addressed here, 21 CFR 211.165(a) requires appropriate laboratory determination of satisfactory conformance to final specifications before release. Section 211.192 requires QCU review and approval of production and control records before a batch is released or distributed. Section 211.165(f) requires rejection of products failing established standards, specifications, or other relevant quality-control criteria. A quality agreement cannot turn a scheduled shipment date into evidence of acceptability.

As site practice, define the exact meaning of every status exchanged between organizations. Specify whether ‘approved’ describes a test report, completed packaging operations, or final lot disposition. Define dispatch permission separately, including who checks the approved quantity and destination. This discussion concerns dispatch for distribution, not every physical movement of material held under control. When the QCUs disagree, retain the applicable restriction and escalate the evidence question rather than seeking a commercial override.

FDA recommends a written quality agreement describing the parties’ respective CGMP-related activities. Its guidance also states that quality agreements cannot delegate statutory or regulatory responsibilities to comply with CGMP. The agreement should make the operating relationship understandable; it should not attempt to rewrite the applicable regulations.

The guidance recommends keeping quality agreements separate from, or at least severable from, commercial contracts. It recommends participation by quality-unit representatives and other relevant stakeholders. As implementation practice, let the people who will investigate, review, store, and retrieve records test the draft. Ask them to work through an incomplete package or a disputed change without relying on informal assurances.

The table is a neutral practice checklist, not a mandatory agreement template. Avoid filling it with identical answers such as ‘per SOP’ unless both parties can identify the relevant procedure and understand how changes to it will be communicated. Referenced documents need clear ownership, revision handling, and an agreed means of access.

Keep timing commitments specific enough to operate: what starts the clock, which role receives notice, what the initial notice contains, and how missing information is supplemented. Choose those commitments for the relationship rather than presenting them as statutory deadlines. The quality agreement glossary provides a shorter explanation of the document’s purpose.

Owner access and FDA inspection disclosure are related but different. Specify contractual access to the records needed for review and investigation; do not claim that 21 CFR 200.10(c) itself grants unrestricted owner access to everything at the contractor. The two relevant paragraphs read as follows.

Binding law — 21 CFR 200.10(c): ‘The Food and Drug Administration reserves the right to disclose to the pharmaceutical manufacturer, or to the applicant of a new drug application (NDA) or to the sponsor of an Investigational New Drug (IND) Application, any information obtained during the inspection of an extramural facility having a specific bearing on the compliance of the manufacturer's, applicant's, or sponsor's product with the Federal Food, Drug, and Cosmetic Act. The Food and Drug Administration's position is that by the acceptance of such contract work, the extramural facility authorizes such disclosures.’

Binding law — 21 CFR 200.10(d): ‘The Food and Drug Administration does not consider results of validation studies of analytical and assay methods and control procedures to be trade secrets that may be withheld from the drug manufacturer by the contracted extramural facility.’

FDA’s nonbinding guidance recommends procedures for communicating all contract-facility laboratory test results to the owner for evaluation in final disposition decisions. It also recommends defining document review, approval, maintenance, and inspection availability. As practice, distinguish routine delivery from deeper access triggered by a discrepancy. A certificate alone may not answer a question about the underlying result or investigation.

Section 211.180(c) addresses availability for authorized inspection at the establishment where the recorded activities occurred, including immediately retrievable electronic records. It is not interchangeable with a sponsor-access clause. As site practice, separately test whether the owner can receive and understand records in ordinary oversight, during an urgent investigation, and after the relationship ends. Where evidence cannot be shared in full, agree a review arrangement that preserves the relevant technical context rather than simply accepting a statement that it is confidential.

Binding law — 21 CFR 211.100(b) requires deviations from written procedures to be recorded and justified. Section 211.192 requires thorough investigation of unexplained discrepancies and specification failures, whether or not the batch has already been distributed. The investigation must extend to other batches of the same product and other products that may be associated with the failure or discrepancy. Its written record must include conclusions and follow-up.

As site practice, establish a common issue identifier or cross-reference the parties’ identifiers. The initial notification should state the facts currently known, affected or potentially affected material, immediate restrictions, records being preserved, and the next decision needed. Do not wait for a polished root-cause statement before telling the other party about an issue that may affect its decisions. The agreement should define the timing appropriate to that initial notice.

For laboratory-result investigations, FDA’s nonbinding guidance recommends assigning responsibility for investigating deviations, discrepancies, failures, out-of-specification results, and out-of-trend results, and sharing the reports. A practical division is for the testing site to reconstruct laboratory execution while the owner contributes product, method-transfer, and prior-history information. Neither contribution should be treated as an automatic conclusion about the cause.

Preserve original unfavorable results and explain the scientific question behind any proposed additional work. Do not use additional passing tests as a substitute for explaining a discrepancy. Before disposition, document the agreed investigation scope, conclusions, unresolved limitations, and follow-up. If the parties disagree about scope or interpretation, record that disagreement and escalate it; replacing one party’s report with a cleaner summary hides the interface problem instead of solving it.

FDA’s nonbinding guidance says either party may initiate changes and recommends outlining how all changes are managed. It distinguishes changes owners should review and approve before implementation from changes contractors may implement without notifying the owner. The agreement should make those categories intelligible for the particular relationship; a blanket statement that every change needs owner approval can be as unworkable as unrestricted contractor discretion.

Binding law — 21 CFR 211.100(a) requires production and process-control procedures, including changes, to be reviewed and approved by the appropriate organizational units and the QCU. Section 211.22(c) establishes QCU authority over procedures and specifications affecting identity, strength, quality, and purity. A contractual notification category does not remove those applicable approvals.

As practice, make each change assessment identify affected products, sites, equipment, documents, methods, materials, and open investigations. For a shared facility, assess the other owners and operations potentially affected without disclosing unrelated confidential information. State who evaluates necessary technical work, who supplies evidence, who approves implementation, and how completion is confirmed. Link the revised instruction to the point at which the new version becomes effective.

Notification, acknowledgement, approval, and implementation are four different events. Track them separately. A contractor should not interpret an unanswered email as agreement, and an owner should not assume that receiving a notice means the site has already made the change. Specify how a disagreement affects continuing operations and who decides whether existing conditions remain acceptable.

Apply the same clarity to subcontracting as recommended site practice. Identify the operation and physical site proposed for the subcontractor, qualification evidence, permitted delegation, result-reporting route, and access to investigation records. Establish who must agree before the work moves. The original contractor should be able to explain how the additional handoff changes its oversight and information flow, rather than simply describing the work as ‘outsourced’. Include a route for urgent contact when an issue originates at that additional site.

A relationship does not end at disposition. Binding law — 21 CFR 211.198 requires written procedures for handling written and oral drug-product complaints. Complaints involving possible specification failure require QCU review and a determination about investigation under 211.192. Complaint records must contain the prescribed information where known; where an investigation is not conducted, the record must include the reason and the responsible person’s name.

As site practice, define who receives a complaint, creates the file, contacts the other party, gathers manufacturing information, replies to the complainant, and coordinates any separately applicable reporting assessment. The owner may hold distribution context while the CMO holds packaging or production records. An effective intake route captures what is known without waiting for every field to be completed. Preserve the original description and distinguish it from later interpretations.

Binding law — 21 CFR 211.204 requires returned drug products to be identified and held. Where storage, shipping, or product and packaging conditions cast doubt on the specified quality attributes, the regulation requires destruction unless examination, testing, or other investigations prove the product meets appropriate standards. It also requires written procedures and return records, and an investigation under 211.192 if the reason for return implicates associated batches.

As practice, separate commercial credit from quality disposition of a return. Record the return’s lot, quantity, reason, condition information, location, and restriction status. Assign who can decide its disposition and who checks the implications for other material. A customer-service agreement to accept the return is not a quality decision to place it back into usable stock.

Link the complaint, return, and investigation records where they concern the same event, but do not collapse them into one vague ‘customer issue’. They answer different questions. Route the findings back to both parties’ relevant records and review activities, including any implications for change control, training, or future oversight.

FDA’s nonbinding guidance recommends that quality agreements cover routine and for-cause audits, inspections, communication of findings, and relevant FDA actions and correspondence. It also recognizes the need to address what a multi-owner contractor reports to each owner about objectionable conditions. Agree an information route that is relevant to the affected product rather than promising indiscriminate disclosure of every other customer’s records.

As practice, give each audit finding a responsible person, agreed action, target date, evidence expectation, and closure reviewer. A response letter is not necessarily closure evidence. Distinguish an immediate correction from action addressing recurrence, and identify how effectiveness will be evaluated when appropriate. Escalate overdue or inadequate responses according to their potential impact, not simply their age in a tracker. Let findings and changing circumstances inform future oversight without inventing a universal audit cycle.

Binding law — 21 CFR 211.180(e) requires records to support evaluation, at least annually, of each drug product’s quality standards and the need for changes to specifications or manufacturing or control procedures. The evaluation includes a representative number of approved and rejected batches, applicable associated records, and review of complaints, recalls, returned or salvaged products, and investigations under 211.192. The regulation does not set a single representative batch count for every relationship.

As practice, agree the review period, input owners, data definitions, transfer dates, reviewer, and route for decisions. Reconcile the owner’s complaint and distribution information with the contractor’s production and laboratory information. Explain missing periods, changed denominators, and differences in status definitions rather than combining incompatible summaries. Assign resulting actions back to named organizations and track completion. The annual evaluation and notification walkthrough carries the same evidence into that review.

Section 211.180(f) separately requires procedures for written notification of responsible officials, when they are not personally involved or immediately aware, about the investigations and other events specified there. Contractual communication and internal management notification should therefore be designed as connected but distinguishable routes.

Northfield owns tablet lot NF-R260601. Ridgeway manufactures, packages, and tests it at the agreed site. Their agreement requires initial notice of a potentially disposition-relevant deviation by the end of the next working day after discovery, with later supplements as evidence develops. Both parties have deputies. This local commitment does not justify delaying an urgent notification.

On 2 June 2026, Ridgeway finds a packaging reconciliation discrepancy and holds the lot. The packaging record accounts for 100,000 tablets issued: 990 acceptable bottles containing 100 tablets each, seven rejected filled bottles recorded on the reconciliation worksheet, 100 documented sample tablets, and 100 loose rejected tablets. The recorded total is 99,000 + 700 + 100 + 100 = 99,900 tablets. The unexplained difference is 100 tablets, or 100 ÷ 100,000 × 100 = 0.10% of the issued quantity.

Ridgeway notifies Northfield on 3 June, meeting the fictional next-working-day commitment. The notice identifies the discrepancy, hold, known quantities, and investigation leads. Together they define the investigation: Ridgeway checks physical rejects, the reject register, packaging records, and reconciliation execution; Northfield reviews relevant product history. The scope also covers the two earlier lots identified as using the same workflow, including another product. That scope is an invented case-specific choice, not a recommended sample count.

By 5 June, the investigation establishes that an eighth rejected filled bottle was already identified in the controlled reject area and recorded in the reject register, but its entry was omitted from the reconciliation worksheet. The correction preserves the original entry and explains the change. The corrected accounting is 99,000 + 800 + 100 + 100 = 100,000 tablets. Acceptable packaged tablets represent 99.0% of the issued quantity. Neither the balanced total nor that percentage independently establishes product acceptability.

By 8 June, the fictional investigation concludes, the earlier-lot review finds no corresponding discrepancy, the reconciliation instruction and reviewer check are corrected, and follow-up verification is documented. Required final testing and the other applicable reviews are complete with satisfactory results assumed for this exercise. On 9 June, Ridgeway’s QCU approves the product or results of its contracted operations. On 10 June, Northfield’s QCU separately approves final disposition of the 990 acceptable bottles. An authorized dispatch instruction is then issued, and those 990 bottles ship on 11 June. The eight rejected bottles do not join that shipment.

On 6 July, Northfield receives a complaint about a damaged closure on one bottle from that lot and routes it to Ridgeway. The bottle returns on 7 July and is identified and held. The joint investigation reviews packaging and shipment evidence and a documented handling incident after delivery. On 10 July, both quality functions review the finding that the incident explains this bottle’s damage and that the reviewed evidence does not implicate associated batches. Because the returned bottle’s subsequent storage conditions cannot establish its acceptability, it is destroyed. Northfield records its reply and closes the complaint with the investigation and return references. These are fictional evidentiary conclusions, not permission to presume that a later complaint is unrelated to manufacturing.

Binding law — 21 CFR 211.180(a) requires batch-associated production, control, and distribution records covered by Part 211 to be retained for at least one year after batch expiration. It specifies three years after distribution for certain qualifying OTC products without expiration dating. Paragraph (b) addresses component, container, closure, and labeling records, including the last-lot basis for that OTC exception. Paragraph (d) permits originals or true copies; a casual summary is not the same thing as an accurate reproduction.

Complaint retention has its own rule. Under 211.198(b), ordinary expiration-dated product complaint records are retained until at least one year after product expiration or one year after receipt of the complaint, whichever is longer. The paragraph also specifies retention for the qualifying OTC exception. Do not assume that closing a complaint or terminating the manufacturing contract starts a universal deletion clock.

As practice, create a record-location and retention map covering both organizations and any subcontractors. Identify the custodian, applicable retention trigger, retrieval method, readable format, and responsibility for preserving links between results, investigations, and decisions. Test whether an independent reviewer can understand a retrieved package without access to the original author. Coordinate owner-held product information with the contractor’s retention calculations.

Exit and transfer arrangements are recommended site practice, not a specific transfer procedure prescribed by the cited regulations. Before the relationship ends, inventory the records, agree originals-versus-copies handling, identify unresolved investigations and retained responsibilities, and verify transfer completeness and readability. Preserve the access needed for continuing retention and inspection obligations; transferring a copy does not automatically extinguish the originating site’s duties.

Finish with a documented handover: what moved, what remains, who can retrieve it, and who answers a future complaint or inspection-related request. A usable exit is the final test of whether the relationship depended on controlled responsibilities or personal goodwill. For a complementary view of evidence within a manufacturing operation, see the GMP manufacturing readiness guide.

Customer-owned stock creates two different boundaries: whose material may be used for a job, and whose information may be disclosed to a reviewer. Neither boundary can safely be inferred from a supplier lot code. A customer may own material that is unsuitable for its proposed use; a site quality reviewer may legitimately examine another customer's records without having commercial authority to divert that customer's stock.

Extend the existing operation map with receipt, reservation, issue, actual charge, unused return, sampling, waste, and record-sharing handoffs. For each, identify the executing role, evidence, reviewer, and recipient. Carry the separate decisions from quality authority through this map: a stock allocation, inventory correction, or accessible record is not a QCU disposition.

FDA's nonbinding 2016 quality-agreements guidance, section IV.B.1.c, recommends addressing inventory reconciliation and product status identification. That supports assigning responsibilities for these activities, not prescribing the particular data model above. The commercial ownership stipulations below do not adjudicate title transfer, bailment, payment, liability, or risk of loss.

In this fictional exercise, Owner A and Owner B have different commercial finished-drug oral-powder products manufactured at Site M. A owns receipt AR-101 and A's WIP; B owns receipt BR-102 and B's WIP. Manufacturer M owns receipt MR-103 and all unconsumed material and unused returns from it. M-origin material incorporated into A's or B's WIP is included in that WIP's stipulated ownership. Samples and waste remain attributed to their source owner. These are scenario assumptions, not conclusions about legal title.

All three receipts begin accepted for their specified uses. AR-101 and BR-102 are both material EX-17 from supplier S1, bearing supplier lot L-42, but they are separate holdings with separate receipt and container records. MR-103 is material EX-22 from supplier S2, also bearing lot L-42. M's EX-22 has separately documented suitability and commercial authorization for both jobs. That does not make the A-owned and B-owned EX-17 holdings interchangeable.

The table tracks only these two component materials, in kilograms, through jobs A-P01 and B-P01. It is not a total formulation or finished-product yield calculation. An issue is a gross movement to the job; a charge is actual process consumption into WIP. Samples are withdrawals from the issued component before charging, not additional product consumption. Unused returns are internal returns from the job, not market returns of finished drugs.

The issue reconciliation is 145 = 129 charged + 3 samples + 3 waste + 10 unused returns. Closing raw stock is 290 − 145 + 10 = 155. The complete component accounting is therefore 290 = 155 raw stock + 129 incorporated into WIP + 3 samples + 3 waste. A-P01 contains 71 kg of these tracked inputs, and B-P01 contains 58 kg; neither figure is the total batch weight. Samples are identified in laboratory custody and waste is identified in waste holding; neither is counted as usable raw stock, and no destruction is assumed.

Site M retains physical custody throughout. The 10 kg of unused returns is held pending review of identity, condition, and handling history, rather than automatically restored to usable stock. No issued component remains unaccounted for in job staging. A's original 65 kg reservation was reduced to the 60 kg actually issued, with the remaining 5 kg canceled in reservation amendment RA-02. The later reservations shown in the closing column are new planning commitments; none reduces physical stock or authorizes the next job to start.

Three events that test whether the ledger means what it says

1. Wrong-owner attempted issue: pick draft PI-A09 selected 12 kg from BR-102 for A-P01 after a search for L-42. The checker stopped the draft before weighing, movement, or posting because BR-102 belonged to B and was not authorized for A's job. The retained draft, checker note, location check, and issue-register review document the attempt and the absence of movement. Its ledger effect is zero—not a fictitious 12 kg issue followed by a fictitious return. A-P01 subsequently used the actual 60 kg issue from AR-101 shown above.
2. Quantity correction with evidence: closeout entry E-31 initially recorded A's unused return as 5 kg and waste as zero. That accounting balanced, but it disagreed with signed return weighing record RT-A01, showing 4 kg, and waste weighing record WW-A01, showing 1 kg. Linked correction E-34/C-02 reduces the recorded return by 1 kg and adds 1 kg to waste. It preserves E-31, identifies the transcription error, source records, author, entry time, reviewer, and affected reconciliation version. The final A raw-stock balance is 64 kg, not 65 kg. This is an accounting correction, not another physical movement or a quality disposition.
3. Revision and WIP decision: A-P01 was charged under the effective instruction revision 3. Owner A then supplied revision 4, changing the order of addition of EX-22. Site change assessment C-17 has not established applicability to the already charged WIP. A-P01 is not retrospectively relabeled as revision 4, and no further processing is authorized in the exercise. The site technical lead and A's process lead must assess the actual sequence and propose a supported continuation, rework, or rejection decision for the designated quality authorities. The 20 kg reservation for A-P02 remains planning only while effectivity is resolved.

These events extend change control rather than bypass it with a stock adjustment. The correction closes a quantity discrepancy only. The WIP decision still follows the quality-authority chapter, and the recipient-specific ledger extracts must follow the records-access arrangements. A manufacturer-owned pool may support two authorized jobs; customer-owned stock may not be silently borrowed merely because the materials look alike or the ledger can balance.

Use the same receipt, job, correction, and revision identifiers to test the records-and-data-access arrangements. Assign the test executor, record custodian, technical reviewer, and recipient in the operation map. Owner A's quality reviewer needs A's material history and the M-origin contribution to A's job, not B's inventory or M's unrelated allocations. Owner B needs the corresponding B evidence. A specifically authorized site quality reviewer needs cross-owner visibility for reconciliation and shared-equipment assessment; this does not imply unrestricted access for every site employee.

Treat four actions separately. View means examining a displayed record. Export means generating a report or structured extract, whose selection rules and hidden content may differ from the view. Download means obtaining a local copy of a file, including its attachments or embedded content. Handover means delivering an agreed record set with a manifest, revision context, missing-item statement, custody arrangements, and recipient acknowledgement. Permission or success for one action does not establish permission or success for the others.

FDA's nonbinding 2016 guidance recommends defining document review and approval expectations. It also recommends explaining communication about preventing cross-contamination and maintaining traceability at multi-owner facilities. Those responsibility themes do not prescribe the following access tests. The matrix uses synthetic records and invented observations; PASS means only that the stated fictional trial met its criterion, not that any application is secure or has the illustrated controls.

Protect unrelated information without hiding the shared-equipment question

B-P01 used mixer MX-7 before A-P01. CL-MX7-18 is the intervening changeover record. Its first page and a summary are available, but the missing second page contains the verification details needed for the current review. Site quality cannot establish from the available record whether that verification was performed and found satisfactory. An accessible summary therefore does not make the record package complete.

A controlled owner-facing derivative can remove unrelated order quantities and commercial details while preserving the sequence and evidence relevant to the owner's product. Keep a stable link to the controlled master and record what was withheld and why. If the prior product's identity or another normally restricted detail is technically necessary to assess cleaning or carryover, arrange appropriately authorized restricted review rather than replacing it with an unintelligible black box. Confidentiality review must not be used to hide an adverse result or a missing record.

Likewise, withdrawing a session changes future access through the routes actually controlled and tested. It does not recall exports, downloaded files, screenshots, printed material, or copies already handed over. Maintain a recipient and copy record and agree follow-up handling separately. A promise that an invitation can be removed is not evidence that prior copies have disappeared.

At this exercise's cutoff, the raw-stock ledger reconciles, but neither WIP batch has a final disposition. A-P01 remains held in MX-7, and B-P01 remains held in its identified WIP tote while site quality assesses the scope of the shared-equipment record gap. A-P01 also has the unresolved revision question. The following actions belong to distinct responsible roles; closing one item does not close the others.

Use the existing operation map to assign deputies and escalation recipients for these actions, and the records-access chapter to define how each party receives the resulting evidence. The quality-authority chapter governs the separate human decisions. An inventory correction may be complete while an investigation remains open; an access correction may be verified while the underlying quality record remains unknown. Neither arithmetic nor an access-test result supplies final disposition, dispatch permission, or legal clearance.