<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Siddhi LLC</title>
    <description>The latest articles on DEV Community by Siddhi LLC (@siddhi_llc).</description>
    <link>https://dev.to/siddhi_llc</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4209650%2Fd4fe606a-92e1-405d-a2d9-01989639d980.png</url>
      <title>DEV Community: Siddhi LLC</title>
      <link>https://dev.to/siddhi_llc</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/siddhi_llc"/>
    <language>en</language>
    <item>
      <title>Why AI on Deviations Needs One Batch Record, Not Three Systems</title>
      <dc:creator>Siddhi LLC</dc:creator>
      <pubDate>Fri, 30 Oct 2026 19:52:06 +0000</pubDate>
      <link>https://dev.to/siddhi_llc/why-ai-on-deviations-needs-one-batch-record-not-three-systems-2ji5</link>
      <guid>https://dev.to/siddhi_llc/why-ai-on-deviations-needs-one-batch-record-not-three-systems-2ji5</guid>
      <description>&lt;p&gt;Ask a plant what happens when a deviation is opened, and you often hear about three places. The batch record is in one system. The equipment and area logbooks are in another. The deviation itself is somewhere else. Someone has to reconcile them before anyone can say what happened.&lt;/p&gt;

&lt;p&gt;Now add AI. If an assistant has to read from three systems, it inherits the reconciliation problem, and it may not be clear which version of an event it is describing.&lt;/p&gt;

&lt;p&gt;A recent CIO.inc interview, &lt;a href="https://www.cio.inc/pharmas-ai-ambitions-run-into-disconnected-systems-a-32962" rel="noopener noreferrer"&gt;Pharma's AI ambitions run into disconnected systems&lt;/a&gt;, points at this gap. This article gives our view as the makers of Atto Pharma eBMR and Atto eLogbooks. It rests on how our own software is documented, and we have kept to that.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem with three systems
&lt;/h2&gt;

&lt;p&gt;A deviation question is rarely about one record. "Which readings were out of limit before this step?" "Who corrected this value, and why?" "What else ran in that area that week?" The answers sit across the batch, the logbooks and the quality system.&lt;/p&gt;

&lt;p&gt;When those are separate systems, three things tend to happen:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Each has its own timestamps, user names and edit history, so they have to be matched by hand.&lt;/li&gt;
&lt;li&gt;A correction in one place may not show in another.&lt;/li&gt;
&lt;li&gt;Any AI layered on top produces an answer that is only as consistent as the weakest link underneath.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The AI is not the main risk here. The reconciliation is. You can't investigate quickly, or let a tool help you, if the facts first need assembling.&lt;/p&gt;

&lt;h2&gt;
  
  
  One database, one audit trail
&lt;/h2&gt;

&lt;p&gt;Atto Pharma eBMR and Atto eLogbooks are delivered as one hosted web application with one database. The batch record and the logbooks sit together. The documented behavior that matters most for deviations is this:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Results are entered once&lt;/strong&gt;, at the step, against limits held in the record, and attributed to a person and time.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A result outside the internal limit&lt;/strong&gt; needs a remark or a deviation number. &lt;strong&gt;A result out of the buyer's specification&lt;/strong&gt; needs a deviation number before work continues.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Each change to a value adds an audit-trail entry&lt;/strong&gt; in the editor's own name. Earlier values are never overwritten or removed, and a correction needs a reason.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The audit trail is computer-generated and time-stamped by the server.&lt;/strong&gt; The audit-trail screen shows the original and the new value, who, when and why.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Records can't be deleted.&lt;/strong&gt; Every saved version is kept in an append-only history, chained by SHA-256, so a change made outside the application is detected.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The batch record can be produced as a PDF at any time&lt;/strong&gt;, with every value, limit, signer, time, exception, correction with its reason, review and release. Logbooks export to Excel and PDF, including corrections and cancelled entries.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;There is one record and one history. When someone, or something, asks "what happened at this step," there is one place to look and nothing to reconcile.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where AI fits, and where it doesn't
&lt;/h2&gt;

