The problem
Repeat work gets done differently by each person, and writing the first version takes longer than it should. Your procedures exist, but they sit in a folder and nobody opens them while doing the task.
How it works
- Repeat work is captured as tasks on a board, each with an owner and a task type.
- Each task type is linked to its written SOP, so the procedure appears beside the task.
- The SOP panel drafts a first pass from the task details and the procedure, following your steps and your wording.
- A person reviews and finishes the work. The draft cites the SOP so the reviewer can check it.
- Gaps become a to-do list. When a task has no SOP, or a draft shows the SOP is out of date, it is flagged for you to fix.
Governance notes
This build depends on the quality of your SOPs: better procedures give better drafts. It is also the clearest way to see why documenting operations comes before automating them. The reference app runs on sample data to show the idea.