Skip to content

Assisted living · Residential care · Memory care

Smarter care. Stronger teams. Better outcomes.

CareAssist runs your whole community on one resident record — from the first inquiry to move-in day, through care plans, the medication pass, incidents, diets and the kitchen — and keeps families close with their own portal. An append-only history and an audit trail sit behind every entry.

22
Care & operations modules
192
Automated tests
2FA
TOTP on every staff account
Append-only
Clinical record

Why communities move

Three things change in the first month.

Give the shift back to the residents

Tasks come from the published care plan, the handoff assembles itself, and the medication pass is recorded as it happens. Less of the shift spent catching paperwork up from memory.

A record that holds up

Append-only clinical history, hash-chained audit trail, and database triggers that block UPDATE and DELETE. Corrections attach as amendments showing both versions — nothing is quietly rewritten.

New staff up to speed faster

Condition flags on the roster row, structured code status, an emergency card that prints. A float caregiver who has never met these residents can still work safely.

The platform

Fourteen jobs, one record, no integrations to buy.

Explore the platform

Admissions & move-in

Inquiry, tour, a scored pre-admission assessment and a paperwork checklist — then the resident record in one step.

Family portal & visits

Families see the updates and photos staff choose to share, and request visits inside your visiting hours.

Residents & condition flags

Structured flags and code status, visible on the roster before anyone clicks into a chart.

Care plans & tasks

Published plans generate the shift's tasks. Refusals are recorded as refusals, with a reason.

eMAR with five rights

Resident, drug, dose, route and time confirmed at administration — enforced in the application.

Incidents & post-fall protocol

Filing a fall opens the observation protocol and starts your state's reporting countdown.

Diets, allergies & IDDSI

Structured allergies and IDDSI textures that reach all the way to the kitchen board.

Shifts, assignments & handoff

Who is on, who they have, and an acknowledged handoff at the end of every shift.

Hospice, providers & therapy

Co-management notes, outside providers and therapy attendance — without giving anyone a login.

Inventory from a ledger

Stock derived from movements, par-level reordering, expiry sweeps, per-resident consumption.

Menus & the kitchen board

Author the cycle once; textures derive per resident and portions tally by texture.

Reports & CSV exports

The questions asked most often, answered from the live record rather than a cached copy.

Audit trail & amendments

Hash-chained, uneditable by any role, covering reads of sensitive records as well as writes.

Downtime Pack

Generated paper — MAR sheets, summaries, emergency cards — for when the network is not there.

Built for the people using it

The same record, three very different days.

The shift, on the phone already in your pocket.

CareAssist runs in the browser on a phone or tablet — nothing to install, nothing to sync. Your assigned residents, the tasks due, and the flags that change how you approach someone are on the first screen.

  • Your assigned residents and what is due, first thing
  • Record care as you go — including refusals, with a reason
  • File an incident in your own words, at the scene
  • Condition flags and code status before you walk in the room
More for caregivers
A caregiver arriving at a residence, phone in hand, greeted at the door.

The medication pass, with the checks underneath it.

Five rights confirmed at administration, an allergy cross-check on drug stems, and an administration record that cannot be quietly rewritten afterwards.

  • Five-rights confirmation enforced, not suggested
  • Allergy cross-check matches drug stems (sulfa → sulfamethoxazole)
  • Holds and refusals recorded as outcomes, never as blanks
  • Post-fall neuro checks scheduled and chased by the system
  • Corrections attach as amendments — the original stays visible
More for nurses
A nurse scanning a medication package at a resident's side, tablet in hand.

Survey-ready as a by-product of the work.

The incident file, the audit trail and the exports are assembled continuously by people doing their jobs — not reconstructed the week a surveyor books a visit.

  • Statutory reporting windows recorded per facility, per state
  • Hash-chained audit trail no role can edit or clear
  • Resident, incident and medication exports on demand
  • Roles and permissions down to the action
  • The move-in pipeline, from first call to move-in day, on one board
  • Visit requests from families confirmed or declined in one place
More for administrators
An administrator reviewing operational dashboards at her desk.

The whole product, in the open

Every screen. Before you buy, not after.

Most vendors show you four screenshots and a video. All 35 screens of CareAssist are published on this site — real captures of the running product, admissions and the family portal included, each labelled with the route it lives at and the behaviour behind it.

/dashboard
The CareAssist Today page: overdue care tasks and open medication passes first, with counts across the top.
Dashboard
/residents/{'{resident}'}/medication-orders
The eMAR for a resident, listing active medication orders and their pass windows.
eMAR
/incidents/{'{incident}'}
An incident record with its post-fall checks and reporting countdown.
Incident detail

Engineering you can hold us to

Eight rules the software enforces, not suggests.

A prompt you can dismiss is not a control. These are enforced in the application and, where it matters, in the database underneath it.

Clinical entries are append-only

Database triggers block UPDATE and DELETE. A correction is an amendment that shows both versions, so nobody can tidy the record after an event.

Five rights are confirmed, not reminded

The administration cannot be recorded without them. A prompt you can dismiss is not a control.

Warnings never block care

An allergy or interaction warning informs the person giving the dose; it does not lock them out. Software that stops a pass creates a workaround.

Free text is never auto-interpreted

Allergies and code status are structured records. The system will not parse a sentence and act on what it thinks it found.

Timestamps come from the server

