Hiring for multiple locations without losing the thread
Hiring for several locations goes wrong in the same place every time: one pooled pipeline for sites that draw from completely different neighborhoods. Treat each location as its own labor market with its own radius, its own pay reality and its own posting, and the pipeline stops collapsing into the busiest store.
Why the pooled pipeline fails
Two of your sites can be nine miles apart and share almost no candidates. The people who can reach one on a twenty-minute drive mostly cannot reach the other, and a single applicant pool hides that completely.
What you see instead is one location filling easily and another never filling, with no obvious reason. The reason is geography, and a pooled pipeline is designed not to show it.
Commute distance is the variable doing the damage. The 2024 American Community Survey put the US mean one-way commute at 27.2 minutes, and 9.3 percent of workers now travel an hour or more each way. Candidates decline quietly on distance far more often than they say so.
Give every location its own radius
Draw the catchment for each site separately, using drive time rather than a mileage ring. A five-mile radius across a river or a rail corridor is not a five-mile radius in practice, and a straight-line circle will tell you it is.
Then look at what is inside each one. Two stores in the same chain can face entirely different competition for the same role: one surrounded by employers bidding for the same shift workers, the other with almost none.
Staff the harder catchment differently rather than harder. More budget, earlier posting, or a shift pattern the competing employers do not offer.
Post per location, always
One posting covering "multiple locations" performs worse than three postings naming three addresses. Candidates filter on distance first, and a listing that cannot answer "how far is it" gets skipped.
Naming the site also fixes the interview stage. A candidate who applied to a specific address has already decided the commute works, which removes the most common late-stage dropout in hourly hiring.
In Colorado, per-location posting also keeps you clean on disclosure: the state's pay transparency rules require the range to reflect what you genuinely expect to pay for that role, including any local minimum wage that applies.
Let pay vary by site, deliberately
Paying identically across locations feels fair and frequently is not. A wage that is competitive in one catchment can be below market four miles away, and the store that cannot fill is telling you which.
Metro-wide averages are the wrong benchmark for this, because they average across exactly the variation you are trying to see. The Bureau of Labor Statistics survey for May 2025 put the Denver metro mean hourly wage at $39.28 across all occupations and food preparation and serving at $21.46 — a spread that tells you nothing about one neighborhood against another.
Set a band per role, then position each site inside it based on what that catchment actually costs.
Move people between sites on purpose
A transfer request is usually a retention save disguised as an inconvenience. Somebody whose circumstances changed and who now has a forty-minute drive will leave; the same person eight minutes from a different site of yours will stay.
Ask about it before the resignation rather than after. Quits were running at 3.2 million a month nationally, a rate of 2.0 percent, in the BLS Job Openings and Labor Turnover Survey for June 2026, and a meaningful share of that movement is people solving a commute problem by changing employer.
Keeping a trained employee by moving them three miles is the cheapest hire you will make.
Coordinate offers, or lose candidates twice
Two sites interviewing the same candidate without knowing it is common and expensive. The candidate gets two calls, forms a view of how organized you are, and frequently takes neither role.
Worse is the near-miss: a strong applicant rejected at one site because the role filled, while an identical opening sits unfilled four miles away. Without a shared view, that person is simply lost, and you pay to source them again the following month.
The cost of losing them is not theoretical. Hires and separations both run in the millions each month — quits alone were 3.2 million with layoffs and discharges at 1.8 million in the BLS Job Openings and Labor Turnover Survey for June 2026 — so the same candidate is very likely to be hired by somebody within weeks.
Agree one rule up front — a rejected candidate is offered to the nearest site with an open role of the same type, before the rejection goes out. A short redirect converts a wasted application into a hire more often than a fresh posting does, and the posting itself may not be the problem.
Keep one view of the whole thing
Per-location does not mean disconnected. Run one place where every open role, every applicant and every stage is visible across all sites, or the fifth location becomes invisible and stays unfilled for a month before anyone notices.
Give each site's manager control of their own pipeline and keep the overview central. Managers who cannot act on their own applicants stop checking, which is how good candidates go cold in a queue.
Review the whole picture monthly: time to fill by site, applications per posting by site, and which catchments are consistently harder. Patterns show up quickly once the data is not pooled.
Where a site is genuinely starved rather than badly managed, the fix is usually visibility rather than budget — the checklist for getting found locally applies per address, not per company. Claim each location separately when you set the business up.
Common questions
Should each location have its own manager doing the hiring?
Where the site has a manager, yes, with the overview held centrally. Local managers know their catchment and can act same-day, and speed matters more than process consistency in hourly hiring.
How different can pay be between nearby sites?
As different as the local markets are, provided the reasoning is documented and applied consistently. Differences that track catchment competition are defensible; differences that track who negotiated hardest are not.
Is one careers page enough for multiple sites?
Only if it lists each location separately with its own address and pay range. A single page describing "various locations" fails the distance filter candidates apply first, and in Colorado it also risks the disclosure requirements.
What is the first sign the pipeline is pooling badly?
One site filling in days while another takes months, with no obvious difference in the role. That gap is nearly always catchment rather than management, and a pooled applicant list is what keeps it invisible.