&lt;p&gt;Atto Pharma has AI agents, introduced from release 1.22.0. It helps to be exact about what they are and what they do.&lt;/p&gt;

&lt;p&gt;The Help agents (Sales, Implementation, Support and, from release 1.38.0, IT &amp;amp; Security) answer questions from Atto Pharma's published documentation. Each answer lists the manual parts, guides or documents it is based on, so you can check anything important. These agents can't see your company's batch records, products, people or files. They see your question, with email addresses, phone numbers and record numbers masked, plus your role and site.&lt;/p&gt;

&lt;p&gt;Separately, a preview feature, agents on this device, answers questions from the company's own records. The Quality Head agent, for example, answers questions such as "Which batches were made for each buyer?" from those records. The charts it can draw include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Out-of-limit values by stage&lt;/li&gt;
&lt;li&gt;Corrections by stage&lt;/li&gt;
&lt;li&gt;Deviations by step&lt;/li&gt;
&lt;li&gt;Batches waiting for QA&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Those charts run across every batch of the product, for the Quality Head. The eLogbook charts, such as temperature and RH trends by area, with out-of-limit days shown in red, come from the same system.&lt;/p&gt;

&lt;p&gt;The documentation is clear on one point. &lt;strong&gt;The answers are not part of the batch record.&lt;/strong&gt; The batch's own screens and audit trail are the record. Atto Pharma records that an agent was used on a batch (who, when, which agent) but never the question or the answer.&lt;/p&gt;

&lt;p&gt;The documentation describes agents that answer questions. It does not describe any agent that signs, approves or edits a batch record. Signatures stay with people. The database decides which role may give which signature: QA Head only for issue and release, QA or IPQA for section review, and a checker must be a different person from the doer. Each signature needs the signer's password.&lt;/p&gt;

&lt;p&gt;For deviations, this means an AI answer can point you to where to look. The investigation, its conclusions and its closure stay in your quality management system, under your procedures.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this means for your plant
&lt;/h2&gt;

&lt;p&gt;If you are thinking about AI for deviation work, a few questions are worth asking of any system, ours included:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Where is the record of truth?&lt;/strong&gt; If it is spread across systems, an AI answer needs a reconciled source first.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Is the audit trail one chain or several?&lt;/strong&gt; Ask whether an edit made outside the application would be detected.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Is the AI's output kept apart from the record?&lt;/strong&gt; An answer should never be mistaken for the entry itself.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What can the AI see?&lt;/strong&gt; Know whether it reads your records, or only documentation.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Who still signs?&lt;/strong&gt; Confirm that approvals stay with named people and roles.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What stays with you
&lt;/h2&gt;

&lt;p&gt;Software records and enforces decisions. It doesn't make them. For deviations, you still:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;investigate and close them in your quality management system;&lt;/li&gt;
&lt;li&gt;set internal limits that make sense for your process;&lt;/li&gt;
&lt;li&gt;train your people and approve who may draft, review and approve;&lt;/li&gt;
&lt;li&gt;validate each release and each product under your own procedures.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Atto Pharma eBMR supports 21 CFR Part 11, EU GMP Annex 11 and ALCOA+ expectations through its controls. Compliance depends on your procedures and your validation. The &lt;a href="https://siddhi.today/blog" rel="noopener noreferrer"&gt;21 CFR Part 11, cGMP and GAMP 5 Whitepaper&lt;/a&gt; and the One Approved BMR, Every Process Area whitepaper set out the controls in more detail. You can find the first in the app under Help → Documents. For IT Heads, the Application Security Whitepaper and the Trust and Security Overview cover hosting, access and records isolation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it in a free 14-day pilot
&lt;/h2&gt;

