Phase 1: Customer account and income qualification

Do this

Choose an IRA staff tester account with access to both live portals.

Expected

Both portals admit the tester; an ordinary customer cannot open staff review screens.

PRE-02 → Open PRE-01 on its own page

Do this

Prepare three separate made-up multifamily building identities labeled APPROVE, DENY and CORRECT.

Expected

Each case has a different building and a unique name or address that can be matched in both portals.

← PRE-01 PRE-03 → Open PRE-02 on its own page

Do this

Prepare harmless sample documents without real names, income or account numbers.

Expected

The files can be uploaded for testing without exposing a real person’s information.

← PRE-02 PRE-04 → Open PRE-03 on its own page

Do this

Check that the live new-customer entry and confirmation email work.

Expected

A new test customer can create an account, confirm its email and sign in; otherwise mark later sign-up steps Blocked.

← PRE-03 PRE-05 → Open PRE-04 on its own page

Do this

Check that staff can save a live building decision and issue a building code.

Expected

A maintainer has cleared staff portal #186 with a successful live check; otherwise mark decision steps Blocked.

Unblocked by customer #108 — please retest.

← PRE-04 PRE-06 → Open PRE-05 on its own page

Do this

Record the tester name and a case ID for each building.

Expected

Every completed row can be traced to one tester and one building without using real personal details.

← PRE-05 PRE-07 → Open PRE-06 on its own page

Do this

Use Yes for a step that worked, No for a tried step that failed, and Blocked for a step you could not try.

Expected

Failed and unavailable steps are not reported as passes.

← PRE-06 PRE-08 → Open PRE-07 on its own page

Do this

Arrange removal of the three made-up accounts, buildings and uploaded samples after the testing round.

Expected

The responsible person and cleanup plan are recorded before testing begins.

← PRE-07 Open PRE-08 on its own page

Do this

Open the live portal’s new multifamily customer path in a fresh browser session.

Expected

The page identifies the multifamily owner path and offers account creation.

APPROVE-02 → Open APPROVE-01 on its own page

Do this

Create a new account with an invented name and a unique test email for this case.

Expected

The portal accepts the account request and tells the customer how to confirm the email.

← APPROVE-01 APPROVE-03 → Open APPROVE-02 on its own page

Do this

Open the confirmation email and complete its link.

Expected

The account becomes active and the customer reaches the portal signed in.

← APPROVE-02 APPROVE-04 → Open APPROVE-03 on its own page

Do this

Sign out, then sign in again with the same test account.

Expected

The same account opens and any saved property remains available.

← APPROVE-03 APPROVE-05 → Open APPROVE-04 on its own page

Do this

Add a named multifamily property and one building with at least four occupied units.

Expected

The property, building and occupied-unit count appear under the test account.

← APPROVE-04 APPROVE-06 → Open APPROVE-05 on its own page

Do this

Use one permitted income-proof route and upload the harmless sample document for enough units.

Expected

The building shows the documents and the number of occupied units still needed for review.

← APPROVE-05 APPROVE-07 → Open APPROVE-06 on its own page

Do this

Review the building’s progress and open its Sign and send step.

Expected

The page states what is ready, names any missing proof and asks who is signing.

← APPROVE-06 APPROVE-08 → Open APPROVE-07 on its own page

Do this

Sign and send this building for income review.

Expected

The building says it was sent to program staff and normal edits are locked during review.

← APPROVE-07 APPROVE-09 → Open APPROVE-08 on its own page

Do this

Sign in to the live staff portal and find this building’s Multifamily Income Qualification.

Expected

The record matches the test account, building and submitted status; it is not another case.

← APPROVE-08 APPROVE-10 → Open APPROVE-09 on its own page

Do this

Open each sample attachment from the building’s review page.

Expected

The actual file opens for staff; seeing only its filename does not count as Yes.

← APPROVE-09 APPROVE-11 → Open APPROVE-10 on its own page

Do this

Confirm the required unit or housing-program proof and approve this building.

Expected

The decision saves as Approved and issues an LEA or MEA building code with an expiry date.

Unblocked by customer #108 — please retest.

← APPROVE-10 APPROVE-12 → Open APPROVE-11 on its own page

Do this

Return to the same building in the customer portal and refresh it.

Expected

The building says Approved and shows its code and valid-until date.

Unblocked by customer #108 — please retest.

← APPROVE-11 APPROVE-13 → Open APPROVE-12 on its own page

Do this

Compare the code prefix with the approved income tier.

Expected

A low-income result has LEA; a moderate-income result has MEA. A wrong prefix is No, even if a code exists.

Unblocked by customer #108 — please retest.

← APPROVE-12 Open APPROVE-13 on its own page

Do this

Open the live portal’s new multifamily customer path in a fresh browser session.

Expected

The page identifies the multifamily owner path and offers account creation.

DENY-02 → Open DENY-01 on its own page

Do this

Create a new account with an invented name and a unique test email for this case.

Expected

The portal accepts the account request and tells the customer how to confirm the email.

← DENY-01 DENY-03 → Open DENY-02 on its own page

Do this

Open the confirmation email and complete its link.

Expected

The account becomes active and the customer reaches the portal signed in.

← DENY-02 DENY-04 → Open DENY-03 on its own page

Do this

