Methodology
We never call a property “legal” or “verified” without the evidence to back it. Here is how we label what we know, and how sure we are.
Verification levels (L0–L4)
Every number in a ScoUT report carries one of five levels. A report's confidence score falls when key inputs sit at low levels.
- L0Modelled. Based on market data and stated assumptions.
- L1Seller-stated. Claimed but not documented.
- L2Documented. Ordinance and parcel reviewed by our team.
- L3Third-party docs. HOA packet, statements or returns.
- L4Platform-verified. Direct OTA or PMS data.
Evidence grades (A–D)
Every legal claim on a rules page is graded by its source.
| Grade | Meaning |
|---|---|
| A | Quoted from the current codified text (municipal.codes, Municode or American Legal) or from an official city/county page, with the section number. |
| B | From an official document that is not code: an approved-properties list, a meeting packet or minutes, a county web page. |
| C | Inferred from primary text. For example, a use missing from a use table is read as prohibited. |
| D | Not confirmed. Recorded and shown as UNKNOWN. |
A city page publishes only when every verdict claim is grade A or B, it has at least 6 cited facts and a “catch” section, and a person has reviewed it. Anything we couldn't confirm is shown as UNKNOWN in a “What we haven't confirmed” box, never guessed.
“Rules last checked” policy
- Every rules page shows a “Rules last checked” date above the fold and in its structured data. We change that date only when a person actually re-reads the code.
- Cities with active ordinance churn (St. George, Hurricane, Park City) are re-checked monthly; the rest quarterly.
- A page more than 120 days past its last check shows a “may be out of date” banner.
- We cite the code section behind every claim and link to the primary source, so you can check it yourself.
Corrections policy
- If you think a rules page or dataset row is wrong, email hello@scoutut.com with the page, the claim and your source.
- We acknowledge within 2 business days. A person re-reads the primary source before anything changes.
- If we were wrong, we fix the page and the dataset, update the “rules last checked” date, and log the correction on the public changelog with what changed. We don't silently edit rules.
- If a correction could affect a buyer's decision (for example, a verdict changes), the changelog entry says so plainly.
Gates before scores
A report runs two gates first: Legal (zone, overlay, license, HOA, occupancy) and Finance (DSCR coverage, insurability, title flags, your cash budget). If a gate fails, the investment score is withheld, so a weak deal never shows up with a decent-looking number. See the sample report.
Estimates are not guarantees and nothing here is legal advice. See Legal & disclosures.