TRACER™
Carries the public pathway: what help exists, what it covers, and where a request stands. This is the policy front door — no account required to read it.
This map shows the whole chain in one place: the problem, the goal, the strategies, the tools and partners doing the work, and the outcomes that come back as evidence. TRACER faces the public. iCARE faces the agencies that run the programs. The map is how both sides stay connected to the same result.
Read this as a proposed framework, not as law. Nothing on this page describes enacted legislation, an appropriation, an official designation, or an endorsement by any government agency. It describes how the ecosystem is designed to work today and the policy pathway the work is intended to inform.
Give every household one public way to understand and request help, give every participating program one shared record to coordinate against, and give every funder and policymaker comparable evidence of what actually changed.
It is not a new agency, a new entitlement, or a replacement for the programs that already exist. It is coordination infrastructure around programs that are already funded.
Each strategy depends on the one before it. A public doorway without coordination behind it becomes another referral dead end; coordination without tracking produces no evidence; evidence that never returns to the policy cycle changes nothing.
Publish what help exists in plain language, free, before anyone is asked to create an account or share a detail.
Let participating programs work one shared, permissioned record so a household does not have to restate the same history to every intake worker.
Make received, served, and closed visible to the referring organization instead of assumed.
Turn closed referrals into comparable outcome reporting that can inform funding, program design, and the next policy cycle.
The tools are not interchangeable, and they do not face the same audience. Keeping the public side and the agency side distinct is what allows one to stay understandable and the other to stay accountable.
Carries the public pathway: what help exists, what it covers, and where a request stands. This is the policy front door — no account required to read it.
Carries coordination and reporting: aligning programs, activating interventions, and returning comparable outcome evidence to funders and policymakers.
Carries safety and documentation, so a safety constraint is part of the record instead of an invisible reason a plan did not complete.
A partnership model only holds if each party knows what it is accountable for. These are the roles the map depends on.
Use the public TRACER pathway to understand options and request help.
Deliver the programs and record what happened, with the household's consent.
Fund, administer, and receive outcome reporting for their programs.
See whether a funded intervention produced the intended result.
Use comparable outcome evidence to inform program design and future policy.
For-profit technology owner and operator. Builds and maintains the tools; does not deliver community programs.
Nonprofit community program deployer. Runs the programs and keeps delivery accountable to the community served.
These are intended outcomes, stated as design targets rather than measured results. The evaluation loop below is how they would be tested over time.
Household need and referral are documented with consent.
Programs align on one plan instead of separate ones.
The intervention is delivered and the closing state is captured.
Outcomes return as comparable evidence, not narrative alone.
Funders and policymakers revise the program or the policy.
The loop only closes if the last step feeds the first. Reporting that no one can act on is not accountability — it is paperwork.