Skip to content
Regi Ellis

Client application

Verify

Compares a case's records with its documents, flags what disagrees, and records the reviewer's decision.

Built for
DHN Attorneys
Status
Deployed 2025
My role
Design & development

The need

A reviewer had to check the same three details in several places.

The firm’s account records and the supporting documents don’t live together. Before a case moves forward, someone has to confirm that the homeowner, the property address, and the legal description match across the whole file. Small differences matter, but so do harmless ones like spelling and formatting. The team needed a way to see at a glance which details line up and which need a closer look.

What I built

Put the records and the documents side by side, then decide.

Verify pulls the account details and the documents from the firm’s Google Drive into one review, using the records the team already keeps.

AI reads the names, addresses, and legal descriptions off the documents. Verify then compares them with the linked records, lets small spelling differences pass, and points at the fields that disagree. Anything missing or misread stays visible so a person can look.

Implementation

Two things I kept in the reviewer’s hands.

A checklist for every review.

The checklist covers whether each document is present and which details need checking before the case moves on. Reviewers approve, reject, or ask for a correction, and their notes stay with the review.

The decision belongs to the legal team.

Verify shows the comparison and the source documents. The attorney or reviewer makes the call, and that call is recorded.

Built with Technical details
  • Python + FastAPI
  • React + Vite + Radix UI + Tailwind
  • SQLite
  • Playwright
  • Google Drive (service account)
  • Claude (Haiku 4.5)

Have a process
that needs better software?

Tell me what needs to change, your budget range, and when you’re ready to begin.

Discuss your project