GAMP 5Good Automated Manufacturing Practice (v5)
GAMP 5 is ISPE's industry guide to a risk-based approach for GxP computerised systems; the current Second Edition was published in July 2022. It is good practice, not a law, regulation or certification.
On this page · 13 sections
- 1What GAMP 5 is
- 2What the Second Edition emphasises
- 3Law, guidance and industry practice
- 4Worked example
- 5Why GAMP 5 matters to regulated manufacturers
- 6Core ideas in plain language
- 7A practical lifecycle a site can follow
- 8Worked example: a cloud batch-record system at a supplement maker
- 9Explain it for your operation
- 10Questions auditors and customers commonly ask
- 11Questions to ask a software supplier
- 12Common failure modes and checks
- 13Where V5 fits
How does GAMP 5 apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What GAMP 5 is
GAMP 5 — full title 'A Risk-Based Approach to Compliant GxP Computerized Systems' — is published by ISPE, an industry association. ISPE describes its aim as a cost-effective framework of good practice so computerised systems are fit for intended use and compliant with applicable regulations.
Regulators do not certify against GAMP, and no software is 'GAMP 5 compliant' in a legal sense. Companies use it to plan how they will meet requirements such as EU GMP Annex 11, 21 CFR Part 11 or Part 820 software validation.
02What the Second Edition emphasises
According to ISPE's public description, the 2022 edition keeps the first edition's principles and updates them for:
- the larger role of service providers, encouraging regulated companies to use supplier knowledge and documentation where possible;
- iterative and incremental development, not only a linear specify-then-verify model;
- software tools and automation across the lifecycle;
- critical thinking by knowledgeable subject-matter experts;
- links to FDA's CSA approach and to data integrity guidance, with appendices on topics such as cloud, AI/ML and open-source software.
03Law, guidance and industry practice
| Document | Who issues it | Status |
|---|---|---|
| 21 CFR Part 11, Part 211, Part 820 | FDA | U.S. regulation |
| EU GMP Annex 11 | European Commission | EU GMP guideline |
| CSA guidance | FDA | Nonbinding guidance |
| GAMP 5 | ISPE | Industry good practice |
04Worked example
A company buying a configurable SaaS quality system uses GAMP thinking to plan validation: it assesses the supplier, reuses supplier test evidence where the assessment supports it, concentrates its own testing on configured workflows that affect product quality, and documents the reasoning. The plan cites Annex 11 and Part 11 as the requirements; GAMP explains the approach.
05Why GAMP 5 matters to regulated manufacturers
Regulators expect computerised systems that support GxP activities to be fit for their intended use and to protect the records they hold. EU GMP Annex 11 asks for risk management across the system lifecycle, documented validation scaled to that risk, and controls over suppliers. FDA's Computer Software Assurance guidance likewise describes a risk-based approach that concentrates assurance effort where a software failure could affect product quality or patient safety. Neither text tells a company exactly how to plan and document that work. GAMP 5 is the industry guide many companies use to fill that gap.
Its value is a shared vocabulary. When a quality team, an IT team, an auditor and a software supplier all talk about intended use, risk, supplier leverage and lifecycle, they are usually working from GAMP-style thinking. That shared language makes supplier assessments, validation plans and audit conversations faster and less adversarial.
It also matters because the alternative is expensive. Before risk-based thinking became mainstream, many sites tested every screen and field to the same depth and produced binders that nobody read. The Second Edition, according to ISPE's public description, places more emphasis on critical thinking and on using tools and automation, which supports spending effort where it reduces real risk.
06Core ideas in plain language
This page does not summarise the paid guide's text. The ideas below are the widely discussed principles that ISPE's public material and the regulator texts point to, written in plain language.
- Intended use first: describe what the system does in your process and which GxP records or decisions depend on it, before deciding how much to test.
- Risk drives effort: functions that could affect product quality, patient safety or data integrity deserve more assurance than reporting conveniences.
- Leverage the supplier: where a supplier has credible development and testing practices, a regulated company can rely on that evidence instead of repeating it, after assessing the supplier.
- Lifecycle, not a one-off event: the validated state is maintained through change control, periodic review, incident handling and eventual retirement.
- Critical thinking over templates: documentation should record decisions and evidence, not fill sections for their own sake.
- Data integrity throughout: records should stay attributable, legible, contemporaneous, original and accurate across their whole retention period.
07A practical lifecycle a site can follow
The steps below are a common way regulated companies organise risk-based work on a computerised system. Each company sets its own procedure; this is an illustration, not a quotation from the guide.
- Concept and intended use: write a short statement of what the system will do, which processes and records it touches, and who owns it in the business and in quality.
- Requirements: capture user requirements in testable language, separating GxP-critical needs from convenience features.
- Supplier assessment: review the supplier's quality practices, release process, security and support. Decide what supplier evidence you can rely on.
- Risk assessment: for each GxP-relevant function, ask what could go wrong, how likely it is to go undetected, and what the impact would be. Record the reasoning.
- Configuration and verification: configure the system for your process, then test what matters most, using scripted tests for high-risk functions and lighter unscripted testing elsewhere where your procedure allows.
- Release and operation: approve the system for use, train users, and set up change control, access reviews, backups and incident handling.
- Periodic review: check at a planned interval that the system still meets its intended use and that changes, deviations and access are under control.
- Retirement: plan how records will remain readable and retrievable for their retention period after the system is replaced.
08Worked example: a cloud batch-record system at a supplement maker
A dietary supplement manufacturer plans to move paper batch records into a cloud manufacturing system. The quality manager writes a two-page intended-use statement: the system will hold master formulas, guide weighing and blending, record in-process checks and route completed batch records for human review before release.
The team splits functions by risk. Recipe scaling, weight capture, lot genealogy, electronic signatures and audit trail are high risk, because an error could release the wrong product or hide a mistake. Dashboards and scheduling views are low risk. The supplier assessment reviews the supplier's release notes, security information and any validation package on offer, and the team records which supplier testing it will rely on.
Internal testing then concentrates on the high-risk functions as configured for this site: does scaling produce the right quantities, does an out-of-tolerance weight block progress, does genealogy trace both ways, and does the audit trail capture changes with user and time. Low-risk views get a short exploratory check. The validation report records what was tested, what was relied on from the supplier and why, and who approved release. The site's own procedure, not the guide, defines the approval.
09Explain it for your operation
- Small food or supplement site: keep it short. A clear intended-use statement, a one-page risk table and focused tests on weighing, labels and traceability are often more defensible than a large template.
- Pharmaceutical manufacturer: expect inspectors to ask how risk decisions were made, how suppliers were assessed and how the validated state is maintained. Link the plan to Annex 11 and Part 11 requirements.
- Medical device manufacturer: align with your quality system procedures and FDA's CSA guidance; GAMP-style thinking can help structure the assurance record.
- Contract manufacturer: customers may audit your computerised systems. A tidy, risk-based validation file that shows supplier assessment and change control answers most questions quickly.
- Warehouse or distribution site: focus on systems that control status, location, expiry and traceability, rather than every report.
10Questions auditors and customers commonly ask
- Where is the intended use documented, and who approved it?
- How did you decide which functions were high risk?
- What supplier evidence did you rely on, and how did you assess the supplier?
- How are system changes, including supplier updates, evaluated before use?
- When was the last periodic review, and what did it find?
- How are access rights granted, reviewed and removed?
- How will records stay readable after the system is retired?
11Questions to ask a software supplier
- What does your development and release process look like, and what evidence can you share?
- How do you notify customers of changes, and how much notice do you give?
- Which documentation is available to support our own validation, and on which plans?
- How are audit trails, electronic signatures and access controls implemented?
- Where is data hosted, how is it backed up, and how are restores tested?
- Will you support a supplier audit or questionnaire?
A supplier cannot validate your use of its system for you. Its evidence can reduce your work, but your company still decides how the system is used and approves it.
12Common failure modes and checks
- Citing GAMP 5 as a legal requirement in procedures or contracts.
- Accepting a vendor's 'GAMP compliant' claim as validation.
- Applying a heavy document template regardless of risk, which the Second Edition explicitly moves away from.
13Where V5 fits
Customers often apply GAMP-style supplier assessment to V5. Enterprise may include IQ/OQ documentation and validation support that a customer can evaluate as supplier evidence. The customer decides how GAMP applies, performs any PQ and approves its validated state.
Frequently asked questions
Q.Is GAMP 5 a regulation?+
No. It is an ISPE industry guide.
Q.When was the Second Edition published?+
July 2022, according to ISPE.
Q.Can software be GAMP 5 certified?+
No. There is no GAMP certification for software.
Q.Were GAMP software categories reviewed for this page?+
No. The guide is a paid publication and was not opened, so this page does not summarise its categories.
Q.Does GAMP 5 require scripted testing of everything?+
No. Risk-based approaches concentrate scripted testing on high-risk functions; your own procedure sets the rules.
Q.Who approves a system as validated?+
The regulated company, under its own procedures. A supplier cannot approve it on the customer's behalf.
Primary sources
Further reading
Explore this topic
GAMP 5 sits inside 2 overlapping topic clusters in our glossary. Every neighbour is one click away.
Electronic records, signatures, audit trail and ALCOA+ data-integrity principles.
URS-through-PQ lifecycle, GAMP 5 categorisation and CSA's modern alternative.
Want to see how GAMP 5 could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
