The Systems Effect

Scaling & Growth

Opening a Second Location: What to Document Before You Sign the Lease

August 29, 2026

The honest answer to how to open a second location is that the lease is the last decision, not the first. Before you sign, write down the processes that make the first location money, name the person who will train the new team, and pick the numbers that prove the model runs without you. A second location does not fix a weak process. It runs a second copy of it.

The Second Location Copies Your Systems, Not Your Success

Your first location works. That is not the same as repeatable. It runs on people who improvise well and know which job to move when the day falls apart, and none of that judgment is written down.

When we map a growing operation the pattern holds: whatever the first site improvises, the second one inherits at full price. One field services client routes crews across four markets, and the owner estimates that routing done wrong costs about 30 percent of revenue: jobs in the wrong slot, cancellations nobody catches, the wrong tech at the wrong job.

That is one undocumented process multiplied by geography, which is why the systems you need before you can scale come before the lease.

Growth never creates a process, it only exposes the one you already have.

Pick the Model Location, Then Freeze It

You cannot document "the business." You can document one location. The triage we run starts with a 1.5x map: zoom in a little for the high level picture, then go department by department.

Geography works the same way. Set the model in the market that is 70 percent of the business, then explain it to everyone else.

The model location is the one carrying the revenue, not the one with the best manager. Best-manager sites are the most dangerous thing to copy, because the manager is the process. Document that site and what you wrote down is a person.

Then freeze it. A process that moves while you document it produces a document that was never true. This is the opposite of standardizing locations that have already drifted apart, where the job is reconciling three versions of the truth. You have one version, so protect it.

How to Open a Second Location: Which Processes Must Exist in Writing

Not all of them. You need what touches the customer and the money in the first 90 days, captured three ways: purpose, the decision points where somebody uses judgment, and the step by step from the person doing it.

Five processes carry almost every location-based business.

  1. Take the order. Who answers, who calls back, how fast, and what gets recorded. If your first location wins on response time, that process lives in one person's habits.
  2. Schedule and route the work. Who assigns it, in what order, and what happens when a job cancels at 7am. This is where that 30 percent lives.
  3. Hand the customer off. Where selling stops and delivering starts. At one staffing client sales and operations never met after onboarding, so reps filled rush orders without seeing the crew they were burning.
  4. Get paid. Invoicing, collection, payroll, commission. One owner covered payables himself after a key person left and found 500 to 800 dollars leaking weekly, up to 10,000 dollars a month, from skipped audits and missed deductions.
  5. Open and close the day. The opening checklist, the closing checklist, and the weekly audit that confirms both happened.

The steps are the easy half. Decision points travel badly, because at location one the judgment call gets made by walking twenty feet and asking. Everything else can wait for the step by step for systemizing a service business.

Who trains the new team, and when do they arrive?

Somebody from the model location, named before you sign the lease, on site before the doors open. Not you.

At one company the exiting bookkeeper spent her final three weeks training her replacement over screen shares, because none of that work had ever been documented. A second location that opens on a hire date is the same bet.

Pick the trainer the way we pick a subject matter expert: they want to participate, they will schedule the time, they set a good example, and they have influence with peers. That last one is the galvanizer, the person who can get everyone out on a Friday. Title does not equal fit, which is the argument for building an internal trainer on purpose.

Timing is the part owners get backwards. Open behind the documentation, because a training system built during a staffing emergency is the worst version of itself. One staffing client was cut to two customer service people overnight, then needed training for hires nobody had posted yet.

Decide What Is Standard and What Is Local

Standardize anything a customer feels, anything that touches money, and anything producing a number you compare between sites. Leave the rest alone. Owners standardize everything or nothing, and both cost them.

DecisionSet once, everywhereLeft to the location
Pricing and discountsRate card, approval limitsNothing
Complaint escalationPath and response timeWho takes the call
Opening and closingSteps and orderStart time
Schedule formatThe fields it must showColors, layout, decoration
Bonus calculationFormula and source numberNothing

