Up close · from the welding dossier to Multilas OS
From day sheet to invoice. No retyping.
This is how a week of day sheets runs through the welding dossier and Multilas OS. The photos come in, AI reads, someone reviews, and the hours go to the invoice. An example with fictitious data.
30 min · online or at your site · no obligation
Scroll along and follow 47 day sheets ↓Skip
Example with fictitious data
How a week of day sheets goes through the system
Step 1 / 5
How it comes in
Day sheets on paper, a photo via WhatsApp, an Excel file in three versions and a Post-it with extra work. Somewhere, someone retypes all of it every week.
› 47 day sheets · 1 WhatsApp photo · 1 Excel · 1 Post-it
Step 2 / 5
How it is read
The system reads every sheet, handwriting included: who, which day, which site, which job reference, how many hours. That is where AI comes in. Every result is a proposal first: nothing has been booked yet.
› day sheet 0412 · Jens V. · job 226050-03 · 7.5 h · proposal
Step 3 / 5
How it is reviewed
One sheet shows a 7 next to a crossed-out 1.5. That sheet goes to someone on your team, with the original next to it. They choose, and only then does the system continue. It does not guess.
› day sheet 0417 · 7 or 1.5? · original alongside
› chosen: 7 h ✓ · by someone on your team
Step 4 / 5
How it is booked
The hours appear per job reference on the phone. Someone on your team confirms them; until then nothing is final. Each subcontractor's rate card is applied: kilometres, travel time, daily allowance. No AI is involved there.
› Job 226050-03 · 7.5 h · confirmed ✓
› subcontractor rate card: km ✓ travel time ✓ · fixed rules
Step 5 / 5
How it goes to the client
Every week a weekly report per client, built from the booked hours: what happened, what is coming, what we need from the client. The hours go to Onfact as an invoice line.
47 day sheets processed
of which 1 reviewed by a person · example, not a client figure