About
Written by someone who is on the floor.
Most software for ABA clinics is written by people who have never run a session. That is not a moral failing, but it shows, and it shows in exactly the places a technician notices and a buyer does not. This page exists so you know which kind of thing you are reading.
Who is writing this.
I am Abdihafid, a behavior technician. I work in an in-person ABA clinic, with autistic children, on the floor, on shift. Cliqit came out of the parts of that job that were obviously broken and obviously fixable.
The specific thing that started it: a parent asking me at pick-up how the day went, and me not being able to answer properly, because the child had been with two other technicians before me and everything they had learned was in their heads or on a sticky note. I could describe my own ninety minutes. Nobody could describe the day.
That is not a documentation problem, it is a shape problem. The clinic had systems for billing and systems for clinical data and no system at all for the thing that happens between a child arriving and a child leaving. So the answers got improvised at the door, every day, by whoever happened to be standing there.
What Cliqit deliberately is not.
Cliqit is not an EHR, not a practice management system, and it never touches a claim. It does not collect trial-by-trial data and it will not replace the system your BCBAs write programs in. Keep CentralReach, Rethink, Motivity, Theralytics or whatever you already run.
That restraint is the product decision, not a gap in the roadmap. The moment a communication tool starts reaching for clinical data collection it becomes something a technician has to be trained on, and a tool that needs training does not get used at 4pm on a hard day. It has to be fast enough to use one-handed between sessions or it is worth nothing.
How the guides on this site are written.
Where a page says something about another product, it quotes that product’s own documentation and links to it, with the date the quote was last checked. We do not repeat what a competitor says about a competitor, and we do not describe a tool as non-compliant because it suits us to. Several of the tools discussed on this site are perfectly good at the job they were built for.
Where a page makes a claim about how clinics behave, it comes from working in one. Any of it can be wrong, and if you run a clinic and something here does not match what you see, I would rather hear it than not.
Tell me where I am wrong.
Fifteen minutes. If what you have works for your caseload, I will tell you to keep it.