We get called in fairly often to "write the SOPs", and a good proportion of the time the SOPs already exist. Someone wrote them two years ago, thoroughly, and they are in a folder on a shared drive that three people know the path to.
Writing a procedure is the part of the job that feels like work. Getting it to the person who needs it, at the moment they need it, in a form they will actually read standing at a bench or on a phone in a truck — that is the part that decides whether any of it mattered.
The test
Ask someone in their second month to find the procedure for something routine. Time it. If it takes more than about ninety seconds, the procedure does not functionally exist, whatever the document control register says.
What usually fixes it
Rarely a new system. Usually: fewer documents, named the way people actually refer to the task, in one place, with the three or four that get used daily separated out from the forty that get used annually. The organization that has 200 procedures and the one that has 12 procedures and 188 reference documents have the same content and completely different outcomes.
The other thing that fixes it is deleting things. A procedure set nobody trusts is one where some of it is out of date and there is no way to tell which parts. Removing what is wrong is worth more than adding what is missing.