For housing teams and agents

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 record-keeping problem, and it is the one Corbely was built around.

Join the waitlist →How we handle your data ↓
In the app

A report, its trail, and what was done.

Permissions

Not everyone should see everything.

A repairs coordinator does not need arrears. A contractor does not need the incident file. Owner, Admin, Member, Viewer and Tenant come built in; build any other role from individual permissions, and rank it. A role only manages the ones below it. It holds on every screen, including the ones people reach by pasting a link.

Tenant data is the most sensitive thing you hold. Everyone starts at the floor, able to open the workspace and nothing else, and every permission above it is given by a role somebody chose.

Casework

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, where the law sets one, 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’s 10 days from the incident and the ICO’s 72 hours from when you knew, shown on the case until somebody logs the report.

Corrective actions

Each with an owner, a due date and a closing note saying what was actually done.

Inspections

Scheduled and recorded, with a damp-and-mould finding on each and a follow-up that stays open until someone acts. A follow-up nobody closed is the finding.

Trends

By category, severity and repeat address, and how many days each took to close. The repeat address is usually the story.

Printable reports

The artefact a board or an ombudsman asks for, generated rather than assembled by hand.

Community board

Tell a building once.

Planned works, a fire door inspection, the water going off on Tuesday. Post it to one building or to all of them. Residents elsewhere never see it, and the ones it is for are notified.

Ask for an acknowledgement and you can see who has read it and who has not. Events go on the calendar, and every notice prints as a sheet for the hallway.

Straight answers

What you will ask in procurement.

Where does our data live?
The database, the API and your uploaded files all run in the EU (Frankfurt). The full sub-processor list, with every provider, what it does for us and where it runs, is published on our privacy policy, and we keep it current as it changes.
Can you watch our staff work?
No. Session replay is banned in this product in writing, because it would record tenant names, addresses and arrears. That rule was written before anybody asked for it.
What happens if we leave?
The main lists (properties, tenants, rent, repairs, incidents, documents, inspections and compliance) export to CSV today. A workspace owner can also download the whole workspace, every list and every file, as one zip from Settings.
Who has seen this record?
Today we log who changed what, not who looked. Every change to repairs, tenancies, incidents, members and roles is recorded with the person and the time, and nothing in the product can edit or delete an entry. If someone deletes their account, their entries stay, with an anonymous label in place of their name. A log of who opened a record is not built yet.

Come and try to break it.

Free during the beta. Tell us what you would test us against. We would rather find out what your team needs now than after you have committed to us.

Which fits you best? (optional)

First access when Corbely opens. We'll only email you about the launch — nothing else, and you can unsubscribe any time.