Every decision program staff make in Phases 1 to 2 of the Tests page, one card per workflow, in the order they meet them: queue and assign; property and building, with the multifamily income qualification application; household income; then contractor registration (Phase 2). Phase 1.5 has no staff decision. Each decision that reaches another portal has a card in that portal's column: the confirmed type and the LEA- or MEA- code in the customer portal, the code used on a project application, and the registration decision in the contractor portal.
Pick a step
Dashed: shown to the other person, the project stays put
Drawn 16 October 2026 from staff portal #254 and #261, cut to Phases 1 to 2 and given the hand-backs to the other portals at Matt's request, checked against this portal's main (My queue, the record pages, the code and link modules, and the Tests page's phase files). Decisions and approvals are yellow diamonds (Matt, 19 October). The numbers give the saved walkthrough order. Diamonds are decisions. Solid arrows are handoffs; dashed arrows share information.
The same chart as a list
Open My queue — Every decision waiting on you, oldest first.
My queue is the first entry in the left-hand menu. Its number shows how many decisions are waiting, and updates about once a minute while the page is open.
The table opens on Assigned to: Me. Staff can switch it to Nobody or Anyone.
Staff can filter by the table's own columns: Assigned to, Entity, Program and Status.
Rows are oldest first.
When nothing matches, the table says "Nothing waiting".
When one queue cannot be read, the table says so where its rows would be, and still shows every other row.
Anyone signed in can take every action on this chart (#183). Settings → Roles and the payment-review team record who holds which seat; they do not limit who can press a button.
Qualifications is no longer in the left-hand menu. Its work is in tabs on the application.
This chart covers Phases 1 to 2 of the Tests page. Phase 1.5 (existing customers) asks staff only to find a customer and check the code; it has no decision.
Pick a row — Filter by Entity; the row opens the record.
No decision is made from the row. Clicking it opens the record, with its decision at the top of the page or on the named tab.
Entity choices: Application, Contractor registration, Property, Building documents, Building qualification, Household income qualification, Reservation request, Correction, Information request, Ownership claim, Focus Core rebate, Appeal, Signed document.
Entity "Property" also lists every building's documents waiting on staff.
Only applications, building qualifications, property type checks and contractor registrations can be assigned. Every other row sits in a shared queue that nobody owns.
Owner sees the type confirmed — The customer portal reads the confirmation.
Confirming writes the property's type, "confirmed" and who confirmed it, when, on the shared property row. Nothing is sent: the customer portal reads the same row.
The customer portal shows it in its own words: "Confirmed by program staff". Until then it reads "Awaiting confirmation by program staff".
If staff corrected the type, the owner sees the corrected type.
Decision:Decide the building qualification — Approve, market rate, send back or deny; approval issues the code.
The decisions sit at the top of the building qualification's "Income qualification progress" tab.
Buttons: "Approve", "Market rate (HOMES market rate only)", "Assign", "Send back for more information", "Deny". The page has no Begin review: #149 removed it. Begin review stays on the application.
Deny, Send back and Market rate need a note, kept on the record with the staff member's name.
Before approving, the 50%-of-occupied-units rule counts the building from its units. On the housing program path, the portal checks the procedure's three conditions instead and names any that is outstanding.
Approval gives the building a code with an expiry: LEA- for low income, MEA- for moderate income. A building that already holds an unexpired code keeps it.
Market rate is refused while the 50% rule is met at low or moderate income. It gives an internal HEA- code that only staff ever see.
It comes to My queue as Entity "Building qualification". It can be assigned.
Owner sees the building's code — LEA- or MEA- code, with its valid-until date.
Approving the building qualification, or the multifamily income qualification application, issues the building's code in the same save.
The code is LEA- (low income) or MEA- (moderate income) plus ten digits, with an expiry. It goes in the shared table the customer and contractor portals read, so nothing is sent.
A market-rate building gets an internal HEA- code instead. It is never put in that table, so the owner and contractors never see it.
A building that already holds an unexpired code keeps it. A new code marks the old one replaced.
Phase 3's first test checks it: the owner opens the approved building and sees Approved, with its code and valid-until date.
Applicant uses the code on a project — The building's code is the link to its income qualification.
On the customer portal, the HOMES or HEAR multifamily project's form asks for the "Income-qualified confirmation code". The applicant types the building's code there.
A contractor can also look a building up by its code on the contractor portal and start a project from it (Phase 3 tests).
Staff do not pick the link: the code the applicant entered is the link (#166).
Household sees its code — Approval gives the household its LEA- or MEA- code.
Approving writes the status, tier, method and the household's code on the household's own row. The customer portal owns that row; the staff portal writes only those columns.
A household sees its code only once its status is approved. A contractor can look it up only then.
Every other outcome's note is shown to the household on its account.
Approving again at the same tier keeps the code. A new tier gets a new number.
Contractor sees the decision — The decision is written on the contractor portal's own row.
The staff portal sends the decision to the contractor portal, which records it on the company's row. Nothing is copied back: staff read the same row.
Approve goes through the contractor portal's own approval rule, which refuses while it lists anything outstanding. Where waivers are allowed, approving with the certification waives each one under the staff member's name.
Phase 2 tests check the result: an approved company can start a project and gets an email; a denied one shows Not approved with the reason and cannot start a project.
Send back leaves it "Corrections required" for the contractor to fix.