&lt;p&gt;If you would like to see one batch record, its logbooks and its audit trail together, you can try Atto Pharma eBMR or Atto eLogbooks in a free 14-day pilot. The pilot runs on the development site, with fictional data or your own non-GMP data. It gives your QA, manufacturing and IT teams a way to check the questions above against real screens before deciding anything.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://siddhi.today/blog/why-ai-on-deviations-needs-one-batch-record-not-three-systems/" rel="noopener noreferrer"&gt;siddhi.today&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>pharma</category>
      <category>auditing</category>
      <category>database</category>
    </item>
    <item>
      <title>One Approved BMR, Every Process Area: Extend It, Don't Retype It</title>
      <dc:creator>Siddhi LLC</dc:creator>
      <pubDate>Fri, 30 Oct 2026 17:16:14 +0000</pubDate>
      <link>https://dev.to/siddhi_llc/one-approved-bmr-every-process-area-extend-it-dont-retype-it-5ha8</link>
      <guid>https://dev.to/siddhi_llc/one-approved-bmr-every-process-area-extend-it-dont-retype-it-5ha8</guid>
      <description>&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why every area needs its own BMR
&lt;/h2&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;The same product needs a separate BMR in each area because:&lt;/p&gt;

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

&lt;h2&gt;
  
  
  What goes wrong with Word copies
&lt;/h2&gt;

&lt;p&gt;Copying and editing creates familiar problems:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Copy errors.&lt;/strong&gt; 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.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Whole-document review.&lt;/strong&gt; QA can't see what changed, so every copy is read line by line, for every area and every revision.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Drift between areas.&lt;/strong&gt; When the master changes, each area's copy must be revised by hand. Copies fall out of step, and nothing shows that they have.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Weak traceability.&lt;/strong&gt; 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.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Buyer specifications make it harder
&lt;/h2&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  Extending an approved BMR to another process area
&lt;/h2&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;After that, on an approved product, you choose &lt;strong&gt;Extend to another process area&lt;/strong&gt;. Here is what happens:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Only valid areas are offered.&lt;/strong&gt; 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.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Equipment is matched by type and capacity.&lt;/strong&gt; Smaller, shared and unmatched items are flagged. An unmatched item is chosen by hand or marked &lt;em&gt;Not used&lt;/em&gt; with a reason.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The area's references are put in place.&lt;/strong&gt; 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.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Every changed parameter needs a reason.&lt;/strong&gt; All limits are listed on a parameter sheet, and the printed instruction that states a limit changes with it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The formula is locked.&lt;/strong&gt; 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.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  Buyer limits, enforced at the step
&lt;/h2&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;Every result is marked as it is entered:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Result&lt;/th&gt;
&lt;th&gt;Shown as&lt;/th&gt;
&lt;th&gt;Needed to continue&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Within the internal limit&lt;/td&gt;
&lt;td&gt;Within&lt;/td&gt;
&lt;td&gt;Nothing&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Outside the internal limit, within the buyer's&lt;/td&gt;
&lt;td&gt;Outside internal limit&lt;/td&gt;
&lt;td&gt;A remark or a deviation number&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Outside the buyer's limit&lt;/td&gt;
&lt;td&gt;Out of specification&lt;/td&gt;
&lt;td&gt;A deviation number&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;In batch review, QA sees the buyers, their STP numbers and markets, the limits the batch used, and every result against them.&lt;/p&gt;

&lt;h2&gt;
  
  
  What an auditor will ask
&lt;/h2&gt;

&lt;p&gt;These capabilities use the same controls as the rest of the eBMR:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Separate people and signatures.&lt;/strong&gt; 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.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Controlled changes.&lt;/strong&gt; 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.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Audit trail.&lt;/strong&gt; Each signature records the signer, the time and its meaning. Every save, return, review and approval is kept in a tamper-evident audit trail.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Data integrity.&lt;/strong&gt; Results are entered once, at the step, against limits held in the record, and attributed to the person and time. Approved versions are locked.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  An illustrative example
&lt;/h2&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Task, per area BMR&lt;/th&gt;
&lt;th&gt;Word copies (hours)&lt;/th&gt;
&lt;th&gt;Extended in Atto Pharma (hours)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Prepare the draft&lt;/td&gt;
&lt;td&gt;4.0&lt;/td&gt;
&lt;td&gt;0.5&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;QA review&lt;/td&gt;
&lt;td&gt;2.0 (whole document)&lt;/td&gt;
&lt;td&gt;0.5 (only what changed)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;QA Head approval and signatures&lt;/td&gt;
&lt;td&gt;0.5&lt;/td&gt;
&lt;td&gt;0.25&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Total per BMR&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;6.5&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;1.25&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to measure on a pilot
&lt;/h2&gt;

