CARES IO — one workspace for the approval journey.
Built for the licensed child-welfare workflow: inquiry, application, training, assessment, approval, placement support, communications, records, and quality — in one place, with the evidence produced by the work instead of assembled afterward.
CARES IO is in staged development. It is not a finished product and we do not sell it as one. Below is the current status of every capability area. Nothing enters your real work until your organization has accepted it in writing, and we will never describe a capability to you, your board, your auditors, your funders, or your accreditors as available before that has happened.
A family record entered once. Document requirements, approval gates, notifications, and drafting support tied to a named step in the approval journey, so the file assembles itself as the work is done. A supervisor able to see a single current picture of a home’s status. And when a licensing analyst, a county, an accreditor, or your auditor asks for a file, an answer that does not take three days.
The platform is multi-tenant. Your data, users, roles, branding, policies, and training content are isolated from every other tenant. Your staff operate your tenant.
Last updated: 26 August 2026. Three statuses are used: In development — being built, not available for use. In pilot — accepted by at least one organization and in limited use. Available — accepted and in production use.
| Capability area | What it is designed to do | Status |
|---|---|---|
| Tenant administration and identity | Administration, credentials, role-based access, environment controls | In development |
| Case and family pipeline | Pipeline visibility, workload, compliance tracking | In development |
| Approval tracker and gating | An eight-step approval journey with document gates | In development |
| Adaptive forms and autofill | Accessible intake, master-profile autofill | In development |
| Document intelligence and version control | Classification, versioning, requirement matching | In development |
| Communications and logging | Multi-channel communication logged to the family and agency timeline | In development |
| Electronic signature and document routing | Signature with audit trail; intake routing to the correct record | In development |
| Scheduling | Scheduling with travel awareness and compliance logging | In development |
| Reference collection and review | Structured reference gathering and review support | In development |
| Drafting support | Draft assessment and affidavit text for staff review and acceptance | In development |
| Gap and consistency analysis | Missing-document and consistency checks with source linkage | In development |
| Placement support | Referral-response and matching aids; staff decide all matches | In development |
| Learning and certification | Training tracking and course authoring | In development |
| Policy and knowledge library | Version-controlled policy library and decision trees | In development |
| Analytics and dashboards | Operational analytics and leadership dashboards | In development |
Your data is yours.
Export everything, at any time, in an open machine-readable format, within ten business days. A production export test is part of every closeout. We do not use your data to train models for other clients.
You keep what you fund.
If you fund the development of capability, you receive a perpetual, royalty-free right to keep using it — including after our engagement ends. A nonprofit should not spend charitable dollars building an asset it retains no interest in, and we will not ask you to.
People decide.
Where the platform drafts a document or scores a referral, the output is a draft. A qualified member of your staff must review and accept it, and the system is built so that step cannot be skipped. Software does not make approval, placement, or eligibility decisions.
Role-based access enforced on the server, tenant isolation across application and storage pathways, tamper-evident logs for material events, and confidence, explainability, and human override switched on by default. The platform is architected to support the workflows required by HIPAA, FERPA, and Resource Family Approval. Architecture is not a substitute for your organization’s own compliance obligations, and we will not tell you otherwise.
We will say so, and we will run the selection for you. Our platform work exists because parts of this market have no product at a price the sector can bear — not because we think you should buy ours.