WorkflowMulti-Site Manufacturing

Master Batch Record Authoring

The master batch record written from the client's own pages, every number threaded to its source, attacked by two challengers, and signed by the author, production, QA and the client.

Follow one client's tablet into the plant's record ↓
Watch with transcript →
The problem

Each reviewer rereads the client's package to check one number

When a client's product moves into the plant, an MSAT engineer opens the last similar master record and overwrites it step by step. Numbers are retyped from the client's documents, scaled by hand from the pilot bowl to the sub-lot and the batch, and equipment settings are checked from memory or a call to the line.

Production marks up what the machines cannot do, QA marks up missing yield limits and stale references, and the client is asked in free-text mail. Each round makes a new file. A parameter quietly changed to suit a pump, or a yield limit nobody wrote, surfaces at the first batch review, after the record has already been copied into a batch.

Built forMSAT process engineersProduction supervisorsQA documentation reviewersQA heads

The Problem Today

Engineers rewrite each client process for the plant's machines by hand, and each reviewer goes back to the sources to check a number.

9
contents a master record must hold, 21 CFR 211.186(b) published
2
signatures, one to prepare and one to check, 21 CFR 211.186(a) published

Retyped and checked by hand

  • Client docs
  • Equipment
  • Yields
  • Emails
  • A client's rate bent to fit a pumpYet the client approves any change to its own process
  • No trail from a number to its pageEach revision is checked against the sources again

The Solution

  1. Drafted from the client's own pagesEach step in the plant's style, from the process description and development report
  2. A thread on each valueEach number linked to the sentence, table or qualified range behind it
  3. Read as the operator and as QATwo challengers attack the draft and flag the agents' own slips
  4. Asked of the client, not changedA process change goes back as a question in fields, with evidence attached

Built-in controls

  • No number without the page it came from
  • Each signer opens what they sign for
  • A change after signing clears all signatures

What You Get

Each client process reaches its first batch as the client wrote it, in the plant's own wording, ready to check by thread.

  • Process questions settled in the draftA rate the line cannot run is answered before the engineering batch
  • New authors draft like the bestApproved reviewer rulings become the plant's drafting rules
  • Clients see their process keptEach number traced to their page, each change asked, never made
Features

Master batch record features, from the client's pages to four signatures

An MSAT engineer turns a client's film-coated tablet into the plant's master record for an engineering batch, while production, QA and the client's tech transfer manager sign in turn.

