Build a GxP Computerized System Inventory You Can Maintain
An inventory is only useful while it stays current. This how-to sets the boundary, reconciles the lists you already have, names owners and records relevance decisions, with a copyable template and three synthetic rows.
Written by CSV/CSA Maturity Editorial TeamPublished 10 min read
On this page12 sections
A GxP computerized system inventory is a maintained list of the systems inside a defined boundary. For each system it records an accountable owner, a short statement of intended use, a decision about relevance to regulated work with a reference to its rationale, and the events that send the entry back for review. To build one that stays current, fix the boundary, reconcile the lists that already exist, and assign owners before filling in anything else.
This how-to applies to a single team, site or system portfolio in a life sciences organization. GxP is shorthand for the good practice requirements that apply to regulated work, such as manufacturing, laboratory and clinical practice. The template further down is an editorial example. It is not a form issued or mandated by FDA or any other regulator, and it needs no particular technology: a controlled spreadsheet is enough. The steps also prepare the first practice area of the CSV/CSA Maturity Assessment, a self-assessment of computer system validation (CSV) and computer software assurance (CSA) practices. CSV here does not mean comma-separated values.
What the primary sources say about inventories
This guide refers to two regulatory contexts, and they say different things. Keep them apart.
EU GMP for medicinal products. Annex 11 [S36] says an up-to-date listing of relevant systems and their GMP functionality should be available (clause 4.3). As of November 12, 2026, the EudraLex Volume 4 index [S04] lists Annex 11 as the January 2011 revision. The European Commission consulted on a revised Annex 11 in 2025 [S05]. As of the same date that text remains a consultation draft, and nothing in this guide relies on it.
Medical device production and quality management system software. FDA's final guidance on computer software assurance [S02], issued in February 2026, gives nonbinding recommendations for software used as part of medical device production or the quality management system. The guidance document [S03] does not mention a system inventory. It does recommend documenting how the manufacturer decided whether software is used as part of production or the quality management system, and it says general business software, such as email or accounting applications, generally falls outside the validation requirement.
Our reading is that an inventory is a practical place to record which systems are relevant and to point to the reasoning, in either context. That is an editorial view. Neither source prescribes the template below, and which requirements apply to your systems is a question for your quality and regulatory specialists.
Step 1: Define the inventory boundary
Decide what the list covers before you count anything. State the boundary in one sentence: the team, site or system portfolio, and what counts as a system. Then settle four edge cases in writing:
- spreadsheets, macros and small tools built in-house that calculate, store or approve something;
- hosted services where the supplier runs the software;
- instruments and equipment with embedded or attached software;
- interfaces and reporting layers that move or reshape records between systems.
You do not have to include all four. You do have to say which are in, so that a reviewer can tell an omission from a decision.
Use the same boundary you would select as the scope of the assessment. Its first question asks how reliably the team can identify the computerized systems "in the scope you selected".
Step 2: Reconcile the sources you already have
No single list is complete. Compare several and record the differences.
| Source | What it tells you | What it misses |
|---|---|---|
| IT application or asset register | Installed and hosted applications, technical contacts | How each one is used, and tools outside IT's view |
| Supplier or vendor list | Who is paid for software and services | Use, ownership and anything built in-house |
| Validation or assurance document index | Systems someone once assessed | Systems added since, and systems never assessed |
| Access or single sign-on application list | What people log in to | Standalone instruments and local files |
| Change and incident records | Systems that changed or failed recently | Stable systems nobody touches |
| Conversations with process owners | What the process actually depends on | Whatever people forget to mention |
A vendor list deserves a specific warning, because it looks like an inventory and is not one. It records who supplies a product. An operational inventory records how a system is used here. One product can appear as two systems with different uses, owners and relevance decisions. A spreadsheet built by a laboratory analyst has no vendor and never appears on a supplier list. Relevance, in particular, cannot be read from a vendor name.
Keep the reconciliation itself as a record: the date, the sources compared, the entries added or removed, who did the work and who reviewed it. A recent reconciliation record is one of the three items the assessment suggests checking for its first question, next to a current inventory and named owners.
Step 3: Name an accountable owner for every entry
The accountable owner answers for how the system is used, and is usually the process or business owner. The person who administers the system technically holds a different role. Record both if that helps, and do not merge them. Use a person's name in your real inventory. The examples below show roles only because they are synthetic.
When no owner can be found, write "Not assigned", add who is pursuing the assignment and by when, and leave the gap visible. Filling the cell with a department name, or with the system administrator by default, hides the ownership gap the assessment asks about.
Step 4: Summarize intended use in one or two sentences
The inventory needs a summary, not the full statement: who uses the system, for which activity, producing which record or output. Write it for the use in this scope. A product category such as "laboratory information management" tells a reviewer nothing about what your team relies on the system to do. The full statement belongs in its own controlled document, and the how-to on writing a clearer intended-use statement covers it.
Step 5: Record the relevance decision and where its rationale lives
For each entry record three things: the decision (relevant to regulated work, not relevant, or uncertain), a reference to the record that holds the rationale, and who approved it. The inventory holds the pointer. The reasoning stays in the referenced record, where it can be approved and versioned. In our view a usable rationale says which regulated activity, record or decision the system touches and what a failure or a wrong output would affect.
"Uncertain" is a legitimate entry. When the decision is open, write the question that has to be answered, name the person who will decide, set a date, and note what the system may be used for in the meantime. Do not close the row with "not relevant" to make the list look finished, and do not infer relevance from the supplier or the product category.
The inventory records relevance decisions. It does not make them, and it does not decide which laws apply. Your procedure should say who makes a relevance decision and who resolves an uncertain one. The assessment's playbook suggests the system owner and the quality lead for this practice area. A reviewer should be able to get the answer from the procedure, not from whoever happens to be in the room.
Step 6: Define what triggers a review
An entry goes stale when the system changes and the row does not. Give every entry a change trigger, meaning the events that send it back to its owner:
- a new module, interface or integration;
- a change in who uses the system or in the records it produces;
- a configuration change that alters a workflow;
- a supplier release that changes functions you use;
- a change of hosting arrangement or supplier;
- the owner moving to another role;
- a set review date reached without any of the above.
The connection between your change process and the inventory is what separates the two highest practice descriptions for relevance decisions in the assessment. The guide to reviewing software changes and supplier releases covers the change side.
Step 7: Handle new systems, retirement and periodic checks
New systems. Decide the entry points and write them down: purchasing requests, IT service requests, project initiation, change control and new subscriptions to hosted services. Each one asks the same question, "Is this a new computerized system or a new use of an existing one?", and routes a yes to the person who maintains the inventory. The entry is created at once with an owner and, if nothing better is known, an uncertain relevance decision. It is not left off the list until the paperwork is complete.
Retirement. Keep the row. Change the lifecycle state to retired, record the date, and note who is responsible for any records that have to remain readable. A reviewer looking at an old record needs to know the system existed.
Periodic checks. At an interval you set, repeat step 2 on a small scale and look specifically for omissions and ownership gaps.
Copyable inventory template
The template has eight fields.
| Field | What to record |
|---|---|
| System ID | A stable internal identifier that survives renaming and supplier changes |
| Site or team scope | Where this use of the system applies. The same product used differently elsewhere gets its own row |
| Accountable owner | The named person who answers for how the system is used. "Not assigned" is a valid, visible value |
| Intended-use summary | One or two sentences: users, activity, output |
| Relevance decision reference | Relevant, not relevant or uncertain, with the ID of the record that holds the rationale and its approver |
| Lifecycle state | Planned, in use, change in progress, or retired |
| Last review | The date the entry was last confirmed against actual use |
| Change trigger | The events that send the entry back to its owner |
Three synthetic rows
Synthetic sample. The systems, identifiers, roles and dates below are invented for illustration and describe no real organization. The eight fields are split across two tables so they read on a phone. In a spreadsheet they form one row per system.
| System ID | Site or team scope | Accountable owner | Intended-use summary | Lifecycle state |
|---|---|---|---|---|
| SYS-001 | Site A, quality operations | Head of document control | Moves controlled procedures through drafting, review, approval, issue and periodic review. Staff work from the effective version it issues. | In use |
| SYS-002 | Site A, quality control laboratory | Laboratory manager | Collects results from analytical instruments for release testing and stores the result files. | Change in progress |
| SYS-003 | Site A, facilities | Not assigned. Facilities lead acting until 2026-12-01 | Schedules maintenance work orders for building services. May also schedule calibration of production equipment: to be confirmed. | In use |
| System ID | Relevance decision reference | Last review | Change trigger |
|---|---|---|---|
| SYS-001 | Relevant. Rationale REL-001, approved by the quality lead | 2026-09-15 | Workflow or approval-route change; supplier release affecting versioning or approval; new user group |
| SYS-002 | Relevant. Rationale REL-002, approved by the quality lead | 2026-10-02 | Instrument added or removed; change to calculations or result transfer; supplier release |
| SYS-003 | Uncertain. Open question REL-003: does the tool hold the calibration record for production equipment, or only a reminder? Decision owner: quality lead with facilities lead. Due 2026-12-01 | Not yet reviewed | Outcome of REL-003; any use of the tool for calibration or production equipment records |
The third row is deliberately unresolved. Nobody has yet established whether the tool holds a record that matters, so the honest state of the entry is "uncertain, with an owner and a date". The template records it that way.
How the inventory supports your assessment answers
The system inventory practice area has two questions. The difference between their third and fourth practice descriptions is the difference between having a list and maintaining one.
| Question | Third description (score 2) | Fourth description (score 3) | Evidence to have on hand |
|---|---|---|---|
| Q01, identifying systems in scope | A maintained inventory identifies the systems in scope and their accountable owners. | The inventory is reconciled against changes and periodically checked for omissions and ownership gaps. | A current inventory, named owners and a recent reconciliation record |
| Q02, relevance decisions | Relevance decisions and their rationale are documented for the systems in scope. | Changes in use or configuration trigger a review of the documented relevance decision. | An approved rationale and one change that prompted reconsideration |
Q02 is one of three questions with a priority review prompt. An answer of 0 raises that prompt and "I do not know yet" raises a verification prompt, whatever the overall score. The assessment asks you not to enter system names, so the inventory stays in your own records and only the practice description goes into the tool. You can read both questions in the system inventory area of the assessment.
Limitations
- An inventory shows what exists and who answers for it. It does not show that any system is validated, controlled or fit for its intended use.
- The template is an editorial example, not a form issued or mandated by any regulator. Change the fields to suit your procedures.
- Relevance decisions need qualified judgment. The inventory records them and cannot make them, and it does not determine which requirements apply.
- The Annex 11 statement applies to EU GMP for medicinal products, and the FDA guidance to software used in medical device production and quality management systems. If your work sits outside both, neither statement addresses it.
- The three rows are synthetic. A higher practice description selected in the assessment remains self-reported until someone checks the records behind it.
Related reading
- Document intended use and clear acceptance expectations: turn the one-line summary in your inventory into a statement a reviewer can test.
- Software change control evidence for changes and supplier releases: what should happen when one of the change triggers fires.
- How to assess CSV/CSA maturity in seven steps: use the inventory boundary as the scope of a full self-assessment.
This article describes assessment model csa-maturity-2.0.0.
Sources and references
- S02Computer Software Assurance for Production and Quality Management System Software. U.S. Food and Drug Administration.
Final guidance (nonbinding), dated February 2026; covers software used in medical device production and quality management systems.
- S03Computer Software Assurance for Production and Quality Management System Software: Guidance for Industry and Food and Drug Administration Staff. U.S. Food and Drug Administration.
Final guidance document (PDF), issued February 3, 2026; nonbinding; supersedes the final guidance issued September 24, 2025.
- S04EudraLex - Volume 4 - Good Manufacturing Practice (GMP) guidelines. European Commission.
Official index of EU GMP guidelines; listed Annex 11 as 'Computerised Systems (revision January 2011)' when checked on November 12, 2026.
- S05Stakeholders’ Consultation on EudraLex Volume 4 - Good Manufacturing Practice Guidelines: Chapter 4, Annex 11 and New Annex 22. European Commission, Directorate-General for Health and Food Safety.
Consultation on draft texts, open July 7 to October 7, 2025; status shown as closed. The drafts are not operative guidance.
- S36EudraLex Volume 4, Annex 11: Computerised Systems. European Commission.
EU GMP guideline, revision 1, with a stated deadline for coming into operation of June 30, 2011; the version linked from the EudraLex index on November 12, 2026.