Log: Knowledge Management and Lessons Learned Register (ICH Q10 Enabler)

This is a ready-to-use register for the knowledge management enabler ICH Q10 names alongside quality risk management. Its job is to capture process, product, and system knowledge as it is generated, not only as an afterthought when someone leaves, and to make that knowledge findable and reusable in the decisions that need it: investigations, risk assessments, change impact reviews, and training. Replace every <<FILL: ...>> placeholder, set your document number, and route through your normal document control. A filled specimen follows. Confirm each cited regulation against the current source before you rely on it.

Log control header

Field	Entry
Log title	Knowledge Management and Lessons Learned Register
Log number	`<<FILL: LOG-ID, e.g. LOG-QA-030>>`
Version	`<<FILL: version, e.g. 1.0>>`
Governing SOP	`<<FILL: SOP-ID for knowledge management, or N/A if this log is the governing document>>`
Maintained by	`<<FILL: role, e.g. Quality Systems / Knowledge Management Lead>>`
Review frequency	`<<FILL: e.g. quarterly, in the quality council meeting>>`

1. What gets an entry

Log an entry whenever one of the following occurs:

A deviation, OOS, or CAPA investigation reveals a root cause or a systemic weakness with value beyond the single event.
A technology transfer, process validation, or method development effort produces process understanding not fully captured in the approved procedure (a sensitivity, a workaround, a failure mode avoided).
A change control reveals an unexpected interaction or an assumption that was wrong.
A subject matter expert with critical, undocumented process knowledge is leaving the role, retiring, or moving to another site.
An external signal (an audit finding elsewhere in the network, a competitor’s warning letter, a literature finding) changes how a risk should be assessed here.

2. Field definitions

Field	Format	Required	Who enters	When
Entry ID	Text	Yes	Submitter	At capture
Date captured	Date	Yes	Submitter	At capture
Source	Deviation / CAPA / Tech transfer / Change control / SME exit / External signal / Other	Yes	Submitter	At capture
Source reference	Text	Yes	Submitter	At capture
Knowledge summary	Text	Yes	Submitter	At capture
Product / process / system	Text	Yes	Submitter	At capture
Category tag	Process / Analytical / Equipment / Facility / Supplier / Regulatory / Other	Yes	Submitter	At capture
Where it should be applied	Text	Yes	Reviewer	At review
Action taken (procedure, training, risk assessment updated)	Text	Yes at closure	Owner	At closure
Status	Captured / Under review / Actioned / No action needed (with reason)	Yes	Owner	Ongoing
Closure date	Date	Yes at closure	Reviewer	At closure

3. Register

Entry ID	Date	Source	Source ref	Knowledge summary	Product/process	Category	Where applied	Action taken	Status	Closure date
`<<FILL>>`	`<<FILL>>`	`<<FILL>>`	`<<FILL>>`	`<<FILL>>`	`<<FILL>>`	`<<FILL>>`	`<<FILL>>`	`<<FILL>>`	`<<FILL>>`	`<<FILL>>`
`<<FILL>>`	`<<FILL>>`	`<<FILL>>`	`<<FILL>>`	`<<FILL>>`	`<<FILL>>`	`<<FILL>>`	`<<FILL>>`	`<<FILL>>`	`<<FILL>>`	`<<FILL>>`

4. Instructions

Capture the entry close to the source event, not weeks later from memory. A knowledge management program that only writes entries during an SME’s exit interview has already lost most of what it should have captured.
Tag the entry with a category and the product, process, or system it applies to, so it can be searched later by someone who was not present when it was written.
Route every entry to a reviewer (the process owner, technical SME, or QA depending on category) within <<FILL: number>> working days to decide where it should be applied.
Close an entry only when the action (a procedure update, a training update, a risk assessment update, or a documented decision that no action is needed and why) is recorded, not merely when it has been read.
At the review cadence in the header, check for entries open past their target review window and for themes across entries that suggest a systemic gap worth a CAPA.
Before a technology transfer, a major change, or a new risk assessment, query this register for prior knowledge relevant to the product, process, or system in scope. Document that the query was performed, even when it returns nothing.

5. Retention

Retain per the records retention schedule, not less than <<FILL: retention period>>. This register is a controlled quality record and a primary artifact of the knowledge management enabler; entries are never deleted, only updated with a traceable history.

6. References

ICH Q10, Pharmaceutical Quality System, section on knowledge management as an enabler. ICH Q12, Technical and Regulatory Considerations for Pharmaceutical Product Lifecycle Management, for how captured knowledge supports established conditions.

Confirm the current version of each reference before issue.

7. Revision history

Version	Date	Author	Summary of change
`<<FILL: 1.0>>`	`<<FILL: date>>`	`<<FILL: author>>`	Initial issue.

Filled specimen

The following shows the register with two entries, one from a departing subject matter expert and one from a deviation investigation. Details are illustrative.

Entry ID	Date	Source	Source ref	Knowledge summary	Product/process	Category	Where applied	Action taken	Status	Closure date
KM-2026-014	03-Jun-2026	SME exit	HR transition notice	Lyophilization cycle for Product X runs a shorter primary drying hold than the batch record implies is optimal; the extra margin was added after an early-development excursion never formally documented in the validation report	Product X, lyophilization	Process	Lyophilization SOP; process validation report addendum	SOP updated with the rationale and the historical excursion referenced; process validation report addendum filed	Actioned	28-Jun-2026
KM-2026-019	11-Jul-2026	Deviation	DEV-2026-0187	Root cause of a recurring CDS audit trail gap traced to a specific software update interacting with the site’s antivirus scan schedule	Chromatography Data System, HPLC-04 to HPLC-09	System	CSV risk assessment for other CDS instances; supplier communication log	Risk assessment updated for two other CDS clusters on the same software version; supplier notified	Actioned	20-Jul-2026

The first entry is the classic knowledge management save: a fact that lived in one person’s head, captured before they left, with the gap between what the SOP implies and what actually happened in development closed permanently. The second shows the register doing double duty as a proactive signal, one system’s root cause protecting two others before they have the same failure.

Common inspection findings this log prevents

A subject matter expert leaves and takes undocumented process rationale with them; the next investigation cannot explain a design decision made years earlier.
The same root cause recurs on a second, similar system because the first investigation’s finding was never checked against other systems that shared the same risk.
Technology transfer packages are thin because development knowledge was never captured anywhere retrievable.
The company cannot demonstrate, when asked, how it operationalizes the knowledge management enabler ICH Q10 names, beyond pointing at individual deviation records.

How to adapt this log

Decide whether this register stands alone or is built into your existing eQMS as a record type; the point is that it is searchable, not that it uses a specific tool.
Set your review frequency and routing rules to match your organization’s size; a large multi-site network may need site-level and network-level tiers.
Build the “query before you start” step (instruction 6) into your technology transfer, change control, and risk assessment procedures as a required check, not an optional courtesy.
Confirm the references in section 6 against the current published version before issue.