Articles

•

November 16, 2026

How to Standardize Processes Across Departments and Locations

Sign up for our newsletter
Read for free. Unsubscribe anytime.
SHARE IT!

To standardize processes across departments and locations at 180 to 225 people, decide which processes must be identical everywhere and which can flex locally, document each standard once with a named owner, assign it by role and location, and track adoption site by site. Trainual is Business Operations & SOP Software that turns company knowledge into employee performance, with Training, Operations, and Performance in one place, so every department and location runs from the same playbook.

Three locations, three ways to open in the morning. The regional ops leader learns this on a Tuesday visit to site two, where the opening checklist is a laminated sheet from a manager who left last year. Site one uses a shared doc. Site three relies on whoever opens first. A customer complaint brought them here, and it traces straight back to a skipped step that only one site knew about.

At 180 to 225 people, this is normal. Departments and locations grow faster than the processes that hold them together, and every site fills the gap its own way. Standardizing isn't about making every site identical; it's about agreeing on what has to be the same and writing it down once.

Updated November 2026.

Key takeaways

  • Decide what must be identical and what can flex locally before you write anything.
  • Write each standard once, with one owner, and put local details in short addenda.
  • Assign by role and location, so each site gets exactly the version it needs.
  • Track adoption site by site. Standards spread when people can see which sites are following them.

Why standardization breaks at 180 to 225 people

The same causes show up in almost every company at this size:

  1. Each location or department wrote its own version when it opened or grew.
  2. The person who built the process left, and the site kept running on memory.
  3. There's no owner for the standard, so nobody resolves the differences.
  4. Training happens locally, so new hires learn the site's version, not the company's.
  5. Nobody compares sites, so the gaps only surface through complaints.

Standard vs. local: decide what must be the same

The first decision is the most important one. Not everything needs to be identical, and trying to standardize everything makes managers push back on all of it.

Process type Standardize everywhere? Example
Safety and compliance Yes, word for word Incident reporting, required training, data handling
Customer-facing steps Yes, the outcome and key steps How a complaint is handled, what every customer hears at checkout
Cross-department handoffs Yes, who hands off what and when Sales to onboarding, service to billing
Local details No, documented as a local addendum Vendors, hours, building access, local contacts
Team rituals Flex, with a shared minimum Huddle format and timing per site, with the same core agenda

A useful rule: if a customer, an auditor, or another department would notice the difference, standardize it. If only the local team would, document it locally.

How to standardize processes across departments at 180 people

At around 180 people, most of the friction is between departments, not inside them. Work breaks at the handoffs.

  1. Map the handoffs first. List where work passes between departments, like sales to onboarding or service to billing.
  2. Name an owner for each department's processes, plus one owner for each cross-department process.
  3. Use one template across departments, so a process from finance reads like one from operations.
  4. Put ownership on a role chart, so it's clear who owns each step, not just each department.
  5. Review cross-department processes together, with both owners in the room.

For more on clarifying who owns what, see how to define ownership across overlapping roles.

How to standardize processes across locations at 225 people

At around 225 people with several locations, the challenge shifts to distance. The standard has to reach people you rarely see.

  1. Write one standard per core workflow, owned centrally.
  2. Add local addenda for details that truly differ by site, assigned only to that location.
  3. Name a lead at every site who owns adoption locally and feeds improvements back.
  4. Assign by location, so every site gets the standard plus its own addendum, automatically.
  5. Compare sites side by side on completion and results, so the ones falling behind get help early.

The franchise version of this playbook is in the 5 SOPs every franchise and multi-location team needs.

How to write a local addendum

A local addendum keeps the standard intact while giving each site what's different. Keep it short and predictable:

  • Link it to the standard. The addendum adds to one specific process; it never replaces it.
  • Cover only what differs: local vendors, contacts, hours, equipment, or regulations.
  • Give it a local owner, usually the site lead, who updates it when something changes on site.
  • Assign it only to that location, so people elsewhere never see details that don't apply to them.
  • Review it with the standard. When the standard changes, check whether each addendum still fits.

If an addendum starts rewriting the core steps, that's a signal: either the site needs help following the standard, or the standard needs to change for everyone.

Which processes to standardize first

With dozens of candidates, start where inconsistency costs the most:

  1. Safety and compliance procedures, because the risk is highest.
  2. The customer moments people remember, like greetings, complaints, and the first visit.
  3. Handoffs between departments, where work most often stalls.
  4. Onboarding for your highest-volume roles, so every new hire starts on the standard.

The rollout plan

Roll standards out in phases, so you can fix problems at one site before they reach all of them.

Phase 1
Define
Pick and define the standards
Choose the 10 processes that matter most and decide what's standard vs. local.
Phase 2
Pilot
Document and pilot one site
Write the standard once, with an owner, and run it at one department or location.
Phase 3
Roll out
Roll out in waves
Expand site by site or department by department, with a lead at each.
Phase 4
Track
Track adoption by site
Watch completion and site scorecards; fix the sites that fall behind.
Ongoing
Refine
Improve the standard
Bring better local ideas back into the standard so every site benefits.
  1. Pick and define the standards. Choose the 10 processes that matter most, and decide what's standard and what's local for each.
  2. Document and pilot at one site. Write each standard once, with an owner, and run it at one department or location for a few weeks.
  3. Roll out in waves. Expand site by site or department by department, with a lead at each.
  4. Track adoption by site. Watch completion and site-level results, and step in where a site falls behind.
  5. Refine the standard. When a site finds a better way, bring it into the standard so every site benefits.