Occurrence times are normalised from the facility timezone server-side. A device with the wrong clock cannot misdate a clinical record.

Reporting defaults fail early

With no state rules recorded, the countdown defaults to 24 hours for every severity — earlier than any realistic deadline. Conservative by design, and it says so on screen.

Move-in waits for the paperwork

The resident record cannot be created until the assessment is signed and the required documents are ticked. A suggested care level is shown with every point behind it, and a nurse who approves a different level must write down why.

Family access needs a legal basis

Nobody sees a resident in the family portal until staff record why they may — the resident's consent, a power of attorney, a guardianship. Access is per resident and can be withdrawn, and the portal never shows the clinical chart.

From the first call to move-in day

Admissions on one board, not in a notebook.

Every prospective resident moves from inquiry to tour to assessment to approval on one board. The pre-admission assessment adds up a suggested level of care while the nurse answers, the checklist holds the paperwork, and move-in creates the resident record in one step — so nothing is typed twice.

  • Katz daily-living and Morse fall-risk scores, with a suggested level of care and every point shown
  • The nurse approves the level — choosing a different one needs a written reason
  • Move-in is refused until the required paperwork is in
  • Occupancy, conversion and time to move in on the same board
See the admissions screens
/admissions
The admissions board: prospective residents by stage, with open inquiries, tours, move-ins, conversion rate and occupancy across the top.
Admissions board
A woman sitting at home, reading an update about her parent's care on her phone.

Families, kept close

The good days reach the family too.

Staff share a moment, an activity or a wellbeing note — with a photo when the resident agrees — and it appears in the family's own portal. Families request visits inside your visiting hours, and you confirm them in a click. And when a daughter rings on Thursday about Tuesday, the resident's timeline still has the whole answer.

  • A separate family sign-in, invited from the resident's record with the legal basis written down
  • Updates and photos chosen by staff — the portal never shows the clinical chart
  • Visit requests confirmed or declined, with an email to the family either way
  • Access is per resident and can be withdrawn at any time

To be clear: the portal is for sharing and visiting, not for urgent questions. Two-way messaging, billing statements and two-step sign-in for family accounts are not in this build.

/family
Three phone screens of the family portal: the sign-in page, a daughter's home screen with the latest update and her next visit, and the visit request form.
The family portal, on a relative's phone

What this is, and is not

We would rather lose the deal than oversell the software.

Assisted living software gets bought on promises and lived with for years. Here is the part most vendors leave for the implementation call.

Shipping today

  • 22 care and operations modules, all built and tested — including admissions and the family portal
  • 192 automated tests covering tenant isolation, ledger immutability, five-rights enforcement, two-factor, admissions and family access — run on MySQL as well as SQLite before every release
  • TOTP two-factor on every staff account, including caregivers
  • Append-only clinical record enforced by database triggers
  • Per-facility timezone and per-facility state reporting windows
  • Runs in the browser on phone, tablet and desktop

Not built, and not implied

  • Offline charting The product tells you when the connection drops and gives you a Downtime Pack. It never pretends a note saved.
  • Family messaging, statements and family two-factor The family portal shows updates staff choose to share and books visits. Two-way messaging, billing statements and two-step sign-in for family accounts are not in this build.
  • Billing, payroll and invoicing Not in scope for this product. We will not claim a billing module we have not written.
  • GPS visit verification That is a home-care capability. CareAssist is built for facilities.
  • A native mobile app It is a responsive web application. It works well on a phone; it is not in an app store.
  • Pharmacy interfaces and SSO Roadmap. Scoped when available, not sold now.

On compliance, plainly

CareAssist is not certified, and we do not represent it as HIPAA-attested. It is built with the controls a regulated deployment needs — individual accounts, two-factor, role-based permissions, an append-only record and a hash-chained audit trail — and an external security assessment is a deferred gate we will complete with a design partner. Any vendor telling you their software makes you compliant is selling you something software cannot do.

Published pricing

Priced by beds. Never by people.

Full pricing

Home

$229/mo

Up to 12 licensed beds · one facility

Recommended

Facility

$429/mo

Up to 30 licensed beds · one facility

Campus

$699/mo

Up to 60 licensed beds · one facility

Small group

$999/mo

Up to 100 licensed beds · up to 3 facilities

Plus a one-time implementation of $1,900 — or 3 monthly payments of $800 ($2,400 in total, because carrying the balance costs something and we would rather print that than bury it).

How is it priced?

By licensed beds — never per user. Four bands: 12, 30, 60 and 100 beds, with the largest also covering up to three facilities. Staff accounts are unlimited on every plan, because assisted living turns over roughly 43% of its caregivers a year and you should not be billed for that.

What does implementation cost?

A flat $1,900, one time, covering provisioning, facility setup, your resident and medication data, role-based training and go-live. Or three monthly payments of $800 — $2,400 total, because carrying the balance costs something and we would rather print that than bury it.

What happens if we take a 13th resident?

Nothing shuts off. We move you to the next band at renewal. Locking a caregiver out mid-pass is a safety problem, not a collections strategy.

Can we get our data out?

Yes, at any time — CSV exports of residents, medications, incidents and the audit trail come from the product itself, plus a full database export on request. Not just on the way out.

See a shift run on CareAssist.

A live walkthrough on the real product — the morning medication pass, an incident filed at the scene, and what a surveyor would see afterwards.