Writing Down How Your Business Runs

Understanding Brain-Dumping and SOPs

Standard Operating Procedures (SOPs) are what keep your coworking space running the same way whether you’re in the building, on a site visit, or dealing with a supplier issue. Think of SOPs as the exact “how we do it here” instructions for every repeatable task: greeting members, handling key access issues, setting up a meeting room, resolving Wi‑Fi complaints, processing invoices, and cleaning standards.

Your goal is simple: create a system where a new team member can be 80% effective on their first day just by following your SOPs. For coworking, that means they can answer the most common questions, take the right next steps when a problem shows up, and keep operations consistent across shifts. When SOPs are good, member experience doesn’t change when you’re busy.

The Importance of Brain-Dumping

Brain-dumping is the process of getting all the know-how in your head into a format someone else can use. If you only hold this knowledge in your own head, your space can’t scale past your personal availability.

In coworking, this often shows up as “tribal knowledge.” For example, you might know the exact steps to fix a printer that “never works,” or how to handle a member who’s unhappy about noise in the focus area—but your front desk lead can’t fully explain it. Brain-dumping turns that experience into repeatable instructions.

Real-World Example: A member reports that their key card won’t open the coworking access door. You know the difference between a “bad card” and a “door controller lockout,” and you know which vendor contact to message immediately. Without brain-dumping, your team guesses—and members wait.

Creating Effective SOPs

Good SOPs are built around three parts:

1. Why: Start with why the task matters.
- In coworking, the “why” is usually member experience and uptime (access working, rooms ready, Wi‑Fi reliable).
2. What: Detail the exact steps.
- Be specific and sequence the actions in the order your team should do them.
3. Outcome: Define what success looks like.
- If the SOP is followed, what should the room/member situation look like afterward?

Real-World Example: An SOP for handling member Wi‑Fi issues should explain why fast triage matters (members need to work), list the steps your team runs (check network status, ask the member to test on another device, confirm whether it’s only one person or the whole area), and state the outcome (issue resolved or escalation sent with required details).

Organizing Your SOPs

SOPs need to live in one central place that your team can reach instantly from the front desk, maintenance closet, or their phone. If it takes too long to find the right SOP, people stop using it.

Real-World Example: Create a “Member Support & Operations” SOP vault with categories like:
- Key access + card issues
- Front desk scripts
- Room setup (small rooms and event spaces)
- Cleaning and restock standards
- Wi‑Fi + common IT problems

Then name files in plain language so the team can search fast, like “Wi‑Fi complaint triage” or “How to handle guest passes.”

The Loom-First Approach

Instead of writing long documents from scratch, record yourself doing the task. Use Loom to capture the steps while they’re fresh and visual. Coworking work is hands-on—your team needs to *see* what “done right” looks like.

Real-World Example: Record yourself setting up a meeting room for a scheduled booking:
- how you confirm the reservation
- how you check displays/TV input
- how you place whiteboards/markers
- how you verify seating layout
- how you start the room’s “ready” checklist

Your video becomes a training tool and reduces mistakes.

Building a Culture of Self-Reliance

Train your team to check the SOP vault before asking you. This does two things: it speeds up resolution and protects your time.

Real-World Example: If someone asks, “What do we do when a member says the printer is broken again?” you point them to the SOP vault: “Printer Troubleshooting + Escalation Steps.”

Over time, your team learns patterns, your member experience becomes consistent, and you stop being the single point of failure.

When you write SOPs for the real work of coworking—access, rooms, Wi‑Fi, member requests, cleanliness—you build a space that can run smoothly on every shift, not just the one you’re working.