Home›Use cases›Incidents & special cases
◉ 3 examples from practice

Automating incidents and special cases
What happens when the standard route does not apply

An accident at work, a written warning, a return-to-work process: things that happen rarely but every time bring deadlines, reporting duties and documentation with them. Precisely because they are rare, nobody knows the process by heart.

Discuss your workflow Calculate your savings
60 min saved per incident estimated from comparable projects
85 minbefore, per incident
25 minafter
completedocumentation for the audit
The starting point

What incidents
cost in time today.

1

Reporting deadlines to the accident insurer and the authorities are watched by hand

2

The documentation happens in emails rather than in the file

3

People get forgotten: the works council, the safety officer, the manager

4

At an audit the complete record is missing

Programmes involved

These are the systems
tied to this area.

All already connected. If yours is missing, we build the integration at no extra cost, on average within three days.

Personio Sage SAP SuccessFactors HRworks Guidecom

Is your programme included?

Three examples

Simple, medium
and genuinely complex.

All of them examples from live operation. What gets built is whatever comes up in your work.

SimpleA few steps, ready straight away

Report an accident at work

TriggerA report from a manager

  1. Record the incident
  2. Inform the safety officer
  3. Set the reporting deadline

ResultThe statutory reporting deadline is no longer missed.

MediumWith conditions and approvals

Document a written warning

TriggerA formal meeting has taken place

  1. Record the facts
  2. Fill in the template
  3. Obtain approval
  4. Document the delivery
  5. Set a follow-up date

ResultComplete documentation that holds up in court.

ComplexBranches, deadlines, several systems

Support a long-term illness

TriggerSix weeks of absence reached

  1. Spot the deadline
  2. Offer a return-to-work process
  3. Document the invitation
  4. Wait for the response and log it
  5. Schedule the meetings
  6. Record the measures
  7. Map the phased return to work
  8. File it separately in line with data protection

ResultThe legally required procedure, cleanly documented and stored separately.

The exceptions

And what about
the special cases?

That is the question most automation projects fail on. With us the exceptions get built in, not left out.

A commuting accident with unclear responsibility
A return to work after long illness in phased steps
A written warning with an objection and a running deadline

Each of these cases can be mapped in the builder as its own branch, with a condition, an approval and a different route. Without a line of code.

Common questions

What we are asked about incidents
most often.

Are reporting deadlines to the accident insurer met?
The workflow starts when the incident is reported and counts the deadline from that point. It reminds you in good time and documents what was reported when.
Who is told automatically about an accident at work?
You decide. The manager, the safety officer, the works council, the board. The workflow tells them all at once rather than one after the other.
How does the return-to-work process run?
As its own workflow with deadlines, an invitation, documentation and follow-ups. A phased return can be mapped with different working time models.
Will the documentation stand up to an audit?
Every step is logged with a timestamp. At an audit the whole history is there in one piece, not spread across inboxes.
Other areas

It rarely stops
at one workflow.

RecruitingSee three examples → OnboardingSee three examples → Employee records & changesSee three examples → Time and attendanceSee three examples → PayrollSee three examples → TrainingSee three examples →
The next step

Tell us
what comes up in your work.

30 minutes on your actual programmes. We rebuild your incident workflow live, not on a made-up company.

Book a demoAll 36 workflows