← Back to Architecture Engineering Firm Modules
Architecture Engineering Firm Guide
Writing Down How Your Business Runs
Master the core concepts of writing down how your business runs tailored specifically for the Architecture Engineering Firm industry.
💡 Core Concepts & Executive Briefing
Understanding Brain-Dumping and SOPs
In an Architecture / Engineering firm, Standard Operating Procedures are not paperwork for the shelf. They are how you keep design quality, project timing, and client trust from depending on one senior person’s memory. Think about how many moving parts sit inside one project: proposal setup, kickoff, code review, drawing standards, consultant coordination, QA/QC, permit submittals, CA responses, and closeout. If those steps live only in a project manager’s head, your firm will always be one sick day away from a mess.
The goal is simple: a new hire should be able to become 80% effective fast by following the process. That does not mean they know everything. It means they can find the right file, follow the right steps, and avoid the common mistakes that cost firms time and profit.
The Importance of Brain-Dumping
Brain-dumping means pulling the knowledge out of the senior architect’s or engineer’s head and turning it into something the team can actually use. Every firm has these hidden experts. One person knows how the city wants structural calcs formatted. Another knows the exact checklist for a health care permit set. Another knows which consultant always misses sheet deadlines. If that knowledge stays personal, the firm cannot grow without adding more stress to the same people.
A better way is to capture the process while the expert is still available. For example, a principal who has handled ten school projects can explain how to move from schematic design to DD, what deliverables are expected at each phase, and what client decisions must be locked before CD starts. Once that is written down, the team stops guessing.
Creating Effective SOPs
1. Why: Explain why the task matters to the project and the firm. In an A/E firm, the reason is usually risk, schedule, or fee protection. A QA/QC checklist matters because one missed code issue can lead to redesign, permit delays, or back charges.
2. What: List the exact steps in plain language. Do not write like a code book. Write like someone who needs to finish the work correctly the first time. Include templates, file names, review gates, and who signs off.
3. Outcome: Define what done looks like. For an architectural drawing set, that may mean the sheets match the firm standard, the consultant backgrounds are current, the redlines are cleared, and the package is ready for internal review.
A strong SOP for an engineering firm might cover how to run a clash review, how to label issue sets, or how to prepare a permit resubmittal response. Good SOPs reduce rework and make handoffs cleaner.
Organizing Your SOPs
Your SOPs should live in one place where the whole team can find them fast. That could be Notion, SharePoint, Google Drive, or an intranet folder structure built for projects and operations. The key is consistency. If one person stores the CA checklist in a personal desktop folder and another keeps the meeting template in email, the system fails.
A good structure for an A/E firm is to separate SOPs into buckets like business development, project setup, design process, QA/QC, consultant coordination, permitting, client communication, and closeout. If a project coordinator needs the submittal checklist, they should find it in under a minute.
The Loom-First Approach
Do not wait until every SOP is perfectly written before you start. Record the process first. In an Architecture / Engineering firm, this works especially well because many tasks are visual. A Loom recording can show how to set up a Revit project, how to export a sheet set, how to log an RFI, or how to update a submittal register.
A short screen recording often teaches better than a long document. A senior designer can walk through the exact steps for assembling a permit set, while a coordinator watches the cursor and hears the reasoning behind each step. Later, someone can turn that recording into a clean written SOP with screenshots and checklists.
Building a Culture of Self-Reliance
The real goal is not just documentation. It is a team that knows to look in the system before interrupting the busiest person in the office. When a junior project architect asks how to name a file, how to upload to the client portal, or how to prepare minutes for a consultant meeting, the right habit is to check the SOP library first.
That culture matters because A/E firms lose time in tiny interruptions. Ten questions about the same submittal process can eat half a day. A good SOP vault makes the firm steadier, faster, and less dependent on one hero. When the process is clear, the work gets done the same way every time, even when the office is busy, the deadline is close, or the principal is on a plane.
⚠️ The Industry Trap
### The 'I'll Just Tell Them' Delusion
A lot of firm owners still run their office like everything can be handled by a quick conversation at the printer or in the hallway. That works until the one person who knows the process is out on site, in a client meeting, or buried in a deadline. Then the team starts making guesses about how to issue a drawing set, how to respond to an RFI, or how to prepare a permit resubmittal.
In an Architecture / Engineering firm, verbal training creates expensive confusion. One project manager might tell a coordinator to save files one way, while another project manager wants a different naming system. Soon the file server is a mess, the redlines are inconsistent, and no one trusts the current version. If your firm depends on you to explain the same steps over and over, you do not have a system. You have a bottleneck wearing a nice title.
A lot of firm owners still run their office like everything can be handled by a quick conversation at the printer or in the hallway. That works until the one person who knows the process is out on site, in a client meeting, or buried in a deadline. Then the team starts making guesses about how to issue a drawing set, how to respond to an RFI, or how to prepare a permit resubmittal.
In an Architecture / Engineering firm, verbal training creates expensive confusion. One project manager might tell a coordinator to save files one way, while another project manager wants a different naming system. Soon the file server is a mess, the redlines are inconsistent, and no one trusts the current version. If your firm depends on you to explain the same steps over and over, you do not have a system. You have a bottleneck wearing a nice title.
📊 The Core KPI
Core SOP Coverage Rate: Measures the share of your firm’s repeatable core processes that are documented, current, and stored in one searchable system. Formula: documented core processes ÷ total core processes x 100. In a healthy Architecture / Engineering firm, target at least 90% coverage across project setup, QA/QC, consultant coordination, permit production, client communication, and closeout. If the process affects schedule, fee, quality, or risk, it should be documented.
🛑 The Bottleneck
### Execution Level: Operations Coordinator or Production Lead
Most Architecture / Engineering firms get stuck because senior people keep the know-how in their heads. That creates a ceiling on growth. The principal cannot delegate permit packaging because no one else knows the exact sequence. The project architect cannot hand off CA because the response rules were never written down. The production lead becomes the only person who can fix a sheet issue, so every problem lands on one desk.
That is not a people problem. It is a documentation problem. Until the firm captures its project workflows, it will keep paying expert wages for repeat tasks that should be done by a coordinator, project assistant, or technical admin. The bottleneck is the missing handoff, not the lack of effort.
Most Architecture / Engineering firms get stuck because senior people keep the know-how in their heads. That creates a ceiling on growth. The principal cannot delegate permit packaging because no one else knows the exact sequence. The project architect cannot hand off CA because the response rules were never written down. The production lead becomes the only person who can fix a sheet issue, so every problem lands on one desk.
That is not a people problem. It is a documentation problem. Until the firm captures its project workflows, it will keep paying expert wages for repeat tasks that should be done by a coordinator, project assistant, or technical admin. The bottleneck is the missing handoff, not the lack of effort.
✅ Action Items
### Steps to Implement SOPs
1. **Record the real work:** Use Loom or a similar screen recorder to capture common tasks like setting up a Revit project, issuing an addendum, logging RFIs, or preparing a consultant coordination checklist.
2. **Turn experts into teachers:** Have your senior architect, engineer, or project manager walk through one task at a time while someone else documents it. Do not ask them to write a perfect manual from scratch.
3. **Add firm standards:** Store your title block rules, naming conventions, QA/QC checklists, and file path rules in the same system as the SOPs.
4. **Make project handoffs clean:** Create SOPs for kickoff, SD, DD, CD, permit, bidding, CA, and closeout so every phase has a clear checklist.
5. **Put one owner on the library:** Assign an operations lead, project coordinator, or admin manager to keep the SOP vault current in Notion, SharePoint, or Google Drive.
6. **Train people to look first:** When someone asks how to do something, point them to the SOP before answering live. That builds independence and keeps the firm from repeating the same mistakes.
1. **Record the real work:** Use Loom or a similar screen recorder to capture common tasks like setting up a Revit project, issuing an addendum, logging RFIs, or preparing a consultant coordination checklist.
2. **Turn experts into teachers:** Have your senior architect, engineer, or project manager walk through one task at a time while someone else documents it. Do not ask them to write a perfect manual from scratch.
3. **Add firm standards:** Store your title block rules, naming conventions, QA/QC checklists, and file path rules in the same system as the SOPs.
4. **Make project handoffs clean:** Create SOPs for kickoff, SD, DD, CD, permit, bidding, CA, and closeout so every phase has a clear checklist.
5. **Put one owner on the library:** Assign an operations lead, project coordinator, or admin manager to keep the SOP vault current in Notion, SharePoint, or Google Drive.
6. **Train people to look first:** When someone asks how to do something, point them to the SOP before answering live. That builds independence and keeps the firm from repeating the same mistakes.
Ready to scale your Architecture Engineering Firm business?
Unlock the full Modern Marks Curriculum and join hundreds of other founders.