Sick Leave Is a Process, Not a Request

At 07:40 someone posts in the team channel: "woke up feeling awful, taking today, will pick up the deploy tomorrow." Six people react with the heart emoji. Nothing else happens.

Three weeks later you are building the payroll file and that day does not exist anywhere except a channel you have to scroll.

Most small companies have a leave system and still handle sick days this way, because the leave system was built around a request that gets approved and sick leave is neither of those things. It is a fact being reported after it started. Everything downstream goes wrong if you model it as a booking.

Approval is the wrong verb

A manager cannot approve an illness. It happened. Sending a "pending" request to someone who will click Approve every single time adds a queue, a notification, and a delay, and buys you nothing — the person is already at home. Worse, it invites a manager to eventually not click, which is a conversation nobody drafted a policy for.

So sick leave should record itself the moment it is submitted. That part is easy and most tools get there.

The part they miss is that removing the approver also removes the only person who was being told.

We found this in our own product. An agent simulation last August walked five personas through a normal working day, and one of the findings was blunt: a manager is never told when a report's sick leave is auto-approved. No approver is asked, so no decision notification is ever addressed to anyone. The system of record knew. Nobody was told. That is a worse failure than a slow queue, because it looks like it is working.

The fix is a separate signal from the approval chain: somebody on your team will be out, sent whether the absence was approved by a human or by the policy. It carries dates and nothing else. Not the leave type, not the reason.

Nobody needs to know why

Health data is special-category data under article 9 of the GDPR, and "the team should know so they can send flowers" is not a lawful basis. In practice this is easier than it sounds, because the useful information and the sensitive information are different fields.

A manager planning next week needs: this person is out, these dates, not coming back until Thursday. A payroll file needs: this many days, under this absence code. Neither needs a diagnosis, and neither needs whatever the employee typed into the reason box at 07:40 while feeling terrible.

Doctor's notes are the sharp edge. They arrive as files, they contain more than you asked for, and once uploaded they sit in whatever folder the tool put them in. The rule worth enforcing in software rather than in a policy document: a note is visible to the person who uploaded it, to admins, and to whoever is actually on that request's approval chain. A manager two teams over who can see the absence must not be able to open the file. And it should not be deletable by an approver after the fact, only by an admin, so the record of what was submitted survives a disagreement about what was submitted.

The four-day gap

Here is the case that breaks most configurations. Someone is ill Monday and Tuesday, comes back Wednesday, and gets round to logging it on Thursday.

Every system with a notice period rejects that, because notice periods are built for holidays. Every system without one lets you file sick leave for last March, which is how a month gets quietly re-written after payroll ran.

You want a bounded window: past-dated sick leave accepted up to some number of days back, and refused after that. Long enough to cover the honest case of a person who was too unwell to open a laptop. Short enough that the payroll cutoff is a real line. Anything older than the window becomes an admin correction with a name attached, which is exactly what it should be.

While you are there, take the balance off. Sick leave with an annual allowance turns into a budget people spend down or hoard, and neither behaviour is one you want. Track it, count it, report on it, cap nothing.

The one conversation to keep

Automating the record does not automate the return. A short, unstructured conversation when someone comes back — how are you, is anything about the job making this worse, do you need the deadline moved — is the only part of absence management with any evidence behind it, and it is the part that gets skipped because it is the only part that requires a human to remember.

Note that this is not the same activity as scoring absence patterns. If you want the pattern view, the Bradford Factor is the standard instrument and that post covers where it earns its keep and where it turns into a stick. Keep the two apart. A return-to-work chat that is secretly a score review will be the last honest one you get.

Where SquadBear keeps this

The seeded Sick leave policy is already configured this way, and the values are worth reading as an argument: no annual accrual, so there is no balance to run out of; approval mode auto, so it records on submit with no approver step; notice period 0, because you cannot give notice of a fever; and a backdate window of 7 days, so Thursday's report of Monday's illness lands without ceremony while last March does not. No replacement required either — a person who is ill should not have to name their own cover before they can lie down.

Managers still find out. The team-absence notification fires on auto-approved leave the same as on approved leave, carrying ids and dates only, never the leave type. Attachments follow the rule above: requester, admins, and approvers of record on that request, at any step and whatever the request's status; a manager who is not on the chain sees the absence and never the file. And the payroll export drops reasons and attachments entirely — the file that goes to your accountant carries types and day counts, nothing else.

If you'd rather not open a report screen:

"Who on my team is out sick right now, and how many working days of sick leave has the team taken this quarter compared with last?"

The leave concepts guide explains untracked types and day counting; approvals covers who can see an attachment.

Start free, or poke at a workspace that already has a quarter of absence in it in the demo.