Pharma manufacturing software: batch, lot and role access

Most plants scatter the batch story. The dispensing sheet sits in the warehouse, the batch manufacturing record travels with the batch, and the analyst notebook lives in the lab. Deviations go in a register. Accounts raises the invoice.

Software joins these under one batch number. That is the whole idea. Open it and you see the material lots dispensed, the equipment used, the in-process readings, the test results, any deviation raised and the final release decision. Add the packing line and the label reconciliation to that chain, so the batch and expiry printed on a carton trace back to the same record.

Gaps become visible, because a release cannot be shown while one assay is still open, one reagent lot is unverified or one deviation lacks a closing signature. Nothing hides.

A batch is only as traceable as its lots, so every received lot gets its own number at the gate, with the supplier’s certificate attached. Quarantine holds it until QC passes it. The supplier’s certificate of analysis, the in-house identity test and the quarantine release each add a line to the lot history. Storekeeper and QA both see all three.

Dispensing then picks lots, not just materials. The screen offers only approved, unexpired lots, suggests the one expiring first and hides any rejected or quarantined lot from the dispensing balance.

Run a recall drill on the screen. Pick one excipient lot, such as lactose or magnesium stearate, and ask which batches used it, which customers received them and what stock remains. The answer should arrive in seconds.

An operator at the dispensing balance should see only the weighing screen and the line entries for that room, never the release or invoice screens. A supervisor verifies. An analyst enters results for assigned tests. Only the QA head approves release.

Separation of duties is the point. The person who enters a result must not approve it, and the system should refuse that shortcut even when the shift is busy. A plant with a contract customer may add a view for the customer’s own quality person, limited to that customer’s batches, certificates and shipment notes.

Access follows the job, not the person. When an analyst moves from the wet lab to the instrument room, the permissions change in one place, and the old ones disappear.

A deviation raised on a granulation step should sit on that batch, not in a separate register that someone matches later. The investigation, the impact assessment and the corrective action all link back by batch number, each with its own approver and date. Reviewers who once chased a granulation deviation through the register, the batch file and a loose investigation report can open one screen and read the whole thread in order.

Out-of-specification results work the same way. The first result, the retest, the stated reason, the approver and the instrument used stay visible together, so a reviewer sees the full sequence without opening the notebook. Nothing is overwritten. A corrected value shows the old figure struck through, with the editor’s name and the moment of the change beside it.

Reviewers then read one record, not four. Any lot of tablets with an open deviation carries a clear hold flag on the dispatch screen, so the van is never loaded with it by accident.

In a loose setup, sales raises the invoice because the customer is waiting, and QA hears about it afterwards, when the consignment is already on the road. Connect the two. The dispatch screen lists only released batches, and the invoice then picks up the batch number, the certificate of analysis and the dispatch date from that same line.

Contract manufacturers gain most. Each customer sees only their own batches, certificates and shipments, and nobody has to filter a shared spreadsheet before replying to a query. A distributor who rings about one carton then gets an answer from the batch record in minutes, including the certificate of analysis and the date of dispatch.

Start with one product. Pick one tablet product, run it through batch, lot and role screens, and fix what the shop floor finds clumsy before adding the next product.