Cookie Settings

    We use cookies to understand how visitors use Triagen — so we can improve the site and show you relevant updates. Your data stays in the EU and is never sold to third parties.

    Learn More
    Triagen LogoTriagen

    Insight into absence

    Getting insight into the causes of sickness absence

    Sickness absence is rarely caused by one factor. It's usually a combination of physical complaints, mental strain, working conditions and personal context — a mix that's easy to miss in a rushed intake. Insight into absence causes means you already know what's really going on before the first conversation with the company physician, so guidance becomes more targeted, faster and more human.

    The numbers

    Why this is urgent for HR and occupational health services.

    #1

    Psychosocial workload (PSA) is, according to TNO/NEA, the most reported work-related cause of absence — exactly the kind of signal that's easily missed in a standard intake.

    TNO · National Survey on Working Conditions (NEA)

    ~5.5%

    Average sickness absence rate in the Netherlands — historically high and rising in labour-intensive sectors. Without insight into causes, you steer after the fact, not in advance.

    CBS · Quarterly sickness absence figures

    Weeks

    OVAL reports that wait times for the first consultation with a company physician run into several weeks in parts of the market — while the right signals are often already present in the first 72 hours.

    OVAL · Sector report on occupational health services

    Figures are indicative; consult the most recent publication from each source for exact percentages.

    Why insight falls short

    Four reasons insight doesn't emerge on its own today.

    Not because people aren't committed. Not because the company physician doesn't know what they're doing. But because the system around the first 72 hours isn't set up for it.

    1. 01

      Intake information is fragmented

      A sick report comes in through HR, phone, email or a portal. The case manager has to open three systems to get a complete picture. What ends up in the file depends on who handled the report and how much time they had. A pile of loose notes never becomes a pattern on its own.

    2. 02

      Not enough time for depth in the first 72 hours

      On a Monday morning, weekend sick reports pile up. Assistants filter urgent cases through rushed phone calls. Deeper context — workload, conflict, caregiving, sleep — rarely comes up. By the time the company physician speaks with the employee, there's more guessing than knowing.

    3. 03

      Subjectivity and unconscious bias in the questioning

      Whoever runs the intake influences which questions get asked. Familiar complaints naturally get more attention than complex or hard-to-explain ones. A calm employee is assessed differently than someone who calls upset — while the underlying cause may be the opposite. Inconsistent questioning produces inconsistent data, and inconsistent data shows no patterns.

    4. 04

      The case management system records but doesn't analyse

      Existing occupational health software is good at administration: files, deadlines, reporting. But early signal detection — which departments, which roles, which shifts? — is rarely at the core of those systems. As a result, insight into causes only emerges after the fact, at individual level, and rarely at organisational level.

    How to get it

    Three shifts that make insight structural.

    Insight into absence causes isn't a separate report or dashboard. It's a change in how the first 72 hours are organised — three shifts, in order.

    FragmentedStructured

    One intake flow for every sick report

    Replace the patchwork of phone calls, emails and forms with one structured intake every employee goes through. Adaptive, so the right questions get asked based on previous answers. The result: every file that lands on the company physician's desk has the same depth and structure — regardless of who received the report.

    ReactiveEarly triage

    Signals visible in days, not weeks

    When the first substantive questioning happens within 24 to 72 hours of the sick report, signals — work stress, caregiving, sleep, conflict — surface early. The company physician opens the conversation with context. The case manager can prioritise meaningfully. No weeks of uncertainty for the employee; no surprises in week six.

    Individual filesOrganisational patterns

    From isolated signals to visible trends

    When every intake has the same structure, aggregate-level patterns emerge that stayed invisible at the individual level: which departments report PSA-related absence more often, which roles, which shifts, which age groups. HR and leadership gain insight into causes — not as anecdote, but as data — and can build policy on the real bottlenecks.

    These three shifts are exactly what AI triage for occupational health.

    Frequently asked questions

    What HR teams and occupational health services often ask.

    Isn't this what a company physician and case manager already do?

    What the company physician and case manager do remains essential — no technology replaces medical assessment or human guidance. What changes is what's ready before the first conversation. Today, professionals spend a large share of their time gathering and organising information. A structured, early intake shifts that time toward what only humans can do: judge, guide, decide.

    How many employees or reports are needed to see patterns?

    At the individual level, every intake delivers value immediately — a structured file before the first conversation. At the organisational level, first patterns typically emerge from several hundred structured intakes per year, depending on the spread across departments and roles. For medium-to-large employers, that is usually reached within a few months.

    How does this fit with GDPR and medical confidentiality?

    Health data is special category personal data under the GDPR and is covered by medical confidentiality (WGBO and Wet BIG). Medical information is only for the company physician; the employer sees only what is necessary for guidance and reintegration. Pattern and trend data at organisational level is delivered anonymised and aggregated, so leadership can steer without traceable individual information.

    Does this replace our case management system?

    No. A structured triage layer works in front of and alongside your case management system — not on top of it. Existing occupational health software like Otherside, Visma Verzuim (formerly VerzuimSignaal and Dotweb) or AFAS Verzuim remains the place for the full absence file, plan of action, Gatekeeper deadlines and reporting. The triage layer delivers structured intake files into those systems.

    How do you start without adding to the team's workload?

    The first step is usually not to disrupt existing processes, but to add one calm channel alongside them where new sick reports flow through. For the employee little changes (a conversation instead of a form); for the team a lot changes (a structured file instead of fragmented information). Once it works, it becomes the new default.

    How do you actually measure 'insight into absence causes'?

    At the individual level: how much context the company physician has before the first conversation, and how often they still need to ask basic information in the first minutes. At the organisational level: what percentage of files show a clear-cut cause versus a complex mix, and which patterns shift quarter-on-quarter. Both questions become measurable once intake is structured.

    Further reading? What is AI triage for occupational health? · Full FAQ.

    Start with real insight in the first 72 hours

    In a 30-minute conversation we'll show how a structured triage layer fits your occupational health service or internal team — without disrupting the existing system landscape.