Hospitality Technology

One Employee List: Choosing a Source of Truth for Your Team

Ask a general manager how many people work at their restaurant and you will often get three answers. Picture a dining room where the point of sale shows 31 active logins, the scheduling system shows 27 people, and the payroll or HR file shows 34. Each number is right inside its own system. None of them answers the question. In my view, good restaurant employee management starts with deciding which list is the real one, letting the other systems add detail, and bringing the whole team in at once instead of one awkward login at a time.

I'm Richard Yu. I have more than 15 years of startup and go-to-market experience, much of it in customer success and solutions engineering, and I'm a co-founder and the Managing Partner for marketing and operations at the restaurant I co-founded in San Francisco. I built Regular, the hospitality operating system, inside that restaurant, one service at a time. Here is how I think about a single staff list, and the weekly habit that keeps it true.

Three Systems, Three Staff Lists

The lists drift for ordinary reasons. Someone gets a point of sale login when they first need to ring in a check. They appear on the schedule when a manager first puts them on the calendar. They land in the HR file when the paperwork clears. Three different moments, often handled by three different people.

Leaving works the same way in reverse. Picture a server who gives notice and works a last Saturday. The manager takes them off next week's schedule. Their login in a system like Toast stays active for months because nobody thought of it. The HR file marks them terminated two weeks later.

Now picture a new host scheduled for Friday who has no point of sale login yet, so a manager rings in her first tables under their own name.

The cost is quiet but real. Sales get credited to the wrong person, so coaching conversations start from bad numbers. Access stays open for people who no longer work there. And any tool that sits on top of these systems, whether it reports on servers or sends a staff message, inherits the confusion. In my experience, most of the strange numbers a manager sees in a report trace back to the staff list, not to the report.

Picking the Source of Truth

A source of truth is simply the one list that decides who works at the restaurant. Everything else defers to it. For most independent restaurants the choice is between three places: the point of sale, the scheduling system, or an HR or PEO export file.

I ask two questions to choose. First, where does a new hire get added first, reliably, every time? Second, where does someone get removed fastest when they leave? The system that wins both is usually your answer.

In many restaurants I talk to, the schedule wins, because the manager lives in a tool like 7shifts daily and a person who is not on the schedule is effectively not working. If you run payroll through a PEO and your manager is disciplined about the paperwork, the HR file can be the cleaner record. The point of sale is the right choice when it is the first thing set up for every hire and the first thing shut off when someone leaves.

I learned to ask this before anything else in software. In customer success, the implementations that went smoothly were usually the ones where we agreed on day one which system owned the customer record. The ones that skipped the question often spent months reconciling.

What the Other Systems Still Add

Choosing a source of truth does not mean ignoring the other systems. It means they stop deciding who exists and start adding what they know about the people who do.

The point of sale knows which employee rang in which check, which is what lets sales and table turns line up with the right server. The schedule knows positions and shifts. The HR file usually holds start dates and legal names. Each of those details is useful. None of them should be allowed to add a ghost employee to the list or remove a real one.

That is how the employee source of truth in Regular works: the owner picks the point of sale, the scheduling system or an HR or PEO export file as the source, and the other systems only add details to the people already on that list.

One practical tip: fix names at the source. If the schedule says Sam and the HR file says Samantha, decide which one your source of truth uses and make the others match over time. Matching is easier when the same person looks the same everywhere. I wrote more about how these systems should work together in what a hospitality operating system does for a restaurant.

Inviting the Whole Team at Once

Once the list is right, employee onboarding into a new tool should take minutes, not a month of chasing people for their email addresses. The usual failure is inviting staff one by one as they happen to ask, which leaves half the team in and half the team out, and the tool looks unused.

A bulk invite fixes that. In Regular, an owner can tick several people on the list and invite them all at once, or mark them active or inactive in the same way. Sign-in is invite-only, so nobody outside the list gets in by guessing a link.

Before you send invites, decide what each person should see. Roles and permissions come built in, and you can add your own custom roles with No Access, View or Full Access for each app. Staff only see their own performance numbers, plus team figures large enough that no one can be singled out. Owners can use View As to see exactly what a given person will see, which I recommend doing once for a server and once for a cook before the invites go out.

Then tell the team in person at lineup why the invite is coming. A text from an unknown sender is easy to ignore. A sentence from the manager they work beside is not. If you want to think about what makes staff open the app afterwards, I covered it in a restaurant staff app your team will actually open.

Keeping the List Honest Every Week

A clean list decays unless someone looks after it. I suggest a short routine on the same day each week, ideally before the next schedule is published.

  1. Count the active people in your source of truth and compare it with the people who actually worked last week. Any gap is a question to answer.
  2. Mark anyone who has left as inactive the same day you find them, in the source first.
  3. Check that every new hire starting this week is on the list and invited before their first shift, not after it.
  4. Confirm each person's role still fits. A server who now trains hosts may need different access.
  5. Use View As on one recent hire to make sure they see what you expect.

Here is what I think technology should do at this moment: hold one list, carry details across from the other systems, and make inviting or deactivating a group of people fast. What it should not do is decide on its own who works at your restaurant, or replace the manager who shakes a new person's hand and tells them who to shadow. Check your local rules on employee records and access where they apply.

You can find me on Instagram. If you want to see how one employee list works with your own systems, you can book a Regular demo.

Frequently Asked Questions

What is a source of truth for restaurant employees?

It is the one system that decides who works at your restaurant. Usually that is the point of sale, the scheduling system or an HR or PEO export file. The other systems still contribute details, such as which checks a server rang in or which shifts they work, but they do not add or remove people from the list. One list means reports, access and messages all start from the same team.

Should my POS or my scheduling system be the master staff list?

Choose the system where new hires are reliably added first and departing staff are removed fastest. In many independent restaurants that is the scheduling tool, because managers use it daily. If payroll runs through a PEO and paperwork is handled promptly, the HR file can be cleaner. The point of sale works when it is the first thing set up and the first thing shut off.

How do I onboard a whole restaurant team to a new app at once?

Clean the staff list first, then set roles so each person sees only what they need. Check what a server and a cook will see before inviting anyone. Send a bulk invite to the whole active team on the same day, and mention it at lineup so staff recognise the message. Inviting people one at a time tends to leave half the team outside the tool.

How often should I review my restaurant staff list?

Weekly works well for most restaurants, ideally before the next schedule is published. Compare active people with who actually worked, mark leavers inactive in the source system, confirm new hires are invited before their first shift and check that roles still fit. It takes a few minutes and prevents stale logins, misattributed sales and confused reports.

Regular

Run the Night Your Regulars Remember

One suite of apps that connects your reservations, POS and schedule, from before the meal to the next visit.