When someone asks
you to prove it.
A regulator, an ombudsman, a board. The question is never “did you care?” — it is “show me what you knew, when you knew it, and what you did next.” That is a data-model problem, and it is the one Corbely was built around.
Not everyone should see everything.
A repairs coordinator does not need arrears. A contractor does not need the incident file. Roles are positional and granular, and they hold on every screen — including the ones people reach by pasting a link.
Tenant data is the most sensitive thing you hold. Least privilege is the default here, not a setting somebody has to remember to turn on.
| Role | Repairs | Rent | Incidents | Docs |
|---|---|---|---|---|
| Housing officer | Full | Full | Full | Full |
| Repairs coordinator | Full | — | — | Own only |
| Finance | — | Full | — | Own only |
| Contractor | Own only | — | — | Own only |
| Tenant | Own only | Own only | — | Own only |
Incidents, inspections and the clock on both.
A hazard, a complaint, a report of damp. Each one is a case with a reporter, an assignee, corrective actions and a statutory deadline — and a printable report at the end.
Incidents
A reporter, a category, a severity and an evidence trail nobody can quietly rewrite.
Statutory deadlines
RIDDOR and ICO clocks tracked as dates on the case, not as something a person is holding in their head.
Corrective actions
Each with an owner and a due date, so an action raised is an action somebody is answerable for.
Inspections
Scheduled, recorded, and their follow-ups tracked separately — a follow-up nobody closed is the finding.
Trends
By category, by severity, by repeat address. The repeat address is usually the story.
Printable reports
The artefact a board or an ombudsman asks for, generated rather than assembled by hand.
What you will ask in procurement.
Come and try to break it.
A walkthrough with your own scenarios rather than slides. We would rather find out what your team needs now than after you have committed to us.