Writing Down How Your Business Runs

Understanding Brain-Dumping and SOPs

Standard Operating Procedures (SOPs) are the “how we run the laundromat” rules. They’re the step-by-step instructions your staff needs to keep machines running, take care of customers the right way, and hit consistent results—without you standing over them.

Here’s the real goal: build a system so a new hire can be about 80% effective on day one just by following your SOPs. That means they can handle the common situations (machine help requests, refunds, outages, supplies, cleaning) using the same playbook every shift, whether you’re there or not.

The Importance of Brain-Dumping

Brain-dumping is getting everything you know out of your head and into something usable. In a laundromat, you probably learn patterns the hard way: which coin jam causes delays, how to talk customers who are frustrated, when to call your machine technician versus when it’s something simple.

If that knowledge stays only in your head, your business is limited by your attention. And when you’re busy—or sick—everything slows down.

Laundromat example: You know that when a washer stops mid-cycle and the customer says, “It stole my money,” 9 times out of 10 there’s a specific error code on the control panel and a repeatable reset procedure. If you don’t write it down, your staff will guess, waste time, and risk wrong refunds.

Creating Effective SOPs

To create SOPs that actually get used, build them in three parts:

1. Why: Explain why the task matters.
- Example: “Why we handle refunds the exact way” — because money disputes create angry customers, chargebacks from card payments, and wasted technician time.

2. What: Write the exact steps.
- Example: “What to do when a dryer won’t start” — check display, check power indicator, verify card/coin reader status, confirm safety reset, then document the issue.

3. Outcome: Describe what “done right” looks like.
- Example: “Outcome” — customer is back in a working machine (or refunded correctly), issue is logged with photos or error code, and your tech gets the right details.

Laundromat example: For a “Customer Money Dispute” SOP, “Outcome” might be: refund processed only after the reader audit/verification, customer receives a receipt, and the machine issue is logged so you prevent the same problem tomorrow.

Organizing Your SOPs

SOPs should live in one place that’s easy to access on shift—like a central “SOP vault.” If your staff has to hunt for instructions, they won’t use them.

Laundromat example: Create a digital folder called “Laundromat SOPs” with clear labels:
- “Washer Not Draining”
- “Dryer Won’t Start”
- “Card Reader Refund Steps”
- “How to Clean Lint Traps”
- “How to Handle Abusive Customers”

When someone asks, “What do I do if a machine eats a card payment?”, you want the answer to be quick: find “Card Reader Refund Steps,” follow it, and move on.

The Loom-First Approach

Instead of writing long paragraphs, start with video. Use Loom (screen recording or screen + you talking) to capture yourself doing the task in real time. Visual instructions beat guesswork.

Laundromat example: Record yourself doing a “Daily Machine Walkthrough”:
- what you check first
- which error lights you look for
- how you log issues
- how you confirm cleaning is complete

Then convert the video into a simple written SOP so staff can skim and still have the steps in front of them.

Building a Culture of Self-Reliance

Your team should treat the SOP vault like the first stop—not the last resort. You want fewer “I’ll ask you” moments and more “I already found the answer.”

Laundromat example: A new attendant gets a call: “This washer won’t drain and the floor is wet.” Instead of waiting for you, they open the vault, go to “Washer Not Draining,” follow the steps, and log the issue. If it escalates beyond their SOP, then they contact you with the correct info.

When you brain-dump and turn your experience into SOPs, you reduce chaos, protect your revenue, and make the business run like you trained it—even on your off days.