Holidays, shifts and attendance still on WhatsApp: the minimum HR app that removes the chaos (without enterprise software)

The “Shifts” WhatsApp group: where holidays get lost

Open your company’s “Shifts” WhatsApp group and scroll. There’s someone asking for leave (“can I stay home next Thursday?”), someone proposing a swap (“can anyone cover me on Saturday?”), someone communicating they’re sick, someone sending a heart as approval. In between, photos of a printed Excel sheet with the shifts, messages three weeks old, and at least one argument about who was supposed to be there and wasn’t. It’s the way a mountain of SMEs manage holidays, shifts and attendance: by chat.

It works, until it doesn’t. Then comes the day when two people have “approved leave” for the same day and there’s nobody in the department. The approval message got lost in the scroll, the owner keeps the remaining days count in their head (and it never matches the payslip), and at month-end the payroll office pieces together attendance and absence from a puzzle of messages. The chaos is invisible until it costs you: unforeseen overtime, an uncovered shift, an argument between colleagues, a dispute over holiday days.

This article is for those managing people in an SME — a shop, a department, a venue, a workshop, a studio — who feel the WhatsApp group can’t hold up anymore, but who (rightly) don’t want a multinational HR software with talent management, OKRs and an internal social network inside. Let’s see what the minimum HR app that is really needed is, what you don’t need, why it has to live on a phone, and how to reach a go-live in a month without turning a simple thing into an endless project.

Shift chaos costs (and you don’t see it on an invoice)

Before talking about solutions, let’s focus on the cost, because “the WhatsApp group is free” is an illusion. The chaos on holidays and shifts costs you on three fronts, all invisible in accounting.

Unforeseen overtime. A shift uncovered at the last minute is covered by calling someone who wasn’t supposed to work — often on overtime, often at a premium rate. Every poorly managed hole is money going out, and they are holes that with a minimum of visibility would have been avoided.
The owner’s (or manager’s) time. Whoever manages shifts by hand spends hours on it: fitting requests together, redoing the spreadsheet when someone changes, keeping the accounts of remaining days. It’s the time of a person paid to do something else, burned in a weekly puzzle.
Arguments and mistrust. “My holiday was approved.” “I’ve done more Saturdays than him.” “It’s not my turn.” When the rules aren’t written down and the accounts aren’t transparent, every shift becomes a potential perceived injustice. And the climate in a small team is an asset you don’t want to burn.

Added to these is the risk of the wrong payslip: if you reconstruct attendance and absence from WhatsApp, sooner or later a data point gets missed, and a wrong payslip is a serious problem — for the employee and for you. Shift chaos isn’t an organisational annoyance: it’s a recurring cost plus a ticking bomb on payroll.

One way to make the cost concrete: think of how much unforeseen overtime you do in a year to cover holes that with a little visibility you would have avoided, and the time you or the manager spend every week fitting shifts together. Even just a couple of hours a week of management plus a few avoidable overtimes a month, over a year, are easily thousands of euros and dozens of hours — spent on a job an app does almost by itself. The WhatsApp group is free as a tool and expensive as a method.

What is really needed: the minimum product

Here is the good news: to remove 90% of this chaos you don’t need complete HR software. You need a minimum app that does a few things, well, from the phone. Four, to be precise.

The request. The employee asks for holiday or leave from the app, in ten seconds: which day, how many hours, with a note if needed. No message in the group that gets lost: a tracked request.
The approval. The manager receives the request, sees if it creates problems (overlaps, uncovered department) and approves or rejects with a tap. The decision is recorded, with a date: there’s no more “but you said yes”.
The shared calendar. Who is at home, who is there, who is on shift: an at-a-glance view of who is there when. So the manager plans knowing, and the employee sees their own calendar without asking.
The balance. The remaining holiday and leave days, updating themselves at every approved request. No more mental counts that don’t add up: everyone sees how much they have left, and the owner too.

This is the core. Request → approval → calendar → balance, on a phone. On top of this you can add the actual shifts — who works when, with tracked swaps between colleagues (Anna asks Luca to cover her Saturday, Luca accepts, the manager sees and confirms, without spoken agreements that nobody remembers later) — and attendance clocking, if you need it. But the core that removes the chaos is this, and it is surprisingly small. It is the same principle of internal apps made of a few screens that remove friction: not “everything HR could do”, but the four things you use every week.

What you DO NOT need (and they sell you anyway)

