---
artifact_id: A30
name: Knowledge and Lessons Management Record
template_version: "1.0.0"
status: "Template · Active"
category: Knowledge Capture and Organizational Learning
authority: "PMBOK8 Guide Table 2-1 Manage Project Knowledge; Resources Performance Domain §2.6; §1.1.3 Organizational Process Assets"
source_type: synthesis
file_path: artifacts/knowledge/A30-knowledge-and-lessons-management-record-template.md
---

## [A30] — Knowledge and Lessons Management Record | Template

> **Usage note:** This is a blank template. Every `[FIELD: ...]` cell must be completed by the project team before use. Static text, rules, and checklist items are pre-filled and must not be removed. Do not pre-populate fields with example data.

---

## Section 1 — Header / Identification

| Field | Value |
|---|---|
| Project Name | [FIELD: Full project name as registered in the project charter] |
| Project Manager | [FIELD: Name and title of the project manager] |
| Knowledge Owner | [FIELD: Name and title of the individual responsible for maintaining this record] |
| Capture Period | [FIELD: Time period covered by this record, e.g., Sprint 3 / Phase 2 / Full Project] |
| Version | [FIELD: Version number, e.g., 1.0] |
| Status | [FIELD: select from Draft / Active / Submitted to OPA / Closed] |
| Linked Artifacts | A18 — Quality Management Plan; A19 — Issue Register; A17 — Risk Register; A07 — Project Schedule; A24 — Project Closure Report; A23 — PMO Improvement Register |

---

## Section 2 — Lessons Register

Categories: **Risk / Schedule / Stakeholder / Technical / Procurement / Resources / Governance / Other**. Validation Status: **Draft / Reviewed / Approved for OPA**. Applicability: **This Project Only / Similar Projects / All Projects / Portfolio-wide**.

| Lesson ID | Capture Date | Source Event | Category | Description | Impact | Recommendation | Applicability | Validation Status | OPA Destination | Owner |
|---|---|---|---|---|---|---|---|---|---|---|
| [FIELD: e.g., LL-001] | [FIELD: YYYY-MM-DD] | [FIELD: Event or situation that prompted this lesson, e.g., schedule slip in Phase 2] | [FIELD: select from Risk / Schedule / Stakeholder / Technical / Procurement / Resources / Governance / Other] | [FIELD: Clear, factual description of what happened and what was learned] | [FIELD: Describe the effect on the project — positive or negative — time, cost, quality, risk] | [FIELD: Specific, actionable recommendation for future projects or current team] | [FIELD: select from This Project Only / Similar Projects / All Projects / Portfolio-wide] | [FIELD: select from Draft / Reviewed / Approved for OPA] | [FIELD: Target OPA repository or category where this lesson will be stored] | [FIELD: Name of the person responsible for validating and submitting this lesson] |
| [FIELD: e.g., LL-002] | [FIELD: YYYY-MM-DD] | [FIELD: Source event description] | [FIELD: select from Risk / Schedule / Stakeholder / Technical / Procurement / Resources / Governance / Other] | [FIELD: Description of what happened and what was learned] | [FIELD: Impact description] | [FIELD: Actionable recommendation] | [FIELD: select from This Project Only / Similar Projects / All Projects / Portfolio-wide] | [FIELD: select from Draft / Reviewed / Approved for OPA] | [FIELD: OPA destination] | [FIELD: Owner name] |
| [FIELD: e.g., LL-003] | [FIELD: YYYY-MM-DD] | [FIELD: Source event description] | [FIELD: select from Risk / Schedule / Stakeholder / Technical / Procurement / Resources / Governance / Other] | [FIELD: Description of what happened and what was learned] | [FIELD: Impact description] | [FIELD: Actionable recommendation] | [FIELD: select from This Project Only / Similar Projects / All Projects / Portfolio-wide] | [FIELD: select from Draft / Reviewed / Approved for OPA] | [FIELD: OPA destination] | [FIELD: Owner name] |
| [FIELD: e.g., LL-004] | [FIELD: YYYY-MM-DD] | [FIELD: Source event description] | [FIELD: select from Risk / Schedule / Stakeholder / Technical / Procurement / Resources / Governance / Other] | [FIELD: Description of what happened and what was learned] | [FIELD: Impact description] | [FIELD: Actionable recommendation] | [FIELD: select from This Project Only / Similar Projects / All Projects / Portfolio-wide] | [FIELD: select from Draft / Reviewed / Approved for OPA] | [FIELD: OPA destination] | [FIELD: Owner name] |

> Add rows as needed. Lessons should be captured continuously throughout the project — not only at closure.

---

## Section 3 — Category Summary

This table provides a summarised view for PMO review. Update counts whenever the Lessons Register (Section 2) is updated.

