StaffCore runs the care — medication, observations, records, residents’ money. CareTime runs the people — rota, clock-in, timesheets, holidays. Built inside two working care homes by the company that runs them.
Tonight’s carer screen. One check couldn’t run and says so instead of ticking itself. It reads 4 of 6, not 5 of 6.
Most homes run one system for records and a spreadsheet for everything else. These are two proper products that know about each other.
The care record. Medication rounds, observations, care plans, incidents, residents’ money and staff compliance — recorded at the bedside on a tablet that keeps working when the signal doesn’t.
The rota and the hours. Publishing shifts, clocking in, timesheets and approvals, holidays, absence, swaps and overtime — with a staff portal your team reaches without another login to forget.
Switch modules on per home. A home that doesn’t buy eMAR never sees it.
Scheduled and as-required medicines, controlled drugs, refusals with reasons, printable MAR charts. A background check every fifteen minutes looks for doses past their window.
Optional moduleNEWS2 and RESTORE2 with soft signs and recheck windows. Scores only when all six measurements exist — an incomplete set is shown as incomplete, never totalled.
CoreCare plans by category with reviews, daily notes, repositioning, bowel records, body maps, food and fluids, weights — written where the care happens.
CoreWaterlow, MUST, Abbey pain, oral health, PEEP and mental capacity — each recorded with who assessed and when, and printable as inspection evidence.
CoreA guided incident record with its own reference number, shift handover, and a transfer pack that prints everything the hospital needs in one go.
CorePurse and account balances from a full cash book, bank statement import that refuses to double-count, home petty cash, and a twice-daily count signed by two people.
Optional moduleTraining matrix with automatic chasing, supervisions, appraisals, induction, sickness and staff files. A monthly report and a clinical hazard log kept to DCB0129.
CoreMaintenance log, food diary to Safer Food Better Business, menus, activities, a home notice board and a Freedom to Speak Up route that goes to the guardian, not the manager.
CoreTablets keep recording through a dropout and sync when they reconnect. If a record is ever rejected you are told, in red, until someone deals with it. Nothing is thrown away quietly.
Built in
Every minute a carer spends fighting a form is a minute they are not here. That is the whole argument for getting the records right — not tidier data, more of this.
Unless the software is built to tell them apart. Every care system asks a database a question. What decides whether it is safe is what it shows when the database does not answer.
The overnight check never ran, so nothing looked missed, so it went green. The score of 1 came from three of the six measurements it needs — the other three were never taken, and missing was counted as normal.
The same night, named. No tick, no green, no reassurance the system has not earned. The observation refuses to produce a score from half a set. The carer opens the round and looks.
Anything that displays a value must be able to say “I don’t know”.
That sentence is written into how both products are built, and it is checked on every release. A medication list that fails to load says so instead of showing an empty round. A count of residents’ money that did not happen never looks like one that passed. And a rota that cannot be read never reports that nobody is on shift.
Who was on, who actually turned up, and who is owed what. CareTime handles the half of a care home that a records system never touches — and when an incident is reviewed months later, the rota is the document that says who was there.

Build the week from templates, publish it, and change it without redoing the lot. Night shifts that cross midnight are handled properly rather than truncated.
A kiosk on the door records real hours as they happen, so the timesheet is what occurred rather than what was planned.
Hours roll up per person per period, with a manager approval step before anything reaches payroll.
Entitlement, requests and approvals against a leave year you set, so the balance is one number everybody can see.
Sickness and unplanned absence recorded against the shift it affected — the history a return-to-work conversation actually needs.
Staff arrange cover between themselves and it lands on the published rota, with a record of who owes whom a shift.
Extra hours requested and approved rather than remembered, and corrections recorded against the period they belong to.
Your team check their shifts, hours and pay period from a link — no extra app to install and no password to forget.
CareTime is a separate product and can be bought on its own, alongside StaffCore, or not at all. A home without it simply does not see the rota screens — absent, rather than permanently saying “can’t check”.
StaffCore reads the published rota, so “who was on when this happened” is answered from the rota rather than reconstructed from memory weeks later. If the rota cannot be read it says so — it never reports that nobody was on duty.
Medication competence, training and induction live in StaffCore, so the person rostered to lead a medication round is one whose competence is on file and in date.
Homes do not fail at this because the software is hard. They fail because it is attempted in a bad week, with no plan for the paper already in the cupboard and no answer for the carer who does not want to.

Your home, beds, staff and residents go in. Existing records are scanned to PDF and attached, so nothing is stranded in a folder nobody opens.
Not a classroom. Tablets and a touchscreen go in, and carers are shown the four things they do every shift, at the moment and place they would do them.
Paper and digital side by side for a week. This is the week that finds the gaps, and the one homes are most tempted to skip.
Digital becomes the record. The paper is filed, not binned, and the manager gets the reports that replace the folder they carried to inspections.
Most care software puts every provider in one shared database and separates you with a column. We give each customer their own. It costs us more and it is the right way round.
These are somebody’s parents. The records are the only account of their days that will outlast the people who wrote them.

Your residents are not rows in a database that also holds another company’s. A mistake in our code cannot show your records to someone else’s home, because they are not there to show.
Your database is hosted in the United Kingdom and every record stays inside it.
Ask and you get your data, in full, in a form you can read. A promise to export is worth nothing unless it has been done. Ours has.
Cash counts and petty cash can be written to and read, and that is all. Not by a manager, not by us, not by the app. An entry made is an entry that stays.
Who wrote it and when, on every entry — including ones the system generated, so an alert can always be traced to what raised it.
If a tablet writes something the database refuses, the record is kept, the failure is logged, and a red banner stays up until a person deals with it.
We don’t, and no software can. Safe, effective, caring, responsive and well-led are judgements about your home, not your system. What we do is make the evidence findable while there is still time to act on it. Any supplier claiming their product produces a rating is selling something that does not exist.
NEWS2, Waterlow and MUST are published, validated instruments. You set your own escalation policy — who is called, and when — recorded against a name and a date. You cannot retune the arithmetic underneath, and neither can we.
What is on this page is built and running. Ask for something we have not built and you will be told so, and when. Selling a care home an unbuilt safety feature is how people get hurt.
Nothing stops. The tablet keeps recording and holds what you write on the device, then syncs when it reconnects, telling you plainly how many records are waiting. If one is ever rejected it is kept and flagged in red rather than discarded — a silently dropped record is worse than an obvious failure, because the pending count returns to zero and reads as success.
Either. They are separate products that work better together. A home without CareTime does not see rota screens at all — absent, rather than permanently apologising that it cannot check.
That is the normal case, not the exception, and it is why training happens on the floor rather than in a room. A carer needs four things per shift and the home screen is those four, in order. The rest is for the manager and a carer never sees it.
Yes, in full, in a readable form. Your database is separate from every other customer’s, which is what makes a clean export possible in the first place.
No. eMAR is a separate module and homes run StaffCore without it. It can be switched on later without moving anything you have already recorded.
Priced per registered bed, per month — not per resident and not per user, so adding another carer never costs more and staff accounts are unlimited. Email us your bed count and which products you want, and you will get a written quote and a service agreement back. Not a call-back form.
Aranet World, a care provider running two homes in Surrey. Both products were built for those homes and are used in them every day before they are sold to anyone else. We are a care provider that writes software, not a software company that discovered care — and we will show you the systems running on a real shift rather than a demo with invented residents.
Not a sales demo with invented residents. A walk through both systems as they are used on a shift, with your own home’s awkward questions in front of them.