WorkflowAPI & Drug Substance

API Batch Production Record Review

A batch record review for drug substance plants that reads each API batch as its stages, redoes every yield and hold clock, reads the equipment logbooks and recovered-solvent lots beside the record, and hands QA only the entries that break a rule.

See one API batch reviewed screen by screen ↓
Watch with transcript →
The problem

The yield needs two pages, and the valve event sits in a reactor logbook

An API batch record is several stage records written across weeks by several shifts and handed to QA as one stack. The checks that matter cross pages: a stage yield needs a wet mass from one page and a loss on drying from another, and a hold clock starts on an isolation page and stops on the next stage's charge page. A page-by-page read finds the missing initials and leaves the cross-page arithmetic to a calculator and a long memory.

Logbooks, maintenance requests and recovered-solvent releases are separate records, opened only when the batch record points to them. A valve adjusted by hand during a cooling ramp can be written in the logbook and nowhere else, so it reaches no deviation, and the reactor fails the same way on a later batch.

Built forPlant QA headsQA batch record reviewersMSAT process engineersProduction shift supervisors

The Problem Today

QA reads each stage record page by page, while the event that matters is often written only in an equipment logbook.

164
FY2025 FDA drug citations of the production record review rule published

Checked by hand on each batch

  • Stages
  • Logbooks
  • Yields
  • Holds
  • Yields redone on a calculatorA sum built on an assumed value reads as right
  • Logbooks opened only on a hintA hand adjustment outside the record reaches no deviation

The Solution

  1. Each stage read side by sideOne reader per stage fills its column; nothing is marked before it is read
  2. Each sum redone and shownStage yields from the wet mass and the measured loss on drying
  3. The records around the recordLogbooks, maintenance requests and solvent lots read beside the batch
  4. QA decides, the QA head second-signsA reason and a meaning on each exception; a second signature on each Major

Built-in controls

  • No cell is marked before an agent has read its page
  • A challenger attacks what the agents cleared
  • Nobody signs or accepts their own work

What You Get

QA decides exceptions instead of reading pages, and each client receives a signed review it can check.

  • Clients read each decisionEvery exception, its decision and its state in the signed summary
  • Logbook signals reach investigationsA hand adjustment becomes evidence before the next batch runs
  • New reviewers check the hard sumsCross-stage yields shown with their pages, not carried in a head
Features

Batch record review of one five-stage API batch, exception by exception

The QA reviewer runs the agents, steers them to the maintenance records, decides each exception and hands the Majors to the plant QA head, up to a disposition that waits for each open item.

