Visit scheduling a family can actually see, and a carer can actually run

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.

I built 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

• 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

1. Map

   A gentle first week

   I shadowed an afternoon at the front desk and counted where the same answer was given more than once.

   A one-page scope: the visiting rules, who gets notified, and what we deliberately leave out.

2. Shape

   Inside the same fortnight

   I designed the carer's log to be one tap, because anything longer would be skipped on a busy shift.

   Clickable screens the manager approved before any backend was built.

3. Make

   The build weeks

   I built 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, family updates landing in a real LINE thread.

4. Prove

   A focused week

   We ran a week with real families and watched whether the phone calls actually dropped.

   A short list of fixes from real use, all closed before launch.

5. Hand-off

   The final days

   I moved every account into the home's name and trained the staff to run it without me.

   The keys: code, hosting, accounts, and a runbook in plain Thai and English.

• 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.

• 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.

• 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 update sends itself, or it never sends

The manager first asked for a family app with a chat and a feed. The real problem was that updates depended on a tired carer remembering to type one. So the one decision that mattered was 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.

• 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.

The result

Carers stopped repeating themselves on the phone and families stopped worrying in silence. After-visit calls to the front desk dropped noticeably, because the answer arrived before the question.

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.