&lt;p&gt;Over one month, compare:&lt;/p&gt;

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

&lt;h2&gt;
  
  
  Try it on a pilot
&lt;/h2&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://siddhi.today/blog/one-approved-bmr-every-process-area-extend-it-don-t-retype-it/" rel="noopener noreferrer"&gt;siddhi.today&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>pharma</category>
      <category>workflow</category>
      <category>compliance</category>
      <category>software</category>
    </item>
    <item>
      <title>Revised Schedule M for MSMEs: What Inspectors Look For in Batch Records</title>
      <dc:creator>Siddhi LLC</dc:creator>
      <pubDate>Tue, 27 Oct 2026 00:09:32 +0000</pubDate>
      <link>https://dev.to/siddhi_llc/revised-schedule-m-for-msmes-what-inspectors-look-for-in-batch-records-5964</link>
      <guid>https://dev.to/siddhi_llc/revised-schedule-m-for-msmes-what-inspectors-look-for-in-batch-records-5964</guid>
      <description>&lt;p&gt;If you run a small or mid-size pharma plant in India, Revised Schedule M is probably already part of your weekly conversations. This article sets out the timeline, what it means for your batch records, and where an electronic batch record (eBMR) can help. It also covers the usual worries about cost, time and validation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where the timeline stands
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Revised Schedule M was notified in December 2023.&lt;/li&gt;
&lt;li&gt;Large firms (turnover above ₹250 crore) had to comply by 28 June 2024.&lt;/li&gt;
&lt;li&gt;MSMEs (₹250 crore or less) that applied with an upgrade plan had until 31 December 2025.&lt;/li&gt;
&lt;li&gt;For those MSMEs, the revised rules apply from 1 January 2026.&lt;/li&gt;
&lt;li&gt;In November 2025, the DCGI directed state regulators to inspect units and report monthly to CDSCO.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So inspections are expected, and the point is to be ready. Plants that prepare calmly and document well usually have a good conversation with the inspector.&lt;/p&gt;

&lt;h2&gt;
  
  
  What changed that touches batch records
&lt;/h2&gt;

&lt;p&gt;Revised Schedule M adds three things that matter here:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;A Pharmaceutical Quality System.&lt;/strong&gt; Quality is managed as a system, not only as a final check.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A section on computerised systems.&lt;/strong&gt; Systems you use must be validated.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Stricter batch processing and packaging records.&lt;/strong&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;One point needs to be stated clearly: &lt;strong&gt;Revised Schedule M does not legally require electronic batch records.&lt;/strong&gt; A well-run paper system can meet the requirement. What an eBMR does is make complete, attributable, reviewable records much easier to produce and to show to an inspector.&lt;/p&gt;

&lt;h2&gt;
  
  
  What inspectors look for in a batch record
&lt;/h2&gt;

&lt;p&gt;We can't speak for any individual inspector, but the practical questions are easy to guess. When someone picks up a batch record, they want to know:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Is it complete?&lt;/strong&gt; Every step, check, limit and reconciliation has a value or a stated reason why not.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Is it attributable?&lt;/strong&gt; You can see who recorded each entry, who checked it, and when.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Is it the right version?&lt;/strong&gt; The batch was made on the approved master record revision, and you can show which one.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Are corrections explained?&lt;/strong&gt; Any change shows the original value, the new value and the reason.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Was it reviewed before release?&lt;/strong&gt; There is evidence of QA review and a named person who released the batch.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Can you produce it quickly?&lt;/strong&gt; A complete copy is available without a hunt through files.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Paper records can answer all of these, but it takes discipline, and gaps are easy to miss: a blank field, an unsigned check, an undated entry, or an old revision on the floor.&lt;/p&gt;