Sign out, then sign in again with the same test account.

Expected

The same account opens and any saved property remains available.

← DENY-03 DENY-05 → Open DENY-04 on its own page

Do this

Add a named multifamily property and one building with at least four occupied units.

Expected

The property, building and occupied-unit count appear under the test account.

← DENY-04 DENY-06 → Open DENY-05 on its own page

Do this

Use one permitted income-proof route and upload the harmless sample document for enough units.

Expected

The building shows the documents and the number of occupied units still needed for review.

← DENY-05 DENY-07 → Open DENY-06 on its own page

Do this

Review the building’s progress and open its Sign and send step.

Expected

The page states what is ready, names any missing proof and asks who is signing.

← DENY-06 DENY-08 → Open DENY-07 on its own page

Do this

Sign and send this building for income review.

Expected

The building says it was sent to program staff and normal edits are locked during review.

← DENY-07 DENY-09 → Open DENY-08 on its own page

Do this

Sign in to the live staff portal and find this building’s Multifamily Income Qualification.

Expected

The record matches the test account, building and submitted status; it is not another case.

← DENY-08 DENY-10 → Open DENY-09 on its own page

Do this

Open each sample attachment from the building’s review page.

Expected

The actual file opens for staff; seeing only its filename does not count as Yes.

← DENY-09 DENY-11 → Open DENY-10 on its own page

Do this

Deny this building and enter a plain-language reason that the customer can act on.

Expected

The denial saves on this building and the staff record keeps the reason.

Unblocked by customer #108 — please retest.

← DENY-10 DENY-12 → Open DENY-11 on its own page

Do this

Return to the same building in the customer portal and refresh it.

Expected

The building says Not approved and clearly shows the reason for denial; no approval code appears.

Unblocked by customer #108 — please retest.

← DENY-11 DENY-13 → Open DENY-12 on its own page

Do this

Reopen the APPROVE building and compare its result.

Expected

The DENY decision did not change the separate APPROVE case.

Unblocked by customer #108 — please retest.

← DENY-12 Open DENY-13 on its own page

Do this

Open the live portal’s new multifamily customer path in a fresh browser session.

Expected

The page identifies the multifamily owner path and offers account creation.

CORRECT-02 → Open CORRECT-01 on its own page

Do this

Create a new account with an invented name and a unique test email for this case.

Expected

The portal accepts the account request and tells the customer how to confirm the email.

← CORRECT-01 CORRECT-03 → Open CORRECT-02 on its own page

Do this

Open the confirmation email and complete its link.

Expected

The account becomes active and the customer reaches the portal signed in.

← CORRECT-02 CORRECT-04 → Open CORRECT-03 on its own page

Do this

Sign out, then sign in again with the same test account.

Expected

The same account opens and any saved property remains available.

← CORRECT-03 CORRECT-05 → Open CORRECT-04 on its own page

Do this

Add a named multifamily property and one building with at least four occupied units.

Expected

The property, building and occupied-unit count appear under the test account.

← CORRECT-04 CORRECT-06 → Open CORRECT-05 on its own page

Do this

Use one permitted income-proof route and upload the harmless sample document for enough units.

Expected

The building shows the documents and the number of occupied units still needed for review.

← CORRECT-05 CORRECT-07 → Open CORRECT-06 on its own page

Do this

Review the building’s progress and open its Sign and send step.

Expected

The page states what is ready, names any missing proof and asks who is signing.

← CORRECT-06 CORRECT-08 → Open CORRECT-07 on its own page

Do this

Sign and send this building for income review.

Expected

The building says it was sent to program staff and normal edits are locked during review.

← CORRECT-07 CORRECT-09 → Open CORRECT-08 on its own page

Do this

Sign in to the live staff portal and find this building’s Multifamily Income Qualification.

Expected

The record matches the test account, building and submitted status; it is not another case.

← CORRECT-08 CORRECT-10 → Open CORRECT-09 on its own page

Do this

Open each sample attachment from the building’s review page.

Expected

The actual file opens for staff; seeing only its filename does not count as Yes.

← CORRECT-09 CORRECT-11 → Open CORRECT-10 on its own page

Do this

Send this building back with one specific request for a correction.

Expected

The staff record shows Sent back and keeps the request tied to this building.

Unblocked by customer #108 — please retest.

← CORRECT-10 CORRECT-12 → Open CORRECT-11 on its own page

Do this

Return to the same building in the customer portal and refresh it.

Expected

The building says Sent back to you and shows what needs correction.

Unblocked by customer #108 — please retest.

← CORRECT-11 CORRECT-13 → Open CORRECT-12 on its own page

Do this

Make the requested change or replace the sample document.

Expected

The edit is allowed after send-back and the updated information appears on this building.

Unblocked by customer #108 — please retest.

← CORRECT-12 CORRECT-14 → Open CORRECT-13 on its own page

Do this

Sign and send this building again.

Expected

The updated building returns to staff review and customer edits lock again.

Unblocked by customer #108 — please retest.

← CORRECT-13 CORRECT-15 → Open CORRECT-14 on its own page

Do this

Reopen the same building on the staff portal.

Expected

Staff can see the new submission and the corrected information or replacement document.

Unblocked by customer #108 — please retest.

← CORRECT-14 Open CORRECT-15 on its own page