A hot week raises your sick leave and triggers a legal duty — few employers can prove what they did about either. Lichen turns your own data into the right measure per site, and documentation designed to be inspection-ready. Starting with heat.
Sick days you pay for, and a duty you must document. Both land unevenly across sites, shifts and roles — and often only become visible once the sick notes arrive. By then the hot week is over, and there is nothing left to prove.
“There is no regulation deficit — there is an implementation deficit.”
DGB · German Trade Union Confederation · June 2026The rules exist. The templates exist. What is missing is execution inside the company — and proof of it. That is exactly what Lichen does.
Your absence data against your site temperatures. Which shifts lose the most, what it costs you, and where the 26, 30 and 35 °C duties bite.
Every site over threshold gets its measure, a named owner and a deadline. The templates are free on the BMAS site. Getting them done on the day it matters is the hard part. That part is ours.
Every reading and every action lands in an inspection-ready Hitzeschutzplan, with the §5 psychosocial documentation alongside. When the inspector or the works council asks, it's already there.
Illustrative preview with example data — not real customer data. Concrete effect figures are established during the pilots.
Follow the path. At each step you see exactly what it costs you in effort — and what you get back. The line ends where you want to be: measures running, proof writing itself.
—
The DWD trend is unambiguous: temperatures are rising nationwide and hot days keep increasing — the next warning is a question of when, not if. Build the baseline now and you enter summer 2027 with a finished plan and defensible numbers, instead of starting from zero when the warning hits.
Excel collects. It doesn't route, it doesn't measure, and it reminds nobody at 11 a.m. on the third hot day. Above all, it can't show an inspector that the measure actually ran — who, what, when, with what effect. That's the difference between a spreadsheet and proof.
The duty already exists — today you discharge it with emails, notices and follow-up calls. Lichen doesn't create the paperwork, it does the paperwork: one warning, one routed task, one entry in the plan. Less admin, not more.
Aggregated absence figures are enough — no diagnoses, no personal profiles. Your data stays yours: export any time, deletion on request, processed under GDPR.
And they stay in charge. Your safety professional decides what applies — Lichen makes sure it actually happens at every site and is documented. A tool for them, not a replacement.
The ASR thresholds start at 26 °C — September counts too. And this season's baseline is your head start on the next one: start now, and you go into summer 2027 with a finished plan and defensible numbers.
For centuries, lichen has been how we read the air. Now Lichen reads the conditions your people work in.
Tell us in one minute where you stand. Within 24 hours you'll get an answer from the founder — with a proposed time for the first call, not a newsletter.
“You'll talk to me directly, not to a sales sequence. And if Lichen isn't right for your operation, I'll tell you that in the first call.”
Kseniia Pavliuchik · Co-founder & CPOWe'll get back to you within 24 hours with a proposed time for the first call. Tip: an absence export (CSV) speeds up your baseline.
Lichen is a software venture in formation. So you can judge every claim on this page, here is what is built, what is proposed, what is illustration, and what is still being proven.