Trust centre

How One Care Home looks after your residents' records: where they're kept, who can see them, and what is in place, in the demo only, being worked towards or planned. We never claim what we don't have.

Last reviewed 29 October 2026

What the four words mean

In place
Done, and we can show you the evidence.
In the demo only
Works in this demo, so you can try it. Not yet running for live homes.
Working towards
Started, with a clear finish line. Not done yet.
Planned
Decided and on our list. Not started yet.

Your data stays in the UK

Today the demo keeps everything in your browser. For live homes, we plan to keep your records in the UK, with a backup copy in the UK or EU, and never anywhere else. The one exception is the optional writing service: only if your organisation switches it on, and where your data protection officer agrees.

  • UK hosting (London)

    Planned

    Your records will be kept on servers in London, with an encrypted backup copy in another UK or EU region. We'll name the hosting company and region here once they're confirmed.

  • Records never leave the UK or EU

    Planned

    No copy of your records will be stored or worked on outside the UK or EU, by us or by any company we use. The one exception is the optional writing service, and only where your data protection officer agrees.

  • This demo keeps everything in your browser

    In the demo only

    Everything you change in the demo is kept in this browser, on this device. Nothing you record about the demo residents is sent to us.

What this means for you

  • Once you're live, you'll be able to tell families their records stay in the UK or EU.
  • Before you go live, we confirm the hosting company and region to you in writing.

Last reviewed 29 October 2026

Security

Your records will be encrypted while they travel and while they're stored, staff will sign in with a second step, and each person sees only what their role needs.

  • Encrypted while records travel

    Planned

    Every connection between a device and our servers will be encrypted with TLS 1.2 or higher.

  • Encrypted while records are stored

    Planned

    Records and backups will be encrypted where they're kept, so a stolen disk shows nothing readable.

  • Two-step sign-in, and single sign-on for groups

    Planned

    Staff will sign in with a second step, such as a code on their phone, and groups will be able to use their own work accounts. The demo lets you tap a person to look around quickly; live homes won't sign in that way.

  • Each role sees only what it needs

    In the demo only

    In the demo, carers see only their own staff record, and each page sends to the browser only what it shows.

  • A full record of who did what

    Planned

    A log of who opened or changed each record, and when, kept on our servers. The demo's admin console already keeps admin and support events.

  • Independent penetration test

    Planned

    Before launch, an independent tester who is a CREST member will try to break in. We'll share a summary of what they found and what we fixed. No result is claimed yet.

What this means for you

  • You'll be able to see who opened a resident's record, and when.
  • Groups will be able to use the work accounts their staff already have.

Last reviewed 29 October 2026

Backups and recovery

We plan encrypted backups every day, kept for 35 days, with a test restore every quarter. Notes written on a phone without signal are kept and sent later.

  • Encrypted backups every day, kept for 35 days

    Planned

    A full copy of your records each day, encrypted and kept for 35 days before it's deleted.

  • A test restore every quarter

    Planned

    Every three months we'll restore a backup somewhere separate to check it works, and keep a note of the result.

  • Recovery within 4 hours, losing under 24 hours

    Planned

    If something goes badly wrong, we aim to be running again within 4 hours (recovery time) and to lose less than 24 hours of records (recovery point).

  • Notes kept when the signal drops

    In the demo only

    On the phone, a note written without signal is kept on the phone and sent once it's back online. Closing the page doesn't lose it.

What this means for you

  • A dropped signal doesn't lose a carer's notes.
  • Once you're live, you can ask us for the latest restore test result.

Last reviewed 29 October 2026

Uptime and support

We aim for 99.9% uptime each month, with a public status page. There's no uptime history to show yet, because there are no live homes yet.

  • 99.9% uptime each month

    Planned

    Our target: no more than about 43 minutes of unplanned downtime in a month.

  • A public status page

    Planned

    A page anyone can check to see whether something is wrong, and when it will be put right.

  • A UK support team, 08:00 to 20:00 every day

    In the demo only

    Support from people based in the UK. These hours are demo figures until we confirm them.

  • An urgent line, 24 hours a day

    In the demo only

    If you can't record care, ring the urgent line at any time, day or night. A demo figure until we confirm it.

  • First reply within 1 hour if urgent

    In the demo only

    Within 1 hour for urgent problems and 1 working day for everything else. Demo figures until we confirm them.