How to tell whether sites are following the standard

You can't visit every site every week, so make adoption visible:

  • Training completion by location: which sites have learned the current version.
  • Site-level scorecards: the same few metrics for every location, side by side.
  • Spot checks on the highest-risk processes, like safety and compliance.
  • Question volume: a spike in questions from one site usually means the standard isn't clear there.
  • Customer signals: complaints or reviews that cluster at one location.

Common standardization mistakes

  • Standardizing everything. Managers resist when local details are treated like company policy.
  • Writing standards at headquarters only. Site leads who helped shape the standard are the ones who enforce it.
  • No owner. Without one person accountable, the differences creep back.
  • Rolling out everywhere at once. A pilot site catches problems before they multiply.
  • Never updating the standard. If sites can't improve it, they'll quietly work around it.

How to standardize across departments and locations in Trainual

Trainual keeps one standard for every process, delivers the right version to each role and location, and shows which sites are following it.

Training: one standard, delivered everywhere.

Operations: see every site side by side.

  • Site scorecards. Goals and scorecards track the same metrics for every location.
  • Regional rhythm. Meetings keep site leads on a standing agenda, with action items that roll over until they're done.
  • People data in sync. Teams with more than one entity can connect several entities from one supported HR system through integrations.

Performance: the same expectations at every location.

  • One standard for every role. Each role's responsibilities are the same company-wide, so a manager at site three holds people to the same bar as site one.
  • Reviews grounded in the standard. In Performance, reviews draw on each role's responsibilities and completed training.

Together, that's the loop:

  • Train: so everyone knows how work should be done.
  • Operate: so everyone knows what needs to happen today.
  • Perform: so everyone knows what's expected and how knowledge turns into better work.

Multi-location teams see it in their results. Pinch improved its Net Promoter Score to 95+; as Laura Lakin, Head of Provider Success, put it, "One of the biggest benefits of Trainual has been the ability to implement consistent training across all our providers' locations." ProTec Building Services runs 600+ SOPs across nine offices. For more, see 5 multi-location companies scaling operations and Trainual for multi-location teams.

Quick wins to start this week

Quick win #1: Pick one process and compare it across sites

Ask each site how they do it. The differences tell you where to start.

Quick win #2: Sort your top 10 processes into standard or local

Use the table above to decide.

Quick win #3: Name an owner for each standard

One person per process, not a committee.

Quick win #4: Choose your pilot site

Pick a site with a supportive lead and typical volume.

Quick win #5: Pick three metrics every site reports

The same three, side by side, every week.

Ready to see how Trainual works?

👉 Book a demo and see how Trainual keeps every department and location on the same playbook.

Want a sneak peek?

👉 Read customer stories from multi-location teams who standardized how work gets done.

Frequently asked questions

How do you standardize processes across departments and locations?

Decide which processes must be identical everywhere and which can flex locally, document each standard once with a named owner, assign it by role and location, pilot it at one site, roll it out in waves, and track adoption site by site.

How do you standardize processes across departments at a 180-person company?

Start with the handoffs between departments, since that's where work most often breaks. Name an owner for each department's processes, use one template across departments, map who owns each step on a role chart, and review cross-department processes together.

How do you standardize workflows across many sites?

Write one standard for each core workflow, add local addenda for details that truly differ by site, assign the right version to each location, name a lead at every site, and compare completion and results across sites so you can see which ones need help.

Which processes should be the same at every location?

Safety and compliance procedures, the customer-facing steps that define your experience, and the handoffs between teams. Local details like vendors, hours, and contacts can vary, as long as they're documented.

How do you get location managers to follow the standard?

Involve them in writing it, give them a clear way to suggest changes, and make adoption visible by site. Managers follow standards they helped shape and can see working.

How do you handle local differences without breaking the standard?

Keep the core process identical and put local details in a short addendum assigned only to that location. That way, the standard stays one document, and each site still has what it needs.

How do you know if sites are following the standard?

Track training completion by location, compare site-level scorecards, run spot checks on the highest-risk processes, and watch for spikes in questions or customer complaints at a single site.

Can one system handle several entities or locations?

Yes. In Trainual, content can be assigned by role, department, and location, and teams with more than one entity can connect several entities from one supported HR system.

📰

Become a better business
leader in 5 minutes or less.

Join over 50K readers who get The Manual in their inbox each month.
Practical, tactical insights you can use right away.
Join our 50k+ readers

Smarter than your smartest employee. Faster than your shared drive.

The know-it-all tool every employee uses to understand what to do, how to do it, and who’s doing what. Purpose-built to make your team instantly more productive, consistent, and aligned from day one to day 1,000.