The Systems That Must Exist Before You Run a Second Crew
Why this matters
A single crew with you present runs on a hundred things that were never written down. You answer the question, you make the call, you catch the mistake, all without noticing you are the system. Put a second crew on the road that you cannot stand over and every one of those undocumented habits becomes a place the work can go wrong. This article is the inventory: the specific systems that have to exist on paper before you split into a crew you cannot watch, and the test each one has to pass.
The one test every system has to pass
A system is not software and not a binder nobody opens. It is the written, repeatable way a recurring task gets done the same way regardless of who does it. The test is blunt: could a competent person new to your shop do this correctly from the document without asking you?
If yes, it is a system and it travels. If no, it is a habit that lives in your head, and a second crew cannot run on your head. The whole job before you expand is converting the habits that only work because you are standing there into things that work when you are an hour away.
A second crew exposes what one crew hides
With one crew, your presence papers over every gap. The tech who is unsure walks over and asks. You spot the shortcut before it becomes a callback. Nothing forces the knowledge out of you because you are always there to supply it.
A second crew removes that safety net. The gap that never mattered, the pricing judgment you make by feel, the "we always do it this way" that was never written, now runs without you and drifts. Expanding does not create these gaps, it reveals ones you already had. So the point of this inventory is not new work, it is writing down what already runs correctly in one place so it can run correctly in two.
The systems that must be on paper
Each of these has to survive your absence before a second crew touches it.
| System | What good looks like | Fails when you are gone if... |
|---|---|---|
| Dispatch and scheduling | A written way jobs get assigned, sequenced, and reprioritized | The right order only exists in your head |
| Pricing and quoting | A price book and quoting rules a lead can follow | Every quote needs your judgment call |
| Job close-out | A defined "done" checklist, photos, and handoff | "Finished" means whatever the tech decides |
| Stocking and inventory | A reorder rule and truck-stock standard per crew | You are the one who notices what is low |
| Quality check | A short checklist built from real callbacks | Quality rides on who showed up |
| Hiring and onboarding | A written way new people are vetted and trained | Every hire learns only by watching you |
| Money handling | Clear rules on collection, deposits, and who can discount | Cash and change orders run on trust alone |
| Communication cadence | A fixed rhythm (huddle, end-of-day report) | You find out about problems by accident |
If any row only works because you are physically present, that row is not ready to be duplicated.
The three that break first
Not all gaps cost the same. In a shop that split too early, the failures cluster in three places, so prove these first:
- Quality check. Without a written standard the crew self-checks against, your reputation becomes a coin flip on jobs you never see.
- Money handling. Loose rules on collection, discounting, and deposits leak margin fastest when nobody is watching the till.
- Communication cadence. Without a fixed reporting rhythm, small problems at the far crew are invisible until they are large and in front of a customer.
What does not need a system yet
Do not try to document everything before you move, or you will never move. Rare, one-off tasks and genuine judgment calls that come up a few times a year can stay in your head or route back to you for now. A system for something that happens twice a year is wasted effort. Standardize the high-frequency, high-impact work first (the daily operating loop and the customer touchpoints), and leave the long tail alone until it earns a document.
Build them, then prove them, then split
Get the order right. Write the system, run it with your current crew while you are still present to catch what the document missed, refine it, and only then hand it to a crew you cannot watch. A system proven with people you can see is one you can trust with people you cannot. Skip the proving step and the second crew becomes your test lab, in front of paying customers.
References
- SBA guidance on operational systems and process documentation for scaling small firms
- Trade-standard practice for standard operating procedures and quality checklists in field service
- See related: Scaling Systems Before Headcount; Ready to Open a Second Location or Not Decision Tree; Standardizing Your Process So Every Crew Runs the Same Way