Writing Down How Your Business Runs

Understanding Brain-Dumping and SOPs

Standard Operating Procedures, or SOPs, are the written instructions for how your architecture or engineering firm completes repeatable work. They help a project manager, designer, engineer, or administrative team member follow the same reliable process without waiting for the principal to explain it again. An SOP is not a design standard or a replacement for professional judgment. It is a clear guide for routine work such as opening a project, setting up a Revit model, issuing a drawing package, processing a consultant invoice, or closing out a project.

The goal is for a capable new team member to complete about 80% of a routine task correctly on the first attempt by following the SOP. For example, a new project coordinator should be able to create a project folder, load the correct templates, enter the job in the timekeeping system, and schedule the kickoff without asking the principal for every step.

The Importance of Brain-Dumping

Brain-dumping means moving the knowledge in your head into a format another person can use. In many firms, important operating knowledge is trapped in the principal's memory: which municipality requires a certain submittal format, how the firm checks consultant backgrounds, how proposals are priced, or which drawing sheets must be reviewed before issue.

This hidden knowledge creates a ceiling on growth. If only one senior person knows how to perform a task, that person becomes the approval point for every project. Work slows, staff hesitate, and the owner cannot leave the office without becoming a bottleneck.

Real-World Example: A civil engineering principal personally reviews every proposal before it is sent because only she knows how the firm calculates survey hours, travel time, and subconsultant markups. She records herself building one proposal in the estimating template, explains the decisions, and saves the recording with the proposal procedure. A project coordinator can now prepare the first draft, while the principal reviews only the final assumptions.

Creating Effective SOPs

Use the same three-part structure for every procedure:

1. Why: Explain why the task matters. For a drawing issue procedure, the reason may be to prevent outdated sheets from reaching the client or contractor.
2. What: List the exact steps, in order. Include the software, file locations, naming rules, approval points, and required checks. State who owns each step.
3. Outcome: Define what finished work looks like. A successful permit submission may include the approved sheet set, correct revision dates, signed forms, a transmittal, and a saved copy in the project records.

Keep the language practical. Instead of writing, “Complete quality assurance,” write, “Open the 60% drawing set, compare each sheet against the current sheet index, confirm all consultant references, and record issues in the project QA log.”

Organizing Your SOPs

Store procedures in one searchable operations library. A firm might use SharePoint, Notion, or a well-structured Google Drive. Organize the library by work area, such as Business Development, Project Startup, Design Production, Engineering Calculations, Quality Control, Billing, and Project Closeout.

Each SOP should show an owner, last review date, version, and related templates. Link directly to the forms, checklists, Revit templates, CAD standards, fee worksheets, or sample transmittals needed to complete the task. Do not bury the process across email threads and personal desktops.

The Loom-First Approach

Start with a short screen recording before writing a long document. Use Loom or another recorder to capture a principal or senior team member completing a real task. For example, record the project manager opening a new project in Deltek, creating the folder structure, assigning labor codes, and reviewing the fee budget. Narrate the decisions and common mistakes while working.

Then have a coordinator turn the recording into a brief written SOP with screenshots and a checklist. The video preserves judgment and context; the written version makes the process searchable and easier to audit.

Building a Culture of Self-Reliance

Teach staff to check the operations library before interrupting a principal or senior project manager. When someone asks how to issue a revised drawing set, the first response should be, “Check the Drawing Issue SOP and tell me which step is unclear.” This does not mean refusing help. It means improving the process when the documentation is missing or confusing.

Ask team members to flag outdated instructions, and review high-risk procedures at least twice a year. With consistent use, your firm becomes less dependent on individual memory, project work becomes more predictable, and principals can spend more time on clients, backlog, and high-value design decisions.