&lt;h2&gt;
  
  
  How eBMR helps with each question
&lt;/h2&gt;

&lt;p&gt;Atto Pharma eBMR turns your own approved Word or PDF batch manufacturing and packing records into electronic screens. It records the batch on them: dispensing, lot processing, in-process checks, packing, reconciliation, review and release.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Complete and reviewable.&lt;/strong&gt; The batch is created and issued by the QA Head. People record on the screens of the operations they are cleared for, checkers verify, QA reviews each section, and the QA Head releases the batch. You can produce the electronic batch record as a PDF at any time, showing every value, limit, signer, time, exception, correction with its reason, review and release.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Attributable.&lt;/strong&gt; Each entry and signature carries the person and the time.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Right version.&lt;/strong&gt; Each revision of the source document and its screens is kept and never changed. A new revision needs a reason, for example the change-control number, and a batch stays on the revision it was made with.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Protected.&lt;/strong&gt; Records can't be deleted. Every saved version is kept in an append-only history, chained by SHA-256, so a change made outside the application is detected.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For equipment, area and instrument records, Atto eLogbooks does the same for logbooks, with export to Excel and PDF that includes corrections and cancelled entries.&lt;/p&gt;

&lt;p&gt;Compliance still depends on your procedures and your validation. The software supports your controls. It does not make a site compliant by itself.&lt;/p&gt;

&lt;h2&gt;
  
  
  The usual hesitations, answered
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;"We can't afford it."&lt;/strong&gt; Prices are published in rupees. In the Admin console (Billing, then Sales proposals) you enter the number of eBMR users and eLogbooks-only users, and the price shows as you type, in rupees with GST for a company in India. You can then make a proposal that is valid for 30 days and print it or save it as a PDF. No call is needed to find out what it would cost.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;"We don't have time to retype all our records."&lt;/strong&gt; You don't retype. Atto Pharma's converter turns your existing approved Word document, or a PDF saved from Word (not a scan), into screens. You then review the result: product details, points to check, and who may record each section. You can load up to 20 BMRs at once, and each becomes a draft for you to review before it becomes a product.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;"Validation will be a mountain."&lt;/strong&gt; It is still your responsibility, but you aren't starting from nothing. Each product is converted and checked in development, qualified (OQ) in QA, and then performance-qualified (PQ) and used in production. Atto Pharma provides an OQ and PQ module for each product version, an installation check (IQ), and a release record with test results for each release. Moving from one environment to the next needs the receiving QA Head's acceptance with a password. Your validation team still plans and signs off the work, but the structure and evidence are there.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it before you decide: the 14-day pilot
&lt;/h2&gt;

&lt;p&gt;A company registers on the development site and, once Atto Pharma confirms it, gets a 14-day pilot. Some details worth knowing:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Up to 10 pilot evaluators per company (a QA Head or Manufacturing Head) can record, check and release every step alone, so you can try the whole flow without gathering a full shift.&lt;/li&gt;
&lt;li&gt;Every batch and every printout made during the pilot is marked &lt;strong&gt;PILOT – not for GMP use&lt;/strong&gt;, so nothing can be mistaken for a real record.&lt;/li&gt;
&lt;li&gt;Atto Pharma asks for your decision once, at the end, and sends no sales messages because of your answer.&lt;/li&gt;
&lt;li&gt;If you decide not to continue, the development site closes to your company.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A practical way to use the 14 days: take one batch record you know well, convert it, and run a batch through. Then ask your QA Head to look at the PDF and ask the same questions an inspector would.&lt;/p&gt;