Support and IT services by Forge9X Ltd. Phone 0333 335 5870 or email support@empliora.co.uk.

What this means for you

  • If carers can't record care, you'll have a 24-hour urgent line (a demo figure until confirmed).
  • We'll never show uptime figures we haven't measured.

Last reviewed 29 October 2026

Certifications and standards

We don't hold any certifications yet. Here is where each one stands.

  • Working towards

    The NHS's yearly check that an organisation looks after health and care records properly. We're working towards "Standards Met" before the first live home.

  • Working towards

    A UK government scheme that checks basic protection against common online attacks. Then Cyber Essentials Plus, where an assessor tests our systems.

  • Planned

    An international standard for how an organisation runs information security. We plan to start on it after launch.

  • NHS Assured Solutions and buying framework listings

    Planned

    Listings that make it easier for the NHS and councils to buy from us, once DSPT and clinical safety are in place.

  • Working towards

    Our target for making every screen usable by everyone. See the accessibility statement below.

What this means for you

  • You can copy these lines into a tender answer exactly as they read here.
  • If a tender asks for something we don't hold yet, ask us when we expect it.

Last reviewed 29 October 2026

You, the care provider, are the controller of your residents' records. One Care Home, a product of Forge9X Ltd, is your processor: we act only on your instructions. Forge9X Ltd is registered with the ICO (ZC188323).

  • A data processing agreement with every contract

    Planned

    It sets out what we do with your records, and what we never do. Ask for a copy below.

  • Planned

    A first draft of your data protection impact assessment, covering how One Care Home uses residents' records. You check it and finish it for your home.

  • Help with subject access and deletion requests

    Planned

    When a resident or family asks for their records, or for something to be deleted, we help you find and export it. The law gives you one month to reply.

  • The writing service in your DPIA

    Planned

    If your organisation switches on the optional writing service, the DPIA starter pack covers what each feature sends, with names taken out (still personal data), where it runs, and how long the service keeps it under its contract.

  • Records kept for as long as your policy says

    Planned

    Your home sets how long records are kept. We show the usual care-record periods as a starting point, and the choice is yours.

Companies we'll use to run the service, named by what they do. We tell you 30 days before adding one.

  • Cloud hosting

    Planned

    Runs the service and stores your records.

    Where: UK

  • Encrypted backup storage

    Planned

    Keeps the encrypted backup copy of your records.

    Where: UK or EU

  • Email delivery

    Planned

    Sends sign-in links and notices. No care records go in emails.

    Where: UK or EU

  • Error monitoring

    Planned

    Tells us when something breaks, with personal details removed first.

    Where: UK or EU

  • Optional writing service

    Planned

    Suggests clearer wording for notes, policies and drafts, only if your organisation switches it on. It keeps what it is sent only as long as its contract allows and never uses it to train.

    Where: To be agreed with you

What this means for you

  • You stay in charge of your residents' records. We only act on your instructions.
  • The DPIA starter pack saves you writing your assessment from a blank page.

Last reviewed 29 October 2026

Accessibility statement

We want everyone to be able to use One Care Home, including people with sight, hearing, movement or reading difficulties. Our target is WCAG 2.2 AA.

  • Display and reading settings

    In the demo only

    Bigger text, stronger contrast, less movement and larger buttons, from each person's own menu.

  • Large buttons

    In the demo only

    Buttons are at least 44 pixels, and 48 to 56 on carers' screens, so they're easy to press in a hurry.

  • Tap-for-meaning words

    In the demo only

    Hard words, like the underlined ones on this page, show a plain meaning when you tap or hover.

  • Screen-reader labels on the bed board

    In the demo only

    Each room on the bed board says who is there and how they are, in words as well as colour.

  • Older screens

    Working towards

    Some older screens haven't been redesigned yet and may not meet our target. We're working through them.

  • A night-shift dark mode and a dyslexia-friendly font

    Planned

    Both are on our list for the carer screens.

On a real home's public page, the official CQC widget is the regulator's own content, and we can't change how it works.