| Category | Lesson Count | Notes |
|---|---|---|
| Risk | [FIELD: Count of lessons in the Risk category] | [FIELD: Notable theme or pattern, if any] |
| Schedule | [FIELD: Count of lessons in the Schedule category] | [FIELD: Notable theme or pattern, if any] |
| Stakeholder | [FIELD: Count of lessons in the Stakeholder category] | [FIELD: Notable theme or pattern, if any] |
| Technical | [FIELD: Count of lessons in the Technical category] | [FIELD: Notable theme or pattern, if any] |
| Procurement | [FIELD: Count of lessons in the Procurement category] | [FIELD: Notable theme or pattern, if any] |
| Resources | [FIELD: Count of lessons in the Resources category] | [FIELD: Notable theme or pattern, if any] |
| Governance | [FIELD: Count of lessons in the Governance category] | [FIELD: Notable theme or pattern, if any] |
| Other | [FIELD: Count of lessons in the Other category] | [FIELD: Notable theme or pattern, if any] |
| **Total** | [FIELD: Total lesson count across all categories] | |

---

## Section 4 — OPA Contribution Queue

List all lessons approved for OPA submission. Confirmation Status: **Pending / Submitted / Confirmed / Rejected**.

| Lesson ID | Recommendation Summary | OPA Destination | Submission Date | Confirmation Status |
|---|---|---|---|---|
| [FIELD: Lesson ID from Section 2] | [FIELD: Brief summary of the recommendation being submitted to the OPA] | [FIELD: Specific OPA repository, folder, or category] | [FIELD: YYYY-MM-DD] | [FIELD: select from Pending / Submitted / Confirmed / Rejected] |
| [FIELD: Lesson ID from Section 2] | [FIELD: Brief summary of the recommendation being submitted to the OPA] | [FIELD: Specific OPA repository, folder, or category] | [FIELD: YYYY-MM-DD] | [FIELD: select from Pending / Submitted / Confirmed / Rejected] |
| [FIELD: Lesson ID from Section 2] | [FIELD: Brief summary of the recommendation being submitted to the OPA] | [FIELD: Specific OPA repository, folder, or category] | [FIELD: YYYY-MM-DD] | [FIELD: select from Pending / Submitted / Confirmed / Rejected] |

> Only lessons with Validation Status = "Approved for OPA" (Section 2) should appear here.

---

## Section 5 — PMO Improvement Inputs

Use this section to track lessons that warrant a process or procedural improvement to be logged in the PMO Improvement Register (A23).

| Item | Source Lesson ID | Recommended Improvement | Forwarded to A23 Date |
|---|---|---|---|
| [FIELD: Brief improvement item title] | [FIELD: Lesson ID from Section 2 that triggered this input] | [FIELD: Specific improvement recommended for the PMO to consider — process, template, tool, or training] | [FIELD: YYYY-MM-DD, or "Not yet forwarded"] |
| [FIELD: Brief improvement item title] | [FIELD: Source Lesson ID] | [FIELD: Specific improvement recommended] | [FIELD: YYYY-MM-DD, or "Not yet forwarded"] |
| [FIELD: Brief improvement item title] | [FIELD: Source Lesson ID] | [FIELD: Specific improvement recommended] | [FIELD: YYYY-MM-DD, or "Not yet forwarded"] |

---

## Section 6 — Capture Rules

The following rules apply to all lessons captured in this record. These are standing operating rules and must not be removed or modified without PMO authority.

1. Lessons must be captured at the time of the event — retrospective capture after project closure reduces accuracy and applicability.
2. Each lesson must be written in neutral, factual language. Blame language is prohibited.
3. Every lesson must include both a description of what happened and a specific, actionable recommendation.
4. Lessons must be validated by at least the Project Manager before submission to the OPA.
5. Lessons classified as "Approved for OPA" must be submitted to the OPA repository within 15 business days of that classification.
6. Duplicate lessons must be consolidated — each unique learning point should appear once with cross-references where the same event generated multiple insights.
7. Lessons rated as "Portfolio-wide" applicability must be escalated to the PMO within 5 business days of approval.
8. This record is a living document — it must be updated at every project phase boundary and at project closure.
9. The Knowledge Owner is responsible for ensuring completeness and accuracy; the PM is responsible for ensuring lessons are acted upon.
10. This record must be linked to A24 (Project Closure Report) at closure and referenced in the closure sign-off.

---

## Section 7 — Waste Test

*Answer each question before finalizing this record. If any answer is "No", revisit the relevant section.*

- [ ] Is every lesson described factually with a clear, actionable recommendation?
- [ ] Has every lesson been assigned a validation status?
- [ ] Does the Category Summary (Section 3) count match the actual entries in the Lessons Register (Section 2)?
- [ ] Are all lessons marked "Approved for OPA" included in the OPA Contribution Queue (Section 4)?
- [ ] Have lessons with PMO-improvement implications been forwarded to A23?
- [ ] Is every lesson assigned a named owner?
- [ ] Has the Knowledge Owner reviewed this record for completeness?
- [ ] Has the PM signed off on all lessons marked "Approved for OPA"?
- [ ] Is this record updated to reflect the current capture period?
- [ ] Is this record referenced in the Project Closure Report (A24) at project closeout?

---

## Change Log

| Version | Date | Author/Event | Description |
|---|---|---|---|
| 1.0.0 | 2026-05-31 | Phase B2 Batch B | Initial template |

---

*Template for: Knowledge and Lessons Management Record*
*Authority: PMBOK8 Guide Table 2-1 Manage Project Knowledge; Resources Performance Domain §2.6; §1.1.3 Organizational Process Assets*
*See definition file: artifacts/knowledge/A30-knowledge-and-lessons-management-record-template.md*
