Occupational health

Choosing a sickness absence system

What a system for sickness absence and rehabilitation must handle: reporting, time limits, patterns, access to health data and what notices may contain.

By PortwayPublished 9 min read

sickness absence, rehabilitation system, sick and recovery, procurement

In this article
  1. Start with who will use it
  2. Criterion 1: reporting that is quick and correct
  3. Criterion 2: tracking the time limits
  4. Criterion 3: patterns in short absences
  5. Criterion 4: access and health data
  6. Criterion 5: what the notices contain
  7. Criterion 6: what the system does not do
  8. Checklist before you decide
  9. How we do it in Portway
  10. Sources
  11. Frequently asked questions

Short answer: A good sickness absence system does three things well: it makes reporting easy, it tracks the time limits so nobody has to remember them, and it shows the right information to the right person and nothing more. Everything else is a bonus. So evaluate the system on how it handles day 15 and day 30, how it catches repeated short absences and what an e-mail to an administrator actually says. Also ask what the system does not do, so that what belongs somewhere else has a place.

This article is for two readers: employers choosing a tool, and occupational health and other care providers who offer sick and recovery reporting as a service to their client companies. The criteria are the same, but the provider also needs a system where each client company is kept apart from the others. The time limits below are Swedish.

Start with who will use it

A sickness absence system has more users than you might think, and they want different things.

  • The employee wants to report quickly, preferably from a phone, without having to explain.
  • The employer, usually an administrator or line manager, wants to know that someone is away, for how long and what has to happen next.
  • Occupational health wants to see cases that need them in time, not once they have passed day 90.
  • Whoever is responsible for data protection wants health information to reach only those who need it.

A system built for one of them and adapted for the others shows quickly. Ask the vendor who the main user is and see whether the answer matches yours.

Criterion 1: reporting that is quick and correct

Reporting is the step most people use, and the one that most often goes wrong. Check:

  • Who can report? The employee, an administrator on someone's behalf, and the provider's staff. All three are needed in practice.
  • Which types exist? Own illness, care of a sick child and care of a relative are treated differently in payroll and follow-up. A field for "other" is needed too.
  • Extent. Part-time sick leave is common. The system should handle 25, 50, 75 or 100 percent and let the extent change during the case.
  • Guards against errors. Two open cases for the same person, or a sick notice starting in the future, should not be possible.
  • Recovery notice. Who can close a case? If only an administrator can, cases are left open.

Criterion 2: tracking the time limits

This is the reason to have a system at all. The time limits are fixed. The employer must report to Försäkringskassan (the Social Insurance Agency) on day 15, and by day 30 there must be a plan for return to work if the absence is expected to last at least 60 days (Försäkringskassan, in Swedish, retrieved 20 October 2026). After that, Försäkringskassan's assessment of work capacity widens after day 90 and day 180 (Social Insurance Code, chapter 27, sections 46 to 49, in Swedish).

Questions to ask:

  • Are tasks created automatically when a case reaches a given day, or does someone have to add them?
  • Does each task have a due date, and what happens when it passes?
  • Is the phase visible in the case, so everyone sees whether it is day 12 or day 95?
  • Are days counted from the first sick day even if the notice was made afterwards?

Ask the vendor to show a case that has passed day 30 with nothing done. It says more than a demo of the normal case.

Criterion 3: patterns in short absences

Long sick leave shows by itself. Repeated short absence does not, because each period is short and over before anyone reacts. Yet that is often where early action helps most.

Ask how the system detects patterns. A simple rule that can be explained is often enough, for example a number of short periods within twelve months. A rule nobody can explain breeds mistrust, and a rule that fires too often stops being read. Also check what happens when the rule fires: is a task created, and who sees it?

Criterion 4: access and health data

