Visit scheduling a family can actually see, and a carer can actually run
The scope I quote a care home that is tired of answering the same phone call all afternoon: families book visits themselves, carers log each visit with one tap, and the LINE update reaches the family before the worried call happens.
The problem it solves
“Families call to ask when they can visit, then call again to ask if mum is okay. The whiteboard never matches the LINE group, and my carers spend the afternoon repeating themselves instead of caring for residents.”
Who it is for
Residential care homes, nursing homes, and assisted-living houses where the same small team handles the schedule, the front desk, and the worried phone calls. Built so the carer on shift and the daughter overseas see the same single source of truth, on the phones they already use.
Scope of work
The build is the smallest thing that gives a worried family peace of mind without adding a single task to the carer's day.
- A family-facing visit booking with the home's real visiting hours and per-slot capacity
- Self-serve reschedule and cancel, so a changed plan does not become a phone call
- A one-tap visit log for carers: who was visited, when, and a short note if needed
- An automatic LINE update to the registered family member after each logged visit
- A staff view of today's visits, who is expected, and which residents have had a visit this week
What you own at hand-off
- The full codebase, in the care home's own repository
- Hosting, domain, and the LINE account set up in the home's name
- A plain-language runbook: add a resident, register a family member, change visiting hours
- A short staff training session, recorded, so a new carer can learn it without you
Package tiers
Essential
For
One home, visit booking and the after-visit family update working end to end.
Includes
- Family visit booking with real visiting hours
- One-tap carer visit log
- Automatic LINE update after each visit
Studio
For
Several carers and multiple registered relatives per resident, with a weekly staff overview.
Includes
- Everything in Essential
- Multiple relatives per resident, each notified
- Weekly staff overview of visits per resident
Signature
For
Care notes, gentle reporting, and the records a family or an inspector may ask to see.
Includes
- Everything in Studio
- Structured care notes attached to each visit
- Exportable visit and care history per resident
Timeline & phases
Map
A gentle first week
I shadow an afternoon at the front desk and count where the same answer gets given more than once.
A one-page scope: the visiting rules, who gets notified, and what we deliberately leave out.
Shape
Inside the same fortnight
I design the carer's log to be one tap, because anything longer gets skipped on a busy shift.
Clickable screens the manager approves before any backend is built.
Make
The build weeks
I build booking, the visit log, and the family notification as one path, so logging a visit is what sends the update, with nothing extra to remember.
A working flow on a real test number, with family updates landing in a real LINE thread.
Prove
A focused week
We run one real week through the system in parallel with the whiteboard and watch whether the phone calls actually drop.
A short list of fixes from real use, all closed before launch.
Hand-off
The final days
I move every account into the home's name and train the staff to run it without me.
The keys: code, hosting, accounts, and a runbook in plain Thai and English.
How pricing works
- Quoted per project after a short scope call. You see the full number before any money moves.
- Payment is phased against the build: a deposit to start, a milestone at a working visit log, the balance at hand-off.
- Fixed scope, fixed price. Care notes or extra homes later are a new, separately-quoted scope, never a surprise.
Assumptions
- Families are willing to register one LINE contact per resident to receive updates.
- Carers each have a phone on shift; the log is designed for a phone, not a desktop.
- One home and one manager-approver for decisions during the build.
Deliberately out of scope
- No medical-records or clinical-charting system; this organizes visits and updates, it is not a health record.
- No live video or camera feed into rooms; that is a privacy decision the family should make separately.
- No billing or invoicing in the first scope; it is a clean place to grow into, not day one.
The one decision that mattered
The update sends itself, or it never sends
The first ask is usually a family app with a chat and a feed. The real problem is that updates depend on a tired carer remembering to type one. So the one decision that matters is tying the family notification to the visit log: the carer does the thing they already do, log the visit, and the update goes out as a side effect. No new habit to build, no message left unsent.
I build the part that earns trust before the part that looks impressive. A care app lives or dies on whether the family believes what it shows, so the first thing I make work end to end is a single logged visit producing a single, accurate LINE update on a real phone.
Only after that update is reliable do families get to book and reschedule on their own. A booking screen is easy; a family that stops calling at 9pm because they already know mum had her visit is the actual deliverable.
The staff overview comes last, and it stays deliberately quiet: a calm list, not a dashboard, because the people using it are caring for someone, not watching metrics.
Search & answer visibility
- A clear, readable public page on visiting hours and how to arrange a visit, so families find the home, not a directory listing.
- Bilingual structure so a relative searching in Thai and one searching in English both land in the right place.
Outcome & what it proves
The result
Built so that carers stop repeating themselves on the phone and families stop worrying in silence, because the answer arrives before the question. The interactive demo above walks this exact flow; a real build starts from it, with the home's own design and brand applied.
What it proves
That software for care wins by removing work, not adding screens. Attach the message to a thing that already happens, and the right people stay informed without anyone being asked to do more.
Elderly-care home
Have a problem that looks like this?
One message in plain language is enough to start. I map the work, scope it fixed, and you see the full number before any money moves. I reply within one business day.