If anything is hard to use, tell us with Talk to us below, or ask your manager to. We'll reply within 1 working day (a demo figure).

This statement was prepared and last checked on 29 October 2026, by our own team. There has been no outside audit yet.

What this means for you

  • Each person can make text bigger or the screen calmer from their own menu, without asking anyone.

Last reviewed 29 October 2026

Writing help suggests clearer wording for notes, policies and drafts. Every suggestion starts on the device and works with no network. A writing service is optional: it's off unless your organisation chooses to switch it on, and where it runs is to be agreed with you. Only the words you're working on are sent, with names taken out. The service keeps them only as long as its contract allows and never uses them to train. Your home can switch it off.

  • On the device, with no network

    In the demo only

    It fixes care spellings, writes shorthand in full and suggests kinder wording. It never adds a fact: numbers, times and names stay as written.

  • Nothing changes until you choose

    In the demo only

    You see what you wrote next to the suggestion, then pick Use this, Edit or Keep mine. Drafts are never sent from where they're written.

  • An external service only if your organisation chooses one

    Planned

    It is asked only when someone presses a button, and it only rewords. Its contract must say it never trains on your records. Where it runs is agreed with your data protection officer before any home uses it.

  • Each home can switch it off

    In the demo only

    Managers, the group office and the owner switch it off for a home in the admin console, under Subscriptions, with a reason kept in the audit trail. Suggestions there are then made on the device only.

  • Handovers and shift summaries stay on the device

    In the demo only

    The shift summary is written up on the device from today's records, with where each line came from. Tidying a handover or a shift summary never uses the writing service until our Clinical Safety Officer signs it off.

  • Only for signed-in staff, for their own home

    In the demo only

    It answers only staff who are signed in, for their own home, up to 10 requests a minute each, with a daily limit for each organisation.

  • Facts are never changed

    In the demo only

    If a suggestion changes, adds or loses a name, number, time, medicine, dose or a "not", it's thrown away and the wording made on the device is shown instead.

  • Contracts and letters are explained on the device

    In the demo only

    A plain-English reading of a contract or letter is made on the device only, until our data protection officer and legal lead have checked it. The letter's own words are what count.

  • Counted, never read

    In the demo only

    Each use writes one line in the audit trail without the words. Your console shows how often it was used this week, as numbers only.

What this means for you

  • Staff get help with wording, and no resident's details leave the device unless your home has chosen the writing service.

Last reviewed 29 October 2026

Safety watch and staff

The Safety watch looks at the care a team gives, never at one person's speed or count, and staff can read every rule it uses. Because it looks at staff work, your home needs its own DPIA before real use, and your staff should be told how it works.

  • Rules staff can read

    In the demo only

    Every rule, what it reads, who it tells and what it never does, on "What the Safety watch checks", open to everyone signed in.

  • Team figures, never a league table

    In the demo only

    Patterns are figures for a team on a shift, with a prompt to talk it through. It never counts, names or ranks a person.

  • One private item, only for that person and the manager

    In the demo only

    When someone does a task after their training for it has lapsed, only they and the manager or deputy see it. It never stops the care being recorded.

  • Planned

    A first draft for your home's assessment of how the Safety watch looks at staff work, following the ICO's guidance on monitoring workers: why it's needed, what it reads, what it never does and how long things are kept. You check it, talk it through with your staff and finish it.

  • Worker privacy notice wording

    Planned

    Plain wording to give your staff: what the Safety watch reads, who it tells, what it never does, how long things are kept and who to ask. Your data protection lead reads it before you use it.

It never tracks where anyone is, never reads messages or what people type, and never counts how fast anyone works.

How long things are kept: "I'm on it" as long as the record it belongs to. Team patterns look back 4 weeks.

What this means for you

  • Your staff can see exactly what is checked, and nothing about them is noted in secret.

Last reviewed 29 October 2026

Documents, signatures and retention

