A home shown as active on one portal, paused on the agency website and withdrawn in a branch diary creates more than a technical inconsistency. Buyers may continue asking to view a property the seller no longer wishes to market, whilst staff may decline valid enquiries because their working screen shows an obsolete status. Resolving the problem requires an authoritative instruction, a map of actual destinations and a verifiable correction. Copying the status from the most recently checked screen into every other system can spread the original mistake.
The principle is evidence before synchronisation. The seller's actual current instruction controls the intended marketing activity, subject to contractual and professional obligations. The Property Ombudsman's residential agency Codes provide professional expectations for participating firms. The Digital Markets, Competition and Consumers Act 2024 is relevant where consumer-facing presentation becomes misleading. Neither source creates a universal status taxonomy or says every channel must be active simultaneously. The agency must distinguish genuinely authorised channel differences from accidental contradictions.

Find the instruction that determines current availability
Start with the property reference, signed instruction or subsequently authorised change and the effective date. Establish whether the seller presently permits full marketing, a temporary pause, selective channels or withdrawal. A CRM label may be a useful summary, but it is not the authority when a later verified client instruction contradicts it. Preserve the actual communication and name the person responsible for clarification.
Be precise about scope. A seller who asks to remove an advert from one portal may still authorise the agency website and appointments. An instruction to stop all viewings is different again. A property described as under offer may still be marketed according to legitimate arrangements; do not invent or automatically impose a universal rule. Document what the terms mean within the agency and what has actually been instructed.
If the controlling instruction cannot be determined, mark the status disputed and escalate. Do not select the most convenient available value merely to make a dashboard consistent. A brief delay while evidence is verified is preferable to advertising on unauthorised terms.
Inventory each internal and external representation
List the CRM master status, branch diary, website property page, search result, portal feeds, social campaigns, automated email sequences and printed materials where relevant. Record the exact property and channel references, what each displayed, and the observation time. A screenshot or supplier event record can be helpful for consequential differences, provided it is managed with appropriate privacy precautions.
Make a distinction between the state submitted and the state visible. A feed may indicate withdrawal accepted whilst the portal's search card remains cached. A website editor may show the new status in preview while the public page still offers an enquiry form. Each observation has a different evidential scope. The reconciliation should make these limits obvious.
Include multiple branches if more than one has marketed the property. Two feeds can create duplicate listings, each with a different status. Correcting one does not resolve the other. Check the canonical record and destination identity before deciding which representation is wrong.
Diagnose whether the source or distribution is defective
Conflicting outputs can arise because the master record is wrong, because an integration has not received a change, because a destination rejected a field or because a cache has not refreshed. Review event history and current mappings rather than guessing at the cause. An upstream error needs a different remedy from a downstream display delay. Repeatedly resubmitting the same update without checking the source may recreate the problem.
Some systems reuse one status field for several meanings: available to advertise, available to book, under negotiation or still under instruction. That design can produce misleading apparent contradictions. Define each state separately where necessary. A pause on new viewings does not invariably mean marketing has stopped, and marketing withdrawal does not erase an existing offer.
Record the diagnostic conclusion as supported, provisional or unknown. A supplier's acknowledgement confirms its own processing report, not necessarily the explanation for an observed public error. Where cause is unresolved, focus first on restoring accurate consumer-facing information and ensuring someone owns further investigation.
Prioritise contradictions that affect buyers and sellers
Different status mismatches have different consequences. A property still displayed as active after an authorised withdrawal may invite wasted enquiries or appointments. A temporarily stale thumbnail may be less consequential if the detail page accurately explains the situation, though it may still be confusing. Consider what a consumer is likely to understand and whether they might make a different decision because of the discrepancy.
Section 227 of the Digital Markets, Competition and Consumers Act concerns misleading omissions of material information within its legal scope. It does not dictate a portal refresh interval. The agency should assess the actual claim, timing and impact, and seek appropriate legal advice where necessary. Avoid claiming that a single stale status is automatically a statutory breach or that a software acknowledgement establishes compliance.
Also consider sellers and occupiers. Wrong status data can lead to unauthorised appointment promises or unnecessary interruptions. Where access is affected, coordinate with the secure viewing and key procedures rather than relying only on a marketing team's update.
Correct each destination without erasing genuine exceptions
Work from the verified intended state and produce a destination-specific action plan. Some channels may require an update, others removal, and others no change because the seller has authorised different treatment. Assign each action to a responsible person and record its submission evidence. Do not force every channel to match one generic label when the marketing plan legitimately differs.
Check scheduled campaigns and communications as well as live pages. A property withdrawn from a portal can still appear in a queued newsletter. A relisting can reactivate a previously suppressed advert under an outdated branch contact. Review dependencies and stop obsolete automatic messages before they create fresh contradictions.
Preserve a historical record of the previous states and corrective actions. Overwriting the only status event makes it harder to reconstruct why customers saw different information. The correct current state should be easy to find, but that clarity should not come from deleting evidence.
Verify outward-facing changes and enquiry routing
After the relevant processing interval, inspect the actual public property pages and search cards. Confirm that the right listing instance has changed, that its price and availability descriptions remain coherent, and that enquiry forms route to the appropriate team. Keep any persistent discrepancy open with a named owner, observed URL, next action and escalation route.
Testing only the internal admin view is insufficient. A portal's acceptance message may not reflect caching or a parallel duplicate listing. Conversely, a temporarily unavailable public page does not necessarily prove a permanent withdrawal. Seek a proportionate second observation or provider confirmation when the outcome matters.
Where previously interested buyers might rely on the old representation, consider whether a direct factual clarification is appropriate. Do not reveal unnecessary private seller reasons. Correct the marketing information without fabricating a transaction status or claiming the home has sold unless that fact is established.
Make reconciliation auditable and repeatable
Create a concise evidence record: original instruction, intended statuses by channel, observed mismatches, corrective submissions, outward verification and unresolved exceptions. A colleague should be able to reproduce the reasoning without searching an individual's private messages. Use a consistent property identifier, but retain the source-specific listing IDs needed to detect duplicates.
Review recurring causes. If two branches frequently republish a withdrawn property, strengthen feed ownership and cutover procedures. If a particular portal consistently shows stale search cards, distinguish caching from bad source data and manage the supplier issue. Do not treat the number of dashboard alerts as an independent measure of service quality.
An AI assistant can help compare descriptions or summarise evidence, but it can also confuse similar properties and invent reasons for status differences. Require exact source references and human review. Application-enforced permissions matter where seller communications and buyer data are involved. A model's explanation should never replace the controlling record or public verification.
Assess improvements using complete outcomes
Evaluate the time to restore truthful public representation, number of unresolved material discrepancies, accidental removals of valid channels, duplicate advertisements and wasted appointment journeys. Compare the existing checklist with any monitoring technology on the same representative cases. Count correction effort as well as detection speed. Do not assert savings based on a vendor's generic demonstration.
For a hypothetical calculation, suppose an office devotes forty hours monthly to resolving status mismatches. Better source mapping saves fifteen hours of initial checking but adds six hours of documented verification. Nine hours of possible capacity remain before licensing, training and incident costs. These values are arithmetic examples, not measured UK estate-agent results. Preventing a materially misleading public advert may matter more than modest administrative capacity.
Conclude only when authorised exceptions are documented and significant channels match the intended current state, or when an unresolved difference is clearly owned and communicated. Reconciliation is not a bulk operation to make data look identical; it is a process for making each published representation true.
Sources: The Property Ombudsman residential estate-agency Codes (professional service context); Digital Markets, Competition and Consumers Act 2024, section 227 (consumer material-information context); ICO organisational data-protection guidance. The status taxonomy and correction workflow are editorial methods, not mandatory software specifications.
Do conflicting statuses always mean an erroneous listing?
First distinguish an authorised channel-specific difference from a stale or mistaken publication. Correcting the latter must not erase the former.
| Review test | Authorised channel variation | Unintended discrepancy |
|---|---|---|
| Source authority | Seller's current documented instruction identifies relevant channels. | No supporting permission or source contradicts the displayed value. |
| Meaning | One destination intentionally inactive whilst another remains active. | Source, feed or public page shows an obsolete state. |
| Diagnostic evidence | Approved channel plan, effective date and property reference. | Event history, provider status and observed public URL. |
| Action | Preserve the valid difference and brief staff accurately. | Correct source or destination and track exceptions. |
| Buyer communication | Explain accurate current availability without private details. | Clarify misleading material presentation where appropriate. |
| Closure | Intended states verified, no forced uniformity. | Public correction observed or remaining issue explicitly owned. |
Decision: Align each destination with authority, not with an arbitrary universal label. Professional context: TPO residential estate agency Codes, standards for participating firms. Consumer information: UK DMCC Act section 227, not a prescribed portal-status taxonomy. This is original qualitative operational comparison.