Making Your Business Run Without You

Understanding the Franchise Rule

The Franchise Rule means building an architecture or engineering firm that can deliver good work without the owner being involved in every decision. It does not mean making the practice impersonal. It means creating a reliable way to win work, run projects, protect quality, and serve clients even when the principal is unavailable.

A strong firm should work more like a well-run design studio with clear standards than like a collection of talented people waiting for one principal's approval. The owner should set the direction, develop key relationships, and make high-value decisions. The team should be able to handle normal project work without constant rescue.

The Importance of Systems

An architecture or engineering firm depends on repeatable systems. These systems cover the full project life cycle, including lead qualification, proposal writing, contracting, kickoff, design reviews, permitting, construction administration, invoicing, and closeout.

For example, a civil engineering firm should have a standard process for starting a land development project. The process might include confirming the scope, reviewing the survey and geotechnical information, listing required permits, assigning staff, setting quality-control dates, and recording client decisions. When this information lives only in a principal's head, each project starts differently and mistakes become more likely.

A system is not just a checklist. It includes the owner of each task, the expected standard, the deadline, the software location, and the point at which an issue must be escalated.

Building a Self-Sufficient Firm

Start by finding the places where the owner is the bottleneck. Look at the decisions and tasks that stop moving when the principal is in a meeting, traveling, or focused on business development.

Common examples include approving every drawing set, answering every technical question, reviewing every fee proposal, assigning staff, resolving consultant conflicts, and responding to ordinary client concerns. For each area, decide what the team can handle without approval, what requires a senior project manager, and what truly needs a principal.

A useful three-level structure is:

- Team level: Routine work that follows documented standards.
- Project-lead level: Decisions involving scope, schedule, coordination, or client risk.
- Principal level: Major fee changes, contract disputes, claims, safety concerns, reputation issues, or strategic client decisions.

This gives people authority without asking them to guess where the limits are.

Real-World Scenario

Consider a 20-person architecture firm where the managing principal reviews every permit submission before it leaves the office. The principal is often traveling or meeting with prospects, so submissions sit in a queue for several days. Project managers begin promising dates they cannot meet, and staff work late to recover the schedule.

The firm can replace this dependency with a documented quality-control process. A senior architect checks code notes, sheet coordination, consultant backgrounds, title blocks, and required forms using a standard review checklist. The project manager records corrections and confirms that the set is ready. The principal only reviews projects with unusual code risk, major contractual exposure, or a client relationship concern.

The principal still owns the firm's standards, but no longer acts as the firm's only quality-control department.

The Role of Documentation

Documentation turns individual knowledge into a firm asset. Write procedures where the team already works, such as the project-management platform, shared drive, or quality-control library. Use short screen recordings, sample files, checklists, and decision rules. A new project manager should be able to find the current proposal template, fee approval limits, kickoff agenda, project folder structure, and drawing-review checklist without asking the owner.

Review procedures after real projects. If a permit package was delayed because nobody knew who owned the agency response, update the process. If a project manager needed three different spreadsheets to understand project profitability, simplify the reporting method.

The Benefits of a Franchise Model

A firm built on clear systems can add staff, open a new office, take on larger projects, and withstand an owner's absence with less disruption. Quality becomes more consistent. Project managers make decisions faster. Senior staff spend more time mentoring and less time repeating instructions. The owner can focus on market position, key accounts, hiring leaders, and long-term value.

This model also makes the practice more transferable. A buyer, successor, or new partner is more likely to value a firm whose client service and project delivery depend on documented methods rather than one person's memory.

Conclusion

The Franchise Rule for an architecture or engineering firm is simple: the practice must own the way work gets done. Build clear systems for project delivery, document the standards, give leaders defined authority, and test the firm by stepping away. The goal is not to remove judgment from professional work. The goal is to reserve the owner's judgment for the decisions that truly need it.

A firm that can complete a project kickoff, coordinate consultants, issue a quality-controlled package, answer normal client questions, and collect its invoices without the principal's constant intervention is a stronger and more valuable business.