← All Insights

Before the inspector asks: what to have ready for your computerised systems

An inspection of a regulated site almost always reaches the computerised systems, because most GMP records now live in one. If you can answer a few predictable questions quickly, with documents in your hand, the conversation stays calm. This article lists eight things to have ready, each tied to the regulations and regulator guidance an inspector works from. It is a preparation guide, not a promise about how any inspection will go.

Start from the inventory, not the binder

Annex 11 (2011) clause 4.3 says an up to date listing of all relevant systems and their GMP functionality should be available. For critical systems it also expects an up to date system description covering the physical and logical arrangements, data flows, interfaces with other systems, hardware and software prerequisites and security measures.

That list is where an inspection of computerised systems naturally starts. If an inspector can pick a system from your inventory and you can immediately produce its description, risk assessment, validation status and owner, you have shown control. If the inventory is out of date or missing stand-alone instruments and spreadsheets, every later answer gets harder.

The eight things to have ready

1. A current system inventory with a risk ranking

Annex 11 clause 1 expects the extent of validation and data integrity controls to rest on a justified and documented risk assessment. The MHRA data integrity guidance suggests a data integrity risk assessment in which processes that produce data are mapped, each data format and its controls identified, and the data criticality and inherent risks documented (section 3.4). Show the ranking, not just the list.

2. Validation status for every system on the list

Clause 4.1 expects validation documentation to cover the relevant lifecycle steps, with change control records and deviation reports included (clauses 4.1 and 4.2). Be ready to say which systems are validated, which are in progress, and which have a documented reason for lighter treatment.

3. Access control and administrator rights

21 CFR 11.10(d) requires limiting system access to authorised individuals, and Annex 11 clause 12 expects physical or logical controls, with creation, change and cancellation of access authorisations recorded (clause 12.3). FDA's data integrity guidance says the system administrator role should go to people independent from those responsible for the record content, and that firms should document each person's access privileges for every GMP computer system (see 21 CFR 211.68(b)). Have a current list of users, roles and administrators for each critical system.

4. Audit trails and the evidence they are reviewed

Annex 11 clause 9 says audit trails need to be available, convertible to a generally intelligible form and regularly reviewed. 21 CFR 11.10(e) describes secure, computer-generated, time-stamped audit trails. FDA's guidance says that where regulations do not set a review frequency for audit trails, you determine it using your knowledge of your processes and risk assessment tools. An inspector will want to see the procedure, and then a real record of a review.

5. Backup, restore and archiving

Annex 11 clause 7.2 expects regular backups of all relevant data, with the integrity and accuracy of backup data and the ability to restore it checked during validation and monitored periodically. Clause 17 expects archived data to be checked for accessibility, readability and integrity. PIC/S PI 041-1 adds that systems should allow backup and restoration of all data including metadata and audit trails. Be ready with a restore test record, not just a backup schedule.

6. The supplier file for each critical system

Annex 11 clause 3.4 says quality system and audit information about software suppliers should be available to inspectors on request. See our separate article on supplier assessment for what the file should hold.

7. Change control and periodic review

Annex 11 clause 10 expects changes, including configuration changes, to be made in a controlled way under a defined procedure. Clause 11 expects systems to be periodically evaluated to confirm they remain in a valid state and compliant with GMP, with the evaluation covering functionality, deviations, incidents, upgrade history, performance, reliability, security and validation status where appropriate.

8. Incidents and business continuity

Clause 13 expects all incidents, not only system failures and data errors, to be reported and assessed, with the root cause of any critical incident identified and used as the basis for corrective and preventive action. Clause 16 expects provisions to keep critical processes running if a system breaks down, for example a manual or alternative system, with the time to bring it into use based on risk and the arrangements documented and tested.

Know who answers

Annex 11 clause 2 says there should be close cooperation between all relevant personnel, such as the process owner, the system owner, Qualified Persons and IT, and that everyone should have appropriate qualifications, access and defined responsibilities. The glossary defines the process owner as the person responsible for the business process, and the system owner as the person responsible for the availability and maintenance of a computerised system and the security of the data on it. For each critical system, decide in advance who speaks to which question. An inspector who is passed from person to person with no clear owner learns something about your control before any document is opened.

Why a document review finds gaps early

The reason to review documents ahead of time is practical. An inspector reads your records against the same texts listed above, and gaps tend to be between documents rather than within one. For example, the inventory lists a system that has no risk assessment, an SOP says audit trails are reviewed monthly while no review records exist, or the validation report describes a version that has since been upgraded. Reading the documents side by side, as an inspector would, finds those mismatches while there is still time to fix them or to document why they are acceptable.

A short check of this kind covers:

  • Does every system on the inventory have a risk assessment, an owner and a validation status?
  • Do the procedures say what the records show actually happens?
  • Are the dates consistent: validation, last periodic review, last restore test, last access review?
  • Are open deviations, changes and incidents on critical systems closed or under control?

Practising the questions

Documents are only half of it. People are asked questions in an inspection, and it helps to have said the answers aloud before the day. A mock question-and-answer session works through the questions above with the people who would answer them: who owns this system, how do you know the audit trail is switched on, what would you do if the server failed tonight, when did you last test a restore. The aim is not to rehearse scripted replies. It is to find out who does not know the answer, and to fix the underlying gap rather than the wording.

Questions that reach beyond your documents are common. The MHRA guidance notes that organisations are not expected to apply a forensic approach to data checking on a routine basis, but that systems should maintain appropriate levels of control and wider governance should let periodic audits detect weaknesses (section 3.5). Be ready to explain how your own periodic checks work.

What preparation cannot do

Preparation improves your position but does not guarantee an outcome. Inspectors follow what they find, and every site and system is different. If preparation shows a real gap, the right response is to record it, assess the risk and put a corrective action in place, not to hide it. A gap that you have found, assessed and started to fix is a very different conversation from one an inspector finds first.

Key takeaways

  • Inspections of computerised systems usually start from the system inventory, so keep it current and include stand-alone instruments.
  • Have eight things to hand: inventory and risk ranking, validation status, access and administrator rights, audit trail review evidence, backup and restore records, supplier files, change and periodic review records, and incident and continuity arrangements.
  • Gaps tend to sit between documents, so read them side by side.
  • Practise the answers with the people who will give them.
  • Preparation does not guarantee how an inspection goes, but a gap you found and acted on is in a far better position than one an inspector found first.

Further Reading

About the author. Iain Littlejohn is the owner and principal computer validation consultant at Compval. He is an engineer with more than 35 years in industry, from aerospace through manufacturing automation to computer system validation in life sciences.

Want articles like this first?

Members get each new article before it is published here, plus the CSV 101 course, the templates and SOPs library, Regulatory Watch and Ask Iain.

This article is general information for people who work in regulated industries. It is not legal or regulatory advice. Check the regulator's own publications and your own quality system before you act on it.