Statutory clocks per property · Group visibility · Court-grade audit
Two systems, two audit trails, one inspection.
A provider running both supported and general-needs stock usually pays for one system for each half — then reconciles them by hand at the moment a regulator asks a single question spanning both.
GDPR-compliant · configurable long-horizon retention for safeguarding-flagged records
Beat 1 · Your week now
You do not manage the stock. You are accountable for it.
Much of the portfolio sits with managing agents, each running their own tools and their own conventions. You receive returns, you chase exceptions, and you assemble a view of compliance from whatever each agent chooses to send.
It works because people are diligent. It does not work because the system makes it work.
Beat 2 · What breaks
The clock is running on stock you cannot see.
Under SI 2025/1042 a social landlord has 10 working days from the day after awareness to investigate a reported hazard, 3 further working days to issue the written summary, and 5 to make safe — 24 calendar hours if it is an emergency. Awareness is the trigger, not attention.
If a tenant reports damp to a managing agent on a Friday, your statutory clock started on Saturday. You will find out on Tuesday. Nothing in the regulation cares where the report landed first.
And when the inspection comes, it asks one question across both halves of the portfolio — which is exactly the question two systems cannot answer together.
- A hazard clock started by a report you never saw
- Compliance evidence in as many formats as you have agents
- Supported and general-needs stock in two systems, reconciled by hand
- A regulator's question that spans both, and a week spent answering it
Beat 3 · Why your current tools can't fix it
Sector systems do supported. Property systems do private. Nobody does both.
The specialist supported-housing systems are built around the service user and stop at the edge of general-needs stock. The mainstream property platforms are built for the private rented sector and have no concept of a support case, a safeguarding stream or a placement approval.
So a mixed provider runs one of each and carries the join as a manual process — two audit trails, two retention regimes, and a reconciliation that only ever gets tested under inspection conditions.
Beat 4 · What changes
One trail, both tenures, and the officer gets their own login.
Group admins see compliance, jobs and tenancies across every managing-agent organisation in one view, without forcing any agent onto a different workflow. Curated templates flow down; data flows up.
Statutory clocks start automatically where they are statutory. Support cases carry a review gate and a two-stream split. And an inspector — a named LA or DWP officer — gets a read-only login of their own rather than a folder of exports.
- Group-level visibility across every managing-agent organisation
- Statutory hazard clocks started from the day after awareness
- Supported and general-needs stock on one audit trail
- Read-only inspector role for a named LA or DWP officer
What ships today
What ships today.
Statutory clocks, started for you.
Hazard reports open the right clock on the right tenure automatically, counted in working days from the day after awareness, excluding weekends and bank holidays.
Explore furtherYour managing-agent network.
Group and branch modelled as your real structure — one console, pooled capacity, and archive-in-place so a wind-down never loses the record.
Explore furtherThe inspector gets a login.
A named local-authority or DWP officer gets read-only access of their own. That is a procurement answer, not a feature.
Explore furtherOne pack, both tenures.
Notices, certificates, messages, payments, inspections and support sessions in one date-ranged, signed PDF — whichever half of the portfolio it came from.
Explore furtherA review gate before it counts.
Draft → submitted → approved, or returned with comments. Seniors work a queue that surfaces safeguarding-flagged notes first.
Explore furtherTwo streams, one honest record.
A shared stream the person can read and a professional stream for the clinical and risk record. Safeguarding notes are forced professional by the system.
Explore furtherThe note lifecycle
A note becomes the record when a senior says it does.
Not when a tired worker closes the laptop.
You are accountable for support delivered in schemes you may not staff yourself. A housing-benefit review will not ask whether the support happened — it asks you to evidence it, per person, per week, going back years. On a thirty-bed scheme a clawback runs to six figures, and it turns on the quality of the record rather than the quality of the care.
The worker writes a draft and submits it. It lands in a review queue where safeguarding-flagged notes sort to the top. A senior approves it, or edits and approves it — with the before and after both kept — or sends it back with a comment saying what needs to change.
Once approved it stops being editable. A correction supersedes it and the chain stays linked, so the earlier version is still there to read. Nothing is quietly rewritten, and nothing disappears without leaving a marker saying something was removed.
- Draft → submitted → approved, or returned with comments
- Review queue ordered safeguarding-first, not just oldest-first
- Modify-and-approve keeps both the original and the edit
- Supersede instead of overwrite — the chain stays readable
- Redaction leaves an audited marker, never a silent gap
Sign-off that leaves the building
Three things that go out, and the decision comes back on the record.
The officer approving a property, a placement or a support note does not work for you — so they get a link, not a licence.
The same problem as the inspector login above, pointed the other way: this is the approval you have to obtain rather than the access you have to grant, and the person giving it sits in a local authority or a commissioning team.
Send a property for approval and the housing officer opens a review page, reads the pack and approves or declines with comments. Send a placement and the signed pack goes to your named placement officers. Send support notes to a commissioner or RSL and they get a read-only seat — with the professional stream withheld until you authorise it for that specific case.
None of them create an account, hold a licence, or occupy a seat. Every decision lands back on the record with the name, organisation, IP address and timestamp attached.
- Property, placement and support notes — three sends, one mechanism
- No account, no licence and no seat for the approver
- Decision stamped with name, organisation, IP and timestamp
- Recipients frozen at send — a later edit cannot retarget it
- Links expire, and can be withdrawn if circumstances change
For housing associations and registered providers — customer stories will appear here when there are real ones to tell
One audit trail across supported and general-needs stock.
Talk to Sales for a scoping call — bring a real scheme and a real review.