Information about sickness absence is information about health, and it belongs to the special categories of personal data in Article 9 of the GDPR (GDPR, retrieved 20 October 2026). That sets requirements on who sees what.

  • Scoping per organisation and department. An administrator in one department should not see another department's cases unless that is intended.
  • The employee's own view. Employees should see their own cases and nothing else.
  • The provider's staff. Not everyone at the clinic needs to read sickness cases. Ask whether read access can be controlled per person.
  • Log. Who read what, and when? The log should exist without anyone having to ask for it.

For a provider offering the service to several client companies there is one more thing: a client company must never see another client company's cases. Ask the vendor to show how it is built, not just to assure you.

Criterion 5: what the notices contain

An e-mail is hard to take back. It is forwarded, stays in inboxes and is read on shared screens. A system that sends "Anna Andersson is on 50 percent sick leave, cause: ..." has moved health information to a place nobody controls.

Ask the vendor exactly what each notice says, and ask to see one. Good notices say that something has happened and where to read more, not the details. Extent, cause and diagnosis belong behind a login.

Criterion 6: what the system does not do

No system does everything, and it is better to know where the line is before rollout than after. Typical boundaries to ask about:

  • Is the return-to-work plan stored in the system, or written elsewhere?
  • Are medical certificates and other documents handled?
  • Is the report to Försäkringskassan sent from the system, or made in Försäkringskassan's own service?
  • Is there data for payroll, or is the absence registered there separately?
  • Are there statistics and exports, and if so which?

None of the answers is wrong in itself. What matters is that each step has a place and an owner.

Checklist before you decide

  • Employee, administrator and provider can all report
  • Type and extent can be set and changed
  • Tasks are created automatically on fixed days, with due dates
  • Repeated short absence is caught by a rule that can be explained
  • Read access to health data is controlled per role and per person, and reads are logged
  • Notices contain no extent, cause or diagnosis
  • It is clear what the system does not do and where that is handled instead

How we do it in Portway

Sjuk & Frisk (sick and recovery reporting) in Portway is built for care providers who offer sick and recovery reporting to their client companies. The employee reports their own absence, or the client company's administrator or your staff report it for them. The types are sick, care of a sick child, care of a relative and other, with an extent of 25, 50, 75 or 100 percent that can be changed. A second open case for the same person and a start date in the future are blocked.

Portway creates follow-ups automatically on days 2, 14, 30, 60, 90 and 180, and the case changes phase on days 15, 91, 181 and 365. Once a week Portway looks for repeated short absence: if a person has five or more absences in twelve months, at least five of them lasting three days or less, Portway creates a follow-up in their active case. You see notifications in Portway and the client company's administrator gets an e-mail. Extent, cause and diagnosis are never in the notice. An administrator on your side can switch off read access to health data for an individual colleague, and every read is logged.

What Portway does not do: the return-to-work plan, medical certificates and the report to Försäkringskassan are handled outside Portway, and there is no payroll export or sickness absence statistics. We go through rehabilitation step by step, with a template for the plan, in return to work step by step.

If you want to see Sjuk & Frisk with your own client companies, you can book a walkthrough.

Sources

Frequently asked questions

What is the difference between a sickness absence system and a rehabilitation system?

The line is blurred. A sickness absence system takes notices and tracks time limits, while a rehabilitation system also handles plans, meetings and documents. Ask the vendor which parts the system actually has.

Do small employers need a system?

Not necessarily. With few employees a routine and a calendar are often enough. A system becomes worth it when nobody has an overview of which cases are approaching day 30.

May an administrator see why someone is sick?

The employer needs to know that someone is away, for how long and to what extent, not the diagnosis. A system should not ask for a diagnosis in the notice.

Can the report to Försäkringskassan be made in the system?

It depends on the system, so ask the vendor. In Portway it is made outside the system.

What should a care provider look at in particular?

That each client company is kept apart from the others, that read access to health data can be controlled per staff member, and that notices to client companies contain no health information.

See Portway in your everyday work.

We show Portway with what you do today, so you can see what would take care of itself at your place.