How to check an AI-generated property research report

Check an AI property report by tracing each decision-relevant claim back to a source. Start with the parcel identity, then examine the source's date and scope, reproduce calculations, and separate documented facts from conclusions that still need confirmation.

A long report can repeat one unverified assumption across several sections. Review the claims that could change your decision first: the right property, ownership evidence, dimensions, permitted use, access, and whatever else your assignment depends on.

Check that the report is about the right property

Ask for the county, parcel identifier, address, and the source used to match them. If the report covers an assemblage, require the constituent parcel identifiers. Keep the site boundary visible alongside any calculations.

If the report relies on an assessor map, preserve its limits. Sacramento County explains that its assessor maps serve tax-assessment purposes and do not determine ownership rights, parcel legality, or a valid building site. That is a specific example of why a map source cannot support every conclusion a report might attach to it. Sacramento County assessor-map guidance

Open the source behind each important claim

A working link is the beginning of the check. Locate the passage, field, or record that supports the sentence. Confirm that it applies to the same geography, entity, and period.

For a hypothetical claim that “the site has 10 usable acres,” an acreage field might support a reported total area while saying nothing about usable land. Record the narrower supported statement and assign the remaining question. Do not allow an unverified conclusion to survive simply because the citation opens successfully.

For conflicting acreage fields, the deeded and GIS acreage guide provides a way to preserve both figures and document the difference.

Label what kind of statement you are reading

Use three working labels:

• Observed: directly reported by the cited record, within its scope.
• Calculated: derived from identified inputs, with the formula shown.
• Unresolved: an interpretation or question that still needs evidence.

These are review labels, not grades of legal certainty. A source can be outdated or wrong even when it has been accurately quoted.

Suppose an illustrative report lists 10.5 deeded acres and 9.8 GIS acres, then says the property exceeds a ten-acre requirement. The arithmetic depends on which field the requirement uses. Preserve both inputs and the requirement's definition before deciding whether the site passes.

Keep dates attached to the facts

Separate the date you accessed a page from the date of the underlying observation or record. A page checked today can contain earlier data. If a date is unavailable, mark it unavailable rather than writing “current.”

Ask whether the period matters to the decision. A historic aerial image might answer how the land was used before; it may be unsuitable evidence for the site's present condition. The report should say which question the image answers.

Use a claim-review sheet

Claim being used in the site decision:
Exact property / geography / entity:
Source URL and relevant record or passage:
Underlying source date; date accessed:
Observed / calculated / unresolved:
Inputs and formula, if calculated:
Scope or limitation:
Reviewer and next verification step:
Decision affected if the claim is wrong:

For the final memo, retain the unresolved questions beside the recommendation. Give the next reviewer enough information to reproduce the critical checks without rerunning the entire conversation. The desktop screening checklist can help organize the site questions after the report's evidence has been reviewed.