Employee recognition across multiple locations

A clinic network opens its ninth site in March. Headcount has nearly doubled in a year. The HR team is still two people, and one of them is spending most of the week on benefits enrollment for the new staff.

Some companies grow one hire at a time. Others grow a location at a time, through new sites, acquisitions, or new states. When that happens, recognition that ran fine while one person knew everyone starts to come apart across multiple locations, usually without anyone deciding to let it go.

What breaks when locations multiply

The person who remembered can no longer know everyone. At three locations, an operations director can keep birthdays in their head. At fifteen, they cannot, and the people at the newest sites are the first to be missed.

Each site invents its own version. One manager brings a cake for every birthday. Another does nothing. A third spends far more than anyone else. Employees at different sites talk, and the differences look like favoritism even when nobody intended it.

Acquired teams bring their own traditions. The company you bought may have had a generous anniversary program, or none at all. Long-tenured staff on both sides watch closely to see whose way wins.

Data lags behind. New sites may join the HR system late, with incomplete birthdays or hire dates, and recognition based on that data misses people quietly.

Decide what is central and what is local

Keep local managers at the center of recognition, and separate the parts that should be the same everywhere from the parts that should feel local.

When the central parts run on their own, site managers only have to do what they are best placed to do: know their people and say something personal about them.

Bring each new location in on day one

Add recognition to the checklist for every new site or acquisition, next to payroll setup and IT:

1. Load the people into your HR or payroll system with birthdays, hire dates, and home addresses, before the first occasion comes due.
2. Decide how acquired tenure counts. Most companies honor the original hire date for work anniversaries. Telling acquired staff that their years count is one of the strongest welcomes you can give.
3. Welcome the whole new team with the same gift every new hire gets, so the acquisition starts with a gesture rather than a memo.
4. Tell the site manager what their part is: what they will be asked to do, and roughly how often.

Watch the tension between old and new

Fast growth often creates a quiet divide. Long-tenured employees feel the company they joined is disappearing. New hires feel like outsiders. Recognition can help with both, if it is fair.

Make sure milestone anniversaries for long-tenured staff are visibly honored, especially in a year of big change. Make sure new hires at a new site get exactly what new hires at the original site get. A ten-year anniversary at the acquired location should look exactly like one at headquarters. People read a lot into that.

Look at it site by site

Once recognition runs on one set of rules, it becomes possible to look at it location by location, as long as your people records carry their location. A quarterly view of who was recognized at each site answers two questions growing companies care about: is every site treated the same, and is every site taking part? A location with no recognition at all for a quarter is worth a phone call.

Set it up before the next opening

The easiest time to put a recognition process in place is before the next location opens, not after the fifth one has been running its own way for a year. Moving a scattered program onto one process later means undoing local habits. Starting with one process means every new site joins it on day one.

Thankscrate reads people and dates from your payroll or HR system, so a new location is included as soon as its people are added, with the same occasions and budgets as everyone else. See how automated appreciation works.