For refuges and residential treatment centres
In a refuge or a residential treatment service, who is on site is a safety question, and who came to the door is a security one. The register is built so the answer is always current, and holds as little data as the job needs.
Who is on site, right now
A live count says how many people are on site at this moment, residents included. Residents are signed in and out like anyone else, an authorised absence carries a return date so a planned night away never reads as missing, and a fire drill runs by building with every warden's phone showing the same list.
Every arrival at the door
Visitors, contractors and suppliers are signed in with their kind, name and company, and signed out on departure, so the roll call's list is everyone on site, not only residents.
Authorised leave, counted fairly
In a residential treatment setting, planned leave and overnight passes are recorded as an authorised absence and excluded from the missed-night counts, so permitted time away is never counted as a miss.
Roll call at 3am
Started from any staff phone, working offline, with the marked-safe list merging across every phone once the connection returns.
Children with a parent
Households group a parent with their children, so a family stays together on the register, and children are marked on the roll call rather than left off it.
Built for confidentiality
The register holds as little as the job needs, and what it holds is described here precisely, not summarised.
No postal address, anywhere
The app has no postal-address field for a site, a building or a resident.
Names go to your own staff only
The Sunday email carries counts and a link in its body, with the full update attached as a document naming residents, on by default — turn it off under Settings if your service wants counts only. The nightly email names each of its four checks in the body, to the staff you tick, and reaches nobody outside the service.
Identity documents, optional
TRC or IRP can be recorded as printed if a service needs it. It is an optional field, left blank by any service that does not use it.
Logged, on a connected phone
Opening a resident's record on a connected phone — the register sheet, the edit sheet, an export — is logged with who and when. A sheet read from a phone's offline copy is not.
One schema per site, in the EU
Hosted in Frankfurt, encrypted in transit and at rest, with each site's records in their own separate database schema.
Erasure on request
A resident's record can be erased on request, and the site's data is removed when the service leaves.
It was built with an accommodation centre's feedback and is offered here because the register is the same; we would want to hear from a refuge or a treatment service before claiming to know its day.
Common questions
Does the app hold the refuge's address or location?
No. A site is a name, with buildings and rooms under it — there is no postal-address field for a site, a building or a resident anywhere in the app.
Does anyone outside the service see the data?
No. Each site's records live in their own separate database schema in the EU, the Sunday email carries counts in its body and, by default, the update attached as a Word document naming residents, and the nightly email to your ticked staff names the residents behind each of its four checks — all to the service's own accounts, and the app itself holds no analytics or tracking.
Can a resident's record be removed when they leave?
A departed resident is archived, with their history kept for the retention period you set. If a service wants a record erased sooner, an administrator can erase it.
Is it a case-management or treatment-record system?
No. It records presence and movement — who was seen, who came and went, who was marked safe at a drill. It holds no case notes, treatment records or support plans.
Try it on your own site
Start a free trial and have a look around, with sample residents already in it. Remove them from Admin when you are ready for your own list. No card, and nothing to install.