A mobile caregiver app is judged on one thing: whether the visit record holds up.
Somebody stood in a kitchen at 07:40, helped a man out of bed, made him breakfast and left at 08:35. A mobile caregiver app exists to turn that hour into a record a payer, a family member and an inspector will all accept. Everything difficult about this category sits in that sentence, not in the scheduling grid people usually build first. It shares a reader with senior care apps and a much heavier set of obligations.
This page covers the six facts a visit has to carry, why a caregiver rota is really a travel problem, what to do with notes and photos of a named person, and what the app does when the house has no signal.
See what a visit record has to proveThe short version
The rota is the easy half, and the visit record is the part that has to hold up.
Two questions decide whether a caregiver app is worth running. Can the visit that happened be proved afterwards, in enough detail that nobody has to take anyone's word for it. And can the caregiver finish that record standing in the house, in under a minute, one handed.
Most homemade tools get the first one partly right and the second one badly wrong. A record that takes nine taps gets filled in later, in the car, for three visits at once. At that point you own a system that produces confident data about things nobody observed.
Six facts a visit has to carry
If any of the care is paid for by Medicaid, the shape of the record is not a design choice. Federal law requires states to use electronic visit verification for personal care services and home health care services that need an in-home visit. The statute lists what the visit is verified with respect to: the type of service performed, the individual receiving the service, the date of the service, the location of service delivery, the individual providing the service, and the time the service begins and ends.
Those dates have passed. Personal care services came under the requirement for quarters beginning on or after 1 January 2020, and home health care services on or after 1 January 2023. States decide how their system works and who is allowed to supply it, so the rules you actually have to satisfy are your state's. Read them before you draw a screen.
Even well outside Medicaid the list is a good specification. Every item on it is a fact rather than an opinion, and most can be captured without the caregiver typing anything. That is the bar worth building to: the phone records, the caregiver confirms.
Location is the element that causes arguments. A phone reports where it thinks it is, with an accuracy figure attached, and indoors that figure is not always small. Store the accuracy next to the coordinates. A record saying the caregiver was within 12 metres of the address is evidence. A 400 metre fix quietly drawn as a pin on the house is not.
42 U.S.C. 1396b(l), electronic visit verification requirement
Try it
What your visit record can prove
Switch off anything your current system does not capture.
4 of 6 captured
Missing: Location of service delivery, Time the service begins and ends. That gap is the part somebody fills in later from memory, which is where disputes start.
A caregiver rota is really a travel problem
The calendar view is the part people demo and the least interesting part of a caregiver scheduling app. The real constraint is the gap between two visits. Travel from job site to job site during the workday, including travel between several clients, is compensable hours worked, and the third party employer is responsible for making sure it is paid. Normal travel from home to work and back at the end of the day is not work time.
That one rule turns the schedule from a list into a graph. Two visits an hour apart in the same street are cheap. The same two across town cost a paid half hour nobody planned. So put the travel gap on the screen beside the appointment, in minutes, at the moment the coordinator drags something. A rota that shows only start times hides your largest avoidable cost.
Continuity is the second constraint and it fights the first. Families ask for the same two or three faces, and for personal care there are good reasons to give them that. Filling a shift and keeping the pairing pull in opposite directions, so show both when a swap is made rather than letting the breakage turn up on Monday.
Be clear which business you are in, because the obligations differ. Personal care is help with washing, dressing, meals and moving about. Skilled clinical work at home, the kind a home health care app is built around, brings orders, clinical documentation and supervision with it. Plenty of trouble comes from one app trying to be both without admitting it.
Notes, photos and who is allowed to read them
The visit record proves attendance. The note says what happened, and it is the thing somebody reads in a hospital at three in the morning. Structure the parts that repeat: fluids taken, food eaten, medication prompted, mood, skin, anything that changed since the last visit. Leave one free box for the rest. A single free box for everything produces paragraphs nobody can search six weeks later.
Photographs are the best record of a pressure sore or a bruise and also health information about a named person sitting in a camera roll. Decide on day one whether images live inside the app's own storage or on the device, and treat that as a decision rather than a default you discover later.
Where the care is delivered by a covered organisation, that note is protected health information and the handling rules travel with it. It is the same problem a hipaa compliant note taking app exists to solve, and the answer is rarely a feature. It is a list of who may read what, enforced on the server rather than by hiding a button in the interface.
Family access is the feature everybody asks for and the one to design slowest. A daughter three hours away wants to know her father ate today. She should not automatically see a caregiver's note about a safeguarding concern. One record, two audiences, so the split has to be a field on the note rather than a habit in somebody's head.
What happens in a house with no signal
Care happens in basements, in thick stone cottages, in flats at the end of a corridor where the lift eats the last bar. An app that needs a network to record a visit will lose visits: rarely enough to survive your testing, often enough to matter in a payroll dispute or an audit.
We did not test this for this page, and the Newly documentation does not describe offline behaviour, so treat any claim about it as unverified until you have watched it happen. The test is quick on any tool you are considering, including ours. Turn the radio off, complete a visit, close the app, turn the radio back on, then check the record came back carrying the original arrival time rather than the time it finally uploaded.
The design that survives does not depend on the answer. Write the entry to the device first, stamped with the device clock, then queue the upload and show the queue. Three visits waiting to send is something a caregiver can act on. A silent spinner is not. Holding visits in houses with no signal and reconciling them afterwards goes further than this page does.
Decide one more thing before you build. What does the app do when the phone insists the caregiver is somewhere else? Refuse the check in and you strand a real person at a real visit. Accept it silently and the location field means nothing. Record the mismatch, let the visit continue, and put it in a short queue a coordinator reads in the morning.
What each approach gives a caregiver and a coordinator
| Option | Arrival and departure captured | Survives no signal | Travel gaps visible | Notes the family can see |
|---|---|---|---|---|
| Paper timesheet | written from memory | Yes | No | No |
| Group chat and a spreadsheet | typed later | Yes | No | all or nothing |
| Telephone check in | Yes | needs a working phone line | No | No |
| Agency platform | Yes | varies by product | Yes | if the plan includes it |
| An app you build | Yes | if you build for it | Yes | Yes |
Building one around your own rounds
Agency platforms are priced per caregiver per month and shaped around an agency of a certain size. A team of nine covering two postcodes usually needs a fraction of that. It also needs two things the platform will not do: a client whose key safe code changes monthly, and a visit only somebody trained to hoist can take. The gap is not features. A home care app that fits your rounds is smaller than the platform and fits better.
Newly is an AI app builder. You describe the app you want, including the rules your rounds actually have. It writes a real React Native and Expo project you own, and runs it on a cloud phone while it builds. Plans start at $25 a month, there is no free plan, and iOS ships through TestFlight using your own Apple Developer account. Android goes to Google Play internal testing from the Deploy tab, or out as a standalone APK. Nothing here is a state certified electronic visit verification vendor. If your funding depends on certification, settle that question before you write anything.
Start with the smallest thing that removes the worst pain, which is almost always the visit itself: arrive, confirm, note, leave. Leave scheduling wherever it lives now for a month. You will learn more from twenty real visits recorded properly than from a rota screen nobody trusts yet.
Questions people ask about caregiver apps
An app a care worker carries into somebody's home to record the visit: who was seen, what was done, when it started and ended, where it happened, and anything that changed since last time. The scheduling side matters, but the record is the part other people rely on afterwards.
Describe the rounds your caregivers actually do
Write down what a visit has to record and what should happen when the phone has no signal, then build the app around those two answers.
Start building