About
Built from inside residential care.
Most compliance software is built by people who've never sat across from a DSS analyst. Title22 started the other way around — from real facility operations, with requirements guided by a certified California RCFE administrator.
Why Title22 exists
Title22 comes out of day-to-day RCFE operations at licensed six-bed care homes in Fresno, California — it's the tool the people doing that work wanted on shift. One place to keep the records a licensing analyst actually checks, instead of a stack of binders you scramble to reconstruct before a visit.
Where the compliance logic comes from
What Title22 flags — the staff file checks, the training and certification deadlines, what the daily briefing surfaces — is guided by a certified California RCFE administrator working with the Title 22 regulations every day, and drawn from the regulation text itself. The correctness comes from the actual rules and real facility experience, never invented by the AI. That's a deliberate line: where a requirement or its frequency isn't grounded in Title 22 or a practicing administrator's knowledge, it doesn't ship.
Who's behind it
Title22 is built and run independently — a small, self-funded software effort in Fresno, California, not a venture-backed team. That means fast iteration on real feedback, and no pressure to expand into anything that doesn't serve RCFE administrators directly.
What Title22 is — and isn't: Title22 is a documentation and readiness tool. It helps you see and close the gaps a licensing survey would catch, and makes your own good work easier to prove. It is not a certifying body, it doesn't file anything with DSS for you, and it never replaces professional judgment. And a hard line we never cross: the AI never suggests, corrects, or comments on clinical dosage — medication decisions belong to physicians and pharmacists, always.