AI System for Comparing Property Listings with Source Documents

The problem

Conflicting information may be published when details are copied from source records during day-to-day operations. When listing drafts, authoritative property documents, portfolio forms, images and versions are scattered across different screens, documents or team records, issues do not become visible in time.

This fragmented data delays preparation of the listing-to-document consistency report and requires staff to search for supporting records again by hand. Before making a decision, the qualified estate adviser has to complete missing fields and verify conflicts one by one.

A common exception is that gross, net and marketing area may be defined differently. If an incomplete or incorrect workflow runs without checking this context, a misleading listing may be published or correct information removed; the output therefore cannot be applied directly.

What we set out to improve

• Number of corrected listing-to-document discrepancies
• Rate of outputs corrected or rejected by the qualified estate adviser
• Time between the source record and the review output

How the system works

1. 01 Define the review scope and the qualified estate adviser role
2. 02 Receive the inputs: listing draft, authoritative property document, portfolio form, image and version
3. 03 Check source identity, date, version and data freshness
4. 04 Extract the listing field and source reference
5. 05 Compare area, floor and use
6. 06 Check the exception: gross, net and marketing area may be defined differently
7. 07 Place low-confidence or conflicting records in a separate human review queue
8. 08 Write the source identity, rule, output and time to the audit trail
9. 09 Have the qualified estate adviser approve, correct, defer or reject the report

Methods we used

• Source-field matching and a discrepancy report
• Source, format, version and required-field checks for the listing draft, authoritative property document, portfolio form, image and version
• A missing-data warning instead of a prediction when inputs are absent or conflicting
• A separate check for the exception outside the main rule
• Joint storage of the source identity, rule result, listing-to-document consistency report and human decision

Where people stay involved

Data and security

Access to listing drafts, authoritative property documents, portfolio forms, images and versions is restricted to the minimum permissions required for each role. Identifiers and sensitive fields are masked where possible, and only the necessary section of a file is sent to the model rather than the complete raw file. Access, output and the qualified estate adviser's decision are logged; production use does not begin until the organisation has approved the retention period and data location.

Who this suits

Frequently asked questions