Writing Down How Your Business Runs

Understanding Brain-Dumping and SOPs

Standard Operating Procedures, or SOPs, are the repeatable instructions that keep a wedding and event photography business consistent. They show your team how to handle a task without needing to wait for you. Think of an SOP as a reliable shot list for the business side of photography: it tells the person responsible what to do, in what order, and what a finished result looks like.

Your goal is not to document every tiny action on day one. Start with the core workflows that affect client experience, revenue, deadlines, and image quality. A new studio manager, associate photographer, editor, or virtual assistant should be able to follow the instructions and reach about 80% effectiveness on their first attempt. They may still need coaching, but they should not need to guess what happens next.

The Importance of Brain-Dumping

Brain-dumping means moving the knowledge in your head into a format another person can use. In a photography business, this includes the steps you take after a couple submits an inquiry, how you prepare for a wedding, how you back up cards after an event, how you select images, and how you deliver a gallery.

Many owners believe their process is obvious because they have repeated it hundreds of times. It is not obvious to a new editor or assistant. For example, you may know that wedding cards must be copied to two separate drives before you format anything, while an inexperienced contractor may copy files once and erase a card too soon. Documenting your method protects the client, the images, and the business.

Creating Effective SOPs

Use three parts for every procedure:

1. Why: Explain why the task matters. This gives the person context and helps them make a sound decision when something unusual happens.
2. What: List the exact steps in the order they should happen. Include file names, deadlines, software, handoff points, and what to do when a problem appears.
3. Outcome: Define what complete and correct work looks like. Use a clear check, such as “all cards copied to two verified locations and the backup log updated.”

For example, an SOP for a wedding card backup should explain why duplicate copies protect irreplaceable images, show how to ingest cards into Lightroom or Capture One, require a second local or cloud copy, and state that no card is formatted until both copies open and the backup is recorded.

An inquiry-response SOP might include checking the date and venue, reviewing the lead source, sending the right pricing guide, entering the lead into your CRM, and setting a follow-up date. The finished result is a complete lead record, a personalized reply sent within one business day, and a clear next step for the couple.

Organizing Your SOPs

Keep every procedure in one searchable SOP library. Notion, Google Drive, or a similar system can work. Organize it by the stages of the client journey and the studio’s main functions: inquiries and sales, contracts and payments, pre-event planning, event-day coverage, file safety, editing, gallery delivery, album orders, and post-event follow-up.

Use consistent titles such as “SOP - Wedding Inquiry Response” or “SOP - Same-Day Card Backup.” Add an owner, last updated date, and links to templates. If a team member cannot find a process in two minutes, the library needs better labels or folders.

The Loom-First Approach

Start by recording yourself doing the task instead of trying to write a perfect manual. Use Loom or another screen recorder to capture how you create a timeline questionnaire, prepare a gallery, export preview images, or send a final delivery email. Talk through decisions as you work. Then have an assistant turn the recording into a short checklist with screenshots and links.

The video captures details you may forget to write down, while the written checklist gives the team a fast reference. Update the recording whenever the software, package, or client promise changes.

Building a Culture of Self-Reliance

Train your team to check the SOP library before asking you a process question. This does not mean ignoring real judgment calls. It means preventing the same basic question from interrupting you every week. When an editor asks how to name exported files, point them to the file-naming SOP. When an associate asks what to pack, point them to the event gear checklist.

If a team member finds an unclear step, improve the SOP instead of keeping the answer in a private message. Over time, the library becomes the studio’s shared memory. That lets you spend more time on creative direction, relationships, and growth while clients still receive the same dependable experience.