Free sandbox

The office decides. Veto records the review.

A Review Record is the file's record of what the office relied on before it acted.

Run a live-file control testFree sandbox signup
Fictional sample · before releaseVeto Record

Payoff demand review · File 26-2287

Recorded
What changedPayee + wire destination
Check resultTrusted-source confirmation open
Office actionHold pending confirmation

Checks are evidence, not approval. The office decides.

Start in browser with one closed file. No live funds, bank login, or release authority. Veto records the review. Your office decides.

  • Buyer funding
  • Seller proceeds
  • Payoff demand
  • Wire instruction
Veto Record — the file-ready review receipt shown as a product artifact

Fictional sample · before release

Veto Record

Payoff demand review · File 26-2287

Recorded
DisbursementPayoff demand · $184,920.16
What changedPayee + wire destination
Retained5 of 6 evidence items
Trigger
Revised payoff demand changed payee and wire destination.
Source
Email sender domain not already documented in the file.
Check
Known servicer path called for revised amount, payee, and destination.
Result
No confirmation before cutoff; message and file note retained.
Limitation
A revised demand can be legitimate. A document alone does not prove source authority.
Office action
Hold pending trusted-source confirmation.
ReviewerJ. Martinez
Signed2026-05-26 14:28 UTC
Hashsha256:4e3cf8a1...6af713

Evidence, not approval. The office remains the release authority.

The gap

What the other tools don't record.

CertifID and Qualia can prove the wire was verified. Can your file prove who decided to send when something didn't match? That decision — the override at release — is the one thing none of their logs show. That's the only thing Veto records.

The office decides. Veto records the review.

Record anatomy

The review as one file record.

A Veto Record keeps the review in a form another person can read later: what changed, what the file showed, what stayed open, and what the office did before release.

Fictional sample · before release

Veto Record

Payoff demand review · File 26-2287

Claim
Payoff demand changed before release
Source
Prior demand, revised demand, known servicer path
Check
Amount, payee, destination, and delivery path compared
Result
Five evidence items retained
Limitation
Trusted-source confirmation still open
Office action
Hold pending confirmation
Six-field grammar
Claim, source, check, result, limitation, and office action stay separate.
Reviewer proof
The person who reviewed the file is named with timestamp and hash.
Open gaps retained
Unconfirmed items stay visible instead of being turned into clean-sounding answers.
Office-owned output
The record stays in the office controls. Veto records the review; the office decides.

See the format in The Standard and a completed example in File 26-2287.

Public-record stack

The sources behind every Review Record.

A Review Record is built from public regulator data, the file's own evidence, and the office's decision. Each source stays separate and traceable.

Public record

EscrowMap

998 DFPI-licensed escrow branches mapped from the public licensee roster. Source-linked, corrections invited.

Open EscrowMap
Source search

DFPI records

Meeting materials, actions, orders, and notices from the California DFPI escrow-law archive.

Search DFPI records
Private file

Review Record

Buyer funding, seller proceeds, payoff demand, and disbursement review become one office-action record.

See the sample record
Owner test

File judgment

The office decides whether the record belongs in the file or feels like extra paperwork.

Run the file test

Public records show the industry. Veto shows the file review. The product is narrow on purpose: one file, one review record, one office decision.

Public record + installed offices

What the public record shows, and who is on it.

Veto is built on public DFPI data and a small set of real installed offices. No logos before three Review Records exist. No fabricated testimonials.

Offices on the record

Named only with documented permission. Listed as installed or in conversation — not as endorsements.

  • Installed
    Citizens Escrow

    Installed and using Veto for file review records.

    Permission ledgerdocs/growth-strategy.md — Real installed offices (with permission)

  • In conversation
    Beach Pacific Escrow

    PJ Garcia — 7x Escrow Industry Coalition president. In conversation; install pending.

    Permission ledgerdocs/growth-strategy.md — Real installed offices (with permission)

  • Open slot
    Your office next

    No logo wall before three Review Records. This slot stays honest and empty until then.

0 of 3 Review Records published — logo wall gated.

Authority shelf

White Paper #1

The Review Receipt Standard

The six-field grammar every Review Record follows: claim, source, check, result, limitation, and office action. The standard that makes a file review legible to the next person who reads it.

Read the Standard
EscrowStack

Public-record tools by Veto

EscrowMap, DFPI records search, and the meeting-minutes index — the public-record stack that feeds every Review Record. Source-linked, corrections invited, not an official source.

Open EscrowStack

EscrowMap is a public-interest project by Veto. See the live coverage at escrowmap.org or read the Record publication.

Pricing

Flat per office. Bill the record, not the transaction.

One monthly price per office. 50 Review Records included every month. $10 per additional record. No per-transaction fees, no wire-volume charges, no hidden line items.

1–3 person office
$495/office/mo

Solo and small independent escrow offices.

4–8 person office
$995/office/mo

Mid-size independent offices with steady file volume.

9–15 person office
$1,495/office/mo

Larger offices managing multiple concurrent files.

16+ person office
$1,995/office/mo

Multi-location and high-volume escrow operations.

Included50 Review Records per month
Overage$10 per additional record
Start a free sandboxTalk to Sebastian

The office decides. Veto records the review. RESPA cleared — pass at cost to consumer.

Start the review

Run a live-file control test.

Pull one closed payoff demand. Mark only what the file itself can prove. If the answer depends on memory, inbox, or phone notes, the review did not survive in the record.

Run a live-file control testSee a sample Review Record

Or send a route note

File type, what changed, office action, and best time to talk. No account numbers, party names, government IDs, live instructions, or unredacted file details. Your note goes to an approval-gated queue — Sebastian reviews every message personally before replying.

File type, what changed, office action, and best time to talk. No account numbers, party names, government IDs, live instructions, or unredacted file details.

The office decides. Veto records the review. Veto does not approve, verify, authorize, or release funds.