Six weeks before the safety commission: a scenario with Paco
An independent 40-room hotel, a periodic visit six weeks out, one missing certificate and one open finding. Here is what Paco would do, week by week — an illustrative scenario with example data, not a customer story.
A scenario, not a case study
Paco is new and shows no logos or testimonials, and we will not invent any. What follows is a constructed scenario: the property is fictional, the dates are examples, but every step described matches behaviour the product actually has — nothing else.
Six weeks out: the real state, not the hoped-for one
The register says what is missing: the electrical check is proven, the extinguishers too, but the smoke-control certificate is not on file and one finding from the last report — an emergency-lighting unit — is still open. Nothing is invented: an obligation without proof shows as exactly that, and never becomes "probably done".
- Every obligation carries its interval and its source text
- A missing proof stays visible, never presumed
- The open finding stays attached to its original report
Five weeks out: the requests go out, under your rules
Paco drafts the request to the smoke-control contractor — site, equipment, deadline, reference of the last report — and shows it to you. It leaves from your mailbox, in your name, when you approve it, or on its own if you have already approved that kind of letter. After a week of silence Paco drafts a reminder for you, then a second if needed; after that it comes back to you instead of slipping.
Three weeks out: the finding closes on WhatsApp
Replacing the emergency-lighting unit falls to your own team. Paco hands the task to the technician on WhatsApp — no new tool — and the task stays open until the photo that proves the fix, time-stamped on arrival, and your validation. The report's finding closes with its evidence attached.
Visit week: the binder in one click
The smoke-control certificate arrived by email; Paco read it and filed it against the right obligation. The inspection pack builds in one click: contents, obligation table, certificates appended, findings and their closure evidence. What the commission looks at first — the register, the reports, the fate of previous findings — is already assembled.
Common questions
Does this scenario describe a real customer?
No. Paco is new and shows no logos or testimonials; the property and the dates are examples. Every function described, however — register, drafted reminders, WhatsApp tasks with photo proof, inspection pack — exists in the product exactly as written.
What if the contractor never answers?
After the planned reminders, the request comes back to you explicitly: the register shows it as waiting with reminders exhausted, instead of letting the obligation drift. Nothing closes without proof.
Want to see the real thing?
Nine minutes is enough to watch your own register build itself.
Book a demo