A library can exist and still be unusable
Most SOP tools write one procedure. The complaint from operations desks is different: the procedure exists, and nobody can tell which file is current. It lives in two drives, the name is the author’s initials, the review date is missing, and the person who knows the answer is interrupted again.
This audit asks twelve questions about that library. Each weak answer becomes a specific gap, not a colour on a gauge. Eight of twelve in place means eight of the checks you answered. It is not a percentile and not a comparison with other companies.
Names, owners, dates, and the old file
Findability fails in a few repeatable ways. There is no single home. The name does not say what the file is. There is no owner. The last review is a file timestamp, which changes when someone opens the document. Old and current copies sit in the same folder, so the sort order decides what people use.
The naming template is there to stop the last of those. Department, process, document type, review date, version. The review schedule is short on purpose: critical SOPs twice a year, the rest yearly, and a same-day move to Archive when a file is replaced. You can edit the cadence. The point is that a date exists.
The questions staff already ask
A findability problem shows up as a repeated question. “Which packing list do we use?” “Who signs a short-supply debit?” “Where is the current goods-receipt instruction?” The sheet has twenty rows because a first pilot does not need a hundred. Paste the ones you can name. Add who asks, how often, which SOP should have answered, and the owner.
Two published surveys describe the same pain in broad office populations, and they are labelled so they are not read as Neurocell results. Starmind’s 2021 report of 1,017 knowledge workers says 49% spend too much time searching documents. Adobe’s September 2023 survey of 1,118 employed Americans says 48% have trouble finding documents quickly, and nearly 2 in 3 have recreated a document they could not find. Neither survey is an India or Gulf sample. Your gaps come from the answers on this page.
If the repeated work is a shipment file rather than an SOP, start with the shipment document checker. If it is a supplier invoice on hold, use the invoice mismatch policy builder.
What a discovery call would use
This page does not index a drive and does not answer questions. The sheet is the scope: those questions, those files, those permissions. A knowledge assistant is only worth building for questions the team actually asks. A short discovery call reads the sheet and quotes a pilot over the documents you choose to include.
That engagement is private knowledge AI. Clear quote after a short discovery call. There is no price on this page. Larger builds start with short paid discovery.