A property can be correct in an agency's working system while an outward-facing portal still shows an old image, missing field or superseded wording. These discrepancies are easy to discuss informally and equally easy to lose once somebody says an update has been sent.
A portal listing discrepancy log turns each difference into a controlled exception. It records what the approved property information should show, what is actually visible, who owns the correction and how the agency will know the issue has genuinely been resolved.
Compare against an authoritative current record
Before logging a discrepancy, establish the internal version that represents the agency's current approved position. Without that baseline, staff may try to correct a portal to match another outdated copy.
Reference the relevant field, text or media item precisely enough that another colleague can reproduce the comparison.
Describe the observed difference without guessing the cause
Record what is wrong on the destination: for example, an old photograph remains visible or a revised detail has not appeared. Avoid immediately attributing the problem to a feed, portal or colleague unless that cause has actually been established.
Separating observation from diagnosis makes troubleshooting clearer and prevents assumptions becoming part of the permanent record.
Prioritise discrepancies by operational significance
Not every difference carries the same consequence. A material information mismatch deserves a different response from a minor presentation inconsistency. Use the agency's own risk and publishing process to determine what must be addressed first.
Priority should guide action, not erase lower-level issues. Keep unresolved discrepancies visible until they are either corrected or deliberately closed with a recorded reason.
Assign one owner for the correction path
Give each issue a responsible person or role even if another system or provider must ultimately process the update. Ownership means somebody remains responsible for checking progress and verifying the outcome.
If responsibility transfers, record the handover rather than leaving two colleagues each assuming the other is following up.
Record the correction submitted
Note the action taken and the working time or sequence needed to understand it. If the correction involved changing the internal master record first, make that clear. If the internal record was already correct and the outward destination required refresh or investigation, preserve that distinction.
This history helps the agency recognise repeated discrepancy patterns without relying on memory.
Verify the customer-facing result
Do not close the discrepancy solely because an update was submitted. Recheck the relevant destination after the normal processing route has had an appropriate opportunity to apply the change.
If the problem remains, keep the issue open and update the latest observed state. Verification should answer whether the public representation now matches the intended current information.
Use recurring discrepancies to improve the publishing process
Periodically review whether the same types of mismatch recur by field, media type or workflow stage. A pattern may point to an internal handover weakness, a configuration issue or another process that needs investigation.
A disciplined discrepancy log helps estate agencies manage the gap between a correct internal property record and what customers can actually see. It gives every exception an evidence trail, owner and verified closure instead of treating publication as complete at the moment an update is sent.