Not an adoption recommendation: Habitable is an alpha. Independent security, cryptography, housing-law, and human accessibility review remain open. A union should not put member data into the tool until its own reviewers accept the risks and procedures.

Name the review team and its authority

A useful evaluation includes the people who would actually capture, organize, review, transfer, and interpret a record. One person can hold more than one role, but every decision should have an owner.

Organizer

Tests intake, issue structure, repair chronology, handoff, training burden, and whether the workflow fits union practice.

Privacy or security reviewer

Checks device controls, key recovery, data minimization, export scope, transfer method, incident response, and threat assumptions.

Legal workflow reviewer

Compares the packet and verification language with local practice, without treating software output as a legal conclusion.

Accessibility reviewer

Tests the task flow with the keyboard and assistive technology used by the team, and records barriers rather than inferring human access from automation.

Run one synthetic scenario end to end

  1. Write the scenario. Use fictional people, addresses, images, messages, and dates. Include at least one repair request, response, attempted repair, and recurrence.
  2. Assign two operators. Have one person capture and another review so handoff and explanation problems become visible.
  3. Follow ordinary practice. Use the union’s real intake categories and review sequence, but never copy a member’s case details into the synthetic record.
  4. Export the minimum packet. Decide what a recipient needs, withhold the rest, and check that the disclosure statement matches the choice.
  5. Give it to a cold reviewer. Ask someone who did not create the record to read the packet and explain what the integrity result does and does not establish.
  6. Delete the exercise. Confirm that the team knows where the local vault, exports, backups, and transferred copies exist.

Try the organizing structure without an intake form

The blank tenant-union building condition survey is a downloadable CSV with pseudonymous references, private-unit and common-area scope, permission-to-aggregate fields, and explicit interpretation limits. Rehearse it with synthetic rows before deciding whether it fits the union’s privacy and storage process.

Use pass, revise, and stop gates

  • Can a new organizer complete the core tasks? Measure errors, time, help requests, and uncertainty instead of relying on general impressions.
  • Can the team explain where data lives? Everyone handling a case should understand the local-only design, backups, keys, transfers, and public-site boundary.
  • Does minimum disclosure work in practice? The reviewer should be able to identify what was included, what was withheld, and why.
  • Can a recipient interpret the verification result? If technical integrity is mistaken for truth, authorship, official endorsement, or a legal outcome, stop and revise the workflow.
  • Are accessibility blockers recorded? Automation can catch some defects; the team still needs human keyboard and assistive-technology testing before reliance.
  • Is there a safe incident path? Stop if the team cannot respond to a lost device, exposed key, mistaken export, unsafe transfer, or unwanted copy.

Offer feedback without exposing a tenant

Start at the 45-minute synthetic organizer review, then read the bounded partner brief and the current trust and limitations record.

Choose the channel by risk: public technical feedback belongs in the review task or Discussion. Organization interest has a private, no-case-data email route on the review hub. Neither route accepts evidence. Never include tenant names, addresses, photos, allegations, files, or case details.