When a record closes it does not leave for an archive; it stays in the portal. The close note, the rejection reason, and the implementation line are not deleted. A lesson learned is not a separate journal application. The same reference becomes the source for later work.
On an approved suggestion the implementation note describes the work on the floor. On a rejected record the reason states why a similar text will not move. Revision history shows which field was missing. All three are lesson lines.
A success story is the period summary of finished work. It does not replace a suggestion or a kaizen. The story writes the measured result and the place of application. The reader opens the source record from the reference.
On a near miss the outcome note states whether the immediate action became permanent work. If it did not, a new suggestion or kaizen is opened. The older place and risk lines are not copied; they are read and written onto the new file.
Quality looks at closed records in the period meeting. A repeating category, a wrong bucket, or a missing measure is marked as a lesson. HR takes the training subject from the same list.
Search runs on older titles and authors. The branch filter shows whether the same lesson was applied at another location. The person who opens a new record finds a similar file by search, not from the task list.
Points are not proof of a lesson. If a point rule exists they post to the balance; the close note remains separate. An audit asks for step history. The lesson sentence is read from that history.
The web-based file replaces a “lessons learned” sheet on a shared spreadsheet. Sign-in is through the browser over SSL. Corporate identity is the same logo and color on this list as well.