Writing Down How Your Business Runs

Understanding Brain-Dumping and SOPs

If you own a restaurant or pub, you already know the hard truth: your place runs on consistency. Guests expect the same beer quality, the same burger doneness, the same speed at the bar, and the same cleanliness standards—whether you’re on shift or not.

Standard Operating Procedures (SOPs) are how you make that consistency repeatable. Think of SOPs as the playbook for your kitchen, bar, host stand, and floor team. When a process is written clearly, you don’t have to “remember everything” or “show it again” every time someone new joins. You can walk into any shift and trust the system.

The goal is simple: create a system where a new hire can become around 80% effective on their first day by following your SOPs, not by guessing and not by waiting on you. For example, a new line cook should be able to prep, hold, plate, and close down using your steps—without you standing next to them for every decision.

The Importance of Brain-Dumping

Brain-dumping is transferring all the details in your head into a format your team can use. In restaurants and pubs, this includes the “small” things that matter most: how you portion chicken, what “clean” looks like on closing, how you build a specific cocktail, the exact ticket pacing you want, and how you handle a complaint without making things worse.

If your knowledge stays only with you, your business is limited by your attention and your availability. That’s why growth is so painful when SOPs don’t exist—you end up hiring, training, and constantly fixing problems that should have been prevented by a documented standard.

Creating Effective SOPs

Great SOPs are not long essays. They’re clear instructions that match how your team works under time pressure.

1. Why: Start with why the task matters.
- In a pub, the “why” might be: consistent beer pour quality protects reputation and repeat visits.
- In a kitchen, it might be: correct holding procedures protect food safety and reduce re-fire waste.

2. What: Detail the exact steps needed to complete the task.
- Include specific actions your team can follow on a busy service.
- Example categories: opening setup, mid-shift restock, closing checklist, ticket routing, allergen handling, void/refund rules, and cleaning schedules.

3. Outcome: Describe what success looks like.
- This is where you remove ambiguity.
- Example: “At the end of prep, labels are legible, lids are sealed, items are dated, and FIFO is followed on every station.”

Organizing Your SOPs

SOPs should live in one place, fast to find, and easy to search. If your staff can’t locate the SOP in 20 seconds, it might as well not exist.

For a restaurant/pubs team, a good structure is by role and by shift.
- By area: Bar SOPs, Kitchen SOPs, Floor SOPs, Host SOPs, Receiving/Supplies
- By timing: Opening, During Service, Closing
- By incident type: Allergens, Spills, Complaints, Power/Internet down

Your SOP “vault” should connect to how your team already works. If you use Toast POS, consider storing SOPs in a system the team can access on the same devices they use for ordering/admin. Many owners use Google Drive or Notion because it’s searchable.

The Loom-First Approach

In restaurants, people learn visually. For your highest-risk or most repeated tasks—beer pour steps, sanitizer mix, line prep, fryer safety, how to plate, how to run the closing checklist—use Loom (or similar screen/video tools) to record yourself doing the task.

A video SOP works especially well for “muscle memory” tasks:
- How you set up the bar before open
- How you portion and date prep containers
- How you checkhold temperatures
- How you confirm allergen notes on tickets

Keep videos short. One SOP = one task.

Building a Culture of Self-Reliance

You want a team that solves problems without constantly pulling you away from running service.

Train your managers and leads to start with: “Check the vault first.” When someone asks, the answer should be as normal as grabbing a checklist.

To make this stick:
- Assign SOP ownership (a lead “owns” updating the bar SOPs, for example)
- Schedule quick refreshes (monthly or when menus/practices change)
- Reward correct use, not constant interruption

When your SOPs are real and current, you’re not just documenting—you’re building a restaurant that can run during vacations, sick days, and growth. And that’s how you stop being the bottleneck.