demoSample data: each batch, vessel, reviewer and figure, and both companies named on screen.

  1. 01Stage view

    API batch record review laid out as the synthesis, one column per stage

    • Seven rows under each stage. Charges, reaction checks, isolation, hold clocks, drying end point, solvents and equipment sit where the chemistry puts them.
    • Each intermediate carried forward. Each isolated intermediate's wet mass, molar yield and hold clock moves into the next stage, with the overall yield summed below.
    • Exceptions pinned to their cell. A Major, a calculation error or a GDP slip shows as a numbered marker on its line, and quiet cells still cite their pages.
  2. 02Steer

    Steering the agents mid-run toward every vessel's maintenance requests

    • A typed instruction becomes a step. A reviewer who knows a reactor's history asks for its maintenance records, and the plan grows a step marked as added by the reviewer.
    • Each steer kept in the trail. The instruction is logged with its time, so an inspector can see why the agents read what they read.
  3. 03Yield check

    Stage yield reconciliation from wet mass and the measured loss on drying

    • Mass and molar yield, each sum shown. Wet cake, dry basis and molar yield sit on the record page, so the reviewer checks the arithmetic instead of trusting it.
    • A right-looking figure still corrected. A yield worked on an assumed loss on drying goes back for correction with a second check even inside its range, and a person judges any yield deviation.
  4. 04Hold clock

    Hold time tracking from isolation to the next charge, against its study

    • A clock timed across two stage records. The hold starts on the isolation page and stops on the next stage's charge page, so an overrun split between two records is still caught.
    • Last time's ruling where it applies. The QA head's ruling on an earlier overrun sits beside this one, so a different reviewer reaches the same decision.
  5. 05Solvent lot

    Recovered solvent check against the lot's status at the moment of charge

    • Each recovered lot traced to its charge. Release, issue and charge times sit side by side, so a lot that went on hold between issue and charge stands out.
    • The agents' own clearance attacked. A lot cleared on its release record alone became a Major once the challenger asked its status when it went into the reactor.
  6. 06Logbook page

    Equipment logbook review beside the batch record, entry by entry

    • Each vessel's logbook read. A hand adjustment written only in the reactor logbook is set against a batch record that never mentions it.
    • The page as it looks on the floor. The reviewer reads the circled entry on the logbook page itself, and the opening is recorded under that reviewer's name.
  7. 07Historian trend

    Process historian cooling trend and the valve's history on one exception

    • The ramp against its allowed band. The trend shows whether the hand adjustment pushed the cooling rate out of its band, before anyone classifies the event.
    • Three signals before a failure. Two work orders and a no-fault-found request are listed with the valve's later failure, so the logbook event reaches the open investigation as evidence.
  8. 08Second signature

    Major deviations second-signed by a QA head who opened the page

    • Raised once its sources are open. The deviation goes in with the reviewer's reason code, and a safer decision such as this one takes effect on signing.
    • A second signer who read it. The plant QA head opens the logbook page personally before adding a second signature, and whoever decided can never second-sign.
    • Looser calls wait. Treating an entry as a correction or as no deviation counts only after the QA head's second signature on the reason as written.
  9. 09Disposition

    Batch disposition readiness that names each open item by record

    • The disposition button stays locked. The plant QA head sees the disposition blocked with its reasons listed, and the review itself never releases anything.
    • The client's qualified person releases. The plant QA head signs the batch's disposition; the client's qualified person decides for the medicine made from it.

The reviewer decides, the QA head second-signs, production answers by the box

Production answers by the box, MSAT reads the campaign, and only QA signs.

QA batch record reviewers

Review each batch production record before disposition and decide every exception

  • Only the entries that break a rule
  • Each sum shown with the pages behind it
  • Logbooks and solvent lots read beside the record
Plant QA heads

Add the second signature on Majors, approve learned rules and disposition the batch

  • Majors read on the page before signing
  • Disposition blocked while anything is open
  • A signed summary to send each client
Production shift supervisors

Answer each correction with a dated late entry or a deviation

  • The exact box and page to fix
  • Corrections sent together, accepted one by one
  • A typed value compared with the sum
MSAT process engineers

Watch yields and hold clocks across the campaign

  • Five batches side by side
  • Long hold clocks highlighted across the campaign
  • Rules proposed from trends, applied once QA approves

A challenger reopened a solvent lot the other agents had already cleared

The agents read, sum, time and challenge; the reviewer and the QA head decide.

Stage readers

Read each stage record against the master instructions, one reader per stage.

  • Never edits a record or fills a blank
Mass and yield reconciler

Redoes each stage's mass and molar yield from the wet mass and measured loss on drying.

  • Never decides a yield deviation
Hold-clock checker

Times each hold from isolation to the next charge against its hold-time study.

  • Never calls a hold beyond the study acceptable
Recovered-solvent checker

Checks each recovered-solvent lot's release, reuse cycle and status at the charge.

  • Never hides a clearance
Logbook and maintenance reader

Reads the logbooks, maintenance requests and historian trends of each vessel the batch used.

  • Never opens, closes or reopens a work request
Exception writer

Pins each exception to its cell with its rule, sources and a proposed action.

  • Never decides an exception
The inspector

Argues as an inspector would against the exceptions and, as hard, against what the agents cleared; the others answer or hand the point to a person.

  • Passes no point that has no answer
  • Never decides
Summary drafter

Drafts the client's summary from the signed review.

  • Never sends
  • Never puts one client's batches in another's summary

A valve adjusted by hand four days before it failed, found in the logbook

Four findings on one sample batch that a page-by-page read tends to pass.

