Writing Down How Your Business Runs

Understanding Brain-Dumping and SOPs

In a wedding/event photography business, SOPs (Standard Operating Procedures) are what keep your client experience consistent—even when you’re busy, sick, traveling, or busy editing after a busy weekend.

Think of SOPs as the playbook that ensures every event runs the same way: your inquiry handling, your consult flow, your contract signing, your shot-list planning, your gear checks, your timeline, your delivery process, and your file handoff. When SOPs are clear, your business doesn’t rely on you being “on” every moment.

A strong goal: create a system where a new hire or freelancer (assistant photographer, second shooter, scheduler, editor) can be around 80% effective on day one just by following the SOPs. That’s the difference between “we can only do this when the owner is available” and “we run like a real studio.”

The Importance of Brain-Dumping

Brain-dumping is the process of moving what’s in your head into a form others can use. In photography, you’ve probably got years of “mental checklists” like:
- Which questions you always ask on a consult call
- How you build a timeline for fast-moving wedding days
- What you check the night before a shoot
- How you handle reschedules, last-minute vendor changes, or client emotion when something goes off-plan
- How you review images for consistency before delivery

If those steps live only in your head, your business is capped by your attention. Brain-dumping removes that bottleneck and makes your studio transferable.

Real-World Photography Example: You know exactly how to troubleshoot when a venue’s reception lighting is darker than expected. You instinctively adjust settings, choose different angles, and plan for fallback shots. If you don’t document your approach, the new second shooter will guess—and consistency will drop.

Creating Effective SOPs

Good SOPs are not long essays. They’re instructions that reduce uncertainty.

1. Why: Start with why the task matters.
- Example: “Why we confirm venue arrival times: it protects your photo coverage windows and prevents missed formals.”

2. What: Lay out the exact steps.
- Example: “What we do after we receive the venue schedule: verify ceremony end time, confirm golden hour estimate, check location access, and request any floorplan/lighting notes.”

3. Outcome: Define what success looks like.
- Example: “Outcome = timeline draft approved by client within 48 hours and all critical photo moments are included.”

Real-World Photography Example: If you’re writing an SOP for client gallery delivery, define what “done” means:
- The exported gallery is the correct size/format
- Galleries are uploaded by the same deadline each week
- Clients get the exact handoff email template
- You confirm no missing images and that watermark/export settings match your brand

Organizing Your SOPs

Your SOPs need a home that’s easy to find under pressure. Wedding days are time-stress days. When something changes, people don’t have time to search through random documents.

Store your SOPs in one centralized “vault” (Notion, Google Drive, or a studio wiki). Use a folder or database structure like:
- Inquiries & Consults
- Contracts & Payments
- Pre-Wedding Planning
- Wedding Day Operations
- Editing Workflow
- Gallery Delivery
- Client Support & Refund/Reschedule Policy

Real-World Photography Example: If your assistant needs to know how you want “must-have family photos” handled, they should be able to open the “Family Photo Process” SOP instantly—without texting you for the 5 steps.

The Loom-First Approach

Writing SOPs can be slow. A faster method is to capture the real process in a video first.

Record yourself doing the task with Loom—screen recording plus a bit of your face if needed. Then later, convert the key steps into a clean SOP document.

Real-World Photography Example: Record your actual workflow for:
- importing images into your catalog system
- exporting for preview/client review
- creating a gallery upload
- running your final image consistency check

These videos become “source of truth” training for editors and assistants.

Building a Culture of Self-Reliance

Your goal is not just documentation. Your goal is independence.

Train your team to check the SOP vault first. If they’re unsure, they should:
1) search the SOP vault, 2) follow the steps, and 3) only then message you with the exact question they still can’t solve.

Real-World Photography Example: On the wedding day, an assistant asks how to handle a couple who wants additional portraits right after the ceremony. Your team member should open “Portrait Timing SOP,” follow the recommended placement and time windows, and only ask you to approve a change if it breaks critical coverage windows.

When SOPs are in place, you stop being the bottleneck. You protect your weekends, your editing nights, and your sanity—while delivering the same level of experience every time.