SystemMulti-Site Manufacturing

Contract Manufacturer Oversight

Contract manufacturer oversight that tests each record a subcontractor sends against the quality agreement clause it serves, as the record arrives.

See one packaging record read clause by clause ↓
Watch with transcript →
The problem

An unapproved foil maker passed record review, and a lot reached the client

A contract giver stays responsible for what its contractors pack, test, store, launder and sterilize. The quality agreement says clause by clause who does what, but that table gets a close reading at the audit, and between audits a reviewer checks each record for its pages and signatures.

So a contractor can switch a material maker without notice, attach the new maker's certificate to an executed record, and declare no changes in its monthly report. The record looks complete, the lot is accepted and released on to the client, and the giver finds out at the next audit, months later, with lots already at the client.

Built forExternal manufacturing quality leadsQA headsQA record reviewersSupplier and contractor auditors

The Problem Today

Contractor records are checked for pages and signatures, while the clause each one serves goes unread until the audit.

62%
of 163 shortages began in manufacturing or quality, FDA published

Checked for pages and signatures

  • Records
  • Certificate
  • Reports
  • Notices
  • A maker not on the listThe certificate names a supplier the agreement never approved
  • A late notice nobody countsDays from a deviation to its written notice go unchecked against the clause

The Solution

  1. Each record read against its clausePages and certificates tested against the clauses due this quarter
  2. Makers set against the approved listEach certificate's maker compared with the appendix and the change log
  3. Earlier lots looked back overThe same material traced into lots already accepted and released
  4. Hold placed, then countersignedThe quality lead holds at once; the countersignature follows a reading of the reason and the certificate

Built-in controls

  • Holds start at once; lifting one takes two people
  • Requests leave in fixed fields
  • Free text from outside waits for a person

What You Get

Each agreement is checked against what the contractor actually sends, and a client hears of a change with its lots named.

  • Quiet changes found on arrivalAn unnotified maker shows on the first record that carries it
  • Clients told inside their clockThe notice the client agreement requires names each lot affected
  • Audits planned from the rowsNext year's visits and their focus come from what each contractor delivered
Features

Contract manufacturer oversight features, from record to client notice

A contract packager's executed packaging record arrives; the external manufacturing quality lead finds an unapproved foil maker, holds the lots, and the QA head countersigns before the client is told.

demoThe contractors, their lots and people, and the numbers shown are sample data.

  1. 01Responsibility table

    Contract manufacturer oversight on the agreement as written, clause by clause

    • Both parties' duties per clause. Each row shows what the giver does and what the contractor does, then this quarter's evidence and its status.
    • Met, late or missing, with the record. A late row shows both dates and a missing row says what was absent, so no lot is taken on an attached file alone.
    • Rows that need a person on top. The quality lead starts from the late and missing rows instead of reading the met ones again.
  2. 02Look-back

    Unnotified supplier change traced back through earlier lots

    • The same material in earlier lots. The look-back finds the earlier lot packed with the same foil, already accepted and released to the client.
    • Scope steered in plain words. The quality lead can widen the look-back to earlier months, and the agents' plan changes with it.
  3. 03Record page

    Packaging reconciliation recomputed from the contractor's own record page

    • Sums redone from the page. The clause matcher recomputes tablets and printed cartons from the page and sets the sum beside the clause's limit.
    • Pages as the contractor sent them. Each page appears as stored in the portal, with highlights where the agents read.
  4. 04Challenger

    The contractor's side argued, and the agents' own day count corrected

    • Arguments a contractor would make. Same specification, short supply, a phone call the next day: each is answered with the clause that still applies.
    • The agents' own miscount fixed. The draft counted calendar days where the clause counts business days, and the row now says how late the notice really was.
    • Settled only after reading the clause. A point stays open until its cited clause has been opened and read, and the reason names that source.
  5. 05Hold

    Hold acceptance of the contractor's lots at once, with a stated reason

    • Safer steps first. The hold takes effect as the quality lead signs; the QA head reviews it afterward, then countersigns or returns it.
    • A reason drawn from the findings. The reason names what was found: an unapproved maker, a missing notice, or both.
  6. 06Inbox

    Contractor records inbox, blocked where a clause row is missing

    • A record blocked by its own rows. A monthly report that declares no change stays blocked while the change row is missing, so nobody accepts it on its word.
    • Accepted only once opened. Records can be accepted only after being opened for the set time, and nothing is accepted in one click.
  7. 07Actions

    Stop-use instruction and a change file request in fixed fields

    • Stop use before the next run. The contractor is told to stop using the material and set the reels aside, then confirms the count in fixed fields.
    • Requests with fixed answers. First date used, lots, the contractor's own audit report and the change record come back as fields checked against the giver's records.
  8. 08Certificate

    Material certificate opened by the QA head before the countersignature

    • Two records opened first. Before countersigning, the quality lead's reason and then the certificate are opened, each counted as read after a short dwell.
    • The mismatch on the document itself. The maker printed on the certificate sits above the approved list's only maker, so the countersignature rests on the page.
  9. 09Client notice

    Client notice under the CDMO's own quality agreement, naming both lots

    • The client's clock from its agreement. The due date comes from the clause, counted from the day the CDMO became aware.
    • Written from approved sentences. Facts from the records fill the CDMO's approved sentences; the client quality liaison prepares the notice and the QA head signs.
    • Market decisions left to the client. The notice says the market status of lots the client holds is the client's decision under its agreement.

