One Approved BMR, Every Process Area: Extend It, Don't Retype It

October 30, 2026 · 7 min read · All articles

A granules product is validated in P-I. Demand grows, and it now has to run in P-IV and P-V of the same block as well. The process is the same. The record is not.

In most oral solid dose plants, each area's batch manufacturing record is a Word file made by copying another one and editing it. Add several buyers, each with its own specification, and the copies multiply. This article describes a different way to handle both problems in Atto Pharma eBMR: extend one approved BMR to other process areas, and enforce each buyer's limits during the batch.

Why every area needs its own BMR

A typical plant is divided into blocks, and each block is designated for a kind of product, such as granules or tablets. Each block holds several process areas (P-I, P-II, P-III and so on), often built at different times with different equipment.

The same product needs a separate BMR in each area because:

• The parameters differ. Inlet temperature, flap position, mixing time or lot size are adjusted to the equipment.
• The references differ. Each area has its own SOP numbers, equipment registers, logbooks and forms.
• The BMR number and name differ. They follow the plant's numbering for that area.

What goes wrong with Word copies

Copying and editing creates familiar problems:

• Copy errors. An SOP number is left over from the source area. A register is named that doesn't exist in the target area. A limit is changed in one place but not in the printed instruction beside it.
• Whole-document review. QA can't see what changed, so every copy is read line by line, for every area and every revision.
• Drift between areas. When the master changes, each area's copy must be revised by hand. Copies fall out of step, and nothing shows that they have.
• Weak traceability. The reason for a difference between areas sits in a change control form, if it is written down anywhere. It is not in the record.

Buyer specifications make it harder

Contract and generic manufacturers often make one product for several buyers. Each buyer has its own specification and test method: the sieves used to size the granules, loss on drying or moisture content with a target, tapped density, and sieve analysis mesh by mesh. The manufacturer usually adds internal limits tighter than the buyer's, to leave a margin before a result goes out of specification.

On paper, these limits sit on an internal-limits page at the back of the BMR. The operator and the in-process QA officer find the right buyer's row, read the limit, and judge each result by eye. When one batch serves two buyers, someone has to work out which limit is stricter. The batch record shows the result, but not which limit it was judged against, or why.

Extending an approved BMR to another process area

In Atto Pharma eBMR, the company's administrator first describes the plant once: blocks and what each is designated for, the process areas in each block with their BMR number prefix and their own SOPs, registers and forms, and each piece of equipment's area, type and capacity. The approval workflow is set up at the same time.

After that, on an approved product, you choose Extend to another process area. Here is what happens:

• Only valid areas are offered. These are the other process areas of the same block, and only when the block is designated for the product's type. The database enforces this, so another block, or an area designated for a different product type, is refused.
• Equipment is matched by type and capacity. Smaller, shared and unmatched items are flagged. An unmatched item is chosen by hand or marked Not used with a reason.
• The area's references are put in place. That covers SOPs, registers and forms. The BMR number comes from the area's prefix, and the new product is named from the product code and the area, as your company has chosen.
• Every changed parameter needs a reason. All limits are listed on a parameter sheet, and the printed instruction that states a limit changes with it.
• The formula is locked. The formula, lots and packing stay as in the source. Unlocking the formula, for example to change the number of lots, is a formula change that needs its own reason.

The draft then goes through your company's workflow. Production drafts by default. There is at least one review, which by default is a QA review. QA reviews only the differences, not the whole document. The QA Head approves with an electronic signature and chooses when the version takes effect: immediately, or from a date. Until then, the version in use stays.

Buyer limits, enforced at the step

Each granules BMR can carry a buyer table: one row per buyer, or per group of buyers with the same requirements. It holds the buyer's name, STP number and market, and limits for sieves, LOD or moisture content, tapped density and sieve analysis. The table can be entered on screen or read from a Word internal-limits page.

Every limit holds two values: the internal limit, which is enforced, and the buyer's limit, which is shown. Atto Pharma refuses an internal limit that lies outside the buyer's, so the limit enforced is always the stricter of the two.

At batch creation, QA ticks the buyer, or several buyers when one batch serves them all. Buyers with different sieves, or limits that don't overlap, can't share a batch, and the system names the clash. For compatible buyers, the stricter end of each limit applies. The batch keeps the specification it was issued with, so a later change to the table never alters a running batch.

Every result is marked as it is entered:

| Result | Shown as | Needed to continue | | --- | --- | --- | | Within the internal limit | Within | Nothing | | Outside the internal limit, within the buyer's | Outside internal limit | A remark or a deviation number | | Outside the buyer's limit | Out of specification | A deviation number |

In batch review, QA sees the buyers, their STP numbers and markets, the limits the batch used, and every result against them.

What an auditor will ask

These capabilities use the same controls as the rest of the eBMR:

• Separate people and signatures. Draft, review and approval are separate steps with separate electronic signatures. At least two people sign, the drafter never reviews or approves, and nobody signs a draft twice.
• Controlled changes. Every changed equipment item, parameter or limit carries its reason. Submission needs a change control number in the company's format, and placeholders such as "TBD" or "XXX" are refused.
• Audit trail. Each signature records the signer, the time and its meaning. Every save, return, review and approval is kept in a tamper-evident audit trail.
• Data integrity. Results are entered once, at the step, against limits held in the record, and attributed to the person and time. Approved versions are locked.

This supports the expectations of 21 CFR Part 11 and EU GMP Annex 11, and the principles of ALCOA+. Compliance itself still rests on your procedures and validation. Software records and enforces decisions. It doesn't make them. You still assess each change, because moving a product to equipment of a different design or operating principle may need a regulatory assessment. You validate the process in the new area. You agree each buyer's specification with the buyer, and you investigate and close deviations in your quality system.

An illustrative example

The figures below are an illustrative model, not measured results. They describe a plant that prepares or revises 20 area BMRs a month. Replace them with your own numbers.

| Task, per area BMR | Word copies (hours) | Extended in Atto Pharma (hours) | | --- | --- | --- | | Prepare the draft | 4.0 | 0.5 | | QA review | 2.0 (whole document) | 0.5 (only what changed) | | QA Head approval and signatures | 0.5 | 0.25 | | Total per BMR | 6.5 | 1.25 |

Across 20 BMRs, that is 130 hours against 25 in the model, or about 105 hours a month returned to Production and QA. The larger gain is harder to price: no copy errors to find in review, no area left on an old revision, and a reason attached to every difference.

What to measure on a pilot

Over one month, compare:

• hours spent preparing and reviewing area BMRs, before and after;
• review comments that are copy errors (wrong SOP number, register or limit);
• time from draft to approved version;
• areas running on an out-of-date revision;
• results judged against a buyer's limit by eye.

Try it on a pilot

Start with a pilot on the development site, using fictional data or your own non-GMP data. Then do the one-time setup: blocks, process areas, equipment types and capacities, the approval workflow and each product's buyer table. A Get started checklist shows what is left to do.

Atto Pharma eBMR can be tried in a free 14-day pilot at pharma-manufacturing.today. A whitepaper, "One Approved BMR, Every Process Area," is available from Atto Pharma.