LunaKareCARE AT HOME
Contact usMy spaces

Family communication and caregiving

“You’re the One Who Lives Nearby” Is Not a Care Schedule

Living close can make a person the default helper. A fairer conversation names the work and assigns complete responsibilities.

How a default becomes permanent

Illustrative scenario: Renee lives fifteen minutes from her mother. Her brother lives two hours away. At first, Renee picks up an occasional prescription. Soon she is handling appointments, groceries, deliveries, and every unexpected call. Her brother says, “Just tell me what you need.” She cannot find the energy to explain that deciding what everyone should do has become another job.

The problem is not solved by proving which sibling loves their mother more. It needs a picture of the work. Geography affects what is practical, but it does not automatically determine who should make every phone call, organize every visit, or absorb every interruption.

Name the work without building a prosecution

Over an ordinary week, note tasks and roughly how they affect your day. Include planning, waiting, travel, and follow-up. “Appointment” might mean arranging transportation, joining the visit, picking up a prescription, and clarifying an instruction afterward. Keep the notes factual so the family can plan from them rather than argue about whether someone is exaggerating.

The National Institute on Aging recommends identifying care needs, deciding how each person will contribute, and revisiting responsibilities as circumstances change. [1] Use that as a starting point for a practical meeting with the parent included. The result should tell everyone what will happen next, not simply recognize that the nearby person is tired.

Illustrative conversation: “I can keep doing Tuesday groceries. I cannot also coordinate every appointment. Could you take responsibility for scheduling and transportation arrangements for the next month, including checking with Mom?” If a sibling cannot do that, ask what they can reliably own. A smaller dependable contribution is easier to plan around than an unlimited offer that never becomes specific.

Agree on the whole responsibility

For each task, define its start and finish. The person handling a repair should contact the provider, confirm the parent’s availability, and communicate any change. They should not send one phone number and consider the task done. Agree on how to handle delays and who needs to know.

Keep separate conversations about time and money. A sibling may contribute financially while another provides visits, but neither contribution should silently purchase authority over the parent or unlimited labor from a relative. If a task remains uncovered, name the gap and explore outside support. Do not assign it to the nearest person by default.

Make responsibility visible without scoring people

LUNAKARE Family is being developed to distinguish a notification from someone taking responsibility for it. If validated, that distinction could help families avoid the assumption that another relative has already called. A proposed acknowledgment record is a coordination aid; it should not become a public ranking of which sibling responds fastest.

The system cannot decide what is fair or make someone available. Before relying on a technology-supported arrangement, the family still needs agreed coverage, a backup, and a way to handle unanswered requests. Those human commitments are separate from the product’s development status.

A plan you can change

Renee’s family does not need to solve every future problem in one evening. They can assign the next month’s responsibilities and set a time to revisit them. The most useful outcome is a smaller burden on the person who has been filling every gap, with fewer assumptions about what living nearby should mean.

Official and reference sources

  1. National Institute on Aging — Sharing Caregiving ResponsibilitiesSource checked:2026-10-14

Eligibility, benefits, fees, and regulations may change. Confirm the latest rules with the responsible authority in your location before making a decision.

Scenarios and dialogue are illustrative, not customer testimonials. Product descriptions reflect development plans and validation limits. Sources support the stated background facts, not the product or a promised outcome.