Multi-site
Four locations, four parent communication tools, one organisation.
This is close to universal in groups above three sites, and it is worth saying early that it is not a failure of the people who run those sites. Every one of those choices was made competently by somebody solving a real problem on a deadline.
The failure is structural, and so is the fix.
How an organisation gets here.
Recognising the mechanism matters, because a rollout that implies the sites were careless will be resisted by exactly the people whose cooperation it needs.
Nobody made a bad decision. Everybody made a local one.
A new site opens, the office manager needs to reach families this week, and no central tool exists. So they pick something in an afternoon. Repeat that four times over three years and you have four platforms, each chosen competently, none chosen by the organisation.
Communication is not on anyone’s procurement list.
The practice management system gets scrutinised, negotiated and rolled out centrally, because it touches billing and everyone accepts that it matters. Parent messaging is treated as an operational detail, so it never reaches the process that would have caught the divergence.
The tools are cheap or free, so there is no invoice to notice.
Divergence usually surfaces through a purchase order. Classroom apps and consumer messengers cost nothing or almost nothing, and personal phones cost less than that, so there is no line item and no finance conversation. The first signal is often an incident.
Each site believes it is the exception.
Sites have real differences: caseload mix, staffing, the age range they serve. That makes it easy to argue locally that the central choice would not fit, which is how a standardisation effort ends with four tools and a fifth one at head office.
What the divergence costs.
Most of these are tolerable individually, which is why they accumulate unexamined. The first is not.
The compliance exposure is organisation-wide
One site on a tool with no BAA is an issue for the whole entity.
A transferring family starts over
Move between your own sites and the history does not follow.
Staff covering two sites learn two tools
Float coverage is where this bites hardest and daily.
No comparable view of anything
You cannot tell which site communicates well, so you cannot tell why one retains better.
Onboarding is different everywhere
Every new hire is trained on local habit rather than a process.
The record leaves with the employee
Where a site is on personal phones, the practice never had the record.
If any site is on a school or consumer app, start with what those vendors say about their own compliance. Several state plainly that they do not certify HIPAA compliance, which tends to end the internal debate faster than any efficiency argument.
Standardising without a rollout that stalls.
The common failure is not choosing the wrong tool. It is choosing a good tool and then rolling it out in an order that guarantees resistance.
Inventory before you procure.
Ask each site what they actually use, including the personal-phone threads, and expect the honest answer to be wider than the official one. Nobody will volunteer it if the framing is disciplinary, so the framing has to be that head office failed to provide a tool.
Pick the constraint that eliminates most options first.
For most organisations it is that families must not have to download anything or remember a password. That single requirement removes most of the market before you look at features, which makes the rest of the evaluation short.
Pilot on the site most likely to refuse.
The instinct is to start with the enthusiastic site, which tells you nothing. The sceptical site is where you find out whether the tool survives contact with a bad week, and if it wins there the rest of the rollout argues itself.
Migrate the channel, not the history.
Trying to import years of threads out of four systems is how these projects die. Set a date, move new communication, keep read-only access to the old tools for as long as your retention position requires, and accept the seam.
One platform, one agreement, every site.
Cliqit is priced per location, per month, so you can pilot one location without an enterprise negotiation and add sites as they are ready. Each site keeps its own practice management system; nothing here touches a claim.
Staff log by tapping rather than typing, which is what makes it survive a short-staffed week at the site that did not want it. The same entries carry the shift handoff and the end-of-day summary, and the practice keeps the record when someone leaves.
Questions clinics ask about this.
Why does every ABA location end up on a different parent communication tool?
Because the need is urgent and local while procurement is slow and central. A new site has families to reach in its first week and no organisational tool to reach them with, so the office manager picks something that afternoon. Each decision is reasonable; the aggregate is four platforms nobody chose. The tools are also usually free, so no purchase order ever surfaces the divergence.
Is inconsistent tooling really a compliance problem, or just untidy?
Both, and the compliance half does not stay local. If one site is running a tool that will not sign a business associate agreement, the exposure belongs to the entity, not to that site. Standardisation is usually justified on efficiency and bought on risk, because risk is the argument that survives a board meeting.
Our sites genuinely differ. Should communication really be identical?
The channel should be identical; the content does not have to be. Sites can differ in what they send and how often while using the same platform, the same access model and the same BAA. What you are standardising is custody of the record and who can see it, not clinical practice or tone.
How do we handle sites currently using personal phones?
Carefully, and not as a disciplinary matter. Staff handed out their numbers because a parent asked a reasonable question and the alternative was being unhelpful. A policy alone will not work, because it removes the solution without replacing it. The replacement has to be faster to use than opening a text thread or the threads come back.
Do we have to change our practice management system to standardise communication?
No. Sites on different practice management systems can still share one communication channel, which is often the fastest win available to a group that has grown by acquisition. Cliqit is not an EHR and never touches a claim, so it runs alongside whatever each site already has.
How is this priced across locations?
Cliqit is 299 dollars per location, per month, so a group pays per site rather than negotiating an enterprise contract before knowing whether it works. That also means a single-site pilot costs one site, which is usually the cheapest way to settle an internal argument.
Related
Show us what you are using now.
Fifteen minutes. If what you have works for your caseload, we will tell you to keep it.