That last column is not a consolation prize. On one franchise walkthrough, store teams asked whether the new schedule could stay "cute," with the palm trees and strawberries they add by hand. Strip the harmless things, leave the expensive ones vague, and you lose the new team in week one.

In one nonprofit's mapping sessions, colleagues in the same department learned mid-interview that they had each run the same process differently for years. Two locations drift the same way unless you decide in writing what may vary.

One System Per Record, From Day One

Double entry is survivable with one location. With two it compounds. A 16-store retail client runs a fragmented stack plus manual spreadsheets, and re-keying records out of supplier PDFs costs roughly 50 staff hours a week across the group.

The same client's managers page through signed contracts one envelope at a time to find the ones missing a countersignature, because contract status is invisible per store.

Every record gets one home and one owner before the second location exists. Decide where a customer lives, where a job lives, where hours live, and where a signed document lives. That decision belongs with the six systems every growing business needs.

The cheapest week to fix double entry is the week before two people are doing it.

The Numbers That Tell You the First Location Is Ready

Readiness is a number, not a feeling. The field services company runs on five leads per tech per day, 50 duct jobs a day, 25 dryer vents, revenue per van, and cancellation rate. A dispatcher tracks them on a physical whiteboard, and targets change verbally mid-conversation, 4,000 per van becoming 6,000.

A number on a whiteboard cannot be copied. Neither can a target that exists only in the last thing the owner said out loud. Each one needs a written definition, a named owner who is not you, and a place anyone can look, which is the point of a weekly scorecard with one owner per number.

One owner we work with planned a two-week absence as a measurement, expecting honest feedback he would never hear while he was down the hall. If the model location holds its numbers while you are unreachable, you have evidence rather than optimism.


What breaks in month two?

The things that were too obvious to write down. Scheduling goes first, because dispatch across two markets is a different job than dispatch across one. Nobody notices until marketing keeps spending in a market the crews cannot reach.

Administrative plumbing goes second. At one company new hires waited three weeks for a company card, so they bought parts and gas personally.

Third, the documentation goes soft. A 55-person cleaning company ended up with three redundant versions of one process, and the team's word for it was cognitive overload. Worse is the version nobody opens: one owner paid five figures to document his operation in a training platform, the team never used it, and calls unused documentation his worst nightmare.

At The Systems Effect we do this by interviewing the people doing the job at the location that already works, because that is where the real process is stored. This week, take the process that would cost you most if a stranger ran it wrong, and have the person who does it record themselves doing it once. That recording is page one of your second location.

Frequently Asked Questions

What should you document before opening a second location?

Document the five processes that touch the customer and the money in the first 90 days: taking the order, scheduling and routing the work, the sales to delivery handoff, getting paid, and opening and closing the day. For each, capture the purpose, the decision points, and the step by step from the person who does it. Decision points matter most, because at a new location there is nobody nearby to ask.

How do you know your business is ready for a second location?

You are ready when the first location hits its numbers with you unreachable, not merely busy elsewhere. That requires every number to have a written definition, an owner who is not you, and a place the team can see it. A planned two-week absence is the cheapest way to run that test.

Who should manage a second location?

Somebody chosen against a written seat, not the most available person. The failure mode we see repeatedly is an undefined role nobody can measure, which goes quiet for years and gets tolerated because the company is not built for turnover. Avoid the leader who already sits in five seats: a manager with no time to build systems produces a bloated playbook.

How do you keep two locations running the same way?

Decide in writing what is standard and what is local before the second site opens. Standardize anything the customer feels, anything touching money, and anything producing a number you compare across sites. Then give every record one home and one owner, so the same customer, job, or contract is never entered twice.

How long before a second location should you start systemizing?

Start at least a full quarter ahead, longer if the knowledge is mostly in people's heads. Most clients see meaningful progress in the first month and a significant shift by month three, while full capture and training deployment for a mid-size operation typically runs 6 to 12 months. Team time is small, 2 to 4 hours per process, so the constraint is calendar, not effort.

Want help putting this into practice?