I didn't think reading can still be a project even after high school when book reports were requirements to get a final grade.
It's the LSOP elevation thing where my department and another one we call CSD embark on reviewing just about 200 local SOPs (LSOPs) developed by colleagues that are either still here or not. These LSOPs come from different properties/branches and from different departments. Just imagine the bulk of the reading material! Eeeek!
Aside from reading them, we have to literally review them one by one and sort them out according to a set of criteria to be able to come up with a list of all the LSOPs that we shall be recommending to be elevated to SOP status. Which means, in normal human language, that once these local SOPs are made into SOPs, they can be implemented or required to be implemented universally or to all properties/branches. Did you understand anything there? lol!
As a backgrounder, so you all won't be too confused about the terms,
An LSOP or Local Standard Operating Procedure is a set of procedures developed by a particular authority, which can be a supervisor or the department head him/herself, submitted for approval, and once approved, can only be implemented or is just applicable to their own branch, and not to the other geographical branches. For example, one Finance LSOP created by the Finance Controller of the Manila Branch is only applicable to the Manila Branch.
On the other hand, an SOP or Standard Operating Procedure, is of course mandatory and applicable to all branches, regardless of location or authorship.