Occupational health

Sick leave process, day by day

Sick leave milestones day by day, from the qualifying day to day 180, and what a sick and well-reporting flow must do at each step.

By PortwayPublished Updated 10 min read

sick leave, absence management, occupational health, process

In this article
  1. The timeline the process should follow
  2. What the flow has to do at each step
  3. Privacy: what the employer gets to know
  4. Why this is business critical for the provider
  5. Common mistakes
  6. How we do it in Portway
  7. Sources
  8. Frequently asked questions

Short answer: A sick and recovery process should follow the dates that already govern sick leave: qualifying deduction and sick pay from the employer on days 1 to 14, a medical certificate that may be demanded from day 8, notification to the Swedish Social Insurance Agency on day 15, and the employer's plan for return to work by day 30 when the absence is expected to last at least 60 days. The system's job is to remind about the right thing on the right day, and to do it without letting the employer see why someone is ill.

Sick and recovery reporting is the most common point of contact between a client company and its occupational health provider. Yet the process is often built around phone and e-mail, which makes it impossible to follow up and easy to drop. This walkthrough starts from the actual milestones of Swedish sick leave, because they are what decides what the flow has to handle.

The timeline the process should follow

DayWhat happensWho is responsible
1Sick report. The qualifying deduction is made, 20% of an average week's sick pay, once per sick periodEmployer
1 to 14Sick pay, 80% of salaryEmployer
8A medical certificate may be demandedEmployee provides, employer requests
15Notification to the Social Insurance Agency, at the latest day 21. Sickness benefit takes overEmployer
30A plan for return to work must exist, if the absence is expected to last at least 60 daysEmployer
90 / 180 / 365The rehabilitation chain's assessments of work capacitySocial Insurance Agency

Two things are worth noting, because they often go wrong in system support.

Day 30 is the plan, not day 14. Day 14 is when the employer's sick pay period ends, a payroll event, not a rehabilitation event. The plan for return to work must be drawn up by day 30 at the latest and only when the absence is expected to last at least 60 days. There are exceptions: if the employee is expected to be back in full within 60 days no plan is needed, and if they cannot return at all because of their state of health, the position should be documented instead. The Social Insurance Agency (Försäkringskassan) can request the plan.

Day 8 is a right, not an automatic. The employer may demand a medical certificate from day 8, but does not have to. A system that sends out "certificate missing" as a mandatory demand to all customers creates irritation for those who have chosen another policy. Make it configurable per client company.

What the flow has to do at each step

The report

The employee reports digitally, around the clock, and the right people are notified directly: whoever handles absence at the employer and, when the agreement covers it, the occupational health provider. No phone chain, no forwarding by hand.

What matters is what the report should not contain. See the next section.

Monitoring

The dates to watch are few and known in advance, which makes them suited to automation: day 8 if the customer applies a certificate requirement, day 15 for notification to the Social Insurance Agency, day 30 for the plan. A reminder should go to whoever is actually responsible. The plan is the employer's obligation, not the occupational health provider's, and a reminder that lands with the wrong party does not get acted on.

Signals

Repeated short-term absence is an established sign that something needs following up, but where the line goes is a policy question for the client company, not a rule. Build the threshold as configurable and describe it as a signal, not a diagnosis. The same goes for unusually high absence in a unit: it says that someone should look closer, not what is wrong.

Recovery report and return

A recovery report closes the case, stops the monitoring and cancels reminders that would otherwise go out needlessly. If the absence has been long, a return conversation should be possible to book directly in the flow, linked to booking, instead of becoming an e-mail someone has to remember.

A case that is never closed is the most common junk in absence systems, and it is almost always a recovery report that was never registered.

Privacy: what the employer gets to know

This is the point where system support most often goes wrong, and the error is hard to fix afterwards.

The employer needs to know that an employee is absent, from which day, to what extent and when they are expected back. The employer does not need to know why. Diagnosis and medical information belong to health care, and the occupational health provider is in that part a care provider with the confidentiality and record rules that follow, the same boundary we go through in the ordering portal requirements.

In practice this means three things for the design:

  • The report form should not ask for the cause. A free-text field called "comment" becomes in practice a diagnosis field, because people write what they think is asked for.
  • The medical certificate should not reach the employer needlessly. Whoever handles the absence needs to know that a certificate exists, not its content.
  • Permissions should follow the organization. Whoever handles absence sees the employees they are responsible for, not the whole company. Sick-leave data is health data, and access should be logged.

