Module M7
DesignedMaintenance and inspections
Recurring statutory obligations with their intervals, a calendar that warns in time, and the certificate kept on the obligation it belongs to.
Data, screens, notifications and settings are decided. No code is written.
What shapes this module
The intervals are data, not code. OVK — the statutory ventilation inspection — is three or six years depending on the system; lifts are two years and then one or two; and systematic fire-safety work has no interval at all, so the model has to allow "continuous" rather than force a number. And the certificate is part of the obligation: "OVK done" without the certificate evidences nothing, and evidence is the entire reason the module exists.
For the manager
- A calendar of what falls due and when
- History per obligation with the certificate attached
- A maintenance plan with cost and year
- Reminders that actually fire, at the lead time you set
What you configure yourselves
- Which obligations apply to you
- An overridden interval with a stated reason
- Lead time per obligation
- Who gets reminded
Not built
Not built. It waits on file storage, on conditional intervals, and on an obligation being able to hang on something narrower than a whole property — a playground and a charging bay are installations, and radon is measured in flats under a duty that applies to the building.
Contact
Tell us how a repair report is handled with you today.
Write a few lines about the portfolio you manage and where the time goes today. We will reply with how that looks in the system, and book a call if it seems worthwhile.