In teamspace, staff report sick themselves, the team sees the absence in the calendar, and the sick day stays overtime-neutral. Three sickness types are kept separately, sick reports and absences evaluated separately. Who may see a sick report is governed by the permission.
Overview
A sick report rarely comes at the right time. But how a company handles it can be ordered: who reports sick, who sees the absence, how the day counts on the account and what can be evaluated in the end.
teamspace keeps sick reports, absences and their evaluation in one place, in the same system as leave and working time. So an unplannable matter becomes a calm, traceable process, without extra effort for staff.
Starting point
Day to day
The most common case needs no form and no call to HR. Staff report sick directly in teamspace, via the overview of working time tracking.
So planning stays in motion, instead of improvising on the phone with last-minute cover.
What matters
A sick report is more than a calendar entry. It must be cleanly separated, fairly evaluated and reliably analysed.
Types
Evaluation
Analytics
Evaluation
Whoever is sick should not be worse off on the time account than someone who worked. teamspace therefore evaluates a sick day overtime-neutral, instead of booking it as missing hours.
The same applies to leave and public holidays. Whoever is absent because they may be absent accumulates no minus.
Data protection
Sickness data is especially sensitive. In teamspace each role sees exactly as much as it may, from the mere absence to the record with certificate.
sees
sees
sees
sees
Who sees what is set by the permissions. Past days are visible only to authorised roles.
First call
In 20 minutes we walk through your sickness types, the permissions and the handover to the payroll office on an example employee. At the end you see where a report becomes fair accounts and reliable figures.
“Our staff appreciate how simple the system is.”
Two metrics
In HR controlling, two questions are often mixed up, although they measure different things. teamspace keeps them separate so the figures stay meaningful.
Anyone with half days and part time in the house notices the difference immediately: a sick day is not automatically a full lost day.
Analytics
Leadership needs a picture of absences without individual sickness data becoming widely accessible. teamspace therefore evaluates in aggregate.
This creates a factual basis for conversations and planning, without reporting becoming disclosure.
Value
Clear sickness management relieves more than just HR. Three groups notice the difference in everyday work.
From report to analysis
Staff report sick in the overview, with date and type. Whoever has the right reports colleagues via the plus.
Colleagues and managers see the absence, the team calendar is updated, a deputy can be assigned.
The doctor's note comes as a photo, PDF or link into the sickness record, where the permission provides for it.
The sick day fills the time account up to the daily target. Neither a minus nor a plus arises.
Sick reports and absences are counted separately, the sick rate per team is ready in aggregate at the push of a button.
Use cases
Sickness is one of several absences. These functions of the same system mesh without double entry.
Master data, contracts, documents and the sickness record on one person.
Learn moreAttendance and project time, into which sick days flow overtime-neutral.
Learn moreRequests, approval and deputy, with the same absence logic.
Learn moreOvertime account with thresholds and three ways to reduce it.
Learn moreAbsences and time off as a data export for the payroll office.
Learn moreSickness and leave feed directly into the available capacity.
Learn moreIn context
A sick report does not stand alone. It changes the time account, the available capacity and the data that goes to the payroll office. Because all of this sits in the same system, transferring lists falls away.
The lost hours and absences are ready as a data export for payroll preparation, separated by sickness type. Capacity planning routes the missing person out of utilisation, and in working time tracking the sick day stays overtime-neutral. teamspace does not take over a payroll run of its own; that happens with the tax advisor or in the payroll office.
Scope
Part of the HR software
Sick report, leave, working time and overtime sit in the same system. A sick report fills the time account, spares utilisation and flows into payroll preparation, without anyone retyping lists. How the whole personnel module connects on one timeline is shown in the HR software overview.
To the HR softwareWhat it is about
Sickness management is the structured recording, evaluation and analysis of sick reports and absences in HR. It ranges from the individual sick report through the effect on the time account and planning to the aggregated sick rate. Because health data counts among the special categories of personal data under Art. 9 GDPR, handling it is especially protected by law.
In teamspace, sickness management forms not as a separate program but from the data already maintained in HR. The sick report runs via the time-tracking overview, the certificate sits in the record on the employee, and the permission decides who sees which data. Anyone already running working time and leave in teamspace manages sickness in the same place, without a media break and without double entry.
The sickness data sits in an ISO 27001 certified data centre in Frankfurt am Main, processing takes place exclusively within the EU. The contracting party is 5 POINT AG, a self-financed German public company from Darmstadt that has developed teamspace since 1999.
Related modules
Anyone who runs sickness and absences almost always touches time, the project and the invoice too. Here are the shortest routes there.
Attendance and project time on the same employee. Sick days fill the hours account up to the daily target.
Sickness and leave feed directly into the available capacity. Utilisation routes the missing person out.
From approved project times comes the fee invoice, with the hourly rate valid on the booking day from the HR timeline.
Sickness management brings sick reports, absences and their effects on accounts, planning and payroll together in one place. Staff report sick themselves, the team sees the absence in the calendar, the sick day stays overtime-neutral, and the sick rate is ready in aggregate for evaluation. Instead of sick reports being spread across sticky notes, mails and an Excel list, they form in the same system as working time, leave and overtime, protected on a need-to-know basis.
We show the sick report, visibility by permission and the sick rate on a real workflow. You see how a report becomes fair accounts and reliable figures.
