A formal orientation for state agencies, county agencies, courts, law enforcement, advocacy organizations, healthcare systems, nonprofits, and institutional funders evaluating the iCARE Ecosystem as a housing-stability and cross-system accountability infrastructure.
Scope note: iCARE is the policy framework and institutional coordination environment. B.E.A.T. (community safety and accountability software) is a distinct application that may be deployed within that broader ecosystem. This white paper lives inside iCARE; it does not describe, bundle, or substitute for B.E.A.T. as a product.
Federal, state, county, and municipal agencies; courts; law enforcement; advocacy organizations; healthcare systems; nonprofits; institutional funders; and the households moving through instability.
A persistent system failure: siloed intake, unduplicated records that re-traumatize households, and accountability gaps between funders, agencies, and frontline providers.
Across intake, risk identification, referral, service coordination, case review, and policy evaluation — the full intervention and oversight lifecycle.
Across jurisdictions and partner networks, jurisdiction-agnostic, connecting federal, state, and local systems through configurable integration points.
Public value: reduced duplication, demonstrate outcomes, cross-system accountability, and a defensible record of who did what, when, for whom.
Phased implementation, tiered pricing and licensing, role-based training, constitutional governance, and measurable evaluation — see the sections below.
iCARE is the integrative policy framework and institutional coordination environment of the MoveQuest Ecosystem™. It provides a shared housing-stability and cross-system accountability infrastructure that links intake, risk identification, referral, service coordination, case review, and policy evaluation into a single, governance-backed record.
For agency executives, procurement officers, grantmakers, legal and compliance teams, and program directors, iCARE answers a single question that legacy point solutions cannot: across every organization and jurisdiction involved, who intervened, when, for whom, with what funding, and to what measurable effect. iCARE is the coordination environment; applications such as B.E.A.T. may be deployed within it as discrete, replaceable components.
The households most in need of stability interact with the most organizations, yet those organizations rarely share a common record. The result is a system failure, not a software gap: duplicated intake, orphaned referrals, invisible funding, and records that cannot survive an audit.
Households repeatedly re-tell their story at every door — courts, shelters, hospitals, agencies — producing duplicated, inconsistent records.
Referrals leave a household in the queue of another agency with no closed loop, so no one owns the outcome and gaps go unseen.
Funders cannot confirm whether dollars produced intervention, only that dollars were spent.
Without a shared governance layer, oversight reviews reconstruct events from memory and email rather than a verifiable chain of activity.
Value to a public agency is not another system of record — it is the connective tissue that makes the systems the agency already operates legible to oversight, funders, and partner organizations.
A shared, governance-backed activity layer means the interventions for each household are visible across authorized partners without duplicating the source data each agency owns.
Every action — intake, referral, service, review — is captured with actor, timestamp, and funding source, producing records that withstand legal, compliance, and grant audits.
Measurement is structured around stabilization and mobility outcomes, so funders demonstrate return on public investment rather than transaction counts.
iCARE is jurisdiction-agnostic; a county program, a state pilot, and a federal initiative can all operate on the same coordination standard.
Because iCARE is the coordination environment and not a captive application, applications such as B.E.A.T. can be deployed, evaluated, and replaced without rebuilding the governance layer.
A constitutional governance framework and role-based access controls give agencies a defensible answer to the question of who saw whose data, and why.
Each stakeholder interacts with iCARE from a different seat and retains ownership of its own records. iCARE governs only the connection points, the accountability layer, and the shared standards.
Set program standards, fund pilots, and receive cross-system outcome reporting across counties and providers.
Operate frontline intake, referral, and coordination on the shared record; own local case data.
Verify intervention chains, conditions of release, and compliance for housing and safety-related matters.
Coordinate safety referrals and accountability through B.E.A.T. where deployed, surfaced in iCARE.
Represent households, submit referrals, and contribute to case review without holding a system of record.
Connect discharge-to-housing pathways and behavioral-health referrals into the stabilization record.
Deliver services against coordinated cases and report outcomes to funders.
Fund, sponsor, or license the framework; receive auditable outcome reporting tied to disbursements.
iCARE is used across the full intervention and oversight lifecycle. The same record that supports an individual case also aggregates into policy-grade evaluation.
A household enters at any door — court, shelter, hospital, agency — and a coordinated record begins without re-telling the full history.
Risk flags (housing, safety, health, financial) are captured once and surfaced to authorized partners under governance rules.
Referrals carry context, consent, and an owning party, closing the loop so a household is not lost between queues.
Multiple providers act on one case with shared milestones, communications, and a single accountability timeline.
Courts, program directors, and oversight bodies review a defensible chain of activity rather than reconstructed narratives.
Aggregated, governance-filtered data lets funders and administrators measure what worked, for whom, at what cost.
Implementation is phased so an agency never replaces its system of record. iCARE layers on top, connecting existing systems through webhooks and governing only the standards and activity that must be shared.
Agency completes the six-dimension readiness assessment (accountability, data security, contracting, funding, reporting standards, tracking) and maps existing systems to integration points.
Constitutional Governance overlay applied; funding agreement and data-sharing terms configured through the agreement builder and reviewer workflow.
Agency webhook account issued with rotated secrets; existing case-management systems connect via the service registry without replacement.
Role-based seats provisioned (admin, agency, partner); standardized training on intake, referral, coordination, and review procedures.
Scoped pilot run on defined cohorts and geographies, or full rollout, with measurement and reporting dashboards active from day one.
Ecosystem certification audit validates controls; ongoing governance audit log maintains a defensible, time-ordered record of activity.
iCARE is designed to fit the way public money actually moves — grants, pooled funds, outcomes-based contracts, and subscriptions — rather than forcing a single commercial model.
Pilot or program funded by a state, federal, or philanthropic grant; disbursement and outcomes tied through the agreement builder.
Multiple jurisdictions or funders pool into a single coordinated cohort, sharing infrastructure cost and outcome reporting.
Payment or milestone releases tied to verified stabilization and mobility outcomes, reported through the evaluation framework.
A recurring seat or jurisdiction subscription for standing operational use outside of a time-bound pilot.
A funder or anchor institution sponsors seats for nonprofits, advocacy organizations, or households that could not otherwise afford participation.
Standard procurement pathways are supported (RFP-ready documentation); licensing terms are configurable per jurisdiction and deployment scope.
Pricing is transparent and aligned to public-sector budgeting. Because iCARE is a coordination environment rather than a captive product, pricing reflects seats and integration scope, not data volume or vendor lock-in. Final pricing is negotiated per engagement and qualifies as a planning estimate until contracted.
Time-bound, scoped deployment for a defined geography and cohort. Pricing is per seat or per cohort and includes onboarding, training, and measurement dashboards.
Annual license for a county, state, or agency domain with role-based seat bundles and integration entitlements.
Subsidized or underwritten seats arranged through an institutional funder for nonprofits, advocates, and households.
A standard pilot runs a defined cycle (e.g., one fiscal quarter or one grant period) with a go/no-go evaluation gate.
Limited to agreed cohorts, partner organizations, and jurisdictions; data ownership remains with the originating agency.
Outputs and outcomes are tracked from day one; the evaluation framework produces the exit report for the pilot.
Agencies retain all case data and may conclude the pilot without lock-in; only the coordination layer is discontinued.
iCARE distinguishes outputs (what was done) from outcomes (what changed for the household and the system). The framework reports both so funders can demonstrate return and administrators can evaluate policy.
Evaluation is not an add-on; it is built into the coordination record from the first intake. iCARE structures measurement so an agency can defend its numbers to a funder, a court, and the public at once.
A staged model links inputs, activities, outputs, and outcomes so every measured result traces back to a hypothesized causal path.
Outcomes are disaggregated by cohort and jurisdiction to expose inequities a single aggregate number would hide.
Where feasible, pilot designs include comparison cohorts so observed change can be attributed with appropriate humility.
Outputs in near-real-time; outcome reporting on a programmatic cadence aligned to the funder or fiscal cycle.
An evaluation exit package pairs outcome findings with the governance audit log so results are reproducible and defensible.
Until independently audited, every impact figure is labeled a planning estimate, never a verified outcome.
A written governance framework constrains what each role may see or do, and is applied uniformly across every application in the ecosystem.
Role-level security (admin, agency, partner) restricts read, create, update, and delete to authorized users only.
Agency webhook accounts use rotated, masked secrets; no shared credentials and no unbounded API access.
Agencies retain ownership of their case data. iCARE governs connection points and the shared accountability record, not the source systems.
Whether you are a procurement officer scoping a pilot, a program director coordinating services, or a funder evaluating outcomes, the recommended first step is the readiness review. No agency replaces its system of record to begin.
Procurement pathways, compliance documentation, and impact data for agencies.
Begin the six-dimension readiness assessment. (Admin)
The central agency entry point for onboarding and partnership.
Review the governance framework overlays applied across the ecosystem.
Configure funding, licensing, and data-sharing terms. (Admin)
Understand the certification and audit posture. (Admin)