← Changelog

Guides put your SOPs where the work happens

Most standard operating procedures get written once, filed in a wiki, and never opened again, so the knowledge that runs your company stays stuck in a few people's heads. Guides change where that knowledge lives. You attach the how-to to the actual action it runs, so it shows up exactly where and when the work happens.

What shipped. Guides let you capture a how-to once and attach it to the actions it belongs to, across your plan and your projects. One guide can run many actions, and it stays with each of them as the work moves.

How Throughline treats an SOP. A standard operating procedure should not be a document someone has to remember to go find. It should sit on the work itself. So a guide lives on the action, and it appears the moment a person opens that action to do it. You write it once, and it becomes something the whole org reuses, not a file that rots in a folder nobody opens.

What you and your org get. For the person doing the work, the steps are right there. Less guessing, less asking around, and a faster start on anything new. For the org, the way you do things stops living in a few heads and becomes something the company owns. Execution gets more consistent, new people ramp faster, and when someone leaves, how they worked stays behind instead of walking out the door.