About
Built inside a working agency, not a boardroom.
ClientCentric did not begin as a product. It began as software written to solve one licensed provider's operational problems — a home- and community-based care agency, and the problems that never appear in a feature list but decide whether a week goes well: a visit nobody documented, hours nobody could reconcile, a client record four people had a different version of.
Every workflow in it exists because somebody needed it on a particular Tuesday, not because a competitor had it. And because the requirements it grew up under are among the strictest in home and community-based care, the platform is layered to travel: a state configuration, a program configuration, and an agency configuration — never a fork per customer, and never a guess about where a legal requirement belongs to you.
That is also why it is opinionated in places.
Each of those choices is the difference between a record and a document.
An approved case note locks and can only gain addenda. A missed clock-out is closed at the shift's scheduled end and flagged for review, never stamped with the time somebody happened to notice. Access follows assignment, immediately, in both directions. Those are not configuration options.
The product has been validated across owner, administrator, staff, client and authorized-representative workflows, and tested across role-based access, assignment visibility, direct-URL restrictions, documentation lifecycles and end-to-end agency workflows.
What we will not claim
We do not say unhackable, or impossible to breach, or fully compliant in every circumstance. Compliance depends on your agency's arrangements, your policies and your agreements — software supports it and cannot confer it. Where a claim would need proof we do not have yet, we leave it out.