Equally important is knowing what to leave out, because the HR software market is full of features an SME doesn’t need and which, in fact, sink it. If they propose a platform with all this inside, for your case it’s dead weight:

Talent management, performance reviews, career plans. Stuff for large organisations with dedicated HR departments. In an SME you do them (rightly) by talking to people, not with software.
OKRs and goal management. Another world, another need. It has nothing to do with covering Saturday shifts.
Internal social network, notice boards, “engagement”. You already have a way to communicate (even too much: the WhatsApp group). You don’t need a company Facebook.
Structured onboarding, training, org chart. Useful maybe one day, not today, and not for solving holidays and shifts.

Every extra feature you don’t use is a cost (in the license), a complication (in the interface) and one more reason for people not to adopt the tool. A “complete” HR software dropped onto an SME of fifteen people is like the fifty screens of an ERP nobody opens: it does everything except the simple thing you needed, and it does that badly too because it’s buried under the rest. The minimum product is not a scaled-down version of the big one: it is the right tool for your size.

It has to live on a phone (for those who don’t sit at a desk)

There is a detail that decides success or failure: the person who must use this app often is not in front of a computer. They are at the counter, in production, in the kitchen, on the shop floor, in the store. If to ask for a holiday they have to turn on a PC, log into an ERP, look for the right screen, they will never do it: they will go back to writing in the WhatsApp group, which is in the phone they already have in their pocket.

So the app must be first and foremost mobile and extremely simple: you open, you ask, you approve, you look at the calendar — all from the phone, with big buttons and zero learning curve. The person in production must be able to ask for leave on their coffee break, in thirty seconds. The manager must be able to approve while walking. If the app is more inconvenient than a WhatsApp message, it has already lost: the yardstick isn’t “a company HR software”, it’s the chat they use today, and it’s extremely fast. Your app must be just as immediate, but orderly.

The rules: who approves, deadlines, overlaps

The piece that turns a shared calendar into a real tool are the rules, and they must be decided before building anything. They are few questions, but the answers make the difference between an app that helps and one that generates more arguments:

Who approves whom? The department head, the owner, both cascading? In a small company one is often enough; in a slightly larger one levels are needed. It has to be decided.
How much notice? Holidays are requested X days in advance, short leave with Y hours? Clear rules remove discretion and perceived injustices.
How many people can be missing together? The golden rule of shifts: the app must warn or block when a request would leave the department uncovered or below a minimum threshold. It is the feature that, alone, prevents the disaster of “two approved on the same day”.
How are swaps managed? If two colleagues swap a shift, who has to approve? The app must make the swap simple but tracked, not a spoken agreement nobody remembers later.

These rules aren’t bureaucracy: they are what makes the system fair and automatic. When they are written into the app, decisions no longer depend on mood or who asked first in the group: they depend on rules equal for everyone. And it’s also what protects the manager, who stops having to say “no” verbally and it becomes the app flagging that that day is full.

The fairness side: written rules = fewer resentments

There is a benefit to this type of app that you see little of at the beginning and matters a lot: fairness. In a small team, most resentments about shifts arise not from the rules themselves, but from the fact that they are implicit and seem applied “by favoritism”. “Why does he always have Saturday off?” “Why were my August holidays denied and his approved?” As long as the rule lives in the owner’s head, every decision seems arbitrary, even when it isn’t.

When the rules are written into the app and the accounts are transparent — everyone sees their own balance, the calendar is shared, approval follows criteria equal for everyone — resentment drops, because perceived injustice drops. It isn’t that the app is magical: it’s that making rules explicit and equal for everyone removes the suspicion of favoritism. It is one of those cases where the tool, besides saving time, improves the climate — and in a small team the climate is worth as much as the money.

Data for payroll: an export, not another silo

Here is the mistake that renders half of the projects useless: building an app for holidays and attendance that becomes another data silo disconnected from the payslip. If then the payroll office (internal or the employment consultant) still has to copy attendance and absence by hand from the app to the payroll software, you haven’t removed work: you’ve moved it, and added an extra system to keep aligned.

The real value arrives when the app produces, at month-end, exactly what is needed for payroll: a summary of attendance, holidays, leave and overtime, in the format your consultant or your payroll software can import. Not another place to look, but the clean source closing the circle. It is the same principle that applies to every internal app: if the data doesn’t come out and connect, you’ve only moved the copy-paste. The goal isn’t “having a holiday app”: it’s that holidays, leave and attendance reach the payslip correct, without anyone re-transcribing them.

Attendance: clocking with the phone, without badges and turnstiles

