Housing document workflows:
show the evidence.

The work described in Production Notes

A housing compliance question can depend on both a scanned regulatory agreement and a separate public record. In Gabriel’s published account, staff connected those sources manually, using shared files, email, and spreadsheets.

The production system combined document extraction, structured records, and reconciliation between systems. Uncertain readings needed human review. Staff needed an answer tied to its source document, rather than a new query language to learn.

The lesson is that extraction is one part of the workflow. Matching records, making uncertainty visible, and letting a reviewer reach the evidence are part of the implementation.

The original dispatch describes qualitative changes in how staff accesses information. It does not publish engagement-specific before-and-after measurements. This field note does not claim a quantified saving or name the client.

Source: What We Learned Building a Compliance Housing non-for-profit Platform, Production Notes, July 6, 2026.

How to evaluate a similar workflow

For a new engagement, establish a baseline before building. Use representative document questions, including incomplete scans, conflicting records, and cases that require escalation. Have the responsible staff review both the answer and its source.

• Time from a request to a reviewed answer.
• Correct matches between records in different systems.
• Corrections and exceptions that require a person.
• Whether the answer’s supporting source is easy to inspect.
• Cost per completed task, including review and repeated attempts.

These are proposed evaluation measures for a new workflow, not results from the published engagement.

Bring the document question your team repeats

A recurring question gives the first conversation a useful shape: which sources hold the answer, how people connect them today, and what an incorrect answer would cost.

AI consulting for nonprofits · Embedded AI engineering