Policies, contracts and each person's documents are kept in one place, with every version and every signature on record. In the demo everything stays on this device: nothing is signed for real, no link is sent and nothing is deleted on its own.

  • Signatures on the screen

    In the demo only

    Staff sign their own contracts and letters by typing their name or drawing it, after ticking that they agree to sign electronically. The person signs first, then someone for the home. Every signing screen says "Demo signature".

  • A signing certificate for every contract

    In the demo only

    Each step is listed with who, their role and when, and a fingerprint of the exact wording. The certificate says the wording hasn't changed only when the fingerprint still matches.

  • Sharing previews

    In the demo only

    The manager or deputy can share one of a resident's documents, or a policy, for 24 hours, 7 days or 30 days, with a lawful reason for anything about a resident. In the demo no link is sent: you see what the person would see, inside the app.

  • Retention review, never automatic deletion

    In the demo only

    Every document shows how long to keep it, from one table per nation. The manager reviews what has reached its date and decides; a legal hold stops disposal, and a disposal leaves a short note of what it was. Nothing is ever deleted on its own.

  • A dedicated signing service

    Planned

    In the live service, signing is handled by a dedicated signing service with its own certificate for each signature, hosted in the UK. We'll name it here once it's chosen.

  • Share links that open only with a one-time code

    Planned

    A real share link will open only for the person it was meant for, with a one-time code, a watermark on the document and a record of every time it's opened. It stops working at its end date or when you stop sharing.

  • File storage in the UK, checked for viruses

    Planned

    Uploaded files will be stored in the UK, encrypted, and checked for viruses and other harmful software before anyone can open them.

The example policies and contract templates in the demo are example wording. Have your policies and contracts written or checked by someone qualified before you use them.

What this means for you

  • You can show an inspector who has read each policy version, and show a new starter exactly what they signed.

Last reviewed 29 October 2026

Admin access and support

Changes to your set-up happen in your own admin console, behind a second sign-in step. Our support team can look at your account only when you say yes, for a set time, and they can't change anything.

  • A sign-in code for the admin console

    In the demo only

    Opening the admin console asks for a 6-digit code as well as who you are. In the demo the code is shown on the screen, so you can try it without a phone.

  • Support access only when you say yes

    In the demo only

    Our support team asks with a reason and a ticket number, for one home or your whole organisation, for 1 hour, 4 hours or a day. You say yes or no, you can end it at any time, and every page they open is written down for you to see. In the demo both sides use the same browser.

  • Authenticator codes and security keys

    Planned

    Your admins will get their sign-in codes from an authenticator app on their phone. Our own staff will also need a physical security key to open our control panel.

  • Sessions kept on our servers

    Planned

    Admin and support sessions will be held on our servers, so they end on time everywhere, and signing everyone out really does sign everyone out.

  • A log of every read and change

    Planned

    Our servers will keep a record of every time a record is opened or changed, and by whom, for 6 years. The demo keeps the latest admin and support events on this device.

  • Support access checked on our servers

    Planned

    Which home support may see, that they can only read, and when their time ends will be checked by our servers on every page, not by the browser.

Our control panel shows your organisation as a business: your homes, plan and set-up progress. It never shows residents' or staff records, unless you give support access.

What this means for you

  • You decide when our support team can look, and you can see every page they opened.
  • Your admin console's audit trail shows who changed your set-up, when and why.

Last reviewed 29 October 2026

Rota, agency staff and moves between homes

The rota, agency hours, cover between homes and moves between homes all work from one rota and one set of bookings. In the demo the rates and budgets are examples, nothing is sent to an agency or a funder, and moves and shared records are held in this browser.

  • Example rates and budgets

    In the demo only

    Agency rates, costs and 4-week budgets are example figures for the demo, shown only to the manager, the group office and the owner. Deputies see hours. Going over budget never stops a booking: it asks why and keeps the reason.

  • Nothing sent to agencies or funders

    In the demo only

    Booking an agency worker, confirming their checks and the funder's report are recorded on this device. In the demo nothing is sent.

  • Moves and shared records held in the browser

    In the demo only

    A move between homes and the records shared for it are kept on this device. The receiving home opens one ticked part at a time, each opening is written down, and sharing ends after 30 days, when it is stopped, or when the person arrives.

  • Only what each person needs

    In the demo only

    Only managers, deputies and the group office see "Off sick"; everyone else sees "Away". Another home sees only who can cover there, by name, role and home. Quality leads see figures with no names.

  • The rota and bookings held on our servers

    Planned

    The rota, agency bookings, cover between homes, moves and shared records will be held on our servers, which will check every change and log every time a shared record is opened.

  • Working with agencies

    Planned

    Bookings sent to agencies, their confirmations received, and their invoices matched to the hours actually worked.

  • Hours sent to payroll

    Planned

    Hours worked, and a leaver's final hours and leaving date, sent to your payroll. No pay rates are shown in One Care Home.

