Care Note Builder

Answer what actually happened on the shift. The builder writes a fresh, person-centred daily care note — worded differently every time, so no two entries read like a paste of the last one.

Offer→Choice→Support→Independence→Observation→Outcome

Initials only — nothing leaves this tablet. There is no account, no server and no internet call. Everything you type stays in this browser, and the builder never adds a detail you did not record.

●

The person

Saved on this device only
How this person communicates
Standing needs & risks (shape the questions asked)
More about this person needs, routines, preferences

Context for the questions the builder asks. Nothing here is ever written into a note.

College timetable

Set once per person. Pick College on a day they have a class and the course and times fill in themselves.

1

Offer

What was offered, and how
How staff communicated this time
Two real options is what evidences choice. Leave the second blank if only one was offered.
2

Choice or response

Their voice, not yours
What they chose or how they responded
How they let you know
Consent
3

Support & independence

Tick only what happened
Each row maps to a field in your care records system. Anything left unticked is not mentioned in the note.
4

Observation

Only what you actually saw
Skin (personal care)
How they presented
Wellbeing
Behaviour you observed optional — describe, don’t label
5

Outcome

How it ended for them
Outcome
What was done about it — only what actually happened

Settings & data

Your service

Adapt the builder to your organisation. Everything is kept on this device only; use Backup and restore below to copy a setup to other tablets. Saving reloads the page.

History and patterns

Kept only in this browser, on this device. Clearing the browser’s site data, resetting the tablet or using a different browser loses it. Export a backup regularly.

When a note is copied, what it observed is saved — amounts, support levels and the choices ticked. The written note and anything typed freehand are never kept. History lets the builder notice changes from each person’s own usual pattern.

Backup and restore

A backup file contains profiles and history. Store it only where your organisation allows personal information to be kept. It is created on this device and is not sent anywhere.

For developers
0 / 7 audit checks · 0 words