When to Split One Team Into Two Groups

You run one export at the end of the month and the total looks right. Then a grant officer asks how many hours went to the after-school program versus the weekend food drive, and you have no clean way to answer. The hours are all there. They are just piled together. That is the moment you needed two worker groups instead of one.

This walks through the decision in order: what a group actually is, the three questions that tell you to split, how to do the split without losing history, and how it changes your reports.

What a worker group does, in one sentence

A worker group is a label on people, not on time. You attach it to the person once, and every entry that person records inherits it, so you can filter a report down to just that set of workers. Tags do the same job for individual entries: you attach a tag to a shift to mark what it was for. People get groups. Time entries get tags. Keep that split straight and most of your reporting problems disappear.

A dishwasher who only ever washes dishes belongs in one group and needs no tags. A tutor who works both the reading program and the summer camp is one person in one group, with tags on each entry to show which program the hours went to. When you are not sure which tool to use, ask whether the thing you want to separate is a who or a what.

The three questions that tell you to split

Do not split a team just because it is large. Fifty volunteers in one group is fine if you never need to report on them separately. Split when the answer to any of these is yes.

Do you ever report on the two sets separately? If a funder, an owner, or a board wants front-of-house hours apart from kitchen hours, those are two groups. If nobody ever asks for the breakdown, one group is less work.

Do the two sets have different pay or credit rules? Paid staff and unpaid volunteers should never share a group, even if they work side by side at the same event. The volunteer summary and the payroll export are different documents with different readers, and you want to filter cleanly to each.

Do people move between the two? This is the tie-breaker. If a person does both jobs in the same week, do not make two groups. Keep one group for the person and use tags on entries to mark which job each shift was. Groups follow the worker; tags follow the shift. A server who covers the host stand on a slow Tuesday is still one person in the servers group, with a tag on that one entry.

Two worked examples

A 12-seat restaurant starts with everyone in one group called Staff. Payroll runs fine. Then the owner wants to know labor cost for the kitchen versus the floor, because the kitchen is going over budget. Now Staff is too coarse. Split into a Kitchen group and a Front group, put each person in one, and the next export gives two subtotals without any hand math. The line cook who occasionally runs food stays in Kitchen; tag that food-running shift if you want it counted toward the floor.

An event lead runs a two-day festival with 40 volunteers. Some work the gate, some work setup and teardown, some run the info booth. The lead does not need three groups. Everyone goes in one Festival group, and each shift gets a tag: gate, setup, booth. People rotate across all three during the weekend, so groups would fight the reality on the ground. Tags win because the assignment changes hour to hour. If the same lead also ran a separate winter fundraiser with a different roster, that roster would be its own group, because those are different people and different programs.

How to split without losing history

Splitting is safe. It relabels people going forward and does not delete or move recorded time. Do it in this order.

1. Decide the group names before you touch anything. Use plain names a stranger would understand on a report: Kitchen, Front, Gate Crew. Avoid initials.
2. Create the two new groups.
3. Reassign each person to exactly one group. One person, one group. If someone genuinely straddles both, that is your signal to use tags instead for that overlap, not to put them in two groups.
4. Retire the old catch-all group name so nobody adds new people to it by habit.
5. Run one test export before payroll and confirm both groups show the head counts you expect. The distinct-worker count per group is the fastest sanity check.

None of this changes how anyone clocks in. Workers still tap a name on the kiosk, scan the poster, or open their link, with no account and no app. Groups are an admin-side label; the person on the floor never sees the change. If you want a shared tablet running before you reorganize anything, the live kiosk demo shows exactly what workers tap.

What changes in your reports after the split

Your CSV keeps the same columns in the same order, so anything you built on top of it still works. What you gain is a clean filter: pull one group and get its hours and its distinct-worker count on their own. For a grant report you can now show the after-school program's volunteers separately from the food drive's, from one export, in one pass.

The mechanics that keep those numbers honest do not depend on grouping. A forgotten clock-out still gets closed at its start time plus a cutoff, never at the current time, so no group's total gets inflated by a punch someone left open overnight. Groups only decide how the honest numbers get sliced.

Start with one group. Split the first time a real question forces you to, name the new groups so a funder can read them, and let tags handle the people who cross the line. If you have not set up your first team yet, start a free workspace and build the groups as the questions come.