Sharing a resident's records with another home asks for the person's agreement, or the decision their nation's law allows when they can't decide. The lawful basis for sharing is their care, not consent, and your data protection lead checks the wording before real use.

What this means for you

  • You can see who worked where, what agency staff cost and what was shared with another home, with every change kept.

Last reviewed 29 October 2026

Home care visits

Carers check in and out of each visit on their phone, and the office sees the day on the visit board. In the demo a check-in records the time of the tap only, no location is used, and nothing is sent.

  • The time of the tap only

    In the demo only

    Check in and Check out record the time, the carer and the visit. No location is read, asked for or kept in the demo.

  • Key safe codes only on the carer's own visit

    In the demo only

    A key safe code shows only on the visit screen while that carer is checked in, and only when they ask. Each view is written down, never the code itself. The client's record never shows it, to anyone.

  • Nothing sent

    In the demo only

    Alerts, I need help, Running late and the funder's report are recorded on this device. In the demo nothing is sent or dialled.

  • Planned

    If your organisation chooses it, the phone will read its location once at Check in and Check out, compare it with the client's address and keep only the result. The location itself is thrown away, nothing is tracked between visits, and checking in without it is always possible. Only after a DPIA and your worker privacy notice.

  • Electronic call monitoring for your funders

    Planned

    Visit times sent to a funder in their own format, if they ask for one, made on our servers.

  • Visit records held on our servers

    Planned

    The visit plan, check-ins and key safe codes will be held on our servers. Codes will be encrypted and given only to a carer the server knows is checked in, with every view logged.

  • Real on-call alerts

    Planned

    Urgent visit alerts and I need help sent by push, text and a phone call to whoever is in charge or on call.

Carers see only their own visits today and tomorrow, and only those clients' records. The office sees names and areas on the board, and quality leads see figures with no names.

What this means for you

  • You can see every visit planned against what happened, with every change and correction kept with who, when and why.

Last reviewed 29 October 2026

Food and the kitchen

The kitchen works from each resident's own care record, so a change the nurse makes is on the kitchen sheet at once. In the demo, menus, recipes, suppliers, labels and prices are examples, readings are typed in, and nothing is sent.

  • Allergen information from every recipe

    In the demo only

    Each dish's 14 allergens are worked out from its ingredients and their suppliers' labels, never typed in, and shown on one allergen chart as Yes, May or –. Any change to a recipe's ingredients, labels or textures, and every new dish, waits for a second person to check it.

  • One check, and a stop can't be overridden

    In the demo only

    "Can they have this?" is one rule for the kitchen, choosing, the table and every save. An allergen, a "may contain" or a texture the dish isn't made at stops, and nothing overrides a stop: if the record is wrong, a nurse corrects it. Intolerances, diet notes, dislikes and allergies not recorded ask staff to check.

  • Allergies linked to the 14 by a nurse

    In the demo only

    Each allergy entry is linked to the 14, to "Not one of the 14" or to "Not a food" by a nurse, deputy or manager. Until then the kitchen treats it the safe way. Removing or narrowing an entry needs a reason and is kept in the audit trail, and "Allergies not recorded" is never read as none.

  • Kitchen records as the home's own diary

    In the demo only

    The daily diary for your home's pack (Safer Food, Better Business in England and Wales, CookSafe in Scotland, Safe Catering in Northern Ireland), with readings typed in, a 4-weekly review and a printed copy for an inspection. A reading is never changed: a correction is a new line pointing at it. Your pack and environmental health officer have the final say.

  • The kitchen sees food needs only

    In the demo only

    Cooks have their own Kitchen role. They see names, rooms, food and drink textures, plain diet instructions, food allergies, likes and dislikes, and who is away with the day they're back. Never medicines, contacts, care notes, MUST, BMI, weight or why someone is away.

  • Labels for food packed in advance

    In the demo only

    Natasha's Law labels, with the full ingredients and the allergens picked out, only when your home switches on "We pack food in advance". It is off by default, because plated and trolley meals aren't prepacked.

  • Nothing sent

    In the demo only

    No order reaches a supplier and no label printer is driven: labels and sheets print through the browser. In the demo nothing is sent.

  • Allergies and recipes checked on our servers

    Planned

    The allergy list, its links and the recipes will be held on our servers, which will run the check again on every choice and plate list. Allergy changes will be kept in the audit trail for 6 years.

  • Fridge and freezer sensors

    Planned

    Kitchen records held on our servers with the server's own time beside the device's, and fridge and freezer sensors that say where each reading came from.

  • Ordering from suppliers

    Planned

    Orders sent to your suppliers, delivery notes and invoices received, and real label printing.

  • Kitchen alerts by push, text and email

    Planned

    A fridge running warm or an allergen recorded as eaten sent to the cook, the manager and whoever is in charge by push, text and email.

