Sample exception review · scripted demo package
Three exceptions, caught before acceptance. Every source page quoted.
This is what comes back after Vetta reads an offer package: not a summary of every page, a short list of the places the documents disagree with each other, or reference a form that isn't in the file, each one quoting the page it came from. It runs on intake, before the package is accepted — which is the difference between a correction and a re-trade.
What this is, and is not
The package below is the scripted demo used in our interactive walkthrough: 1847 Willow Glen Way, fictional parties, fictional figures. It shows the exact shape of the output. It is not a review of a real file, and no customer outcome is described on this page.
The checks themselves are not scripted. The same two the production pipeline asserts on real files — an amount that disagrees across two documents, and a form the package names but does not contain — are the first two shown here.
The package as received
Every file is hashed on arrival. Eleven checks cleared. Three did not.
Exception 1 of 3 · critical
Financing terms do not match
Purchase agreement, page 3 · Financing addendum, page 1
Purchase agreement · page 3
Purchase price: $1,825,000
Down payment: $365,000 (20%)
Loan amount: $1,460,000
Financing addendum · page 1
Financing type: Conventional
Down payment: $273,750 (15%)
Loan amount: $1,551,250
Brokerage policy it tripped
Financing terms must match
Purchase price, down payment and loan amount must agree across the RPA and every financing addendum before approval.
Policy CA-BUY-04 · version 3.2
What the reviewer does
Two buttons: assign a reviewer or request a correction from the agent, with both citations attached to the request. Nothing approves itself. The finding is advisory until a licensed person acts on it.
47 pages read → 2 fields to decide (illustrative target, not a measured customer figure)
Exception 2 of 3 · missing document
The package references a form that isn't in it
Purchase agreement, page 11 · no matching document in the file
Purchase agreement · page 11
…Buyer's waiver of the appraisal
contingency is attached hereto as
Addendum BWA-1 and incorporated
herein by reference.
What the file actually contains
Purchase agreement · 47 pages
Financing addendum · 1 page
Agency disclosure · signed
Seller credit addendum · 1 page
No Addendum BWA-1.
This is the cheapest finding to believe and usually the most useful. It needs no interpretation and makes no accusation: a document the package itself names is not in the package. Nobody has to agree about what a report means for this one to be worth catching before the file moves.
Exception 3 of 3 · change control
A document changed after it was approved
Seller credit addendum, version 2 · received 9:14 AM, after the 8:31 AM approval
The broker approved the package at 8:31 under policy CA-BUY-04. At 9:14 a replacement seller-credit addendum arrived with a different credit amount. The approval it carried is marked superseded, version 1 is preserved unchanged, and delivery to the other side is blocked until a person re-approves the changed page.
This is the failure the audit trail exists for: a changed package going out under an old review. It cannot happen here without someone choosing it.
The evidence timeline the file keeps
Document received
Email attachment stored; source hash recorded
Automated review completed
11 checks cleared; 2 exceptions created
Correction requested
Agent notified with source citations
Replacement received
Previous document preserved as version 1
Broker approval recorded
Policy CA-BUY-04 v3.2
Approval superseded
Seller credit changed; delivery blocked
The whole file exports as an archive with a per-file SHA-256 manifest and a recomputable root hash, so an auditor can verify it without trusting us. That export is real and runs in production; the review above is the demo package.
This is not an audit of your brokerage
It runs on intake, inside your own workspace, on your own tenant. The findings are yours: we do not train models on your documents, and your tenant data is deleted on request, in writing. Nothing is graded, nothing leaves the brokerage, and no finding approves or rejects anything on its own — every one of them stops for a licensed person.
The reason to run it before acceptance rather than after close is arithmetic, not compliance. A loan amount that disagrees with itself is a correction on Tuesday and a re-trade in week three.
Related: security & data handling · pilot terms