A yield worked out on an assumed value

Stage 4 was written as 87.2% on an assumed 5.0% loss on drying; the measured 6.8% gives 85.6%, and both sit inside 82–90%.

A hold that ran across two records

The Stage 2 intermediate waited 73 h 45 min against a study that supports NMT 72 h, timed from its isolation page to the Stage 3 charge.

A hand adjustment only the logbook knew

The brine valve was slow to open at 21:40 and the cooling was adjusted by hand; it stuck on a later batch, and the entry is now evidence in that investigation.

Solvent from a held lot, already in the reactor

The agents first cleared the recovered THF on its release record; asked about its status at the charge, they re-marked it a Major.

demoSample data, from the working solution.

More screens

Four of five batches in the campaign held the intermediate over 60 hours

Past the one batch: a second product, the campaign, corrections in flight, the queue, learned rules and the trail.

A second product, six stages, its own limitsAnother client's six-stage active, on the same review under its own instructions: 7,410 entries read, a charge unit written as L, a Stage 6 yield rounded down.
Five batches of one campaign, side by sideHighlighting hold clocks over 60 h puts four of five batches above it, beside their stage yields and Impurity C.
Four corrections out, each with its pageOne signature sent four corrections at 09:30; each is accepted alone after the corrected page is opened, and any that cannot be corrected becomes a deviation.
The plant's queue, with its due clocksSix batches for two clients: one review two working days late, one partly read while two scanned pages wait for a rescan, one on hold.
A rule proposed by the agents, not yet in forceTwo rules in force from earlier QA rulings, and a proposed rule to read each vessel's logbooks and maintenance requests, waiting for the plant QA head.
Each source opened before the corrections wentEach record the reviewer opened, minute by minute, then the signed send and one line per correction; the trail downloads as CSV.

demoSample data, from the working solution.

Stage records, reactor logbooks, the historian and the solvent recovery log

Stage batch production recordsScanned paper and electronic stage records, read against the master instructions.
Master instructions and hold-time studiesExpected yields and hold, cooling and drying limits, from the approved versions.
Equipment logbooks and maintenance requestsUse, cleaning and repair entries for each vessel, centrifuge and dryer the batch touched.
Process historianTemperature and cooling-rate trends for the steps a logbook entry touches.
Recovered-solvent releases and lab reportsEach lot's tests, reuse cycle and status when it was charged.
Deviations and investigationsOpen records the batch may fall inside.

What QA reviewers ask about API batch record review

What is batch record review for an API?

Batch record review is the quality unit's check of each batch production record before an API batch is dispositioned, which ICH Q7 asks for on critical process steps. Here agents read the stage records and the logbooks, maintenance requests and solvent releases around them, redo the sums and leave QA only the entries that break a rule.

What belongs on a batch record review checklist for a drug substance?

Charges against their ranges and second-person checks, in-process results, yields at each isolated stage, hold times against their studies, allowed loops such as drying on, recovered-solvent lots, label reconciliation, GDP corrections and the equipment logbooks. Here the checklist is read from each product's own master instructions.

How is review by exception different from reading each page?

Each entry is still read and cited; what changes is who reads it first. A person decides the entries that break a rule, and items cleared by a rule, such as drying continued and re-tested, are listed with the rule instead of hidden.

Can it review paper and scanned batch records as well as electronic ones?

Yes. Stage records may be scanned paper, hybrid or electronic, and the logbooks, maintenance requests and solvent releases sit in other systems. A scanned page that cannot be read is marked as not read, and a rescan is asked for.

Does the review release the batch?

No. The review is signed only once each exception is decided and each correction accepted or raised as a deviation, and the plant QA head's disposition waits for the deviations, the linked investigation and release testing. The client's qualified person decides for the medicine made from it.

Which part of the review reaches the client?

A summary of the signed review for its own batches only, with each exception, its decision and its state, which the QA head opens before it is sent. A summary withdrawn after a later change stays listed as withdrawn.

Bring one batch record
and its reactor logbook.

Send one closed API batch record with its logbooks and solvent releases, and we will lay it out stage by stage and mark its exceptions.