In the demo the browser holds the demo's resident records behind the kitchen's screens. The live build will send a kitchen session its food parts only.

The food budget and prices are seen by the cook, the manager and the group office only. Quality leads see figures with no names.

What this means for you

  • Your kitchen and your care team read the same allergies and textures, and every allergy change, recipe change and kitchen reading is kept with who, when and why.

Last reviewed 29 October 2026

Clinical safety (DCB0129 and DCB0160)

As the maker of the software, we follow DCB0129, the NHS clinical safety standard for health and care software. Your home follows DCB0160 when it starts using it, and we give you what you need for that.

  • Working towards

    How we find, record and reduce the ways the software could put a resident at risk.

  • Hazard log

    Working towards

    Every way the software could contribute to harm, what we've done about each one, and what is left.

  • Clinical safety case report

    Working towards

    Our written case that the software is safe enough to use, signed off by our Clinical Safety Officer.

  • Clinical Safety Officer: to be named

    Working towards

    A registered clinician with clinical safety training, who signs off the safety case. We'll name them here.

  • Risk tool licences: MUST, Waterlow and Braden

    Working towards

    To be confirmed before real use. The demo uses MUST and Waterlow; Braden waits until a licence is in place.

  • Planned

    We give you our safety case and hazard log, so you can build your own for your home.

