How it works

One shared view for the people helping care.

CareLedger connects the everyday pieces of care: the person at the centre, the people helping, the plan for the day, and the updates that make a handoff easier.

The CareLedger approach

Good care coordination is not about adding more administration. It is about making the right context visible at the moment someone needs to act.

01

Care coordination starts with a shared view

When several people help care for one person, the difficult part is often not willingness. It is the space between what one person knows, what another person assumes, and what still needs to happen. A message can be missed. A notebook can be out of date. A family conversation can answer today’s question without creating a reliable record for tomorrow. CareLedger gives a care circle one calm place to make the everyday plan visible.

The product is designed around coordination rather than clinical complexity. You can see what is scheduled, identify who a care item belongs to, record what happened, and leave a useful update for the next person. That makes it easier to move from “I think someone handled that” to a shared understanding of the current day. The point is not to turn family care into administration. The point is to remove the avoidable uncertainty that makes family care feel heavier than it already is.

02

Start with the person receiving care

Every care circle has a person at its centre. CareLedger keeps that person distinct from the signed-in account and from the wider care team. That distinction matters because the person receiving care may not be the person creating the plan, and the person creating the plan may not be the person completing every task. Keeping those entities clear helps the app communicate accurately: whose routine is this, who can see it, and who recorded the latest update?

A care recipient profile can hold the practical context a circle needs for everyday coordination, such as routines, preferences, and general care information. It is not intended to become a complex clinical record. The structure is deliberately focused on the information that helps trusted people support a shared day without implying that CareLedger is a diagnostic or treatment system.

Choose the selected care recipient before reviewing the day.

Keep care-recipient details separate from personal account settings.

Link the people who are actually helping with this person’s care.

03

Build a care plan that reflects real life

A care plan is more useful when it contains the whole shape of a day, not just one category of reminder. CareLedger supports everyday tasks, routines, appointments, and other care items as distinct activities. That gives a family room to plan the practical work around care: checking in, preparing something, arranging transport, following a routine, or recording a handoff. Each item can be reviewed in context instead of disappearing into a single undifferentiated list.

Recurring items are created through frequency choices and suggested times rather than manual date construction. The person creating the item can review each suggested time, edit the schedule, choose a start date, and add optional details after the essential setup is complete. This reduces typing while keeping the user responsible for confirming that the schedule reflects the instructions and circumstances they already have.

Medication-specific functionality, when enabled, remains truthful about what the item is. General navigation does not need to be medication-first, but a medication screen should not hide a medication action behind vague language. This is part of making coordination easier without making claims the product cannot support.

04

Invite people with clear roles

The right care team is not necessarily the biggest care team. CareLedger makes invitations specific to a care recipient and explains the invited person’s role before access is sent. An owner can manage the care recipient, care plan, invitations, and permissions. A caregiver can view the information assigned to them, complete care items, and add permitted notes or updates. The minimum role model stays understandable so families can make decisions without learning an enterprise permissions system.

A good invitation flow answers four questions before the message goes out: which person is being supported, who is being invited, what will that person be able to do, and what happens next? CareLedger keeps those questions together. After an invitation is sent, the circle can see its pending status. That is more useful than asking someone to check their inbox and hoping everyone remembers whether access was accepted.

Personal account settings remain personal. Authentication methods, notification preferences, privacy, terms, and account deletion live under the user’s account rather than inside an ambiguous circle menu. This separation helps prevent the common mistake of changing the wrong person’s information while trying to manage the team.

05

Use Today for the next useful action

The Today view is designed for scanning. It should answer what is next, what has been completed, what needs attention, and who an item belongs to. Scheduled times are easy to find, item titles carry more visual weight than metadata, and tasks remain distinguishable from medication-related items. A selected care recipient is visible when a user manages more than one person, so the timeline does not become a list without context.

A clear status is more than a colour. CareLedger uses words and interaction states for upcoming, completed, skipped, missed, and needs-attention outcomes. The card can be completed directly, while less common outcomes remain available through a deliberate secondary interaction. Tapping the card body opens more detail, including the schedule and activity history, so the main page can stay readable without hiding the context a caregiver may need during a handoff.

06

Leave a handoff, not just a checkmark

A checkmark tells the next person that an item was recorded as complete. A handoff helps them understand the situation around it. CareLedger’s Updates area brings together completed items, notes, changes, and caregiver activity so a circle can review what has happened without searching through separate conversations. The history is intended to be practical: what changed, when it changed, and which caregiver recorded the update when that information is available.

This does not mean every moment needs a long note. Most care coordination should remain lightweight. The value comes from making the important changes findable when a family member joins later, a routine changes, or someone needs to understand why the day looks different from the original plan. A useful shared record is selective, readable, and honest about what it knows.

07

Designed for trust and boundaries

Care information deserves careful handling because it relates to a real person and a real relationship. CareLedger separates care-recipient information, care-team collaboration, and personal account controls. It explains notification permissions before asking for them, keeps permission requests contextual, and provides access to privacy and terms before account creation as well as from settings.

The product language also matters. CareLedger describes itself as a place to coordinate care, not as a source of diagnosis, treatment recommendations, or emergency support. If a feature genuinely handles medication information, it should say so in that context. Softer words cannot change what a feature does, and clear language is better for the people using it and for the policy obligations that follow from actual behavior.

08

A calmer system for the people doing the work

Family care rarely follows a perfect plan. People work different schedules, live in different places, and step in at different moments. The system needs to be useful when one person is planning ahead, when another is arriving for a handoff, and when someone simply needs to know whether an item was already handled. CareLedger brings those moments into one design language instead of asking the family to remember which tool contains which part of the day.

The best starting point is small: choose the person, add the essential care items, invite the people who need to help, and use Today and Updates consistently. Over time, the shared record becomes more valuable because it reflects the circle’s actual routines. CareLedger is built to make that consistency easier without asking a family to become a project-management department.

09

A calm workflow for changing days

No care plan stays identical forever. A person’s routine can change, a caregiver can be away, a task can become unnecessary, or a new helper can join the circle. CareLedger treats those changes as normal states rather than exceptional failures. The plan can be updated, the team can be reviewed, and the activity history can show what changed so the next person is not working from an invisible version of yesterday.

The workflow is designed to keep the decision close to the relevant context. Edit the item where it lives, review the updated schedule, and use Updates to understand the resulting handoff. That is more reliable than making a change in one place and explaining it from memory somewhere else.

Common questions

Questions families ask about CareLedger.

Clear answers help a care circle decide whether the product fits the way they already share responsibility.

What is CareLedger for?

CareLedger helps families and trusted helpers coordinate everyday care through shared care items, routines, reminders, updates, and handoffs.

Who can use a care circle?

A person organizing care can invite family members or other trusted caregivers to a specific care recipient. Roles stay separate from each person’s personal account.

Does CareLedger provide medical advice?

No. CareLedger is a coordination and record-keeping tool. It does not diagnose, recommend treatment, or replace professional advice or emergency services.

Can I join without the app installed?

Yes. An invitation opens a web handoff that can direct you to the app store and preserve the invitation context for the app flow where supported.