On top of the holiday/shift core, many SMEs also want attendance clocking — entry and exit — for payroll or to understand the real hours. Here too the minimum version is almost always the best: clocking from the phone, with a tap, instead of buying badges, turnstiles and expensive terminals. The employee arrives, opens the app, clocks in; at month-end the hours are already there, ready for payroll.

Pay attention to two things. The first is trust: clocking from the phone must be introduced as a tool of correctness (the right hours, for everyone), not as police control, or it generates resistance. The second is location: if you need to know someone actually clocked in on site, it can be done — sensibly and transparently — but for many SMEs trust plus a light check is enough. You don’t need a technological fortress: you need a simple and honest way to record hours, connected to the same source as holidays and shifts, so payroll builds itself.

When the ERP module is enough (and you don’t need an app)

Honesty first: you don’t always need to build something. Many ERPs and payroll software already have a module for holidays and attendance. If you have it and — crucially — if people actually use it from their phones, you might not need anything else. The right question isn’t “do I have a module?”, it’s “do they use it?”.

The problem is that those modules are often designed for the HR office, not for the employee on the shop floor: heavy, PC-based, with complicated screens. Result: they exist, but nobody opens them, and everyone goes back to WhatsApp. In that case the module “is there” but it solves nothing, and that’s where a minimum, mobile app makes the difference — often hooked right into the payroll software you already have, so as not to create the silo we talked about.

The rule of thumb: if your ERP module is usable from the phone and people use it, keep it and don’t let anyone sell you anything. If you “have it” but everyone manages shifts on WhatsApp, the module doesn’t count: the problem is the mobile UX, and a minimum app solves it.

A typical case: from Excel sheet to covered Saturday

A typical profile, architectural, no names. A venue with about fifteen people between front of house and kitchen, shifts managed by the owner on an Excel sheet and communicated on the WhatsApp group. Holidays asked verbally or in chat, balances kept by memory. Every month the payroll office (the external consultant) received a laboriously reconstructed summary, with a few errors. And a couple of times a year, an uncovered Saturday because two people had called in sick at the last minute and nobody had the overview.

What was done. First the rules were written: who approves, how much notice for holidays, minimum number of people per shift in FOH and kitchen, how balances are counted. Then a minimum, mobile app: request, approval with overlap warning, shared calendar, automatic balance, and monthly export for the consultant.

After: holidays no longer get lost (tracked and approved), balances match because the app counts them, and the owner stopped spending hours fitting shifts together. The uncovered Saturday is rarer, because the app warns when a request would leave the shift below threshold, and the summary for payroll comes out with a click, correct. With the usual note: the real value wasn’t “the app”, it was putting in writing rules that lived in the owner’s head — and which, made explicit, also removed resentments about “why him yes and me no”.

Go-live in a month (if the rules are clear)

Good news on timings: a minimum HR app is one of the quickest projects to set up, on one condition — that the rules are clear. The time isn’t eaten up by technology (request, approval, calendar, balance are simple things): it is eaten up by undecided rules. If before starting you sit down and establish who approves, how much notice, how many simultaneous absences are allowed, how balances are counted, then the app is built and released in a few weeks, with a month of running-in.

If instead you start without having decided the rules, the project drags on, because every edge case becomes a meeting. So the first job is not technical: it is putting into writing the holiday and shift rules that today live in the owner’s head. That document — a few lines — is half the project, and it is also the opportunity to finally make explicit rules that today generate resentments precisely because they are implicit.

There is also one more reason why this project is fast: it is low risk. It doesn’t touch production, it doesn’t block sales if something needs adjusting, and it can run alongside the old method for a few weeks — the WhatsApp group stays until the app has entered into habits. No big bang, no operational risk: you turn it on, try it, adjust it, and the old chaos turns itself off when the app is more convenient.

It’s not control, it’s correctness

It’s worth addressing head-on, because it’s the fear holding many back: “won’t an app for attendance and shifts make people feel controlled?”. It depends entirely on how you present it and how it is made. If it arrives as “now we’re watching you”, it generates resistance and they bypass it. If it arrives as “no more lost holidays, no more accounts that don’t add up, no more Saturdays covered always by the same people”, it becomes a tool that protects them too — because rules equal for everyone and transparent accounts protect the employee as much as the owner.

The difference between a hated HR app and a gladly used one, in an SME, is almost always this: if it removes a common annoyance (lost holidays, unfair shifts) it is adopted; if it adds surveillance without giving anything in return, it is sabotaged. Present it for what it is: a fairer and simpler way to manage a thing that today is chaos for everyone.