A hold's countersignature must come from someone other than its author

The quality lead owns the agreements and acts on them, reviewers accept records, the auditor plans visits from the rows, and countersignatures come from the QA head.

External manufacturing quality leads

Own each subcontractor's quality agreement and act on what its records show

  • Each clause with this quarter's evidence
  • Unnotified changes found on arrival
  • Holds and requests in one place
QA heads

Countersign holds, sign client notices, approve rules, plans and settings

  • The reason and the certificate opened first
  • Sign-offs queued with their clocks
  • No sign-off on their own proposals
QA record reviewers

Review and accept what contractors send

  • Records blocked by their own rows
  • Each record opened before acceptance
  • Contractor dates already counted
Supplier and contractor auditors

Plan contractor audits and propose the plan

  • Audit dates proposed from the rows
  • Past rulings kept as the agents' memory
  • For-cause visits where rows fail
More screens

The packager's next audit is proposed as a for-cause visit

Around the table: the contractors side by side, the audit plan, the QA head's queue, and the settings and trail behind them.

Five contractors, one way of oversightEach contractor with what it does, the plants and clients it serves, its agreement, this quarter's rows and its audit dates, ready to export.
Where to audit nextNext year's plan proposed from each contractor's rows and the rulings the agents remember; the auditor proposes it, and a different person, the QA head, approves.
The QA head's queueItems waiting for the QA head with their clocks; the client notice shows as not yours yet until the liaison has prepared it.
Countersign or send backWith both records read, the QA head countersigns or returns the hold with a reason; the hold stays in force either way.
Settings proposed, then approvedLook-back scope, read time, maker checks and retention change only on the QA head's approval; agreement clocks change only with a new agreement version.
The trail behind each decisionEach step, whoever took it, keeps its record, reason, stated meaning and run, and the trail exports to CSV with a separate evidence file.

demoSample data, from the working solution.

The client notice needs the liaison's preparation before the QA head signs

Signatures follow a named record opened first, and the trail keeps what each one means.

External manufacturing quality lead
Sees
The responsibility table, the challenge points and the cited clauses
Signs
Holds, stop-use instructions, requests and the rows shared with the contractor
QA head
Sees
The hold's reason and the material certificate
Signs
Countersignatures, client notices, rules, the audit plan and settings
Client quality liaison
Sees
The notice draft against the client agreement's clause
Signs
The notice as prepared, before it reaches the QA head
QA record reviewer
Sees
Each contractor record, opened for the set time
Signs
Acceptance of records whose rows are met
Supplier and contractor auditor
Sees
The quarter's rows for each contractor
Signs
The proposed audit plan

Releasing a held lot waits for the client's written approval of the new maker

Judging a material safeThe change spotter compares makers with the approved list; whether the material is acceptable stays with QA.
Releasing a holdNeeds the contractor's accepted answer and stop-use confirmation, the client's written approval, a change control to the approved list and a second person.
Sending to the clientThe notice drafter drafts; the client quality liaison prepares and the QA head signs.
Free text as an answerA contractor's comment waits for a person and never changes a field.
Approving a new makerA contractor's own audit of a maker never puts it on the approved list; that takes the giver's written approval.

The contractor's own certificate showed the change its monthly report denied

Records are read as contractors sent them, and each status on the table cites the page behind it.

Executed recordsPackaging records and certificates of conformance as the contractor sent them
Material certificatesCertificates from the contractor's own suppliers, with the maker named
Notices and monthly dataDeviation and change notices and monthly reports from each contractor
Agreements and change logsQuality agreements, approved-maker appendices and the contractor's change log
Audits and requestsPast audits and earlier requests with their answers
Client agreementsThe CDMO's own client clauses on subcontractor changes

What external manufacturing quality leads ask about oversight

What is contract manufacturer oversight?

Contract manufacturer oversight is the contract giver's continuing check that each contractor meets its quality agreement; EU GMP Chapter 7 asks the giver to monitor the acceptor's performance and review its records. Here agents test each record a contractor sends against the clause it serves, and people hold, countersign and sign.

Why does a contract giver stay responsible for outsourced activities under GMP?

FDA treats a contractor's facility as an extension of the owner's own, and the owner's quality unit approves or rejects what is made, packed or held under contract. ICH Q10 asks the owner to monitor the contract facility and to check that incoming materials come from approved sources through the agreed supply chain.

Who is the contract giver and who is the contract acceptor?

The giver outsources the work and stays responsible for it; the acceptor does the work under contract. A CDMO is an acceptor to its clients and a giver to its own subcontractors, which is the side this oversight covers.

How is an unnotified change at a contractor found?

The change spotter compares each maker, material, piece of equipment and site named in an arriving record with the approved list and the change log, then looks back over earlier lots for the same material.

What happens to lots that are already with the client?

They are named in the notice the CDMO's agreement with the client requires, inside its clock. Their market status is the client's decision; the CDMO holds acceptance of the contractor's lots it still controls.

Does CMO management software replace the contractor audit?

No. Audits still happen, but the plan for them is proposed from the rows, so a contractor whose evidence slips gets a for-cause visit and one whose rows hold keeps its interval.

Send us one agreement
and a month of records.

Share one subcontractor's quality agreement with the records it sent last month, and we will mark which of its clauses those records meet.