A flow that leaks the cause is not only a privacy problem for the individual. It is a work environment problem, because employees who suspect that the manager gets to know too much stop using the system and start texting instead.

We go through the requirements in more detail in GDPR and security in occupational health, and describe our technical handling on the security page.

Why this is business critical for the provider

For the client company, sick leave is a cost that shows directly in the payroll run and indirectly in production. A provider that makes the handling understandable, who does what on which day, solves a problem HR has every week.

It is also a flow that creates recurring contact without costing clinical time, and that provides a basis for advice: an overall picture of absence per department and period is strong material when the contract comes up for renewal. In procurements, digital absence management weighs heavily, which we look at more closely in how clients choose providers.

Common mistakes

  • The process is built around e-mail. Then it cannot be followed up, and nobody can say where a case stands.
  • Reminders without a responsible recipient. A reminder about the day-30 plan that goes to the occupational health provider instead of the employer does not get done.
  • Free-text fields in the report. See above: it becomes a diagnosis field.
  • No recovery report. Without a close, monitoring continues and the statistics become unusable.
  • Dispatch without a trace. If you cannot show that the reminder went out, you do not know whether the automation works; we develop why in reducing administration.

How we do it in Portway

Sjuk & Frisk is its own module in the platform, switched on per client company. The employee reports themselves, or the client company's administrator or your staff report on their behalf. A case has a type (sick, care of a sick child, care of a relative, or other) and a degree (25, 50, 75 or 100 percent) that can be changed while the case runs. There is no field for the cause.

Portway adds follow-up actions to the case on day 2, 14, 30, 60, 90 and 180, and marks the phases at day 15, 91, 181 and 365. Once a week the system looks for one pattern, five or more absences within twelve months of which at least five lasted three days or less, and then adds a follow-up to the open case. It is a signal, not a verdict.

Notifications reach you as the provider in the app and the client company's administrator by e-mail. The notice never contains the degree, the cause or a diagnosis. Comments from your staff are internal by default, and on your side only colleagues with access to health data see the cases. A recovery report closes the case; the employee, the client company's administrator or your staff can do it.

What Portway does not do matters as much: the plan for return to work, medical certificates and the report to Försäkringskassan are handled outside the system. The day-30 action reminds you of the plan on the case, but the plan is written elsewhere.

If you want to see the flow, you can book a walkthrough.

Sources

The dates and responsibilities were checked against primary sources on 20 October 2026 (Swedish-language pages):

  • Försäkringskassan, Om din medarbetare blir sjuk (sick pay for at most 14 calendar days, medical certificate on day 8, report on day 15 and by day 21 at the latest, plan for return to work; page updated 28 July 2026).
  • Försäkringskassan, Att göra när en medarbetare är sjukskriven (the plan must be ready on day 30 if the sick leave is expected to exceed 60 days; coordination meeting; updated 28 July 2026).
  • Sick Pay Act (1991:1047), section 6 (sick pay 80 percent, qualifying deduction 20 percent of an average week's sick pay).
  • Social Insurance Code (2010:110), chapter 27, sections 46–49 (assessment of work capacity after 90, 180 and 365 days).

Frequently asked questions

When must a plan for return to work be ready?

By day 30 of the sick period at the latest, and only if the employee is expected to be on sick leave for at least 60 days. The responsibility is the employer's. If a full return is expected within 60 days no plan is needed; if the employee cannot return at all, that position should be documented instead.

From which day is a medical certificate required?

The employer has the right to request a medical certificate from day 8. It is a right, not an obligation, and some employers apply other rules; collective agreements and special reasons can affect it.

When must the employer notify the Social Insurance Agency?

On day 15, and at the latest day 21. From day 15 the Social Insurance Agency takes over with sickness benefit; on days 1 to 14 the employer pays sick pay.

How large is the qualifying deduction?

20 percent of an average week's sick pay. It is made once per sick period, not per sick day.

Can the manager see why an employee is on sick leave?

No. The employer has the right to know that the employee is absent and to what extent, but not the diagnosis. Medical information stays with the care provider, and the system should be built so that it cannot end up in the wrong place by mistake.

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.