demoThe CDMO, its client, the people, products, documents and figures are sample data.

  1. 01Drafting table

    Master batch record authoring from the client's process description

    • Client pages beside the plant's record. The process description, development report and pilot record sit on the left as written, so each step is drafted against the page it comes from.
    • Written in the plant's own style. Steps follow the plant's record structure, current SOPs and approved drafting rules, so a new author's draft reads like the plant's best records.
  2. 02Source threads

    A source thread from every number to its page, table or qualified range

    • One click from number to passage. Selecting a step draws a line from each value to its highlighted sentence, table or range, so reviewers follow threads instead of rereading the package.
    • Qualified ranges from the plant's reports. Equipment settings are threaded to the qualification report that bounds them, never to memory or a call to the line.
    • Unsourced shown as unsourced. A value the sourcer cannot place is marked in place, and a hand-typed edit is flagged until a person reads it.
  3. 03Challengers

    Operator and QA challengers that read the draft before any reviewer does

    • The operator's reading of each step. The operator challenger reads each step as the person at the machine would, citing the client's page and the plant's qualification side by side.
    • The QA reviewer's reading of each line. The QA challenger asks where the yield limits and the calculated excess are, gaps that otherwise wait for the first batch review.
    • The agents' own errors labeled. Each point says when the slip was the agents' own, so the author knows which part of the draft to read hardest.
  4. 04Master formula

    Master formula record threaded line by line to the client's formula

    • Per core and per batch side by side. Milligrams per core and kilograms per batch are threaded to the client's own table, so a scale slip shows as a thread that does not land.
    • Binder water listed, then dried off. The binder's purified water sits on the formula marked removed in drying, so nobody counts it in the dried granule's weight.
  5. 05Rule check

    21 CFR 211.186 and EU GMP Chapter 4 checked on the draft itself

    • Each required content as a line. Each item of 211.186(b) and the two signatures of 211.186(a) is a line linked to the block or step that meets it.
    • Manufacturing formula and processing instructions. EU GMP 4.17 and 4.18 are read on the same draft, so the plant keeps one record for both rule sets.
  6. 06Client question

    Structured questions to the client instead of changing its process

    • The agents never bend a parameter. When a client's rate sits outside what a pump is qualified for, the step waits and a question is drafted, and the process stays the client's.
    • Fields instead of an email thread. The rate to use, the allowed range, a basis from a list and a required attachment come back in fields the record can thread.
    • Sent by the author, on the agreement's clock. Only the author sends it, and the due date follows the answer time the quality agreement sets.
  7. 07Client portal

    A client portal where the transfer manager answers in fields, with evidence

    • The client sees its own transfer. The client's tech transfer manager answers and later approves the record in the portal, while the plant's internal screens stay closed.
    • No answer without its study. The answer cannot be sent without an attachment, so a rate change rests on the client's development data.
  8. 08Rewritten step

    Step rewritten from the client's answer fields once the author accepts

    • Accepted only after the study is opened. The author must open the attached study before accepting, so no client evidence is taken unread.
    • Re-checked against the pump. The equipment fitter re-checks the answered range against the pump's qualification, and an answer still outside it keeps the step waiting.
    • A new version, compared. The record moves up a version, and the change shows beside earlier drafts and the client's pilot record.
  9. 09Sign-off

    Production and QA review of each step before a new record is approved

    • No sampling on a new record. Production opens all steps, then QA opens the formula and all steps, before either may sign.
    • Signatures that state their meaning. QA's approval says what the record may be used for, such as the engineering batch only, and later uses wait for their own approval.
    • Issue blocked until the floor is ready. The issue panel lists what still stands, from the client's approval to tooling, so nobody prints a record the plant cannot run yet.

QA reads the record only after production signs that the line can run it

MSAT owns the words, the floor owns what is possible, and QA owns the meaning of the approval.

MSAT process engineers

Write each new master record and revision from the client's package

  • A full draft with its numbers threaded
  • Questions to the client drafted in fields
  • Threaded steps accepted after opening a sample
Production supervisors

Review each record for what the line can really run

  • Steps read first as an operator would
  • Pump and machine ranges cited, not remembered
  • A review QA must wait for
QA documentation reviewers

Independently check and approve master records with a stated meaning

  • Yield limits and excess checked against the rule
  • Threads to follow instead of pages to reread
  • Signatures cleared by any later change
QA heads

Approve drafting rules and any loosened setting

  • Reviewer habits turned into rules only on approval
  • One way of drafting across plants and clients
  • Each signature's meaning on the audit trail

A send-back from the client clears every signature the plant has given

MSAT author
Sees
The threads, the sampled steps and the client's answer with its study
Signs
Prepared: written from the cited sources
Production supervisor
Sees
All steps of a new record, on the plant's own equipment
Signs
Reviewed: the plant can run this as written
QA documentation reviewer
Sees
The formula and all steps, once production has signed
Signs
Approval with a meaning that limits use, such as the engineering batch only
Client tech transfer manager
Sees
The record itself, opened before approving
Signs
Approval under the quality agreement, or a send-back that clears the plant's signatures
QA head
Sees
A reviewer's ruling and the steps it would rewrite
Signs
Approval of a drafting rule or of a loosened setting
More screens

Only the author's own acceptance is sampled; reviewers open all of them

