Guide
Writing procedures is a project. Keeping them current is a process — and it is the one that determines whether anything you wrote still matches the operation a year from now.
Staleness is rarely caused by carelessness. It is caused by a structural mismatch: procedures change through decisions, which happen constantly and informally, while documentation changes through projects, which happen rarely and formally.
A chef adjusts a portion in a Tuesday conversation. A GM works out a better closing sequence over a month. A vendor substitution changes a prep step. Each of these is a legitimate operational decision, and none of them naturally produces a document update.
The gap compounds quietly. Nobody notices at three months. At eighteen, the written standard and the actual operation are visibly different, staff have learned to trust people over documents, and you are looking at a second documentation project.
Calendar-based review alone catches the wrong things — it reviews stable procedures on schedule and misses volatile ones between cycles. Use events as the primary trigger.
A menu change, equipment change, vendor change, layout change, or supplier substitution. These have a known blast radius: each touches a specific, listable set of procedures. Review should happen within days, not at the next quarterly cycle.
A guest complaint pattern, a failed inspection, a near miss, a safety incident, or a recurring question from staff. Each is evidence that either the procedure is wrong or it did not reach someone. Both are fixable; neither fixes itself.
When a GM, chef, or key manager leaves, review what they owned. This is one of the highest-value review moments in a restaurant group, because it is when undocumented knowledge is simultaneously most discoverable and most at risk of walking out the door.
If you only implement one thing from this page: when a key person gives notice, schedule a session to capture what they know that is not written down.
Most groups discover how much of the operation lived with that person about two weeks after they leave.
Rotating quarterly review is the difference between a cadence that survives and one that gets skipped. “Review everything” is a task nobody starts.
The reason most updates fail is not that the SOP file goes unedited. It is that the SOP was never the only artifact.
A single portion change from 5 oz to 4.5 oz typically touches five things: the recipe standard, the prep guide, the line reference, role training, and whatever answer an employee gets when they ask. Updating one of five and announcing the change feels like completion. It is not.
Write down, for each procedure, what it is related to. Then a change becomes a checklist rather than an act of memory:
Operating procedures get corrected on the floor because experienced staff notice when something is wrong. Training material does not, because its only readers are people who do not yet know the right answer.
This makes onboarding the highest-risk place for an outdated standard to persist. A new hire learns the old version, gets corrected in week two, and concludes the official material is unreliable. That conclusion is rational, it spreads, and it is very hard to reverse.
Any update process that stops at the procedure and does not reach training will produce exactly this outcome.
The people best positioned to notice that a procedure no longer matches reality are the ones doing it daily. Most groups have no route for that information, so it surfaces as a complaint to a manager and stops there.
A simple intake — one place where “this procedure is wrong now” or “nobody has told us what to do here” can be raised and stays visible until resolved — converts ongoing friction into maintenance input. It also tells you which procedures are volatile, which is useful for setting review priority.
The critical property is that items stay visible until someone closes them. An inbox nobody empties is worse than no inbox, because it teaches staff that reporting does nothing.
Maintenance is invisible unless the reader can tell what they are looking at. Three fields do most of the work:
Unversioned printed material is a common way a superseded procedure survives for years.
Everything above is straightforward. None of it is difficult. It fails for one reason: in a lean leadership team, maintenance has no owner, and it loses to service every single week.
The options are to hire for it, protect time for it in an existing leader’s week with explicit scope, or buy it as a service. Trensli exists because for most growing groups, the first is not yet justifiable and the second does not survive a busy quarter.
More on SOP management across locations, or see how the managed model works.
See it with your operation in mind
When a procedure changes, Trensli finds the training, checklists and answers it touches, prepares the updates and has a reviewer check them before they go live.
Get a Private Walkthrough →A short walkthrough tailored to your restaurants. Sent within one business day. No call required.