&lt;h2&gt;
  
  
  Practical takeaways
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Know your unit's date and position under Revised Schedule M.&lt;/li&gt;
&lt;li&gt;Review a few recent batch records for blanks, unexplained corrections and version control. This works with paper or electronic records.&lt;/li&gt;
&lt;li&gt;Remember that computerised systems you use must be validated, so plan for it early.&lt;/li&gt;
&lt;li&gt;If you are considering an eBMR, test it with your own record, not a demo.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Atto Pharma eBMR and Atto eLogbooks can be tried in the free 14-day pilot. If it isn't right for your plant, you will know within two weeks.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;This article is not legal advice. Check the official Schedule M notification and your State Drugs Controller for your unit's position.&lt;/em&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://siddhi.today/blog/revised-schedule-m-for-msmes-what-inspectors-look-for-in-batch-records/" rel="noopener noreferrer"&gt;siddhi.today&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>pharma</category>
      <category>compliance</category>
      <category>manufacturing</category>
      <category>healthcare</category>
    </item>
    <item>
      <title>Paper vs electronic batch records: what changes for QA and production</title>
      <dc:creator>Siddhi LLC</dc:creator>
      <pubDate>Mon, 26 Oct 2026 23:53:20 +0000</pubDate>
      <link>https://dev.to/siddhi_llc/paper-vs-electronic-batch-records-what-changes-for-qa-and-production-4f7e</link>
      <guid>https://dev.to/siddhi_llc/paper-vs-electronic-batch-records-what-changes-for-qa-and-production-4f7e</guid>
      <description>&lt;p&gt;Moving from paper to electronic batch records is often described as "going digital." For the people who run the batch and the people who review it, the change is more specific than that. The same approved master record is used, but some checks move from a person's attention to the system, and the review works differently.&lt;/p&gt;

&lt;p&gt;This article walks through what changes for production and QA at a small or mid-size plant, and what stays exactly as it is.&lt;/p&gt;

&lt;h2&gt;
  
  
  What stays the same
&lt;/h2&gt;

&lt;p&gt;Your approved batch manufacturing and packing records remain the basis of everything. With Atto Pharma eBMR, the site's own approved Word or PDF BMR or BPR is converted into screens. Each revision of the source document and its screens is kept and never changed. A new revision needs a reason, for example the change-control number. A batch stays on the revision it was made with.&lt;/p&gt;

&lt;p&gt;The roles also stay familiar. The QA Head creates and issues the batch. People record on the operations they are cleared for, checkers verify, QA reviews each section, and the QA Head releases the batch.&lt;/p&gt;

&lt;h2&gt;
  
  
  What changes for production
&lt;/h2&gt;

&lt;p&gt;On paper, the operator is trusted to follow the page and to notice a missing check or an out-of-limit value. On screen, the system enforces more of this:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Steps run in order.&lt;/strong&gt; A lot step opens only when the step before it is done and checked.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Limits are checked as values are entered.&lt;/strong&gt; An out-of-limit value is flagged at the field and needs a deviation number before its section can be signed off.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The checker is a different person.&lt;/strong&gt; The same person cannot do and check a step.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You see only what you are cleared for.&lt;/strong&gt; Screens outside your cleared operations are hidden and refused.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Dispensing has pre-checks.&lt;/strong&gt; Temperature, humidity and pressure-difference checks, area clearance, a certified operator, an approved and clean booth, and equipment and material lots fit for use all come first.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Equipment status blocks use.&lt;/strong&gt; Unqualified equipment, equipment past calibration or PM due, or equipment with a missing daily check cannot be used.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Mistakes are handled differently too. Nothing can be deleted. A wrong entry is fixed by a correction with a reason, and the original value stays visible in the audit trail.&lt;/p&gt;

&lt;p&gt;One practical point: weights and readings are still typed in by the operator. There is no balance or instrument interface at present, so the entries are checked against the BMR's limits but not captured automatically.&lt;/p&gt;

&lt;h2&gt;
  
  
  What changes for QA
&lt;/h2&gt;

&lt;p&gt;On paper, QA often meets the batch for the first time at the end, as a stack of pages. In an electronic record, QA is involved throughout:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Only the QA Head issues and releases the batch. Nothing can be recorded before issue or after release.&lt;/li&gt;
&lt;li&gt;QA or IPQA reviews each section, and once QA has signed a section's review, nothing in it can be changed.&lt;/li&gt;
&lt;li&gt;Every exception appears in one list, so QA does not need to hunt through pages for flagged values.&lt;/li&gt;
&lt;li&gt;The complete batch record can be produced as a PDF at any time, with every value, limit, signer, time, exception, correction, review and release.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Review by exception: what it can mean in practice
&lt;/h2&gt;

