User-provided evidence
The primary source is the report text supplied by the user. That can include pasted inspection summaries, quick-add findings, PDF report text, TXT exports, and OCR-backed image uploads.
Data sources
Data Integrity & Sources
LifeVerdict uses multiple layers of data, but the product still begins with the user's inspection text. Data supports the packet; it does not replace the report.
Repair basis libraries
Cost sizing draws from the integrated construction cost library, metro labor/logistics indices, metro master data, and the repair engine specification bundled with the app. These libraries help scope leverage; they do not define the packet on their own.
Rule layers
Lender-visible rules, component signals, must-request terms, and do-not-lead filters shape how findings are framed. These rules exist to keep the packet narrow, defensible, and usable in a real transaction.
Open Data Downloads (CSV/JSON)
We publish derived metro-level open-data files for traceability and regional context.
Snapshot date: February 28, 2026. Sources include FEMA OpenFEMA disaster declarations and U.S. Census ACS 2024 5-year tables.
How to read the packet
The packet never claims that the open-data files are the same thing as the user's property. They are context layers. The report text, uploaded evidence, and matched lead items are what define the packet.
Validation signal
Success is measured by packet actions such as copy, print, and useful feedback in active deal flow. The core question is whether the packet is strong enough to use when a response is actually due.