| S.No. | Checkpoint | IS Requirement | Status |
|---|---|---|---|
| A. REGISTER COLUMN DEFINITIONS | |||
| A1 | Column 1: LESSON NO — unique identifier (LL-PROJ-###) Acceptance: Format consistent; unique; sequential by capture date | Cl. 7.5.3 — Documented information | OK NC NA HOLD |
| A2 | Column 2: DATE CAPTURED — date lesson was identified and logged Acceptance: Within 14 days of triggering event; not aggregated to year-end | Cl. 10.3 — Timely capture | OK NC NA HOLD |
| A3 | Column 3: SOURCE EVENT — NCR/CAR/Audit/Incident/Success/Workshop Acceptance: Source identified with reference number; balanced negative and positive sources | Cl. 9.1 — Sources of learning | OK NC NA HOLD |
| A4 | Column 4: SITUATION — context of what happened Acceptance: Brief narrative; what/where/when; allows others to recognize similar situations | Cl. 9.1.1 — Factual context | OK NC NA HOLD |
| A5 | Column 5: WHAT WORKED / WHAT DIDN'T — outcome and contributing factors Acceptance: Clear cause-effect; both positive and negative outcomes captured | Cl. 10.3 — Improvement insight | OK NC NA HOLD |
| A6 | Column 6: LESSON — generalizable principle or recommendation Acceptance: Lesson stated as principle; transferable to other contexts; not just project-specific | Cl. 10.3 — Generalizable insight | OK NC NA HOLD |
| A7 | Column 7: CATEGORY — Quality / Safety / Schedule / Cost / Procurement / Design / People Acceptance: One primary category; allows filtering for future project teams | Cl. 9.1.3 — Categorization | OK NC NA HOLD |
| A8 | Column 8: ACTION TAKEN — implementation in this/future project (procedure update, training, etc.) Acceptance: Action specified; tied to QMS document or training plan; not just FYI | Cl. 10.3 — Action on lesson | OK NC NA HOLD |
| A9 | Column 9: STATUS — CAPTURED / SHARED / IMPLEMENTED / EMBEDDED IN QMS Acceptance: Status updated; EMBEDDED only when QMS revision issued or training rolled out | Cl. 10.3 — Implementation tracking | OK NC NA HOLD |
| A10 | Column 10: OWNER & TARGET DATE — who follows up and when Acceptance: Named individual; target date for next-step action; reviewed monthly | Cl. 5.3 — Ownership | OK NC NA HOLD |
| B. CAPTURE TRIGGERS AND CADENCE | |||
| B1 | Lessons captured at end of each project phase (mobilization, structure, MEP, finishes, handover) Acceptance: Phase-end workshops scheduled; minimum 5 lessons per phase | Cl. 10.3 — Phase-end review | OK NC NA HOLD |
| B2 | Major NCR/incident closure triggers lesson capture; integrated with CAR effectiveness review Acceptance: Each Major NC closure produces a lesson entry; cross-referenced to CAR no | Cl. 10.2.1 — Learning from NC | OK NC NA HOLD |
| B3 | Successes also captured: where work delivered ahead/under/with high quality — what made it work Acceptance: ≥30% of lessons are about successes; ratio reviewed quarterly | Cl. 10.3 — Positive learning | OK NC NA HOLD |
| C. SHARING AND DISSEMINATION | |||
| C1 | Project lessons shared via monthly newsletter, PMO portal, or knowledge base Acceptance: Lessons published monthly; accessible to all projects; searchable by category | Cl. 7.4 — Internal communication | OK NC NA HOLD |
| C2 | Lessons reviewed at start of new projects; relevant ones built into project plan Acceptance: Project kick-off includes lessons review; relevant lessons cited in project QA plan | Cl. 8.1 — Operational planning | OK NC NA HOLD |
| C3 | Cross-project lessons workshops held annually; org-wide trends identified Acceptance: Annual workshop documented; cross-cutting themes; corporate-level actions launched | Cl. 10.3 — Org-wide learning | OK NC NA HOLD |