eSubmission
A secure digital portal for submitting official documents and records to local government recording offices.

Recording a deed meant a vendor in the middle.
Counties scanned paper. Submitters paid a go-between. Nobody saw status until it cleared. So I interviewed both ends of it: the title companies sending documents and the county offices receiving them.
Both sides wanted the middle gone.
Submitters paid a fee for status they couldn’t see. Counties re-keyed data already typed correctly once. So: a direct-to-county portal: upload, validate, pay by ACH. No go-between.
A pass through the portal's main screens
One task at a time.
A step-by-step package, start to finish. Jump around, or save and come back.
Invite a teammate in one modal.
Email, role, send. The old security loop is gone.
One ACH report. Per company. Per period.
The county authorizes the transfer. Reconciliation is a line, not a pile.
Tested until it held. Accessible by requirement.
Round after round with real submitters, until they stopped finding problems. And a VPAT: keyboard and screen-reader support designed in rather than bolted on. A county can’t buy what its staff can’t use.

Submitters drop the vendor fee.
One bulk ACH. Direct status. No go-between.
You could pull someone off the street and show them how to do this in about 20 minutes.

Counties stop scanning paper.
One clean report. Serve submitters directly.
A fantastic opportunity to more directly and better serve our title companies.
What changed after launch.
Citizen completion
42% to 86%
Validation errors
34% to 8%
Time to submit
14.5min to 4.2min
The Team
- 1 Lead Product Designer
- 1 Product Manager
- Engineering partners
- County & title stakeholders
Timing
2023–2024
Discovery through launch
Live
Self-serve product shipped
Tools Used
Figma
Gemini
UserTesting
Miro
Jira
Claude
The Figma file.
Up next