Built from both sides of residential care.

Why I built ResiNotes.

I have experienced residential care from two very different positions: first as a child whose life was being recorded, discussed and decided upon, and later as a practitioner responsible for providing care, making decisions and creating those records.

That perspective sits underneath ResiNotes. Working in residential childcare made me increasingly interested in how digital systems can better reflect the way a home actually works: the connections between a child’s day-to-day experience, safeguarding, staff practice, management oversight and the records that bring those things together.

ResiNotes grew from that idea. The aim is to make information easier to follow, reduce avoidable repetition and build useful connections between records without losing the professional judgement behind them.

Alongside residential childcare, I have worked with web design, coding and product development. That has allowed me to take ideas from practice and turn them into working tools, while keeping the design grounded in the realities of residential care rather than in software for its own sake.

I continue to work in residential childcare, which helps keep ResiNotes close to the reality of shifts, handovers, safeguarding concerns, medication, appointments, incidents, recording, management oversight and all the things that rarely arrange themselves neatly for a software diagram.

My own experience of care also matters here. A child’s life should not become a pile of disconnected forms simply because an organisation needs different pieces of information. Their story should remain connected, their voice should remain visible and records should be created with an understanding that the child may one day read them.

ResiNotes is still being built. Some areas are mature, some are in beta and some remain planned. I would rather be clear about that than pretend a roadmap is a finished product. Residential care changes, regulation changes and good practice develops, so the platform should be capable of developing with it.

The purpose has stayed simple: build something that works better for practitioners without forgetting that every record is ultimately about a child.