Where to start

If we decided to start, the first step is not choosing software: it is writing the rules that are in your head today. Sit down for half an hour and put on paper: who approves holidays and leave; how much notice is needed; how many people can be missing together by department or shift; how remaining days are counted (calendar year? monthly accrual?); how shift swaps are managed. This document is half the project, and you can do it yourself, for free.

The second step is looking at the last few months: how many times was a shift left uncovered? How many disputes over balances or holidays? How much time do you spend fitting shifts together every week? Those numbers tell you if the problem is real and how much it weighs — and they are the baseline to understand, afterwards, if the app worked.

A note, from an owner and not a lawyer: holidays, attendance and absence are personnel data, and must be treated with a minimum of care. You don’t need a treatise, you need three common-sense things. One: the right access — every employee sees their own data and the shared calendar, not the personal info of others (a sickness absence is not everyone’s business). Two: the data is under your control, not scattered in a chat that anyone can screenshot. Three: if you use location for clocking, state it clearly and use it only for the declared purpose.

Note the paradox: a well-made app, with role permissions, is actually much more respectful of privacy than the WhatsApp group, where today everyone’s absences are read by everyone.

It’s for you if / it’s not for you if

It’s for you if: you manage holidays, shifts and leave on WhatsApp, spreadsheets and memory; you’ve happened to have uncovered departments or double approved absences; balance counts never match the payslip; you have people who don’t sit at a desk and will never use a PC ERP.

It’s not for you if: you are two or three and organize verbally without problems (then it’s fine as it is); you already have a module that people actually use from the phone; you are looking for a complete HR system with talent, performance and training — that is another product, for another company size.

Frequently asked questions

Isn’t it enough to tidy up the WhatsApp group? No, because WhatsApp doesn’t track, doesn’t count and has no rules. Approvals get lost, you keep balances in your memory, nobody sees overlaps until they happen. You can be extremely tidy: it remains the wrong tool for the job, because it doesn’t preserve state.

How much does it cost compared to a subscription HR software? Complete HR software has per-user fees that, on features you don’t use, become expensive and scale up. A minimum and targeted app costs less to run precisely because it does little, and the expense is compared with the unforeseen overtime and the manager’s time you burn today. Often it pays for itself quickly just in better managed shifts.

Does it connect to the payslip? It must. The point isn’t having an extra app, it’s that attendance, holidays and leave arrive in the payslip correct. The app must produce the export that your employment consultant or payroll software can import, without re-transcription.

Will people use it or go back to WhatsApp? They will use it if it’s more convenient than WhatsApp to make the request and clearer to see the calendar and balance. That’s why it must be mobile, extremely simple and fast. If it’s more inconvenient than chat, they go back to chat: the yardstick isn’t “serious software”, it’s the immediacy of the message.

How long to get started? A few weeks plus a month of running-in, if the rules (who approves, notices, overlaps, counts) are decided beforehand. Undecided rules eat the time, not the technology.

What about actual shifts, not just holidays? The core (request, approval, calendar, balance) naturally extends to shifts: who works when, swaps between colleagues, warnings on uncovered departments. You often start from holidays and leave (simpler) and add shifts when the first piece is run in. Better a piece that works than everything half-done.

Does it work even if not everyone has a smartphone? Yes: whoever doesn’t have or doesn’t want to use a smartphone can be managed by the manager (who enters it for them) or with a shared workstation. But most people already have their phone in their pocket, and that’s where the app lives.

Is it also needed for companies with complicated shifts and contracts? The more complicated the rules, the more an app is needed — provided they are written well at the beginning. Night shifts, rotations, minimums per department, different contracts: all manageable, if the rules are explicit. The complication is not a reason to stay on WhatsApp, it’s one more reason to leave it.

Does the data stay mine? Yes. Master data, balances, history of holidays and attendance stay yours, no lock-in. They are delicate personnel data: they must stay under your control, with the right access.

In one line

If holidays, shifts and attendance still live on WhatsApp, you don’t need a multinational HR software: you need a minimum app that does four things from the phone — request, approval, shared calendar, balance — with written rules (who approves, notices, how many absences together) and a clean export for the payslip. It removes unforeseen overtime, double approvals and arguments, without adding another data silo.

If you want to understand what the minimum your company needs is and how to hook it to the payslip, look at the projects I’ve built or drop me a couple of lines: we start from your rules and your people, not from catalogue HR software.