Running one program
across many sites

Why arrangements drift apart

Nothing goes wrong dramatically. A plant manager solves a problem locally. A site inherits an arrangement from a previous tenant. A regional team sets something up that works well. Years pass, people move on, and the original reasoning leaves with them.

The result is not usually bad service. It is an absence of comparison. When no two sites are on the same structure, nobody can tell which ones are doing well, which are overpaying for the same thing, or what would happen if one changed.

What one program actually standardizes

Four things, and deliberately not more: how material is classified, how it is documented, how it is reported, and who is accountable when something goes wrong.

Those four create comparability. They do not require every site to run identically, and attempting that is where most consolidation efforts fail.

What has to stay local

Collection frequency, equipment, and which facility receives the material are all local questions, and they should stay local. A site in a dense metro and a site two hours from anywhere do not have the same options, and pretending otherwise produces a program that works on paper and fails at the dock.

The goal is one structure with local execution, not one arrangement imposed everywhere. A site that cannot work the way the structure assumes will quietly go around it, and then you have thirty-one arrangements instead of thirty.

Reporting in one format

This is the part that pays for the whole exercise. One format across every site means the numbers can be added up, compared, and taken to a board or a customer without a month of reconciliation first.

It also surfaces things no individual site would notice. One location generating a stream nobody else has. A material being disposed of at one site and recovered at another. Seasonal patterns that only appear at the network level.

Rolling it out without disrupting anything

Do not change every site at once. Start with the sites that are already causing problems or generating the most volume, prove the structure works there, and use that as the reference the rest are moved onto.

Existing commitments at each site need to be mapped before anything moves, including notice periods and anything auto-renewing. A rollout that collides with those is how a consolidation ends up costing more in its first year than it saves.

What to watch once it is running

Three things are worth tracking at the network level: which sites are outliers on any stream, where documentation is incomplete, and what changed after each site was moved over.

The third is the one usually skipped, and it is the one that tells you whether the program is working or whether the sites have simply gone quiet.