In a 20-person team, attendance usually needs no system at all: everyone can see everyone, absences are obvious, and one spreadsheet covers month-end. At 200 people the same method stops working - and that is nobody's fault. Attendance for growing companies does not get harder in a straight line; it changes in jumps at particular points. This article shows where those jumps sit. The numbers are illustrative and are not any product's limits.
What works at 20 people
In a small team the attendance process rests on three things: seeing each other, memory and direct conversation.
All three are cheap and fast. When somebody is missing, everyone knows; time off is agreed verbally; at month-end one person fills in a sheet and the job is done.
The important point is that this method is not bad. At its own scale it is optimal. The trouble starts only when the scale changes.
The first jump: seeing stops working
The first critical point arrives when the team no longer fits in one room. That usually happens around 30 to 40 people, or when a second department or floor appears.
From that moment "who is in?" no longer answers itself. Somebody has to ask and somebody has to answer - and that becomes daily work.
In practice this is the stage where a company creates its first spreadsheet. The sheet itself is not the problem; the question of who fills it in is.
The second jump: sources multiply
The second point is not about headcount but about structure: a second site, a second shift or a field team appears.
This is where the attendance process changes most. The reason is simple: data now arrives from several places rather than one, and the formats differ.
A new task appears at month-end - consolidation. That work grows in proportion to the number of sources, not the number of people.
The third jump: schedules diversify
A small company usually runs one schedule. As it grows, three or four types appear: the office on fixed hours, retail on shifts, the warehouse with nights, the field team on flexible hours.
From that point a single measurement baseline becomes useless. A shift team measured against 09:00 looks late every day and the report loses credibility.
In practice this is the jump most often missed - because headcount does not rise, only variety does.
The fourth jump: other people need the report
In a small company attendance data is needed by one person. As it grows, three or four roles need it: department managers, operations leadership, finance.
Each role asks a different question and one report satisfies none of them. HR starts preparing the same data in several formats - which can consume several days a month.
The picture in numbers
| Dimension | 20 people | 60 people | 200 people |
|---|---|---|---|
| Data sources | 1 | 2-3 | 5-8 |
| Schedule types | 1 | 2 | 3-5 |
| Report audiences | 1 | 2-3 | 4-6 |
| Month-end corrections | 0-1 | 3-6 | 10+ |
| "Who is missing?" | Self-evident | Asked | Investigated |
The figures are approximate and vary between companies. The direction, however, is always the same: when headcount triples, process load more than triples.
Why growth is not linear
The reason is arithmetic. Workload is proportional not to the number of people but to the number of connections.
Two sources involve one reconciliation; five sources involve ten. So when site count doubles, consolidation work roughly quadruples rather than doubles.
The same logic applies to schedule types: every new type affects every existing report.
The signs of a jump
Rather than calculating in theory, look for practical signals:
- Consolidation takes more than a day at month-end.
- The question "what does this cell mean?" repeats every month.
- Corrections after payroll have become normal.
- One team sits outside the reporting entirely (field, shift, part-time).
- Department managers message HR every morning.
Three of those five means the jump has already happened - the process simply has not changed yet.
When to change what
The most common mistake is changing too late. The second most common is changing too early - building a complex system for a 15-person team.
The practical trigger is not headcount but an event: opening a second site, introducing a second shift, or forming a field team.
If any of those three happens, the process needs to change - even if headcount stays exactly the same. We cover the wider picture on the automating employee attendance page.
Preparing before you grow
The easiest transition is the one made before the growth. The reason is simple: when a new site opens, everyone's attention is divided anyway.
Writing down three things in advance is enough: the list of schedule types, how time off is requested, and who receives which report in which format.
Those three documents take an hour to produce and shorten the later transition to a few days.
What does not need changing
Growth creates an urge to change everything at once. In practice that backfires.
Excel does not have to go - it remains as an output format. Existing hardware does not have to be replaced immediately either; a hybrid model is fine as long as the sources combine into one report.
Only one thing genuinely has to change: where the master data lives.
A practical example
A 28-person retailer kept attendance in one spreadsheet with no problems at all. Over a year the company opened two new locations and headcount reached 74.
Headcount had roughly tripled, but month-end work grew about sixfold: three files, two different schedules, four different reporting requirements.
The company made the transition after opening its third location. Their own assessment afterwards is telling: had they moved when the second location opened, they would have saved about two months of manual work. We collected the selection criteria on the choosing employee attendance software page.
How to assess your situation
Three questions describe it: how many sources feed your data; how many schedule types exist; how many hours of manual work does month-end take?
If the first number is above three, your process is already constrained by structure rather than headcount. We describe the benefits on the benefits of attendance software page.
Next step
Write down the changes you have planned for the next twelve months: a new site, a new shift, a new team. Then ask one question of each - what will this add to the current process?
QRGate keeps attendance in site, schedule and role context, and a new location does not create another file. See what QRGate can do or calculate the price.
