Coordinated entry decision support that shows its work.

HEAT is a deterministic assessment, documentation, and case-conferencing platform for Continuums of Care (CoCs). Every determination explains itself: what is known, what is missing, which documentation is still needed, and what to discuss next. Same answers, same result, every time.

Public beta in development. Not for production decision making.

Try the assessment preview

New here? See a sample result first, no questions asked. Or read every question we ask.

Four outputs, never one score

01Immediate action

A neutral safety screen that routes emergencies to live help first. Workflow only, never allocation.

02Chronicity, computed

HUD chronic homelessness status under 24 CFR 578.3, with the arithmetic shown and a checklist of the documentation still needed.

03Housing support need

Categories, not scores. Missing or declined answers are reported as missing, never counted against anyone.

04Intervention discussion

Options to discuss, each with reasons, open eligibility questions, and cautions. Decision support, never automated placement.

Built to be checked

Deterministic. Identical answers always produce identical results, byte for byte.
Transparent. The complete assessment logic is published and versioned. Nothing is hidden.
Private. In public mode, answers never leave your device. Nothing is stored unless you choose it.
No AI in any determination. Every conclusion comes from published rules a person can read.
No numeric priority scores. Anywhere. Priority policy belongs to your CoC, in your CoC's own words.
A standard first. The schemas, rules, and formats are open; this site is one implementation of them.

For CoCs: pilot without replacing anything

Switching assessments is a governance decision. Piloting HEAT is not. In a shadow pilot, HEAT runs after your current assessment, takes about seven minutes, and affects no referrals. Your case conference compares the two outputs side by side: which one explains itself, which one arrives with the chronic homelessness documentation checklist already computed, which one your staff trust more. The comparison data is yours, and it doubles as validation evidence.

Step 1Keep your current tool. HEAT runs after it, in shadow.

Step 2Case conferences see both outputs side by side.

Step 3Your community judges decision quality with its own data.

Step 4Adoption, if it earns it, through your own written-standards process.

Book a virtual meeting about piloting

Roadmap

Phase 1Public beta: self-administered, no login, no server storage, feedback built in.

Phase 2Shadow mode: runs alongside a CoC's existing assessment for comparison. Affects no referrals.

Phase 3HMIS-assisted: confirm known data instead of re-asking it. Less duplicate questioning.

Phase 4Full deployment: case-conference workspace, documentation engine, referral workflow, audit history.

Current status: deterministic engines live for immediate action, HUD homeless category, chronic homelessness (rules encoded from the Federal Register and HMIS Data Standards with a cited rules document), housing support need, soft supports, and reassessment guidance, and institutional-stay rules. 133 automated tests. Next: expert review of the scenario corpus, and cognitive testing of question wording.