Someone asks a question the way they would ask a colleague. The assistant answers using only your own approved documents and attaches the source. Where the material does not cover it, it says so instead of guessing.
On a phone, mid-task. No folder trees, no laminated printouts from last quarter, no doubt about which version is current.
Always verify critical instructions against the source document.
The film follows the doubt from the moment it appears until the answer stands with its source — in a hospital and in an industrial laundry. And it shows what happens when the answer is not there.
1 min 12 sec · no sound · plays by itself · on-screen text in Danish 1 min 12 sec · no sound · tap for full screen
The procedure exists. It is current. It is simply not where the work is being done.
He has been told to run the backup collection route, but does not know the pickup points. The route is pinned to a noticeboard five to eight minutes' walk in the wrong direction. So in practice the answer becomes a guess, a phone call to someone more experienced, or “the way we usually do it”.
The procedure is corrected on the shared drive, while last month's version is still hanging in a folder on the floor.
Staff ask in their own words and get the answer from the current, approved version of the procedure, every time.
This is not a chatbot that knows your industry. It is a search engine over your own documents that happens to write in plain language.
Staff type a question on a phone and get the specific answer — not the whole document. The full procedure is attached, so any answer can be checked in seconds.
“Where do samples get collected when the tube system is down?”Every procedure categorised and readable. Search is for when you know your question. The library is for when you do not.
What gets asked, where the procedures fall short, and which ones are approaching their review date. Measurement instead of instinct.
Most objections to AI in a regulated workplace come down to these four. So they are stated outright.
Retrieval records the outcome of every single query. This is the point where the product stops being a search box and becomes a management instrument.
The procedure existed, the user was cleared to see it, the answer held up.
A fair question. No document covers it. Now management knows that.
The document exists, but this user was not cleared for it. Permissions do not match the job.
The document exists and was found — it just does not answer the question well enough.
Ask a quality manager which procedures are failing their staff and you get an opinion. This turns it into a number, and it accumulates from day one without anyone filing a report.
The documents change from sector to sector. The mechanism does not.
Room turnaround, positioning, transport and hygiene. Answers on the move, mid-shift, on a phone.
HACCP records, machine procedures and safety data sheets. No more printouts living a life of their own.
Medication handling, hygiene, transfers and observation. Staff look it up mid-task instead of walking back to an office.
Cleaning standards, routes and workflows. New colleagues become self-sufficient sooner.
We can be deployed where SaaS is ruled out. Same containers, same features — the only difference is whose machines they run on.
You start without going through your IT department first. Our infrastructure inside the EU, our model access, a data processing agreement signed before onboarding begins.
The same containers and a licence key. Your infrastructure, your integrations and your own model provider if that is a requirement. The documents never leave your building.
Public-sector buyers increasingly run their own language models on their own hardware. For them, self-hosting is not a concession we make — it is the entry ticket. A vendor that can only offer SaaS never gets to the second meeting.
The assistant was built for the whole hospital, not a single ward. It pulls procedures from the hospital's own document system, and each professional group sees its own work instructions — anaesthesia, surgery, recovery and service staff kept separate — while shared clinical guidelines apply to everyone. A large share of that material consists of regional guidelines used identically across the region, which makes the step from one hospital to the rest of it a short one. How it started.