Most multi-location roofing companies don’t struggle because they hired the wrong people. They struggle because the same job, sold and built in three different branches, quietly turns into three different products. Pricing drifts. Job boards stop matching. Monday morning meetings turn into arguments about whose numbers are right instead of conversations about what to do next. By the time the problem shows up on a P&L, it has usually been leaking margin for two quarters.
If you’re running somewhere between two and five branches, this is probably the most expensive problem you have, and it doesn’t show up as a single line item anywhere.
Where the margin actually leaks
The leaks don’t announce themselves. They show up in the gaps between branches:
- Add-ons and upsells that one branch quotes every time and another forgets entirely
- Waste factors that vary by estimator instead of by job type
- Supplements and change orders that run through three different paperwork flows with three different approval limits
- “Rework” that can’t be compared across branches because each location defines it differently
- Labor overruns hiding inside vague stage names like “in progress”
Two branches doing $4M each can post wildly different gross margins on the same mix of jobs. That gap usually isn’t talent. It’s the system. Without consistent job-costing definitions, you’re not really running a multi-branch company. You’re running several small companies under one logo.
What standardization is (and isn’t)
Standardization doesn’t mean every branch does every job identically. It means everyone making the same decision arrives at the same outcome. Branches keep control of their inputs: which supplier to call, which crew to send, how to read the local market. They give up control of outputs: how a job is named, priced, staged, and reported.
A good way to think about it is guardrails versus scripts. A script tells people what to say. A guardrail tells them what’s out of bounds. You want guardrails on pricing, job stages, and KPIs, and real freedom inside them.
Settle who owns what before you touch any software
The single most important document in a multi-location rollout is a one-page agreement on what headquarters owns and what each branch owns. Get it settled in a room with your branch managers first, or every disagreement for the next year turns into a referendum on the whole operating model.
A sensible split looks like this:
- HQ owns: the master pricebook (line items, naming, units, base costs), workflow stages and the rules for moving between them, KPI definitions and reporting cadence, and the safety baseline
- Branches own: supplier contacts and terms, day-to-day dispatch and crew scheduling, regional price adjustments, and notes on local anomalies
- Guardrails that keep it honest: a quarterly pricebook audit, locked status definitions, a required update window for job status, and one source of truth for reporting
On safety, don’t treat this as a margin issue. Fall protection has been the most-cited OSHA standard for fifteen years running, and the Bureau of Labor Statistics counted 421 fatal falls to a lower level in construction in 2023 alone. Your fall protection checklist belongs at the company level, documented on every job.
Resist the urge to over-centralize, too. Branches stripped of all autonomy build shadow systems out of spreadsheets and group texts. The labor market in Houston isn’t the labor market in Charlotte, and a branch that has worked its market for three years knows which inspector wants what and which neighborhood association has opinions about shingle color. Paying corporate to relearn that is a waste.
Score where you are before you fix anything
Before you write a single new SOP, rate each branch from 1 to 5 across three layers:
- Estimating: 1 means every estimator freelances. 3 means shared templates with mixed line items. 5 means a master pricebook with locked rules.
- Production: 1 means “ask Bob how we do it.” 3 means shared stages with inconsistent handoffs. 5 means standard boards with quality gates.
- Reporting: 1 means the numbers get argued about weekly. 3 means basic dashboards with weak definitions. 5 means trusted KPIs on a real cadence.
If most branches score 1 or 2 across the board, you don’t have a software problem. You have a definitions problem. If estimating scores a 3 or 4 but reporting sits at 1 or 2, your sales motion is running ahead of your operations. Each pattern points to a different first move, and it keeps you from the “let’s blame the new branch manager” reflex.
Layer one: estimating that protects margin
Estimating is where margin is won or lost before anyone touches a shingle. Your master pricebook needs more than a spreadsheet. It needs naming conventions, units, waste factors, bundle logic, and a rhythm for refreshing base costs. Standard should include locked line-item names, bundles versus à la carte rules, estimate templates by job type (retail, insurance, service, commercial), add-on menus that catch ventilation, decking, and gutters consistently, and approval limits on who can create a line item versus who can only select one.
Handle local pricing with branch adjusters rather than separate pricebooks. Each branch applies a multiplier on top of the master cost, so when a supplier changes prices in Tampa but not Atlanta, only the Tampa adjuster moves and reporting still rolls up cleanly.
Layer two: production that moves the same way everywhere
The stage names matter less than the entry and exit rules. A job shouldn’t move from pre-production to scheduled without permits, ordered materials, and a signed scope. It shouldn’t move to closeout without final photos, customer signoff, and invoiced amounts reconciled. Without those gates, “in progress” becomes a black box where margin disappears. Let crews update jobs from their phones so one action moves the job, records the photo, and feeds the report. Double entry is the surest way to kill any rollout. Storm surges and emergency repairs deserve their own lane with simpler rules so they don’t blow up the standard board.
Layer three: reporting you can trust
If the first two layers are right, reporting gets easy. Lock these definitions in writing: what counts as a completed job, what’s included in gross profit versus gross margin versus contribution margin, how change orders and discounts get categorized, and which timestamps count for lead-to-sale and cycle time. Then set a cadence: daily for blockers and overdue handoffs, weekly for pipeline health and variance flags, monthly for margin by job type and branch comparisons.
A 90-day rollout
- Days 1–15: Agree on the ownership rules, freeze new line items, statuses, and fields, and pick one pilot branch and one or two job types.
- Days 16–45: Build the minimum viable standard: pricebook v1 for your top revenue jobs, shared stages with handoff checklists, KPI definitions, and first dashboards. Aim for consistent, not comprehensive.
- Days 46–75: Roll out to every branch with role-based training, weekly audits on estimate variance and stage aging, and a feedback loop that improves the standard without reopening every debate.
- Days 76–90: Lock it in with owners for the pricebook, workflow, and reporting, a monthly change-control meeting, and a quarterly calibration.
The proof is simple. When the same job type quoted in two branches comes back with comparable margin and cycle time, you have a standard. When the Monday meeting stops being about why the numbers differ and starts being about what to do about them, you have a company.
Where tools fit
Software doesn’t create the standard. It enforces the one you’ve already defined. Look for shared line items with role-based permissions, visual workflows with stage gates, cross-branch rollups with locked KPI definitions, and consistent handling of subcontractors. The most common failure is copying boards between branches without defining entry and exit rules, then blaming the dashboard when the data doesn’t line up. If you’re at the point of choosing a platform, it’s worth a look at roofing software for multiple locations, and JobNimbus also offers an Enterprise plan built for running multiple crews and branches with executive reporting.
This post was inspired by an article from JobNimbus. Read their original piece, Multi-Branch Roofer’s Standardization Playbook for 3+ Locations, which includes their full maturity scorecard and FAQ.