Hazards we already design for

  • A note is never lost when the signal drops: it's kept on the phone and sent later.
  • A record is never changed silently: a correction keeps the original, with who changed it, when and why.
  • Post-fall wording and timings wait for a named clinician's sign-off before real use.
  • Medicines brought in from another system, or changed by a hospital stay, show "Check needed before giving" and aren't given until a nurse has checked each one against the prescription (where no nurses are on site, the senior in charge with the GP or pharmacy).
  • Doses are counted by active ingredient over 24 hours, so a when-needed or homely dose can't quietly add to a regular one, and a dose outside its limits is refused unless a nurse records who advised it.
  • Controlled drugs: every register line needs a second person as witness, the balance is worked out from the records rather than typed in, and a count that doesn't match goes to the manager.
  • Medicines given covertly need a recorded plan; once its review date has passed, giving covertly is refused until it's reviewed.
  • Escalation numbers are shown as text to read out. Nothing in the app dials 999 or 111, and the 999 step always comes before any form.
  • Wound photos are taken only with consent, kept small on the device and never sent.
  • The NHS links demo is clearly marked, so it's never mistaken for a real record.
  • A reworded note could change a fact, so every suggestion is checked against the words it came from (names, numbers, times, medicines, doses and every "not") and thrown away if anything changed, and a person always chooses whether to use it.
  • A summary could leave out a resident who needs someone now, so the shift summary is written on the device from the Safety watch, puts urgent alerts first and links to where each line came from.
  • Words inside a record could try to steer the writing service, so they're sent as words to reword, never as instructions, and the reply is checked and shown as plain text.
  • A plain-English reading of a clinical policy could drop a time limit, so every number and time in the passage must survive, and the policy's own words are one tap away.
  • Safety watch: an alert nobody picks up climbs to the next person on your home's list, up to on call, so it can't sit unseen.
  • Safety watch: a wrong "Who gets told" list could send alerts to the wrong person, so only the manager or the group office changes it, every change is kept, and "nurse in charge" is refused where no nurses work.
  • Safety watch: too many alerts can be tuned out, so only urgent ones ring at every step; the rest ring once for whoever holds them.
  • Whether the Safety watch's clinical rules count as a medical device is a question for our Clinical Safety Officer to answer with the MHRA before real use.
  • Support could see a resident's care record, so care records open to support only with the home's consent, for one home and a set time, read only, and every page support opens is written down for the home to see.
  • A resident's liberty authorisation could lapse unnoticed, leaving them without the law's protection, so the Safety watch tells the manager 28 days before it runs out and again, as urgent, once it has.
  • A shift could be planned or left below safe staffing with nobody told, so the rota says Safe or Short in words, and the Safety watch tells whoever is in charge and the manager 12 hours ahead, and again as urgent once the shift is running short.
  • An agency worker could start without their checks confirmed, so a booking can't be confirmed until the agency confirms each check for the nation, and the Safety watch tells whoever is in charge at once if someone is on shift without them.
  • A missed home care visit could go unnoticed, so the Safety watch tells the office 15 minutes after a visit should have started with nobody checked in (10 for a time-critical dose), and as urgent at 30, climbing to the manager and then on call.
  • A carer alone could need help with nobody hearing, so I need help is urgent for whoever is in charge at once, out of office hours the person on call, and a carer not checked out 30 minutes after a visit should have ended is checked on.
  • A two-person transfer could be done alone, so a two-carer visit says to wait for the second carer, and the office is told if the second carer isn't there 5 minutes after the start.
  • A visit with a time-critical dose could be moved too far from its time, so moving it by more than 15 minutes warns and asks why.
  • A check-in sent late from a phone with no signal could read as a late visit, so the phone keeps the time of the tap and the office sees when it was sent.
  • A key safe code could be shown to the wrong person, so it shows only to the carer checked in to that visit, never on the client's record, and every view is written down.
  • An allergy could be missed because an entry was linked wrongly, so an entry no nurse has linked stops on its suggested allergens and on its own words in an ingredient's name, a link that narrows needs a reason, and every change is kept in the audit trail.
  • A supplier could leave a "may contain" off a label, so a "may contain" stops the same as "contains", every ingredient keeps its supplier's label, and any change to a recipe's ingredients or labels waits for a second person.
  • A dish could be made or labelled at the wrong texture, so a texture the dish isn't made at stops, a change to a dish's textures waits for a second person, and a texture recorded as served that isn't the person's is urgent for whoever is in charge, with what to watch for.
  • An allergen could be eaten with nobody told, so what was eaten is never refused: an allergen recorded as eaten is urgent for whoever is in charge, the manager is told at once, and it ends only once they've said "I'm on it" and an incident is reported or the record corrected.
  • Poor eating could go unseen if meals aren't recorded, so carers record each meal at the table with one tap per person, and a quarter or less at 3 main meals running tells the nurse in charge, suggesting a MUST re-screen.
  • An allergy could be removed in error, so only a nurse, deputy or manager can remove one, with a reason kept in the audit trail, and a meal is judged against the allergy list as it was when it was eaten.
  • A fridge or freezer could run warm unnoticed, so a reading above the recommended figure asks for another in 30 minutes, and one beyond the pack's limit needs what was done, with the cook and the manager told through the Safety watch.

What this means for you

  • You'll have our safety case and hazard log to start your own DCB0160 work.

Last reviewed 29 October 2026

Talk to us

Questions about anything on this page? Note a request. In the demo nothing is sent: your note is kept on this device.

One Care Home is independent software and is not endorsed by any regulator.

One Care Home is a product of Forge9X Ltd, registered in England and Wales, company number 16867624. Registered office: 140 Avon Road, Chelmsford, Essex, CM1 2LB. ICO registration ZC188323.

Support and IT services by Forge9X Ltd. Phone 0333 335 5870 or email support@empliora.co.uk.

Last reviewed 29 October 2026