DEV Community: Siddhi LLC

Revised Schedule M for MSMEs: What Inspectors Look For in Batch Records

Siddhi LLC — Tue, 27 Oct 2026 00:09:32 +0000

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.

Where the timeline stands

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

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.

What changed that touches batch records

Revised Schedule M adds three things that matter here:

A Pharmaceutical Quality System. Quality is managed as a system, not only as a final check.
A section on computerised systems. Systems you use must be validated.
Stricter batch processing and packaging records.

One point needs to be stated clearly: Revised Schedule M does not legally require electronic batch records. 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.

What inspectors look for in a batch record

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:

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

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.

How eBMR helps with each question

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.

Complete and reviewable. 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.
Attributable. Each entry and signature carries the person and the time.
Right version. 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.
Protected. 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.

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.

Compliance still depends on your procedures and your validation. The software supports your controls. It does not make a site compliant by itself.

The usual hesitations, answered

"We can't afford it." 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.

"We don't have time to retype all our records." 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.

"Validation will be a mountain." 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.

Try it before you decide: the 14-day pilot

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

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.
Every batch and every printout made during the pilot is marked PILOT – not for GMP use, so nothing can be mistaken for a real record.
Atto Pharma asks for your decision once, at the end, and sends no sales messages because of your answer.
If you decide not to continue, the development site closes to your company.

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.

Practical takeaways

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

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.

This article is not legal advice. Check the official Schedule M notification and your State Drugs Controller for your unit's position.

Originally published on siddhi.today.

Paper vs electronic batch records: what changes for QA and production

Siddhi LLC — Mon, 26 Oct 2026 23:53:20 +0000

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.

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

What stays the same

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.

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.

What changes for production

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:

Steps run in order. A lot step opens only when the step before it is done and checked.
Limits are checked as values are entered. An out-of-limit value is flagged at the field and needs a deviation number before its section can be signed off.
The checker is a different person. The same person cannot do and check a step.
You see only what you are cleared for. Screens outside your cleared operations are hidden and refused.
Dispensing has pre-checks. 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.
Equipment status blocks use. Unqualified equipment, equipment past calibration or PM due, or equipment with a missing daily check cannot be used.

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.

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.

What changes for QA

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:

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

Review by exception: what it can mean in practice

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.

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.

21 CFR Part 11: what the software supports

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:

Signatures. 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.
Password at each signature. 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.
Audit trail. 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.
Server time. 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).
Access. 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.
Record protection. 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.

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.

Practical takeaways

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

Try it in a 14-day pilot

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.

Originally published on siddhi.today.