Restaurant and hotel operations
One system for hotels and restaurants: rotas, training that gates shift access and maintenance tickets, in staff apps and a manager back office.
Service
We build learning platforms for teams: versioned courses, tests, clearance for work after training, and an overview for managers — who can already be put on shift. Our basis is the system for restaurants and hotels, where training is tied to shift clearance; it is currently at prototype stage.
Animation: lessons are marked complete one by one, answers are chosen in a test, the test is passed — and the lock on clearance for work opens.
Situations that bring people to us for this service.
Instructions sit in documents and chats, and nobody knows which version a person has read.
People are put on shift without checking that they have been briefed.
Finding out who has completed what means asking around.
After an instruction is updated, there's no way to check that everyone has learnt the new version.
Which knowledge is needed for which work, and what should happen if someone hasn't confirmed it.
Course materials and the current version: after a course is updated, clearance depends on the new version.
A test at the end of the course; the result counts towards clearance.
A passed test on the current version clears people for the shift; a failed one blocks them.
The manager sees straight away whether someone may take a shift, instead of asking around.
Staff take the course and test in their own app — the same place they see their rota.
Who creates courses, who assigns them, who takes them — separate permissions, and every change leaves a record.
The project path
Every step ends with a decision: go on or stop. We don't start the next one until the previous one has given its answer.
You describe the process and what gets in the way. We reply by email with questions and arrange a call.
We study the process with the people who work in it and write down what the system must change and how we will check it.
We build a working prototype of the key scenario to test the idea on real data rather than on polished screens.
We run the system in your real environment with agreed outcome criteria and a deadline. After the pilot we decide together whether to go further.
We bring it to daily use: reliability, access rights, links to other software, documentation, support. Then we develop it based on user feedback.
Systems where we have already done this kind of work.
A course platform usually ends with a test result. We tie training to work: without passing the test on the current version, a person can't take a shift.
A new version of the course appears, and clearance depends on the test for that version.
Yes, if it has work that needs clearance — a rota, tickets, access to a work area. How exactly we decide during discovery.
It's a prototype: the apps and back office run on demo data, and the end-to-end shift scenario, including the test and clearance, already works on them.
Describe it in a few sentences: how things work today and what gets in the way. We reply by email with questions on the next business day.
Get in touch