Write the standard once, for every location.

One place the standard actually lives, instead of a folder of documents nobody opens twice.

From the folder on the shelf to one living standard.

One library, and you write in it
Folders per part of the operation, and every procedure written and kept in Kimchi itself. Not a shared drive nobody opens, not a folder of documents four people have their own copy of.
Build from what you already have
Hand Kimchi the welcome book and ask for the onboarding procedure. It asks the few things the document does not say, who runs the first shift, when the sign-off is due, and writes the SOP around your answers.
Scope it to the locations it applies to
One version for the whole estate, one for a region, or one location’s exception. People see the version for where they work, and nothing else.
Build training and checklists straight from the SOP
The procedure becomes a training with a quiz in one click, or the shift’s checklist through the builder, without anyone retyping it. Both read from the SOP, so when the standard changes they change with it.
A self-updating SOP library
Kimchi reads what happens on the floor, the checklist that keeps failing, the review, the question asked five times, and proposes the change to the procedure. Accept it and the standard moves up a version, every time.

One place, not four.
The standard lives somewhere findable, and there is only one of it.
Scoped per location.
Locations see the version that applies to them, without a folder each.
Kept current.
A change to the standard is a change everywhere it is referenced.
Nothing saved behind your back.
It drafts, you read it, and only then does it land in the library.