Eagle currently does not identify or warn users when a property address being created already exists within the database. As a result, our database has accumulated a significant number of duplicate property records over time.

This creates several issues:

Duplicate property records can lead to fragmented ownership, enquiry and contact history.
Users may unknowingly create additional duplicates when searching for an address that already exists under a slightly different format.
Database integrity and reporting become less reliable.
Cleaning up duplicate records is currently a very manual and time-consuming process.

Suggested Improvements

Introduce a duplicate address warning when creating a new property record. If a similar or matching address already exists, Eagle should alert the user before the record is created.
Provide a "Potential Duplicate Addresses" report that allows administrators to identify duplicate or near-duplicate property records across the database.
Include tools to merge or review duplicate addresses where appropriate.
Consider using address standardisation (for example, recognising that "Street" and "St" may represent the same property) when checking for duplicates.

This would help maintain database accuracy, reduce duplicate records being created and significantly improve long-term data quality.When adding a listing,