&lt;p&gt;Many QA teams want to spend review time on what is unusual, not on re-reading every routine entry. An electronic record helps with this because the exceptions are already collected. Out-of-limit values are flagged where they happen, each needs a deviation number before sign-off, and QA sees them together in a single list.&lt;/p&gt;

&lt;p&gt;Two cautions apply. First, QA still reviews each section and signs that review. The software gives the reviewer a better starting point, but it does not replace the review. Second, how far your site relies on exceptions is a decision for your own procedures. Write it into your SOPs and test it during validation. The deviation itself is also handled in your quality system. Deviations, CAPA and change control are recorded in the eBMR by reference (their numbers), and their workflows stay in your own quality management system.&lt;/p&gt;

&lt;h2&gt;
  
  
  21 CFR Part 11: what the software supports
&lt;/h2&gt;

&lt;p&gt;A computerized system is not "Part 11 compliant" by itself. Compliance comes from the system's controls together with your procedures and validation. Here is what the software contributes on the electronic-record and signature side:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Signatures.&lt;/strong&gt; Each signature stores the signer's name, its meaning (such as Done by, Checked by, Approved and released by QA) and the server's date and time. It cannot be changed, removed or copied to another record.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Password at each signature.&lt;/strong&gt; In QA and production, every signature needs the signer's password at that moment, checked by the database. Five wrong passwords in 15 minutes lock signing for 15 minutes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Audit trail.&lt;/strong&gt; It is computer-generated and time-stamped by the server. Each change adds an entry in the editor's own name, earlier values are never overwritten, and a correction needs a reason.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Server time.&lt;/strong&gt; Entry and signature times come from the server clock, not the device, and record dates cannot be in the future (expiry, retest and due dates excepted).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Access.&lt;/strong&gt; Accounts use the company's own work email domain, are approved by the company's administrator, and sign out automatically after 15 minutes of inactivity. Two-step sign-in is optional.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Record protection.&lt;/strong&gt; Records cannot be deleted. Every saved version is kept in an append-only history chained by SHA-256, so a change made outside the application is detected.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The supplier also provides validation support: OQ and PQ modules for each product version, and an installation check for each release. The software is a configured product (GAMP 5 Category 4), delivered as software as a service. Your part is still the user requirements, risk assessment, validation plan and report, IQ/OQ/PQ execution, SOPs, training, periodic review and the decision to release the system for GMP use. A site also moves to a new release only when its own QA accepts it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Practical takeaways
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Start from your approved BMR.&lt;/strong&gt; Choose one product and see how its screens compare to the paper record, section by section.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Decide your exception rules before go-live.&lt;/strong&gt; Write down what QA reviews in full, what it reviews by exception, and how deviation numbers are raised.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Plan training for both groups.&lt;/strong&gt; Operators need to know the new checks, and reviewers need to know the exception list and section lock.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keep your boundaries clear.&lt;/strong&gt; Balance readings are manual, and deviation, CAPA and change workflows stay in your own system.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Plan validation early.&lt;/strong&gt; Use the OQ and PQ modules, and put your own validation report and SOPs in place.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Try it in a 14-day pilot
&lt;/h2&gt;

&lt;p&gt;If you want to see how this works with your own record, Atto Pharma eBMR and Atto eLogbooks can be tried in a free 14-day pilot. During a pilot, an evaluator may check their own work, and such entries are marked TEST. This makes it easy to walk through a batch alone before involving the wider team. Use the pilot to judge the screens, the checks and the review flow against your own procedures.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://siddhi.today/blog/paper-vs-electronic-batch-records-what-changes-for-qa-and-production/" rel="noopener noreferrer"&gt;siddhi.today&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>pharma</category>
      <category>gmp</category>
      <category>compliance</category>
      <category>saas</category>
    </item>
  </channel>
</rss>
