A few years into the modern category of family caregiving software, shared caregiver workspace has become accepted shorthand for a particular kind of product: a place where two or three or four siblings can all leave notes about Mom, see each other's updates, share a calendar, file a power-of-attorney scan in the same vault. The phrase is everywhere on caregiver-app landing pages, including ours. It is also doing less work than it sounds like.
The question hiding inside it is: shared with whom?
In most of the apps in the category, the answer turns out to be: shared with the caregivers. The siblings can read each other's notes. The cousin in Houston can drop a question into the feed. The home-health aide can see Mom's schedule. The cardiologist can be sent a link. The single person who is conspicuously left out of the shared caregiver workspace is, in many of these products, Mom — the person being cared for, the person whose body and life and decisions the whole workspace is organized around.
That is not a small oversight. It is the difference between an app that helps a family carry a parent and an app that helps a family carry a parent while she watches.
Three failure modes
There are three common ways an app advertised as a "shared caregiver workspace" excludes the cared-for person from participation:
1. Language. The workspace is English-only. The parent reads in Mandarin, Korean, Spanish, Vietnamese, Tagalog, Cantonese, Tagalog-English code-switch, Punjabi, Russian, or any of the seventy-plus languages spoken in American homes. The bilingual daughter holds the translation work, in real time, all the time, alone. The "shared" workspace contains updates the parent cannot read.
2. Role. The parent is given a "view-only" or "patient" role with restricted visibility, or no role at all — they are present in the workspace as the subject of records rather than a member with login credentials. Most family-caregiving products were designed under the implicit assumption that the patient is too old, too sick, or too overwhelmed to participate. That assumption is sometimes true. It is, in the average case, wrong. Aging parents who can read a phone screen can read their care plan, and many want to.
3. Attention. Even when the parent has a login and reads the same language, certain notes are written for the caregivers about the parent in a register the parent is not meant to see. "Mom seems more confused this week." "Dad's hygiene is slipping." "I think we should start the conversation about giving up the car." Caregiver-only notes are a real necessary surface — there is information the family needs to coordinate without putting it directly to the patient yet — but a workspace that defaults to caregiver-only writing, with no transparency to the patient that those notes exist, builds a parallel record that excludes the person it describes.
A product can solve any one of these and still fail the test. A product can solve all three and still feel exclusionary if the patient doesn't realize they have access. The bar is not "is there a setting"; the bar is "does the parent participate in their own care."
Why this matters more than it used to
Two demographic facts make the bar higher than it was ten years ago. First, more than 67 million Americans speak a language other than English at home, and roughly 25 million speak English less than "very well." A meaningful share of those are aging. A meaningful share of their adult children read English as their primary language. A workspace built for the family that all reads English will systematically fail the family that doesn't.
Second, the population of older adults using smartphones daily has crossed over 75% for ages 65–74 and continues climbing in the 75+ bracket. The assumption that "she's old, she won't use it" is doing less work than it did. The mother who hesitates to use a new app for two weeks will, often, settle into it and start reading her own care plan on her own phone — if the app gives her something readable to read.
What used to be a fair design simplification ("the caregivers will use the workspace; the parent is the subject of it") is no longer a fair design simplification. It is a choice with a cost.
What "shared" should mean
A useful working definition: a shared caregiver workspace is one where every member of the family — including the person whose care it concerns — can read what's happening, in a language they actually read, with a documented role and a documented basis for being included.
That definition has four parts. Each one is testable, and each one quietly disqualifies a lot of what the category currently markets.
A shared caregiver workspace is one where every member of the family — including the person whose care it concerns — can read what's happening, in a language they actually read, with a documented role and a documented basis for being included.
Can read what's happening. Not just the caregivers. The patient too, by default, with caregiver-only as a deliberate exception they know exists. The activity feed feature in Kintaria is built around this: every member with read access — including the parent role — sees the same timeline of who changed what, when, and on what basis.
In a language they actually read. This is what Kintaria's bilingual workspace does: every English note is automatically translated to the parent's preferred language and shown side-by-side, so a mother in Queens can read her after-visit summary in Cantonese while her sons in Cleveland and Phoenix read it in English, on the same record. The English original is the artifact of record; the translation is the bridge.
With a documented role. Family members + roles makes membership explicit — owner, caregiver, observer, parent — and every change in the workspace is stamped with the role at the moment of writing.
With a documented basis for being included. The consent basis feature records why every workspace member has access — family member helping coordinate, healthcare power of attorney, court-appointed guardian, HIPAA personal representative. The basis is visible to the family and snapshotted in the audit log, so any future hospital, attorney, or court can see who authorized what, when, on what grounds.
These four together are what we think the phrase shared caregiver workspace should mean. They are also, not coincidentally, the four design decisions that took the longest to get right, and that we are most willing to be argued with about as the category matures.
The honest comparison
We've written a direct comparison with TendTo, the caregiving workspace closest in shape to Kintaria. They have a clearer marketing surface than we do in some places. They built broad coverage on the financial-and-document side of caregiving — the bills nobody else is paying — and they ship features quickly. For a single-language family whose hardest caregiving problem is paying Dad's electric bill on time, TendTo is probably the right tool.
What we chose to optimize for is different. We went narrower and deeper on the clinical, linguistic, and consent-infrastructure side — the bilingual workspace, the medical timeline, the recorded consent basis that an estate attorney or hospital social worker would actually trust, the audit log that follows the role and the basis as well as the action. We did this because of the failure modes above: the family where Mom reads in Mandarin and her American-raised kids read in English; the family where Dad's cardiologist and rheumatologist disagree about the prednisone taper; the family where the sister is the court-appointed guardian and every change to her father's record needs to be stamped with her consent basis. Those are the families we built for first.
If the phrase shared caregiver workspace is to mean anything sturdy, it has to include the person being cared for. That is the test. We hope the rest of the category moves toward it.