Connecting sold-price data to an energy assessment workflow

A

ari.brooks

Homeowner
Established
A recent workflow review has left us with a narrower question: should sold-price history sit inside the energy-assessment case, or remain a separate reference tool? Bringing it in sounds convenient, but it could also make the main record dependent on data that varies considerably between countries.

We already use different systems for enquiries, documents, appointments and progress updates. The worthwhile connection would reduce rekeying while carrying notes, attachments and changes in status into the next stage. Listing imports may offer a simpler gain, especially for staff working on mobile. Has anyone found a sold-price connection that genuinely shortens the process across several markets, rather than giving the team one more place to check?
 
Listing imports are usually the clearest place to remove work, provided the field mapping is reliable. Property details should enter once and then follow the case into documents and scheduling. Sold-price history is harder across countries because similarly named fields may not mean the same thing. I would favour separate country mappings feeding one case record rather than pretending the data is uniform.
 
Where does your master property record live now? That determines whether this is an integration problem or just several tools competing to own the same data. Also, what context is currently lost at handoff: attachments, notes, status, or the reason a value changed? Moving fields without that history can make the workflow look connected while staff still have to investigate everything manually.
 
I would push back on the idea that another dashboard is automatically a failure. A specialist view can be useful if it does one task well and writes the result back cleanly. The worse outcome is a nominally unified screen with delayed synchronisation and unclear versions. For assessors working away from a desk, mobile usability and access to the latest document may matter more than reducing the screen count.
 
Bruno’s point depends heavily on permissions. If every connected tool can overwrite core property details, the audit history becomes essential: who changed a field, when, and what the previous value was. Documents need similar discipline. A link to the current version is better than copying files between systems, but only if users can still see which version supported an earlier decision.
 
I’d test this with a small scripted case rather than another general demo. Import one listing, add sold-price information, revise a document, change a permission, then hand the case to someone using a phone. Count re-entry and clarification requests, and note anything that fails to return to the master record. Run the same script for each country, because that is where supposedly open integrations may expose different assumptions.
 
That gives us a better way to frame the decision. Our first task is to identify the master record and list exactly what the next person needs at each handoff. We’ll then test listing imports and sold-price feeds country by country, including the mobile handoff, permissions and document revisions. A separate specialist screen can stay, but only if its result and audit trail return to the case without retyping.
 
You must log in or register to reply here.
Back
Top