Partner Referral Review

Staff workflow prototype

The referral is complete, required fields and all. Nothing on it reaches the applicant.

The public partner referral step asks three required questions about the referring case manager before it asks anything about the applicant, and every applicant telephone number on it is optional. On R-1027 the Mobile Phone field carries the case manager's own number, Preferred Phone points at it, and the one number that would reach the applicant is written in the free text area. This desk reads what was submitted, separates what has to be asked of the partner from what has to be asked of the applicant, places the reported income against the figures published for 2026 in code, quotes the public rule that governs each question, and hands the file to a person. It determines no eligibility, answers no legal question and contacts nobody.

Measured here, end to end on one referral: run one and watch. That covers the documentary work before an intake worker picks the referral up. It makes no eligibility determination, accepts and declines nothing, and states no deadline.

1. Observed public material

The questions, options and branches read on the public partner referral step on 2026-09-15, each with its status: observed, partly observed, not accessible, or added. Nothing was submitted and nothing behind the Continue button was opened.

2. Simulation

Ten invented referrals, invented partners and case managers, and the invented internal policy of an invented program. Every clause of it is labelled simulation policy, not this organization's policy.

3. Public rules, verbatim

45 CFR 1611, 1620 and 1626 and the 2026 income appendix, quoted from eCFR with the source and the date. Real rules, never paraphrased, never attributed to the organization.

What this shows

The problem
A partner referral arrives with two people to contact and an incomplete picture. Somebody has to work out what is missing, who can answer it, what the public rules actually require, and what is reserved for a person, before an intake worker can pick it up.
The result
The run below is real and is recorded: the referral read field by field, the contact and income checks run in code, the questions split between the case manager and the applicant, the public rule quoted verbatim, and a handoff sheet that names every decision it does not take.
Where it sits
It prepares a staff handoff and hands over a sheet that can be copied out. Standalone demonstration. It connects to nothing, writes into nothing, and is not a form.
What is simulated, and what is not covered
The program, the ten referrals, the partners and the internal policy are invented, and that policy is one invented program's own, not anybody's law. The observed field dictionary is real and is marked field by field; the steps behind the Continue button were not opened and nothing is guessed about them. There is no scanned document and no optical character recognition here, no connection to any case management system, and no eligibility determination, no acceptance or refusal of representation, no legal advice, no conflicts check and no deadline. The tool layer refuses all of those, and refuses a figure that is not written in a section it was cited from.
What a pilot would need from your side
A sample of real referrals with the names removed, the intake policy in whatever form it exists today, and one person who can say whether an answer is right.
Who built it
Frederic de Lavenne de Choulot, The AI Pipe. Built as a demonstration, not sold as a legal, eligibility or compliance product.

Simulated intake activity

The library

Fictional desk. Do not paste real applicant, client or case records.
Enter to send, shift and enter for a new line. Live tool use over ten invented referrals, the observed field dictionary and the public rules.