How the draft is accepted, compared and governed once the agents have finished writing.

The author's acceptance, by sampleThe author opens two sampled steps for three seconds each before one acceptance covers 45 threaded steps; a step waiting on the client is left out.
A critical step with a stop ruleWet massing stops on the impeller power plateau or at 3.0 min at the latest, each limit threaded to the plant SOP or the client's page.
The draft beside the pilot recordEach difference from the client's pilot, from batch size to drying both sub-lots in one load, carries its reason and its source.
Master records by plant and clientOpen records with their stage, due date and the batch each one holds; a draft whose source cannot be read stops and says so.
Drafting rules learned from rulingsA reviewer's ruling becomes a proposed rule, which waits for the QA head's approval before it touches a draft; one was declined.
The trail behind each signatureWho acted, what changed and why, with each signature's meaning and session, from the question sent to the author's signature; CSV and evidence pack exports.

demoSample data, from the working solution.

Four of the ten challenger points were the agents' own mistakes

A binder rate the pump cannot run

The client's 2.0 kg/min sat above the pump's qualified 0.4–1.2 kg/min; the fitter had read only the granulator's summary.

A critical step with no stop rule

Wet massing had no end; the operator challenger caught it, and the step now stops on the power plateau or at the client's maximum time.

Theoretical yield with no limits

The rule checker had passed the yield line on theoretical yield alone; the QA challenger added limits at four phases from the client's development report.

A coating excess marked not applicable

The spray-loss excess was missing; the formula now states it, with the suspension weight worked out beside it.

demoSample data, from the working solution.

Two challengers read the draft as the operator and the QA reviewer would

Agents read, draft and ask; people send, decide and sign.

Step writer

Writes each instruction in the plant's style from the client's process description, the record structure and current SOPs.

  • Writes no number it cannot source
  • Never rewrites the client's process
Range sourcer

Threads each number to its passage: client page, gap assessment line, qualification report or SOP.

  • Estimates no range
  • Leaves a gap marked as no source
Equipment fitter

Checks each step against the plant's qualified equipment ranges.

  • Moves no process parameter to fit a machine
Rule checker

Checks the draft against the federal master record rule and the EU GMP documentation chapter.

  • Marks no record approved
Operator challenger

Asks of each step whether it can be done on this machine as written.

  • Closes none of its own points
QA challenger

Reads as the QA reviewer and the inspector, line by line.

  • Closes none of its own points
Client question agent

Drafts structured questions and reads answers only through their fields and attachment.

  • Sends nothing itself
  • Lets no free text change a step

Questions MSAT and QA teams ask about the master batch record

What is a master batch record?

A master batch record is the approved set of instructions every batch of a product is made from: formula, yields, equipment, steps, checks and signatures. Here agents write the master batch record from the client's transfer package and thread every number to its source, and the author, production, QA and the client each sign.

What is the difference between a master batch record and a batch record?

The master is the approved original for a product and batch size; each executed batch record is a copy completed on the floor for one batch. An error in the master is copied into every executed record, which is why every number here carries its source.

Is a master production record the same thing?

In practice, yes. The federal rule calls it the master production and control record, EU GMP calls it the manufacturing formula and processing instructions, and most plants say master batch record. The rule check reads the draft against both.

Can the agents change the client's process to fit our equipment?

No. The equipment fitter flags a step it cannot fit, and the step waits. The change goes to the client as a structured question, and only the client's returned fields and an attachment the author opened can change the step.

Does it replace our MES or electronic batch record system?

No. It reads the client's package, the plant's qualification reports, SOPs and existing master records, and writes the master content with its threads; the plant's own systems of record stay in place.

What happens when a signed record changes?

All signatures are cleared, the version goes up and downloads are marked unsigned, so no signature rests on wording it never saw.

Send one client's package.
Read the draft by its threads.

Send a process description, a development report and your equipment register, and we will draft one section of the master record with each number traced.