How it works
Six parts, one record.
Kinbase has a small job it takes seriously: remember everything about your parent’s care, and give the right piece of it to whoever needs it, when they need it. Here is the whole product.
You say what happened, confirm it, and it is written down.
Whoever is with your parent holds the mic and says what happened: “she ate half her lunch, said she wasn’t hungry.” Kinbase turns that into a dated entry and shows it back for a one-tap confirmation, whether it is a meal, a med, a fall, a mood, or an appointment. A visit takes about thirty seconds to log, which is why people keep doing it.
Voice in, structured entry out, you confirm
The timeline keeps the handbook honest
The handbook writes itself from the timeline.
When the same fact shows up in entries twice, Kinbase suggests adding it to the handbook, and you approve or dismiss: routines, med tricks, the things that upset her, the things that settle her. When a new caregiver starts, you send one link and she reads it before her first shift.
The record answers three questions on its own.
“What would a doctor need in an emergency?” produces the emergency sheet: meds, conditions, baseline, recent falls, one link, no login. “How was Mom this week?” becomes the Sunday digest your siblings get by email. “What should a new agency know?” compiles into a packet. Nobody writes these; they are put together from what was already logged.
Compiled from the record, not written by you
Four roles, set by you, changed anytime
Everyone in her care works from one record, on your rules.
You invite people by link, by email, or with a QR code: show the code, they scan it, they are in. Each person gets a role. Family reads everything and can write. Caregivers write entries and read the handbook. An agency sees what you choose to share, and stops seeing it if you leave. A relative who only wants the Sunday email can be added by address alone. No account, nothing to install. A caregiver who moves on can let themselves out, and when they do they take nothing with them, though every entry they wrote stays in the record. Nobody needs to install anything to join.
The medication list keeps itself, and reminds the phones that ask it to.
Every medication your parent takes lives in one list: the name, the dose, the reason. That list is what the emergency sheet reads from, so a doctor never gets a copy from two hospitalizations ago. Put a reminder time on a medication and the phones that opt in get the nudge at the right hour, while the ones that don’t stay quiet. When a dose changes, you change it once.
One list, on the emergency sheet, reminders where wanted
Open shifts, shared tasks, and the family thread in one place
The week runs on a shared list, not a group text.
Tasks live where the whole circle can see them, so a job is either done or waiting, never buried in someone’s inbox. The family chat sits beside the record instead of in a separate app. And when a caregiver cannot make Thursday, the visit shows up as open, a family member flags it, and someone taps once to cover it.
The whole system, briefly
Six parts, working as one record.
Each part feeds the next, so the record only gets more useful the longer your family keeps it.
Whoever is with your parent says what happened, and Kinbase turns it into a dated entry you confirm with one tap.
When the same fact shows up twice, Kinbase offers to add it, so a new caregiver can read it before her first shift.
The emergency sheet, the Sunday digest, and the agency packet are put together from what was already logged, not written by you.
Everyone you invite works from the one record, each with a role you set and can change anytime.
One medication list feeds the emergency sheet, and reminder times reach the phones that opt in.
Shared tasks, family chat, and visit coverage: when a caregiver cannot make Thursday, someone taps to cover it.
Start your family’s record.
Name the book, invite the people who help, and the record starts keeping itself. Most families are set up inside ten minutes.
Free for families to start. Everyone you invite joins from a link or by scanning a code, and nobody has to install anything to read or write.