Product · Routines & scheduling
Recurring work that schedules itself.
Define a routine once — what to check, where, how often, who is responsible — and Vabumi generates the work every time it comes due. Daily fire-door checks, weekly pool tests, monthly legionella flushes, annual boiler servicing: each on its own cadence, none of it depending on somebody remembering.
Daily to annual
Plus fixed seasonal dates.
Failed item → follow-up
Created automatically, tracked.
ICS calendar export
Subscribe from any client.
What today looks like without it
- Compliance that lives in a binder, and one person who knows where the binder is.
- A check recorded as done with no evidence attached, which is the same as not done when an inspector asks.
- A heavy routine week landing on top of two people being on leave, discovered on the Monday.
What it does
Any cadence you actually run
Daily, weekly, monthly, annual, or a fixed seasonal date — tied to specific rooms, surfaces or pieces of equipment rather than to a generic checklist floating free of the building.
Pass, fail, or skip — with evidence
Every item takes a photo. A failed item creates its own tracked follow-up task automatically, so a fail is the start of work rather than a note in a column.
Misses are recorded, not blank
A routine not started by the end of its window is recorded as missed; one an admin dismisses is recorded as skipped. Compliance accounts for every outcome, not only the flattering ones.
One calendar for the whole operation
Routine occurrences, task due dates, team shifts and absences overlaid in day, week, month and year views. The heavy week that collides with leave is visible before it arrives, not during.
The building as the interface
A printed QR code on the fryer opens that routine pre-scrolled to that step. A code on a door opens today’s work for that room. Codes export as a printable A4 grid or as PNGs.
It leaves the building too
A live ICS feed of routines, due dates, shifts and absences subscribes into any standard calendar client, so the schedule is visible without asking anyone to log in.
Set it once
- 01
Define
What gets checked, on what, how often, and who owns it. Templates cover the routines typical for a property of your size; you keep the ones that fit and change the ones that do not.
- 02
It generates
Instances appear on schedule, assigned, on the calendar, and on the phone of whoever is working. Nobody has to raise them.
- 03
It records itself
Each completed instance becomes a permanent timestamped record with its checklist results and photos attached — the audit trail, built as a by-product of doing the work.
See it on your own building.
A short call, then a walkthrough on a model of a property like yours. If it is not a fit we will say so — we are a small team and we would rather spend the hour on the right hotels.